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.

  • As of today (Nov 17th), after Bamboo's upgrade to 5.7, users are currently unable to attach EBS volumes to *S3* backed AMIs. The following error shows up on the UI: {noformat} System Error Details Elastic Bamboo Error : EC2 Instance failed to start: EC2 instance order failed. (com.amazonaws.AmazonServiceException : EBS block device mappings not supported for instance-store AMIs. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 717d6a12-45f8-44d4-8133-a4c69133d42c)) Occurred: 17 Nov 2014, 9:00:00 AM com.amazonaws.AmazonServiceException: EBS block device mappings not supported for instance-store AMIs. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 717d6a12-45f8-44d4-8133-a4c69133d42c) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1053) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:662) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:428) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:290) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:4382) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:129) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:460) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:443) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:103) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) {noformat} *Workaround* Change your Image Configurations to use a *EBS* backed AMI instead of a S3 backed one.
    via by Marlon Aguiar [Atlassian],
  • As of today (Nov 17th), after Bamboo's upgrade to 5.7, users are currently unable to attach EBS volumes to *S3* backed AMIs. The following error shows up on the UI: {noformat} System Error Details Elastic Bamboo Error : EC2 Instance failed to start: EC2 instance order failed. (com.amazonaws.AmazonServiceException : EBS block device mappings not supported for instance-store AMIs. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 717d6a12-45f8-44d4-8133-a4c69133d42c)) Occurred: 17 Nov 2014, 9:00:00 AM com.amazonaws.AmazonServiceException: EBS block device mappings not supported for instance-store AMIs. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 717d6a12-45f8-44d4-8133-a4c69133d42c) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1053) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:662) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:428) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:290) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:4382) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:129) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:460) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:443) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:103) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) {noformat} *Workaround* Change your Image Configurations to use a *EBS* backed AMI instead of a S3 backed one.
    via by Marlon Aguiar [Atlassian],
  • As of today (Nov 17th), after Bamboo's upgrade to 5.7, users are currently unable to start *EC2* instances with an EBS volume attached to them. Even though the EC2 instance has an EBS volume attached, Bamboo keeps searching for a snapshot ID. It fails with the following error message: {noformat} 2014-11-17 15:05:18,884 ERROR [elastic-pool-4-thread-1] [RemoteEC2InstanceImpl] EC2 instance order failed. com.amazonaws.AmazonServiceException: The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1053) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:662) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:428) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:290) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:4382) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:129) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:460) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:443) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:103) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {noformat} Looking at the error message we can see that it's trying to find a snapshot with ID 'vol-f4a60dec', but this is not a snapshot ID, it's an EBS volume. *Workaround* Create a snapshot from the EBS volume inside AWS and use the snapshot ID in Bamboo while this is not resolved.
    via by Bruno Rosa,
  • As of today (Nov 17th), after Bamboo's upgrade to 5.7, users are currently unable to start *EC2* instances with an EBS volume attached to them. Even though the EC2 instance has an EBS volume attached, Bamboo keeps searching for a snapshot ID. It fails with the following error message: {noformat} 2014-11-17 15:05:18,884 ERROR [elastic-pool-4-thread-1] [RemoteEC2InstanceImpl] EC2 instance order failed. com.amazonaws.AmazonServiceException: The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1053) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:662) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:428) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:290) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:4382) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:129) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:460) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:443) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:103) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) {noformat} Looking at the error message we can see that it's trying to find a snapshot with ID 'vol-f4a60dec', but this is not a snapshot ID, it's an EBS volume. *Workaround* Create a snapshot from the EBS volume inside AWS and use the snapshot ID in Bamboo while this is not resolved.
    via by Bruno Rosa,
    • com.amazonaws.AmazonServiceException: EBS block device mappings not supported for instance-store AMIs. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 717d6a12-45f8-44d4-8133-a4c69133d42c) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1053) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:662) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:428) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:290) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:4382) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:129) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:460) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:443) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:103) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

    Users with the same issue

    Unknown visitor1 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