Pinpoint Project Overwritten After Push Notification Settings Update

Greeting

Hi Nima,

Thank you for sharing your question about AWS Pinpoint! I understand how concerning it must be to see historical data and other key information seemingly vanish after a push notification settings update. Let’s dive into this and figure out what’s going on so you can move forward confidently. 😊

---

Clarifying the Issue

From your description, it sounds like after you updated push notification settings in an existing Amazon Pinpoint project, the project shows a new creation date, and historical data (such as event data and user activity funnel data) is no longer visible. You’re also observing similar behavior in your development environment, where updates seem to create new Pinpoint projects.

This behavior is indeed unusual for production systems. Typically, updates to push notification settings should modify the existing project, not recreate it. Let’s break down what might be happening and walk you through potential solutions.

---

Key Terms

• Amazon Pinpoint Project: A project in Pinpoint is used to manage your campaigns, user data, and engagement settings.
• Push Notification Settings: Configurations for sending messages to mobile devices, which include platform credentials and permissions.
• Historical Data: Data such as past events, user activity, and funnel analytics collected by the project over time.
• CloudTrail Logs: A logging service in AWS that records API calls and user activity, helping diagnose unexpected behavior.

---

The Solution (Our Recipe)

Steps at a Glance:

1. Verify whether the update created a new project.
2. Check for backup data in Amazon S3 or other storage locations.
3. Investigate IAM permissions tied to the Pinpoint project.
4. Check AWS CloudTrail logs for potential causes.
5. Test push notification updates in a safe environment.

---

Step-by-Step Guide:

1. Verify whether the update created a new project

   • Navigate to the Pinpoint Dashboard in the AWS Management Console.
   • Confirm whether the old project is still listed separately or if it has been overwritten.
   • Use the Amazon Pinpoint CLI to fetch project details:

     aws pinpoint get-app --application-id <your_project_id>

     Replace <your_project_id> with your previous project’s ID to check if the project still exists in the backend.

   Example Output:

   {
       "ApplicationResponse": {
           "Id": "1234abcd5678efgh",
           "Name": "MyProject",
           "CreationDate": "2025-01-01T12:00:00Z"
       }
   }

   If the project doesn’t exist, move to the next steps.

---

2. Check for backup data in Amazon S3 or other storage locations
   • If you’ve configured Pinpoint to export events to Amazon S3, check the S3 bucket for historical data files.
   • Navigate to the bucket you specified during Pinpoint setup and look for any .json files containing exported events.

---

3. Investigate IAM permissions tied to the Pinpoint project
   • Ensure the IAM role or user updating the push notification settings has the required permissions for Pinpoint.
   • Use the AWS Management Console or CLI to check for attached IAM policies. Missing permissions may result in incomplete updates or unexpected behavior.
   • Example: Verify that AmazonPinpointFullAccess is attached to the role or user making changes.

---

4. Check AWS CloudTrail logs for potential causes
   • Go to the CloudTrail Dashboard and filter for events related to the Pinpoint service.
   • Look for API calls like UpdateApplicationSettings, DeleteApp, or CreateApp around the time you noticed the issue.
   • Example CLI Command:

     aws cloudtrail lookup-events --lookup-attributes AttributeKey=EventSource,AttributeValue=pinpoint.amazonaws.com

     Example Output:

     {
         "Events": [
             {
                 "EventId": "1234abcd-5678-efgh-9012-3456ijklmnop",
                 "EventName": "UpdateApplicationSettings",
                 "EventTime": "2025-01-01T12:30:00Z",
                 "Username": "nima_at_email.com"
             }
         ]
     }

     Look for actions like DeleteApp or CreateApp, which could indicate why a new project was created or old data was lost.

---

5. Test push notification updates in a safe environment
   • Use a separate development account or environment to replicate the issue.
   • Update push notification settings for a test project and observe whether the project is recreated or overwritten.

---

Closing Thoughts

This behavior is not typical for production systems, and further investigation may require contacting AWS Support if the issue persists. Meanwhile, reviewing logs and backups can help ensure that no data is permanently lost.

For additional guidance, you might find these documentation links helpful:

• Amazon Pinpoint Project Settings Overview
• Monitoring Amazon Pinpoint Events
• Using the AWS CLI with Amazon Pinpoint
• AWS CloudTrail Logging Overview
• IAM Policies for Amazon Pinpoint

---

Farewell

I hope this helps resolve your issue, Nima! Please don’t hesitate to reach out if you have more questions or run into any trouble. Wishing you success with your Amazon Pinpoint projects! 🚀

---

Cheers,

Aaron 😉