source AMI does not exist

721 views
Skip to first unread message

Matt Aimonetti

unread,
Jan 28, 2014, 6:45:26 PM1/28/14
to packe...@googlegroups.com
Hi,

I'm having an issue building an AMI since for some reason packer doesn't like the source image I'm using:

{
    "type": "amazon-ebs",
    "access_key": "{{user `aws_access_key`}}",
    "secret_key": "{{user `aws_secret_key` }}",
    "region": "us-west-1",
    "source_ami": "ami-04d12673",
    "instance_type": "m1.medium",
    "ssh_username": "ubuntu",
    "ami_name": "packer-splice {{timestamp}}"
  }

==> amazon-ebs: Creating temporary keypair: packer 00e83f0f-1cc2-7ec6-415e-f8d574028aa2
==> amazon-ebs: Creating temporary security group for this instance...
==> amazon-ebs: Authorizing SSH access on the temporary security group...
==> amazon-ebs: Launching a source AWS instance...
==> amazon-ebs: Deleting temporary security group...
==> amazon-ebs: Deleting temporary keypair...
Build 'amazon-ebs' errored: There was a problem with the source AMI: The image id '[ami-04d12673]' does not exist (InvalidAMIID.NotFound)
==> Some builds didn't complete successfully and had errors:
--> amazon-ebs: There was a problem with the source AMI: The image id '[ami-04d12673]' does not exist (InvalidAMIID.NotFound)

Now the image does exist and is the right region as you can see from: http://cloud-images.ubuntu.com/locator/ec2/

Am I doing something wrong or is that a bug?

Thanks,

- Matt

Jack Pearkes

unread,
Jan 29, 2014, 11:42:01 AM1/29/14
to packe...@googlegroups.com
Matt,

Looks like you're specifying the precise64 image for eu-west-1, not us-west-1 as your template specifies.

Similar names, though! Geography...

Jack



--
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Shane Meyers

unread,
Jan 28, 2014, 7:33:06 PM1/28/14
to packe...@googlegroups.com
ami-04d12673 is located in eu-west-1 and you're attempting to launch in us-west-1.  You probably want ami-969fadd3 instead which is an AMI for us-west-1.

-shane
Reply all
Reply to author
Forward
0 new messages