[IAM Credentials Migration] [Code build & CR package] Update the codebuild spec to use the IAM role created to replace the credentials from secret manager
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
Update the codebuild spec to use the IAM role created to replace "packages-e2e". Look for the packages_ci_beta:aws_access_key_id and packages_ci_beta:aws_secret_access_key_id
Update the codebuild spec to use the IAM role created to replace "non-regional-packages-e2e". Look for the packages_ci_beta:non_regional_aws_access_key_id and packages_ci_beta:non_regional_aws_secret_access_key_id
Update the codebuild spec to use the IAM role created to replace "cert-manager-e2e". Look for the packages_ci_beta:route53_access_key_id and packages_ci_beta:route53_secret_access_key
Refer to
https://repost.aws/knowledge-center/codebuild-temporary-credentials-docker for details on how to use the credentials from IAM role
Contributor guide
Research direction
Locate the CodeBuild specification and search for packages_ci_beta:aws_access_key_id, packages_ci_beta:non_regional_aws_access_key_id, and packages_ci_beta:route53_access_key_id, along with their secret counterparts. Read the referenced AWS guidance on temporary credentials for Docker. Done means all three credential pairs are replaced with the corresponding IAM roles without retaining the Secret Manager credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- ci-cd, cloud, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100