You don’t have access to this AMI. Check its launch permissions on AWS

We are using bamboo v8.2.4.
This started being a problem on the 17th July.

Problem Symptoms
Our bamboo builds are not able to be started, all builds say ‘No agent can build this job’. When looking at the image configuration used by the agents, the image is disabled. Enabling the image and running a build causes the image to be disabled again.

Our Bamboo builds based on image ami-00d3257706c9cff62 (image.ASIA_PACIFIC_SE_2.EBS.x86_64.linux.HVM.Ubuntu - for bamboo v8.2.4) are failing with the message.

java.lang.IllegalStateException: Unable to find image: ami-00d3257706c9cff62
	at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl.initEc2InstanceObject(
	at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl.access$100(
	at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$
	at java.util.concurrent.Executors$
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(
	at java.util.concurrent.ScheduledThreadPoolExecutor$
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$

Trying to create a new elastic image using ‘ami-00d3257706c9cff62’ returns the error

You don’t have access to this AMI. Check its launch permissions on AWS

When trying to create an image using ami-0323877238e2add03 (for bamboo v8.2.3) there seems to be no problems. I’m not sure if there would be any problems with us using a different image on this version of bamboo.


  1. Is there a way to solve this problem?
  2. Is there a work around?
  3. Is this something I can avoid in the future?

Thanks :slightly_smiling_face:


Hello @GeneCulling,

Can you please try that again? We have adjusted the image permissions and it should be fine by now.

Kind regards,

Eduardo Alvarenga
Atlassian Support APAC

It’s all working fine now, thanks for your help :+1: