Docker Runner Credentials Passing Best Practices

[Sean Feeney]

Can anyone suggest a best practice for passing AWS credentials to a Docker Runner? Or really any way to pass sensitive variables short of baking them into your Docker image?

[Sean Feeney · Accepted solution]

For anyone stumbling across this, Bamboo variables are available to Script tasks in a Docker Runner.

[Steffen Opel _Utoolity_]

Thanks for sharing your findings! In terms of security best practices, given your usage of AWS, allow me to also suggest a more secure alternative for handling AWS credentials and other sensitive variables in Bamboo with two AWS focused apps:

• Disclaimer: I'm a co-founder of these app's vendor Utoolity.

Identity Federation for AWS (Bamboo)

Rather than persisting long-term AWS credentials as global or plan variables, our (commercial) Identity Federation for AWS (Bamboo) app provides an AWS Credentials Variables task that allows to inject variables with temporary AWS credentials for reuse in subsequent tasks, e.g. the Bamboo Script task you seem to use, here's an example:

• How to provide temporary AWS credentials to the AWS Command Line Interface (AWS CLI) via Bamboo variables

Tasks for AWS (Bamboo)

Rather than persisting secrets and configuration data as global or plan variables, our (commercial) Tasks for AWS (Bamboo) app provides an AWS Systems Manager Parameter task that allows to inject variables with SSM secure string parameters (and also AWS Secrets Manager secrets) for reuse in subsequent tasks:

• Using the AWS Systems Manager Parameter task in Bamboo (Get Parameter)

Both tasks ensure that no sensitive information is persisted in Bamboo and instead retrieved at task execution time so that secrets can be securely managed in AWS and any access is automatically audited via AWS CloudTrail.