You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the ability to specify the AWS CLI profile name for each command, as is (mostly) done in the circleci/aws-ecr orb.
Background
Many projects start out with a single AWS account and put credentials for that account into AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in the CircleCI environment. In fact, many CircleCI examples assume this has been done. When it comes time to create separate AWS accounts (e.g. for development vs. staging vs. production), credentials for these accounts need to be added to the CircleCI environment. Typically, these credentials are selected in a given job using the setup command of the circleci/aws-cli orb, which creates a CLI profile. By default, the credentials go into the default profile, which the CLI will use automatically, but only if AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY are not in the environment. Since removing those variables would break all existing workflows and jobs, having a way to explicitly specify the profile (even if it is "default") allows different credentials to be used alongside the original ones.
Describe Request:
Add the ability to specify the AWS CLI profile name for each command, as is (mostly) done in the
circleci/aws-ecr
orb.Background
Many projects start out with a single AWS account and put credentials for that account into
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
in the CircleCI environment. In fact, many CircleCI examples assume this has been done. When it comes time to create separate AWS accounts (e.g. for development vs. staging vs. production), credentials for these accounts need to be added to the CircleCI environment. Typically, these credentials are selected in a given job using thesetup
command of thecircleci/aws-cli
orb, which creates a CLI profile. By default, the credentials go into thedefault
profile, which the CLI will use automatically, but only ifAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
are not in the environment. Since removing those variables would break all existing workflows and jobs, having a way to explicitly specify the profile (even if it is "default") allows different credentials to be used alongside the original ones.Examples:
Supporting Documentation Links:
The text was updated successfully, but these errors were encountered: