aws-amplify / aws-amplify/amplify-hosting

Error status 429 on protected branches

Open
#3,465 12 comments 0 reactions 0 assignees View on GitHub
access-control bug pending-prioritization
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 bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d31nsviof9mm88

### AWS Region

eu-west-3

### Amplify Hosting feature

Frontend builds

### Describe the bug

Referring to issue #1823, I am having problems with loading server files properly, for example, images, CSS, or even Javascript files. The files affected by this behavior seem to be random. I am protecting the deployment with credentials.

### Expected behavior

Not receiving the error message: `Failed to load resource: the server responded with a status of 429 ()` (on Safari)

### Reproduction steps

1. Deploy the frontend application and protect the master branch with credentials;
2. Go to the site and read the console errors, for example, the following ones:

Screenshot 2023-05-06 at 2 44 00 PM

OR

Screenshot 2023-05-06 at 2 47 41 PM

OR

Screenshot 2023-05-06 at 2 48 46 PM

### Build Settings

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing issue #1823 and the linked FAQ and contributing guide, then reproduce the protected master-branch deployment in AWS Amplify Hosting for the reported eu-west-3 app. Check whether the intermittent 429 responses affect images, CSS, and JavaScript requests; the issue is resolved when those assets load without 429 errors while branch protection remains enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, devops, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.