- Newest
- Most votes
- Most comments
Hello.
The following documentation states that you need owner privileges to connect to a GitHub repository belonging to your organization.
This document is for CodePipeline, so it might be easy to overlook.
https://docs.aws.amazon.com/codepipeline/latest/userguide/connections-github.html
To create the connection, you must be the GitHub organization owner. For repositories that are not under an organization, you must be the repository owner.
Thank you for bringing this to our attention. You've identified an important clarification that needs to be made in the documentation.
Based on the current documentation, you're correct that it states you need "organization owner permissions or admin permissions to the repository to create the connection." However, your experience highlights a critical distinction that isn't explicitly documented: the permission requirements depend on how the AWS Connector for GitHub app is installed.
When the AWS Connector for GitHub app is installed at the organization level (as in your case with installation ID 85319298), GitHub's security model requires that only users with organization owner permissions can authorize connections through that installation. This is a GitHub platform requirement, not an AWS-specific limitation. Repository admin permissions alone are insufficient in this scenario because the app installation scope is at the organization level.
The documentation would benefit from clarifying that:
- For organization-level GitHub App installations: Organization owner permissions are required to create connections, regardless of repository-level permissions
- For repository-level GitHub App installations: Repository admin permissions are sufficient
The error message you encountered - "An owner with access to installation [ID] must create the connection" - is GitHub's way of enforcing this requirement. This specific error and its context should indeed be documented in the troubleshooting guides.
Your workaround of having the GitHub organization owner create the connection is the correct approach for organization-level installations. Once created, the connection can be used by other team members with appropriate AWS permissions.
This feedback about the documentation gap is valuable and should be addressed to prevent confusion for other users in similar situations.
Sources
Troubleshooting connections - Developer Tools console
I thing is not possible "For repository-level GitHub App installations: Repository admin permissions are sufficient"? Currently aws need github owner access to establish the connection along with installed the connection apps
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago

This is the valid answer