Error launching source instance: Unsupported

[surenraju-zz]

Overview of the Issue

While i am trying to create AMI in region me-south-1, i am getting the following error

==> learn-packer.amazon-ebs.ubuntu: Error launching source instance: Unsupported: The requested configuration is currently not supported. Please check the documentation for supported configurations.
==> learn-packer.amazon-ebs.ubuntu:     status code: 400, request id: 5d9a1080-73da-4fd8-afec-8f89f75ec471

Following is the packer template. I took this from official website.
https://learn.hashicorp.com/tutorials/packer/aws-get-started-build-image?in=packer/aws-get-started

packer {
  required_plugins {
    amazon = {
      version = ">= 0.0.2"
      source  = "github.com/hashicorp/amazon"
    }
  }
}

source "amazon-ebs" "ubuntu" {
  ami_name      = "learn-packer-linux-aws"
  instance_type = "t2.micro"
  region        = "me-south-1"
  source_ami    = "ami-0eddb8cfbd6a5f657"
  ssh_username  = "ubuntu"
}

build {
  name = "learn-packer"
  sources = [
    "source.amazon-ebs.ubuntu"
  ]
}

Reproduction Steps

Steps to reproduce this issue

Packer version

packer --version
1.7.6

Operating system and Environment details

IOS

Log Fragments and crash.log files

learn-packer.amazon-ebs.ubuntu: output will be in this color.

==> learn-packer.amazon-ebs.ubuntu: Prevalidating any provided VPC information
==> learn-packer.amazon-ebs.ubuntu: Prevalidating AMI Name: learn-packer-linux-aws
    learn-packer.amazon-ebs.ubuntu: Found Image ID: ami-0eddb8cfbd6a5f657
==> learn-packer.amazon-ebs.ubuntu: Creating temporary keypair: packer_61594b83-a37b-6e96-26d4-86a8d52c09b3
==> learn-packer.amazon-ebs.ubuntu: Creating temporary security group for this instance: packer_61594b86-4f87-a362-5859-cf0925b905b3
==> learn-packer.amazon-ebs.ubuntu: Authorizing access to port 22 from [0.0.0.0/0] in the temporary security groups...
==> learn-packer.amazon-ebs.ubuntu: Launching a source AWS instance...
==> learn-packer.amazon-ebs.ubuntu: Adding tags to source instance
    learn-packer.amazon-ebs.ubuntu: Adding tag: "Name": "Packer Builder"
==> learn-packer.amazon-ebs.ubuntu: Error launching source instance: Unsupported: The requested configuration is currently not supported. Please check the documentation for supported configurations.
==> learn-packer.amazon-ebs.ubuntu:     status code: 400, request id: 9cb9f91d-2634-4d0f-84cd-214d0b6e1db8
==> learn-packer.amazon-ebs.ubuntu: No volumes to clean up, skipping
==> learn-packer.amazon-ebs.ubuntu: Deleting temporary security group...
==> learn-packer.amazon-ebs.ubuntu: Deleting temporary keypair...
Build 'learn-packer.amazon-ebs.ubuntu' errored after 8 seconds 474 milliseconds: Error launching source instance: Unsupported: The requested configuration is currently not supported. Please check the documentation for supported configurations.
        status code: 400, request id: 9cb9f91d-2634-4d0f-84cd-214d0b6e1db8

==> Wait completed after 8 seconds 476 milliseconds

==> Some builds didn't complete successfully and had errors:
--> learn-packer.amazon-ebs.ubuntu: Error launching source instance: Unsupported: The requested configuration is currently not supported. Please check the documentation for supported configurations.
        status code: 400, request id: 9cb9f91d-2634-4d0f-84cd-214d0b6e1db8

[nywilken]

This looks like an AWS unsupported instance type error, meaning the instance type of t2.micro might not be supported.

Have you tried building with a different instance type that you may already be running in me-south-1?

I quickly searched for supported instances types in Middle East region and found the blog post https://aws.amazon.com/blogs/aws/now-open-aws-middle-east-bahrain/ which does not include t2 instances as supported types. I would try to run the build with a supported instance, t3.micro and see if that works for you.

I'm going to close this issue as I don't believe it to be a bug, but if after you've tried with a new instance you find that you are still running into issues which might be a bug. Please reach out and we will gladly reopen.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.