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

Clarify amplify-admin local AWS setup profile #7854

Open
carlschroedl opened this issue Jul 27, 2024 · 0 comments
Open

Clarify amplify-admin local AWS setup profile #7854

carlschroedl opened this issue Jul 27, 2024 · 0 comments
Labels
amplify/cli Issues tied to CLI

Comments

@carlschroedl
Copy link

Describe the content issue:
Currently the amplify-admin local AWS setup profile documentation (step 4) includes the following CLI session:

CLI profile name [amplify-policy-<your-aws-account-id>]: default
To use this profile, specify the profile name using --profile, as shown:

aws s3 ls --profile default

When I ran the suggested command, I got an error:

$ aws s3 ls --profile default

An error occurred (AccessDenied) when calling the ListBuckets operation: Access Denied

I suspected something went wrong during the previous steps, but after troubleshooting I discovered that the role associated with the profile intentionally lacks permissions to list S3 buckets, and that this is expected. To prevent others from spending time troubleshooting this, I suggest that a note be added after the output aws s3 ls --profile default clarifying that running that generic example command will fail because the amplify admin user's least privilege role intentionally does not include this permission, and that you should proceed to the next step to verify your amplify setup.

URL page where content issue is: https://docs.amplify.aws/vue/start/account-setup/#4-set-up-local-aws-profile

@esauerbo esauerbo added the amplify/cli Issues tied to CLI label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
amplify/cli Issues tied to CLI
Projects
None yet
Development

No branches or pull requests

2 participants