Docker Runner Credentials Passing Best Practices

Sean Feeney March 1, 2019

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?

2 answers

1 accepted

2 votes
Answer accepted
Sean Feeney March 5, 2019

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

1 vote
Steffen Opel _Utoolity_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 7, 2019

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:

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:

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events