aws-amplify / aws-amplify/amplify-hosting

cloudfront:ListDistributionsByLambdaFunction invalid action

Open
#2,253 2 comments 0 reactions 0 assignees View on GitHub
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-console/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-console/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

n/a

### Region

n/a

### Amplify Console feature

Backend builds

### Describe the bug

Documentation listed on the following link describes adding `cloudfront:ListDistributionsByLambdaFunction` permission to the iam service role https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md#error-accessdenied-access-denied

When attempting to add this to my service role I am getting `Invalid Action: The action cloudfront:ListDistributionsByLambdaFunction does not exist.`

I am not sure if something should be used in its place or if this might cause problems.

Ideally, the console can add these permissions and role with the proper ARN but I wanted to make sure the manual process was properly documented.

I hope to be able to offer a merge request with the proper clarification.

### Expected behavior

Docs do not include an invalid permission.

### Reproduction steps

View iam permissions under https://github.com/aws-amplify/amplify-console/blob/master/FAQ.md#error-accessdenied-access-denied

### Build Settings

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Open FAQ.md at the error-accessdenied-access-denied section and verify the listed CloudFront IAM action against the AWS permission reference. Correct or remove the invalid permission, and confirm the documented permissions no longer include an action that AWS rejects.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.