Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update pinpoint IAM policy to use mobiletargeting instead of mobileanalytics #326

Merged
merged 2 commits into from
Oct 23, 2018

Conversation

kaustavghosh06
Copy link
Contributor

Description of changes:
Due to a recent change with Pinpoint API's, IAM policies need to be changed for the newly created Pinpoint API's. This PR modifies the IAM policies generated for a pinpoint endpoint using the CLI.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@@ -96,7 +96,7 @@ function getPolicyDoc(context) {
{
Effect: 'Allow',
Action: [
'mobileanalytics:PutEvents',
'mobiletargeting:PutEvents',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't move this line to be next to line 108?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Those are copied over from the old implementations, but I think it does make sense to combine both in a single policy statement and restrict the putEvents action to only the specific pinpoint project.

Copy link
Contributor

@UnleashedMind UnleashedMind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can combine the policy statements as suggested by @powerful23

@@ -96,7 +96,7 @@ function getPolicyDoc(context) {
{
Effect: 'Allow',
Action: [
'mobileanalytics:PutEvents',
'mobiletargeting:PutEvents',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Those are copied over from the old implementations, but I think it does make sense to combine both in a single policy statement and restrict the putEvents action to only the specific pinpoint project.

Copy link
Contributor

@powerful23 powerful23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@kaustavghosh06 kaustavghosh06 merged commit 96fcde6 into aws-amplify:master Oct 23, 2018
@ghost ghost removed the review label Oct 23, 2018
onlybakam added a commit to onlybakam/amplify-cli that referenced this pull request Oct 24, 2018
* upstream-master:
  fix: update pinpoint IAM policy to use mobiletargeting instead of mobileanalytics (aws-amplify#326)
  Update native_guide.md
onlybakam added a commit to onlybakam/amplify-cli that referenced this pull request Oct 24, 2018
* upstream-master: (125 commits)
  fix: update pinpoint IAM policy to use mobiletargeting instead of mobileanalytics (aws-amplify#326)
  Update native_guide.md
  Fixing aws-amplify#183 (aws-amplify#285)
  Initial work on @http directive (aws-amplify#255)
  Add option/flag in amplify push command to not automatically re-compile annotated GraphQL schema (aws-amplify#328)
  chore(release): Publish [ci skip]
  chore(release): Publish [ci skip]
  ci: run integration tests before release
  ci: merge release branch after publishing
  Update Readme.md (aws-amplify#324)
  Update Readme.md (aws-amplify#323)
  Update native_guide.md (aws-amplify#321)
  updating cypress test for auth message
  updating cypress test for auth1
  updating cypress test for auth
  running graphql integration tests only for merged PRs
  fixes(aws-amplify#303)
  fix frontend config
  fix(graphql-auth-transformer): Modifies the name of the user pool resource
  Fixing integration tests & moving amplify init to seperate expect script (aws-amplify#291)
  ...
@github-actions
Copy link

This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants