AWS CodeConnections is the connection layer between supported Git providers and AWS services that consume repository content or repository events. Instead of placing a developer's personal access token directly into each delivery workflow, engineers create a connection, authorize access at the repository provider, and give an AWS service permission to use that connection. The connection is represented by an Amazon Resource Name, or ARN, which consuming services reference in their configuration.
A connection has both AWS-side configuration and provider-side authorization. Creating the AWS resource alone does not necessarily make it usable: connections created through an API or infrastructure-as-code workflow typically remain pending until an administrator completes the provider authorization process. For GitHub, this involves authorizing the appropriate GitHub App installation and repository access. Treat authorization completion and verification of the available connection status as explicit deployment prerequisites rather than assuming that successful resource creation means the integration is ready.
In a common delivery architecture, AWS CodePipeline uses a connection-backed source action to obtain a selected repository and branch. Repository events can initiate pipeline executions, while source action configuration determines how repository content is passed to downstream actions. AWS CodeBuild can also use supported connections for source access. Engineers should distinguish a connection's provider permissions from the AWS IAM permissions granted to the consuming service: both must allow the intended operation.
For supported self-managed providers, CodeConnections uses a host resource to represent the provider installation. Depending on the provider and deployment, host configuration can include VPC connectivity, security groups, subnets, and certificate information. Validate DNS resolution, network reachability, and provider-specific prerequisites before troubleshooting the pipeline itself. Support differs by provider, AWS Region, and consuming service, so a provider supported by CodeConnections is not automatically supported in every downstream workflow.
CodeConnections also supports repository links and synchronization configurations for supported Git synchronization scenarios. For example, AWS CloudFormation Git sync can monitor repository-managed deployment files and templates and use changes to update a stack. These resources describe the repository relationship and synchronization target; they are separate from the connection that supplies authorization.
Operationally, apply least-privilege IAM permissions to connection administration and use, restrict provider installations to necessary repositories, and record administrative API activity with AWS CloudTrail. When diagnosing failures, check connection status, provider installation permissions, repository and branch identifiers, consuming-service role permissions, and any host networking requirements. AWS CodeConnections was previously named AWS CodeStar Connections, so older resource names, ARNs, policy examples, and integration identifiers may retain the earlier terminology. Preserve the correct identifiers for existing resources rather than assuming a rename requires resource replacement.
AWS CloudFormation
AWS CloudTrail
Amazon VPC
AWS CodeBuild
AWS CodePipeline