Hi @Sam welcome to the Atlassian Community!
Unfortunately there is no way to achieve that, please watch and vote for the following issue to raise Atlassian's awareness of this notable gap for Enterprise customers following AWS multi-account best practices:
That being said, as you can infer from this issue being ignored since 2013, despite a solid number of votes and Enterprise relevance, I consider it highly unlikely that this will ever be tackled, because Atlassian effectively stopped improving Elastic Bamboo beyond basic maintenance quite some time ago.
I haven't tried this myself, but depending on your scenario, Andrew Hemming's slightly hacky workaround might help:
I managed to solve this problem using cross-account IAM roles and STS credentials.
http://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html
http://docs.aws.amazon.com/STS/latest/APIReference/Welcome.html
Basically, I make an STS call at the beginning of the job that obtains the credentials for the role I need to assume, then I either write those credentials to a config file and/or expose them as environment variables.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.