com.amazonaws.AmazonServiceException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • The instance schedules so far works for most of the stock images like the "Unknown OS stock image" but this fails when the chose image is "Ubuntu Stock Image". The bamboo logs throws: {code} 2015-05-29 18:45:00,033 INFO [scheduler_Worker-1] [ElasticFunctionalityFacadeImpl] Adjusting elastic agents with schedule: com.atlassian.bamboo.agent.elastic.schedule.ElasticInstanceScheduleImpl@3f36a682[25296897,0 0/15 18-20 ? * *,com.atlassian.bamboo.agent.elastic.server.ElasticImageConfigurationImpl@5b50e640,EQUALS,1,true] 2015-05-29 18:45:00,033 INFO [scheduler_Worker-1] [ElasticFunctionalityFacadeImpl] Starting up 1 of 'Ubuntu stock image' elastic instances 2015-05-29 18:45:04,911 INFO [http-bio-10581-exec-16] [AccessLogFilter] admin GET http://localhost:10581/bamboo581/ajax/viewPlanUpdates.action?sinceSystemTime=1432896283920&lastProject= 65053kb 2015-05-29 18:45:06,370 INFO [scheduler_Worker-1] [ElasticFunctionalityFacadeImpl] Requested that new elastic instance be created for configuration: Ubuntu stock image / ami-8946a989 2015-05-29 18:45:06,376 INFO [elastic-pool-4-thread-1] [RemoteElasticInstanceEbsHelperImpl] Running non-BDM EBS handling code 2015-05-29 18:45:06,704 ERROR [elastic-pool-4-thread-1] [RemoteEC2InstanceImpl] EC2 instance order failed. com.amazonaws.AmazonServiceException: The image id '[ami-8946a989]' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidAMIID.NotFound; Request ID: 5739d640-fce7-4adc-ae08-e2cb40360778) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1077) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:725) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:460) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:295) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9823) at com.amazonaws.services.ec2.AmazonEC2Client.describeImages(AmazonEC2Client.java:4911) at com.atlassian.aws.ec2.caches.ImageCache.describeImages(ImageCache.java:43) at com.atlassian.aws.AWSAccountImpl.describeImages(AWSAccountImpl.java:645) at com.atlassian.aws.AWSAccountImpl.describeImage(AWSAccountImpl.java:639) at com.atlassian.aws.ec2.InstanceLauncherFactory.getBlockDeviceMappings(InstanceLauncherFactory.java:294) at com.atlassian.aws.ec2.InstanceLauncherFactory.access$300(InstanceLauncherFactory.java:41) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.getRunInstancesRequest(InstanceLauncherFactory.java:139) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.runInstance(InstanceLauncherFactory.java:114) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:101) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:462) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:445) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:104) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:84) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} *Note:* It appears this issue is happening when the region is *US EAST*. This works with other regions like *Asia Pacific (Tokyo)*
    via by Sultan Maiyaki [Atlassian],
  • The instance schedules so far works for most of the stock images like the "Unknown OS stock image" but this fails when the chose image is "Ubuntu Stock Image". The bamboo logs throws: {code} 2015-05-29 18:45:00,033 INFO [scheduler_Worker-1] [ElasticFunctionalityFacadeImpl] Adjusting elastic agents with schedule: com.atlassian.bamboo.agent.elastic.schedule.ElasticInstanceScheduleImpl@3f36a682[25296897,0 0/15 18-20 ? * *,com.atlassian.bamboo.agent.elastic.server.ElasticImageConfigurationImpl@5b50e640,EQUALS,1,true] 2015-05-29 18:45:00,033 INFO [scheduler_Worker-1] [ElasticFunctionalityFacadeImpl] Starting up 1 of 'Ubuntu stock image' elastic instances 2015-05-29 18:45:04,911 INFO [http-bio-10581-exec-16] [AccessLogFilter] admin GET http://localhost:10581/bamboo581/ajax/viewPlanUpdates.action?sinceSystemTime=1432896283920&lastProject= 65053kb 2015-05-29 18:45:06,370 INFO [scheduler_Worker-1] [ElasticFunctionalityFacadeImpl] Requested that new elastic instance be created for configuration: Ubuntu stock image / ami-8946a989 2015-05-29 18:45:06,376 INFO [elastic-pool-4-thread-1] [RemoteElasticInstanceEbsHelperImpl] Running non-BDM EBS handling code 2015-05-29 18:45:06,704 ERROR [elastic-pool-4-thread-1] [RemoteEC2InstanceImpl] EC2 instance order failed. com.amazonaws.AmazonServiceException: The image id '[ami-8946a989]' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidAMIID.NotFound; Request ID: 5739d640-fce7-4adc-ae08-e2cb40360778) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1077) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:725) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:460) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:295) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9823) at com.amazonaws.services.ec2.AmazonEC2Client.describeImages(AmazonEC2Client.java:4911) at com.atlassian.aws.ec2.caches.ImageCache.describeImages(ImageCache.java:43) at com.atlassian.aws.AWSAccountImpl.describeImages(AWSAccountImpl.java:645) at com.atlassian.aws.AWSAccountImpl.describeImage(AWSAccountImpl.java:639) at com.atlassian.aws.ec2.InstanceLauncherFactory.getBlockDeviceMappings(InstanceLauncherFactory.java:294) at com.atlassian.aws.ec2.InstanceLauncherFactory.access$300(InstanceLauncherFactory.java:41) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.getRunInstancesRequest(InstanceLauncherFactory.java:139) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.runInstance(InstanceLauncherFactory.java:114) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:101) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:462) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:445) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:104) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:84) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} *Note:* It appears this issue is happening when the region is *US EAST*. This works with other regions like *Asia Pacific (Tokyo)*
    via by Sultan Maiyaki [Atlassian],
  • GitHub comment 41#135877614
    via GitHub by denis-yuen
    ,
  • AWS API get flooded after AMI change
    via by Unknown author,
    • com.amazonaws.AmazonServiceException: The image id '[ami-8946a989]' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidAMIID.NotFound; Request ID: 5739d640-fce7-4adc-ae08-e2cb40360778) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1077) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:725) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:460) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:295) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9823) at com.amazonaws.services.ec2.AmazonEC2Client.describeImages(AmazonEC2Client.java:4911) at com.atlassian.aws.ec2.caches.ImageCache.describeImages(ImageCache.java:43) at com.atlassian.aws.AWSAccountImpl.describeImages(AWSAccountImpl.java:645) at com.atlassian.aws.AWSAccountImpl.describeImage(AWSAccountImpl.java:639) at com.atlassian.aws.ec2.InstanceLauncherFactory.getBlockDeviceMappings(InstanceLauncherFactory.java:294) at com.atlassian.aws.ec2.InstanceLauncherFactory.access$300(InstanceLauncherFactory.java:41) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.getRunInstancesRequest(InstanceLauncherFactory.java:139) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.runInstance(InstanceLauncherFactory.java:114) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:101) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:462) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:445) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:104) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:84) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

    Users with the same issue

    Unknown visitor2 times, last one,
    tvrmsmith
    12 times, last one,
    aldrinleal
    38 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    43 more bugmates