- Newest
- Most votes
- Most comments
Based on the context above, you seem to have encountered a problem while attempting to select the project for deployment after pushing a commit. Let's guess some steps and potential solutions to resolve this issue.
-
Check Repository Permissions: Ensure that the AWS Amplify IAM user or role you use has the necessary permissions to access the repository in Bitbucket. Double-check the access permissions associated with your Amplify environment.
-
Verify Branch Protection Rules: If the branch you want to select has branch protection rules enabled in Bitbucket, it might be preventing Amplify from accessing it. Make sure the rules allow Amplify to read and retrieve the branch.
-
Review Webhooks Configuration: AWS Amplify relies on webhooks to detect changes in your repository and trigger the deployment process. Check if the required webhooks are configured correctly in your Bitbucket repository settings. Incorrect webhook configurations can prevent Amplify from detecting commits and initiating deployments.
-
Ensure Repository Visibility: Confirm that the repository you wish to connect to Amplify is not set to private. If it is, you may need to adjust the visibility settings or provide the necessary credentials to enable Amplify's access.
Also, you can go through Configure the Bitbucket Repository topic from this AWS doc and Atlassian Authentication Method
I hope this will help you to connect the project 🙏
Relevant content
- asked 4 days ago
- Accepted Answerasked a month ago
- asked 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago