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?
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:
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.
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events