Skip to content

AWS Transform is not discovering Github repositories.

0

I have been trying to use AWS Transform providing the source repository in GitHub which sits inside my company org. Although I am able to add the connection details and able to create AWS code connection as specified by AWS documentation, the repositories that I own are not visible in the AWS transform.

Please can you help me know what I am missing.

Below are the verifications that I have already done.

  1. Transform Connector state is Active
  2. My Github account is having the AWS connector for Github app installed and configured
  3. Below are the permissions given to all the repositories that I own in github. a. Read access to actions, deployments, environments, issues, and metadata b. Read and write access to administration, code, commit statuses, pull requests, and repository hooks
  4. The AWS connector for Github is authorized and is visible in "Authorized Github Apps"

Below is the screenshot of the issue I am facing on the transform Job.

Enter image description here Enter image description here

2 Answers
0

Based on the information provided, here are some potential issues and solutions to explore:

Repository Access Configuration: Even though you have the AWS Connector for GitHub app installed and configured, the connection may not have been granted access to your specific repositories. After installing the app, you need to explicitly configure which repositories the GitHub App connection can access. Check your GitHub App settings to ensure the repositories you want to transform are included in the access list.

Project Membership and Permissions: Verify that you are an active member of the project containing the source repositories and that you have accepted any invitations. If you cannot see the repositories, you may need to confirm your project membership status or accept pending invitations.

Connection Region Mismatch: Ensure that your AWS CodeConnections connection was created in the same region where you're running your AWS Transform job. If the AWS Connector for GitHub was installed but the connection was created in a different region than intended, you may need to create a new connection in the correct region using the existing installation ID.

Repository Administrator Approval: Depending on your repository permissions, an administrator of the code repository may need to approve the connector and explicitly grant AWS Transform access to the repositories. Check if there are any pending approval requests that need to be addressed.

Recommended Next Steps:

  1. Review your GitHub App installation settings to confirm repository access is properly configured
  2. Verify the connection was created in the correct AWS region
  3. Check with your repository administrators to ensure all necessary approvals have been granted
  4. Confirm your IAM role has the necessary permissions to use the connection

If the issue persists after these checks, you may need to recreate the connection or contact AWS support for further assistance.
Sources
Creating the AWS Transform .NET job plan - AWS Transform
Troubleshooting problems with source repositories - Amazon CodeCatalyst
GitHub App connections for GitHub and GitHub Enterprise Server - AWS CodeBuild

answered 3 months ago
EXPERT
reviewed 3 months ago
0

Thanks Team,

The issue I was related to the Github Organization not having access. After personalizing the repository to my account, The issue got resolved

answered 3 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.