- Newest
- Most votes
- Most comments
Hello.
I think the answer at the following URL is relevant:
CodeConnections was previously known as CodeStar until a few years ago.
Using "codestar-connections" may solve the problem.
https://repost.aws/questions/QUWOxbjBL-S4SkUoK0ameT-g/codepipeline-service-role-insufficient-permission-for-codestar-connections
Hey,
Hope you're keeping well.
For a GitHub source stage using CodeConnections, the CodePipeline service role must have codestar-connections:UseConnection on the specific connection ARN, not just *. Go to IAM, edit the pipeline’s role, and add a statement granting codestar-connections:UseConnection for the exact ARN you see in the CodeConnections console. Also verify that the connection status is Available and that the role trust policy allows codepipeline.amazonaws.com to assume it. If you updated the role after creating the pipeline, redeploy or manually retry the execution so the new permissions are applied.
Thanks and regards,
Taz
answered a year ago
Hey,
Hope you're keeping well.
For GitHub source actions in CodePipeline using CodeConnections, the service role needs both codeconnections:UseConnection and codestar-connections:UseConnection on the specific connection ARN, not just "*" as the resource. Make sure the policy is attached to the pipeline’s execution role (visible under CodePipeline > Your Pipeline > Settings > Service role), and that the connection status in Developer Tools > Connections is Available. If the connection is in Pending or Needs Update, reauthorize it from the console before running the pipeline. Also confirm that the service role trust policy allows codepipeline.amazonaws.com to assume it.
Thanks and regards,
Taz
answered a year ago
