Skip to content

chore: update domains for proxy #7808

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jul 9, 2024
Merged

chore: update domains for proxy #7808

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/pages/gen1/[platform]/tools/cli/project/troubleshooting/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,14 @@ To debug deployment issues, it's helpful to understand the [file structure of yo

1. Amplify CLI walkthrough input parameters artifacts: All inputs provided by the user during a CLI walkthrough are stored in JSON files in the `/amplify/backend` folder. For example, `cli-inputs.json` or `amplify-meta.json`. These files let you inspect the configurations, both developer-provided and Amplify-generated, to root cause potential problems. Refer to [Amplify backend files documentation](/gen1/[platform]/tools/cli/reference/files/#backend-configjson) to determine if a file is safe to edit manually.

#### Domains that Amplify CLI requests when running `init`, `publish`, and `push`.

If you run Amplify CLI via proxy, make sure to add the following domains to the allowlist.

- amazonaws.com
- amplifyapp.com
- aws-amplify.github.io

### For Amplify CLI projects with GraphQL API

To debug deployment issues in projects with GraphQL API, it's helpful to understand the various artifacts generated by Amplify in a GraphQL project.
Expand Down