Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,062
Community Members
 
Community Events
176
Community Groups

Docker Runner Credentials Passing Best Practices

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

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

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

Atlassian Community Events