CodePipeline GitHub source step – some repositories not visible, but accessible via full path

Question

Hi everyone,

We're experiencing a strange issue with AWS CodePipeline when using GitHub as a source provider.

**Problem:**
In the Source step configuration (via the AWS Console), only some of our GitHub repositories are visible, while others are missing from the dropdown/list. However: all repositories are confirmed to be present and active in our GitHub org. The GitHub connector (via AWS CodeStar Connections) has full access to all repositories in the org. If we manually provide the full path to a missing repository (e.g., org-name/repo-name), the pipeline works as expected.

**What we've checked:**
- All affected repositories contain active branches and recent commits.
- The connector is authorized and not limited to specific repos.
- There are no known permission or visibility restrictions on the GitHub side.

We're wondering whether this might be a bug on the AWS side, or a known limitation in how CodePipeline loads GitHub repository lists.

Any guidance would be greatly appreciated!

Thanks in advance!

re:Post Agent · Answer

This issue with not all GitHub repositories being visible in the CodePipeline source configuration dropdown is likely related to permissions or the connection configuration rather than a bug.

Based on similar cases, here are some potential causes and solutions:

1. **GitHub Token Permissions**: The personal access token or connection might not have sufficient permissions to view all repositories. Even though you've confirmed the connector has full access, it's worth verifying that the GitHub user associated with the connection has at least "Reporter" access to all repositories you're trying to access.

2. **GitHub Organization Association**: The list of repositories shown in the CodePipeline console is based on the GitHub organization the authorized account belongs to. Verify that the account used for the connection is associated with the correct GitHub organization where all your repositories are created.

3. **Connection Revalidation**: Try revalidating your GitHub connection:
- Go to the AWS CodeStar Connections section in the AWS Console
- Revalidate the connection to ensure it's still active and properly configured
- Test the connection to see if it successfully links to all your GitHub repositories

4. **Connection Recreation**: If the issue persists, you might need to:
- Delete the existing CodeStar Connection
- Uninstall the GitHub application from your GitHub Organization/Repository
- Recreate the CodeStar Connection
- Reinstall the GitHub application

5. **Service Role Permissions**: Ensure your CodePipeline service role has the correct permissions, specifically `codeconnections:UseConnection` for the appropriate resource ARN.

The fact that manually entering the full path works suggests that the connection itself is functioning correctly, but there might be an issue with how the repositories are being listed or filtered in the UI. This is a known behavior in some cases rather than a bug.  
**Sources**  
[CodePipeline self-managed Gitlab does not list all repositories | AWS re:Post](https://repost.aws/questions/QUfrtEQyESTgS0k7b6YC-y4w/codepipeline-self-managed-gitlab-does-not-list-all-repositories)  
[Troubleshooting CodePipeline - AWS CodePipeline](https://docs.aws.amazon.com/codepipeline/latest/userguide/troubleshooting.html)  
["[GitHub] Not Found" - CodePipeline (Github V2) | AWS re:Post](https://repost.aws/questions/QUZJc39BJTSuShvT_2g_WAYA/github-not-found-codepipeline-github-v2)

CodePipeline GitHub source step – some repositories not visible, but accessible via full path

Add your answer

Relevant content