aws-amplify / aws-amplify/amplify-hosting

Manual deploys via zip file

Open
#3,195 29 comments 11 reactions 0 assignees View on GitHub
compute 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 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

d113cc0qzdxa93

### AWS Region

us-east-1

### Amplify Hosting feature

Deployments

### Describe the bug

Trying to upload a zip build of Next.js with SSR. It says deployment successful but the environment URL says Access Denied.

### Expected behavior

The URL should show the Next app instead of Access Denied.

### Reproduction steps

1. Go to any environment URL of the app.

### Build Settings

_No response_

### Log output

```
# Put your logs below this line
2022-12-12T18:21:36 [INFO]: Starting Deployment
2022-12-12T18:21:37 [INFO]: Updating Edge config
n, buildId 0000000008
2022-12-12T18:21:37 [INFO]: Got archive: 29260413 bytes
2022-12-12T18:21:46 [INFO]: Deployment complete

```

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

No source files or tests are named. Start by reviewing the manual zip deployment path for Next.js SSR and the provided deployment log, then reproduce the environment URL returning Access Denied. Done means a manually uploaded Next.js SSR zip deploys successfully and its environment URL renders the application.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, next.js
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.