You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are setting up a Bamboo system in AWS with a Bamboo Server, and remote & elastic agents. (no local agents) The Bamboo server uses an external database, which is a Multi-AZ Postgres Server in AWS RDS.
Currently we have just one instance of the Bamboo Server hidden under an AWS ELB.
And everything is working great, including remote agents and elastic agents.
We would like to setup a farm of Bamboo Servers (at least 2) for availability purposes.
alright. so it looks like automatic fail-over is not possible. in that case, does the following setup does the closest to it?
when the primary bamboo system goes down for some reason, we do the following things manually:
and everything works normal within minutes.
though the 2 instances eventually use the same external database, they don't do it simultaneously. and hopefully can take turns.
will the above mechanism work without any glaring issues?
Why not use an auto-scaling group with your min/max/desired set to 1 instance. That way if your primary bamboo instance becomes unhealthy, auto-scaling will replace it with a new one. You can also manually trigger this scaling process to replace the instance at any time with an updated build, version, or config, etc.