- Newest
- Most votes
- Most comments
-
Ensure that the IAM role associated with your CodeBuild project has the necessary permissions to access GitHub. This includes permissions to pull from the repository and any other actions your build process requires.
-
Ensure that the GitHub integration with AWS CodeBuild is correctly configured:
OAuth App Authorization: Confirm that AWS CodeBuild is authorized as an OAuth app in GitHub. GitHub: Go to GitHub Settings > Authorized OAuth Apps and ensure AWS CodeBuild is listed with access to your repositories. If needed, reauthorize CodeBuild: Go to AWS CodeBuild console. Navigate to the Source section and reconfigure the GitHub connection.
-
Update GitHub Token An expired or incorrectly configured token can cause issues:
Generate a New Token: Go to GitHub Tokens. Generate a new token with the necessary scopes, typically repo (for private repositories) or public_repo (for public repositories). Update Token in CodeBuild: In the AWS CodeBuild console, update the source settings with the new token.
-
Ensure there are no restrictive rules in your network ACLs or security groups that might be blocking communication between AWS CodeBuild and GitHub. This includes checking for any rules that might block outbound HTTPS traffic to GitHub.
Relevant content
- Accepted Answerasked 3 years ago
- asked a month ago
- asked 2 years ago
- Accepted Answerasked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago