nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we configure bamboo instance in AWS singapore region?

Development7

All our database and webserver instances are in AWS singapore region.

And our bamboo instance is in AWS N.Virginia region.

Because of this we are not able to run automatic deployments from bamboo to our test instance which are in different regions.

Is it possible to move existing bamboo from N.Virginia to Singapore region?

If possible, please guide us. If not possible then how can we have automated deloys between diff regions?

Thank you.

Accepted answers

All comments

vu chinh

f possible, please guide us. If not possible then how can we have automated deloys between diff regions

Przemek Bruski

With Bamboo OnDemand or Bamboo 5.2 Standalone, you can configure it to use a different region in Administartion/Elastic Configuration. There's a combo box that'll let you select Singapore.

Andrey AndreySh

But the main issues are:

1. After selecting the Singapore region in bamboo i don't see any image configuration on "Manage elastic image configurations" page.

2. Second issue related to security group. We have staging instances in VPC and non-VPC but from bamboo instance these instances not accesible by "\\hostname\C$". So we are trying to put bamboo instance under the same security group as our staging instance but this option is disabled for bamboo instance.

Przemek Bruski

1. Atlassian does not provide/support images for regions other thatn US East 1. You can copy an image from US East to Singapore.

2. I don't really understand what you're trying to achieve. Bamboo instances will be started with two groups - elasticbamboo and ControlledByBamboo. You can add rules to these groups, but you cannot remove rules or add security groups.

Andrey AndreySh

We copied exist image from Virginia to Singapoor with AMI ID = ami-52570300

But when i try to register new image configuration in bamboo and map it to ami-52570300 i recived error:

Unable to contact AWS to get AMI details: AmazonServiceException: Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: d747904a-e399-45b6-a907-06a0e277c272, AWS Error Code: InvalidAMIID.NotFound, AWS Error Message: The image id '[ami-52570300]' does not exist

What you can advice ?

Przemek Bruski

Double chceck: the region selection in your Bamboo configuration and your AMI permissions (i.e. are you using the same account/credentials in the server and while registering it).

Development7

Hi,

What have we done....

1) Copied the AMI image from N.Virgibnia region to Singapore region

2) Logged in to Bamboo admin-->Configuration Edit --> Changed AWS Region from (US East - Northern Virginia) to Asia Pacific (Singapore)-->Save

All settings were working when linked to N.Virginia. So, We have not changed any other settings like AWS access key id

3) Clicled on image Configurations--> New Name Given--> Copy,Pasted the AMI id from AWS console (ami-52570300)-->Selected Windows from Product dropdown-->Save.

Results in error "Unable to contact AWS to get AMI details: AmazonServiceException: Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: 30858045-5bc2-4656-bec9-e4a20109202f, AWS Error Code: InvalidAMIID.NotFound, AWS Error Message: The image id '[ami-52570300]' does not exist"

With respective to your previous reply,

We have only 1 account with AWS. So we are using that account for both N.Virginia and Singapore regions.

Please let us know, if we are missing any thing. How do we link this new copied image to our Elastic Bamboo.

Do you want us to provide any screen shots of our image properties or any other information?

Przemek Bruski

Tokyo and Singapore regions are swapped. Just use Tokyo when you want to use Singapore.

Andrey AndreySh

Thank you Przemek

With Tokyo we are able to create new image configuration in appropriate region

But there is other issue related to perfomance. Now on this new instance the "Publishing an artifact" proccess takes much more time than before when instance was in Virginia - now 50 mins and before was 2 mins

What you advice ?

Przemek Bruski

I don't think you'll be able to fix it. Try voting/commenting here:

https://jira.atlassian.com/browse/BAM-11876

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

aws