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,462,702
Community Members
 
Community Events
176
Community Groups

Configure AWS Cross-account for Elastic Bamboo

Edited
Sam I'm New Here Jan 18, 2023

Is there away to configure multiple AWS account for Elastic Bamboo?

1 answer

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.

Potential workaround

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events