From 7bfbcd0b4d8b1e0495133653d05d6dbeb5ed0505 Mon Sep 17 00:00:00 2001
From: MJ Zhang <0618@users.noreply.github.com>
Date: Tue, 9 Jul 2024 10:54:55 -0700
Subject: [PATCH] chore: update domains for proxy

---
 .../tools/cli/project/troubleshooting/index.mdx           | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/src/pages/gen1/[platform]/tools/cli/project/troubleshooting/index.mdx b/src/pages/gen1/[platform]/tools/cli/project/troubleshooting/index.mdx
index a89af5eff36..70405821378 100644
--- a/src/pages/gen1/[platform]/tools/cli/project/troubleshooting/index.mdx
+++ b/src/pages/gen1/[platform]/tools/cli/project/troubleshooting/index.mdx
@@ -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.