DevOps / Bamboo: Continuous Integration & Deployment Interview Questions
When would you choose Elastic Bamboo on AWS?
Elastic Bamboo provisions remote agents as EC2 instances on demand — spinning them up when the build queue grows and terminating them once idle — so it fits situations where load is bursty rather than constant.
It makes sense when:
- Build volume spikes at predictable times (end of sprint, pre-release crunch) but is otherwise light, so paying for fixed always-on agents would waste capacity most of the week.
- The team already runs Bamboo on or near AWS and has an AWS account to authenticate against (via access key or an EC2 instance profile).
- Different jobs occasionally need a fresh, disposable environment rather than a long-lived agent that could accumulate state between builds.
It's a weaker fit when the version control system sits behind a strict internal firewall, since elastic agents on EC2 need network access to it — that's a security trade-off worth reading Atlassian's Elastic Bamboo security guidance on before enabling it.
Elastic Bamboo is the best fit for workloads that are:
What's a weaker-fit scenario for Elastic Bamboo?
More Related questions...
