23 KiB
description | layout | page_title | sidebar_current |
---|---|---|---|
The amazon-ebs Packer builder is able to create Amazon AMIs backed by EBS volumes for use in EC2. For more information on the difference between EBS-backed instances and instance-store backed instances, see the storage for the root device section in the EC2 documentation. | docs | Amazon EBS - Builders | docs-builders-amazon-ebsbacked |
AMI Builder (EBS backed)
Type: amazon-ebs
The amazon-ebs
Packer builder is able to create Amazon AMIs backed by EBS
volumes for use in EC2. For more information on
the difference between EBS-backed instances and instance-store backed instances,
see the "storage for the root device" section in the EC2
documentation.
This builder builds an AMI by launching an EC2 instance from a source AMI, provisioning that running machine, and then creating an AMI from that machine. This is all done in your own AWS account. The builder will create temporary keypairs, security group rules, etc. that provide it temporary access to the instance while the image is being created. This simplifies configuration quite a bit.
The builder does not manage AMIs. Once it creates an AMI and stores it in your account, it is up to you to use, delete, etc. the AMI.
-> Note: Temporary resources are, by default, all created with the prefix
packer
. This can be useful if you want to restrict the security groups and
key pairs Packer is able to operate on.
Configuration Reference
There are many configuration options available for the builder. They are segmented below into two categories: required and optional parameters. Within each category, the available configuration keys are alphabetized.
In addition to the options listed here, a communicator can be configured for this builder.
Required:
-
access_key
(string) - The access key used to communicate with AWS. Learn how to set this. -
ami_name
(string) - The name of the resulting AMI that will appear when managing AMIs in the AWS console or via APIs. This must be unique. To help make this unique, use a function liketimestamp
(see template engine for more info) -
instance_type
(string) - The EC2 instance type to use while building the AMI, such ast2.small
. -
region
(string) - The name of the region, such asus-east-1
, in which to launch the EC2 instance to create the AMI. -
secret_key
(string) - The secret key used to communicate with AWS. Learn how to set this. -
source_ami
(string) - The initial AMI used as a base for the newly created machine.source_ami_filter
may be used instead to populate this automatically.
Optional:
-
ami_block_device_mappings
(array of block device mappings) - Add one or more block device mappings to the AMI. These will be attached when booting a new instance from your AMI. To add a block device during the Packer build seelaunch_block_device_mappings
below. Your options here may vary depending on the type of VM you use. The block device mappings allow for the following configuration:-
delete_on_termination
(boolean) - Indicates whether the EBS volume is deleted on instance termination. Defaultfalse
. NOTE: If this value is not explicitly set totrue
and volumes are not cleaned up by an alternative method, additional volumes will accumulate after every build. -
device_name
(string) - The device name exposed to the instance (for example,/dev/sdh
orxvdh
). Required when specifyingvolume_size
. -
encrypted
(boolean) - Indicates whether to encrypt the volume or not -
iops
(number) - The number of I/O operations per second (IOPS) that the volume supports. See the documentation on IOPs for more information -
no_device
(boolean) - Suppresses the specified device included in the block device mapping of the AMI -
snapshot_id
(string) - The ID of the snapshot -
virtual_name
(string) - The virtual device name. See the documentation on Block Device Mapping for more information -
volume_size
(number) - The size of the volume, in GiB. Required if not specifying asnapshot_id
-
volume_type
(string) - The volume type.gp2
for General Purpose (SSD) volumes,io1
for Provisioned IOPS (SSD) volumes, andstandard
for Magnetic volumes
-
-
ami_description
(string) - The description to set for the resulting AMI(s). By default this description is empty. This is a template engine where theSourceAMI
variable is replaced with the source AMI ID andBuildRegion
variable is replaced with the value ofregion
. -
ami_groups
(array of strings) - A list of groups that have access to launch the resulting AMI(s). By default no groups have permission to launch the AMI.all
will make the AMI publicly accessible. AWS currently doesn't accept any value other thanall
. -
ami_product_codes
(array of strings) - A list of product codes to associate with the AMI. By default no product codes are associated with the AMI. -
ami_regions
(array of strings) - A list of regions to copy the AMI to. Tags and attributes are copied along with the AMI. AMI copying takes time depending on the size of the AMI, but will generally take many minutes. -
ami_users
(array of strings) - A list of account IDs that have access to launch the resulting AMI(s). By default no additional users other than the user creating the AMI has permissions to launch it. -
ami_virtualization_type
(string) - The type of virtualization for the AMI you are building. This option must match the supported virtualization type ofsource_ami
. Can beparavirtual
orhvm
. -
associate_public_ip_address
(boolean) - If using a non-default VPC, public IP addresses are not provided by default. If this is toggled, your new instance will get a Public IP. -
availability_zone
(string) - Destination availability zone to launch instance in. Leave this empty to allow Amazon to auto-assign. -
custom_endpoint_ec2
(string) - This option is useful if you use a cloud provider whose API is compatible with aws EC2. Specify another endpoint like thishttps://ec2.custom.endpoint.com
. -
disable_stop_instance
(boolean) - Packer normally stops the build instance after all provisioners have run. For Windows instances, it is sometimes desirable to run Sysprep which will stop the instance for you. If this is set to true, Packer will not stop the instance and will wait for you to stop it manually. You can do this with a windows-shell provisioner.{ "type": "windows-shell", "inline": ["\"c:\\Program Files\\Amazon\\Ec2ConfigService\\ec2config.exe\" -sysprep"] }
-
ebs_optimized
(boolean) - Mark instance as EBS Optimized. Defaultfalse
. -
ena_support
(boolean) - Enable enhanced networking (ENA but not SriovNetSupport) on HVM-compatible AMIs. If true, addec2:ModifyInstanceAttribute
to your AWS IAM policy. Note: you must make sure enhanced networking is enabled on your instance. See Amazon's documentation on enabling enhanced networking. Defaultfalse
. -
force_deregister
(boolean) - Force Packer to first deregister an existing AMI if one with the same name already exists. Defaultfalse
. -
force_delete_snapshot
(boolean) - Force Packer to delete snapshots associated with AMIs, which have been deregistered byforce_deregister
. Defaultfalse
. -
encrypt_boot
(boolean) - Instruct packer to automatically create a copy of the AMI with an encrypted boot volume (discarding the initial unencrypted AMI in the process). Packer will always run this operation, even if the base AMI has an encrypted boot volume to start with. Defaultfalse
. -
kms_key_id
(string) - The ID of the KMS key to use for boot volume encryption. This only applies to the mainregion
, other regions where the AMI will be copied will be encrypted by the default EBS KMS key. -
iam_instance_profile
(string) - The name of an IAM instance profile to launch the EC2 instance with. -
launch_block_device_mappings
(array of block device mappings) - Add one or more block devices before the Packer build starts. These are not necessarily preserved when booting from the AMI built with Packer. Seeami_block_device_mappings
, above, for details. -
mfa_code
(string) - The MFA TOTP code. This should probably be a user variable since it changes all the time. -
profile
(string) - The profile to use in the shared credentials file for AWS. See Amazon's documentation on specifying profiles for more details. -
region_kms_key_ids
(map of strings) - a map of regions to copy the ami to, along with the custom kms key id to use for encryption for that region. Keys must match the regions provided inami_regions
. If you just want to encrypt using a default ID, you can stick withkms_key_id
andami_regions
. If you want a region to be encrypted with that region's default key ID, you can use an empty string""
instead of a key id in this map. (e.g."us-east-1": ""
) However, you cannot use default key IDs if you are using this in conjunction withsnapshot_users
-- in that situation you must use custom keys. -
run_tags
(object of key/value strings) - Tags to apply to the instance that is launched to create the AMI. These tags are not applied to the resulting AMI unless they're duplicated intags
. This is a template engine where theSourceAMI
variable is replaced with the source AMI ID andBuildRegion
variable is replaced with the value ofregion
. -
run_volume_tags
(object of key/value strings) - Tags to apply to the volumes that are launched to create the AMI. These tags are not applied to the resulting AMI unless they're duplicated intags
. This is a template engine where theSourceAMI
variable is replaced with the source AMI ID andBuildRegion
variable is replaced with the value ofregion
. -
security_group_id
(string) - The ID (not the name) of the security group to assign to the instance. By default this is not set and Packer will automatically create a new temporary security group to allow SSH access. Note that if this is specified, you must be sure the security group allows access to thessh_port
given below. -
security_group_ids
(array of strings) - A list of security groups as described above. Note that if this is specified, you must omit thesecurity_group_id
. -
temporary_security_group_source_cidr
(string) - An IPv4 CIDR block to be authorized access to the instance, when packer is creating a temporary security group. The default is0.0.0.0/0
(ie, allow any IPv4 source). This is only used whensecurity_group_id
orsecurity_group_ids
is not specified. -
shutdown_behavior
(string) - Automatically terminate instances on shutdown in case Packer exits ungracefully. Possible values are "stop" and "terminate", default isstop
. -
skip_region_validation
(boolean) - Set to true if you want to skip validation of the region configuration option. Defaultfalse
. -
snapshot_groups
(array of strings) - A list of groups that have access to create volumes from the snapshot(s). By default no groups have permission to create volumes from the snapshot(s).all
will make the snapshot publicly accessible. -
snapshot_users
(array of strings) - A list of account IDs that have access to create volumes from the snapshot(s). By default no additional users other than the user creating the AMI has permissions to create volumes from the backing snapshot(s). -
snapshot_tags
(object of key/value strings) - Tags to apply to snapshot. They will override AMI tags if already applied to snapshot. This is a template engine where theSourceAMI
variable is replaced with the source AMI ID andBuildRegion
variable is replaced with the value ofregion
. -
source_ami_filter
(object) - Filters used to populate thesource_ami
field. Example:{ "source_ami_filter": { "filters": { "virtualization-type": "hvm", "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*", "root-device-type": "ebs" }, "owners": ["099720109477"], "most_recent": true } }
This selects the most recent Ubuntu 16.04 HVM EBS AMI from Canonical. NOTE: This will fail unless exactly one AMI is returned. In the above example,
most_recent
will cause this to succeed by selecting the newest image.-
filters
(map of strings) - filters used to select asource_ami
. NOTE: This will fail unless exactly one AMI is returned. Any filter described in the docs for DescribeImages is valid. -
owners
(array of strings) - This scopes the AMIs to certain Amazon account IDs. This is helpful to limit the AMIs to a trusted third party, or to your own account. -
most_recent
(boolean) - Selects the newest created image when true. This is most useful for selecting a daily distro build.
-
-
spot_price
(string) - The maximum hourly price to pay for a spot instance to create the AMI. Spot instances are a type of instance that EC2 starts when the current spot price is less than the maximum price you specify. Spot price will be updated based on available spot instance capacity and current spot instance requests. It may save you some costs. You can set this toauto
for Packer to automatically discover the best spot price or to "0" to use an on demand instance (default). -
spot_price_auto_product
(string) - Required ifspot_price
is set toauto
. This tells Packer what sort of AMI you're launching to find the best spot price. This must be one of:Linux/UNIX
,SUSE Linux
,Windows
,Linux/UNIX (Amazon VPC)
,SUSE Linux (Amazon VPC)
,Windows (Amazon VPC)
-
sriov_support
(boolean) - Enable enhanced networking (SriovNetSupport but not ENA) on HVM-compatible AMIs. If true, addec2:ModifyInstanceAttribute
to your AWS IAM policy. Note: you must make sure enhanced networking is enabled on your instance. See Amazon's documentation on enabling enhanced networking. Defaultfalse
. -
ssh_keypair_name
(string) - If specified, this is the key that will be used for SSH with the machine. The key must match a key pair name loaded up into Amazon EC2. By default, this is blank, and Packer will generate a temporary keypair unlessssh_password
is used.ssh_private_key_file
orssh_agent_auth
must be specified whenssh_keypair_name
is utilized. -
ssh_agent_auth
(boolean) - If true, the local SSH agent will be used to authenticate connections to the source instance. No temporary keypair will be created, and the values ofssh_password
andssh_private_key_file
will be ignored. To use this option with a key pair already configured in the source AMI, leave thessh_keypair_name
blank. To associate an existing key pair in AWS with the source instance, set thessh_keypair_name
field to the name of the key pair. -
ssh_private_ip
(boolean) - Deprecated usessh_interface
instead. Iftrue
, then SSH will always use the private IP if available. Also works for WinRM. -
ssh_interface
(string) - One ofpublic_ip
,private_ip
,public_dns
orprivate_dns
. If set, either the public IP address, private IP address, public DNS name or private DNS name will used as the host for SSH. The default behaviour if inside a VPC is to use the public IP address if available, otherwise the private IP address will be used. If not in a VPC the public DNS name will be used.Where Packer is configured for an outbound proxy but WinRM traffic should be direct
ssh_interface
must be set toprivate_dns
and<region>.compute.internal
included in theNO_PROXY
environment variable. -
subnet_id
(string) - If using VPC, the ID of the subnet, such assubnet-12345def
, where Packer will launch the EC2 instance. This field is required if you are using an non-default VPC. -
tags
(object of key/value strings) - Tags applied to the AMI and relevant snapshots. This is a template engine where theSourceAMI
variable is replaced with the source AMI ID andBuildRegion
variable is replaced with the value ofregion
. -
temporary_key_pair_name
(string) - The name of the temporary key pair to generate. By default, Packer generates a name that looks likepacker_<UUID>
, where <UUID> is a 36 character unique identifier. -
token
(string) - The access token to use. This is different from the access key and secret key. If you're not sure what this is, then you probably don't need it. This will also be read from theAWS_SESSION_TOKEN
environmental variable. -
user_data
(string) - User data to apply when launching the instance. Note that you need to be careful about escaping characters due to the templates being JSON. It is often more convenient to useuser_data_file
, instead. -
user_data_file
(string) - Path to a file that will be used for the user data when launching the instance. -
vpc_id
(string) - If launching into a VPC subnet, Packer needs the VPC ID in order to create a temporary security group within the VPC. Requiressubnet_id
to be set. If this field is left blank, Packer will try to get the VPC ID from thesubnet_id
. -
windows_password_timeout
(string) - The timeout for waiting for a Windows password for Windows instances. Defaults to 20 minutes. Example value:10m
Basic Example
Here is a basic example. You will need to provide access keys, and may need to change the AMI IDs according to what images exist at the time the template is run:
{
"type": "amazon-ebs",
"access_key": "YOUR KEY HERE",
"secret_key": "YOUR SECRET KEY HERE",
"region": "us-east-1",
"source_ami": "ami-fce3c696",
"instance_type": "t2.micro",
"ssh_username": "ubuntu",
"ami_name": "packer-quick-start {{timestamp}}"
}
-> Note: Packer can also read the access key and secret access key from environmental variables. See the configuration reference in the section above for more information on what environmental variables Packer will look for.
Further information on locating AMI IDs and their relationship to instance types and regions can be found in the AWS EC2 Documentation for Linux or for Windows.
Accessing the Instance to Debug
If you need to access the instance to debug for some reason, run the builder
with the -debug
flag. In debug mode, the Amazon builder will save the private
key in the current directory and will output the DNS or IP information as well.
You can use this information to access the instance as it is running.
AMI Block Device Mappings Example
Here is an example using the optional AMI block device mappings. Our
configuration of launch_block_device_mappings
will expand the root volume
(/dev/sda
) to 40gb during the build (up from the default of 8gb). With
ami_block_device_mappings
AWS will attach additional volumes /dev/sdb
and
/dev/sdc
when we boot a new instance of our AMI.
{
"type": "amazon-ebs",
"access_key": "YOUR KEY HERE",
"secret_key": "YOUR SECRET KEY HERE",
"region": "us-east-1",
"source_ami": "ami-fce3c696",
"instance_type": "t2.micro",
"ssh_username": "ubuntu",
"ami_name": "packer-quick-start {{timestamp}}",
"launch_block_device_mappings": [
{
"device_name": "/dev/sda1",
"volume_size": 40,
"volume_type": "gp2",
"delete_on_termination": true
}
],
"ami_block_device_mappings": [
{
"device_name": "/dev/sdb",
"virtual_name": "ephemeral0"
},
{
"device_name": "/dev/sdc",
"virtual_name": "ephemeral1"
}
]
}
Tag Example
Here is an example using the optional AMI tags. This will add the tags
OS_Version
and Release
to the finished AMI. As before, you will need to
provide your access keys, and may need to change the source AMI ID based on what
images exist when this template is run:
{
"type": "amazon-ebs",
"access_key": "YOUR KEY HERE",
"secret_key": "YOUR SECRET KEY HERE",
"region": "us-east-1",
"source_ami": "ami-fce3c696",
"instance_type": "t2.micro",
"ssh_username": "ubuntu",
"ami_name": "packer-quick-start {{timestamp}}",
"tags": {
"OS_Version": "Ubuntu",
"Release": "Latest"
}
}
-> Note: Packer uses pre-built AMIs as the source for building images.
These source AMIs may include volumes that are not flagged to be destroyed on
termination of the instance building the new image. Packer will attempt to clean
up all residual volumes that are not designated by the user to remain after
termination. If you need to preserve those source volumes, you can overwrite the
termination setting by specifying delete_on_termination=false
in the
launch_block_device_mappings
block for the device.