Thanks for clarifying! I understand now that when you’re setting up the Amplify app in the new AWS account, the repository you want to deploy isn’t appearing in the AWS Amplify UI under the list of available repositories, and in your Git provider (likely GitHub, based on the "installed" tag), the repo shows as "installed" under "Only select repositories." This points to a specific issue with how the repository’s integration is configured between your Git provider and the new AWS account. Let’s dive into why this is happening and how to fix it.
The "installed" tag next to the repository in your Git provider’s settings (e.g., GitHub under "Settings > Integrations & services" or "Settings > Applications") indicates that the repository is already associated with an existing AWS Amplify integration—likely the one tied to the first AWS account where you deployed the app. When you try to connect the same repository in the new AWS account’s Amplify UI, it doesn’t show up because the Amplify GitH