AWSPinpointProvider - Please ensure you have updated you Pinpoint IAM Policywith the Action: "mobiletargeting:PutEvents" in order tocontinue using AWS Pinpoint Service

AWSPinpointProvider - Please ensure you have updated you Pinpoint IAM Policywith the Action: “mobiletargeting:PutEvents” in order tocontinue using AWS Pinpoint Service

componentDidMount() {
    Analytics.record('APP_STARTED');
}

[ehorodyski]

The documentation on how to add the additional permission is quite confusing:

1. What policy needs to be updated? I assume it’s the MobileHub project’s Cognito policy?
2. If you’re looking to use the Policy dashboard to update your policy, PutEvents does not show up as an available option for Pinpoint. You have to edit the JSON policy directly.
3. After doing so, you have no way to verify that you’ve correctly added the policy, as the warning message still shows up. Analytics are also being posted to an endpoint with legacy in it, which doesn’t make me feel confident that I correctly applied the permission to the right policy.

I hate saying this, but Pinpoint is one of the poorest AWS services available. It’s nowhere near as granular as the rest of AWS, with policies that are coupled with other services (I think you need Mobilehub permissions to create a Pinpoint project) – when I really just want a lightweight analytics solution. The analytics portion of it is not nearly as fleshed out as Mobile Analytics was and has tons of odd limitations, like only storing the last 30 days of data. Sorry for the rant; just not happy in the slightest with Pinpoint, and now it’s affecting Amplify.

[eturner0]

Are there instructions on how to change the IAM policy to correct this error?