aws-amplify / aws-amplify/amplify-hosting

Amplify Console does not warn user they are missing amplify:ListBackendEnvironments policy

Open
#3,291 1 comment 1 reaction 0 assignees View on GitHub
feature-request
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

NA

### AWS Region

us-west-2

### Amplify Hosting feature

Not Applicable

### Is your feature request related to a problem? Please describe:

When viewing the AWS Amplify Console, I am unable to view the backend environments if my policy is missing `amplify:ListBackendEnvironments`. This isn't a bug in itself, but I was presented with a blank screen instead of telling me I couldn't view the backends. As a consequence I spent a few hours trying to figure out why the backend isn't deploying, when it actually was, I just couldn't view it.

Screenshot 2023-02-04 at 19 03 42

### Describe how you'd like this feature to work

I would prefer the AWS Console present a message to the user that they are missing a permission to view the backend.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the AWS Amplify Console backend-environments view with a policy that lacks amplify:ListBackendEnvironments. Trace how the blank screen is handled when that permission is missing. Done means the console clearly tells the user which permission is required instead of showing an empty view.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
authorization, cloud
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.