Bamboo can't start Amazon Elastic Instance agent after being added to VPC

[Ryan Vice]

After updating my Elastic Image configuration to be in my company's Amazon VPC, Bamboo is no longer able to start the Elastic Agent on my Elastic Intances. I'm able to RDP to the instance and I can verify that the VPC is working but for whatever reason Bamboo can't launch the Agent. I've updated the security as shown below which to me doesn't seem like it should impact Bamboo's ability to access it.

[Przemek Bruski · Accepted solution]

Does your instance have EIP?

[Ryan Vice]

Nope, that was the setting. For anyone else having this problem do the following:

1. Click the Gear and select Overview
2. Select Configuration in the Instances section
3. Select Edit
4. Check "Enable elastic IP management"

[Lee Myring]

Please take note of the way Bamboo deals with Elastic IPs. It will delete ALL Elastic IPs that are not associated unless you whitelist them. We have failover ENIs with EIPs attached but they are not associated, without whitelisting them they would be deleted...

[mfobrien NA]

This option does not seem to be available. Running inside the default 172.31 amazon public VPC does not need an EIP - just a public IP. The issue on the other post is also fixed - but does not fix the fact that bamboo cannot connect to the instance it created inside the private subnet of the VPC. https://answers.atlassian.com/questions/231544/answers/11990736?flashId=1954419289