2014-07-23 23:41:48 +02:00
|
|
|
---
|
|
|
|
layout: "aws"
|
|
|
|
page_title: "AWS: aws_instance"
|
|
|
|
sidebar_current: "docs-aws-resource-instance"
|
2014-10-22 05:21:56 +02:00
|
|
|
description: |-
|
|
|
|
Provides an EC2 instance resource. This allows instances to be created, updated, and deleted. Instances also support provisioning.
|
2014-07-23 23:41:48 +02:00
|
|
|
---
|
|
|
|
|
|
|
|
# aws\_instance
|
|
|
|
|
|
|
|
Provides an EC2 instance resource. This allows instances to be created, updated,
|
|
|
|
and deleted. Instances also support [provisioning](/docs/provisioners/index.html).
|
|
|
|
|
|
|
|
## Example Usage
|
|
|
|
|
|
|
|
```
|
2015-02-24 18:00:22 +01:00
|
|
|
# Create a new instance of the ami-1234 on an m1.small node
|
|
|
|
# with an AWS Tag naming it "HelloWorld"
|
2014-10-13 22:55:59 +02:00
|
|
|
resource "aws_instance" "web" {
|
|
|
|
ami = "ami-1234"
|
|
|
|
instance_type = "m1.small"
|
|
|
|
tags {
|
|
|
|
Name = "HelloWorld"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
2014-07-23 23:41:48 +02:00
|
|
|
## Argument Reference
|
|
|
|
|
|
|
|
The following arguments are supported:
|
|
|
|
|
|
|
|
* `ami` - (Required) The AMI to use for the instance.
|
|
|
|
* `availability_zone` - (Optional) The AZ to start the instance in.
|
2014-09-08 01:03:48 +02:00
|
|
|
* `ebs_optimized` - (Optional) If true, the launched EC2 instance will be
|
|
|
|
EBS-optimized.
|
2014-07-23 23:41:48 +02:00
|
|
|
* `instance_type` - (Required) The type of instance to start
|
|
|
|
* `key_name` - (Optional) The key name to use for the instance.
|
2015-01-14 18:28:25 +01:00
|
|
|
* `security_groups` - (Optional) A list of security group IDs or names to associate with.
|
2015-01-07 12:52:20 +01:00
|
|
|
If you are within a non-default VPC, you'll need to use the security group ID. Otherwise,
|
|
|
|
for EC2 and the default VPC, use the security group name.
|
2014-07-23 23:41:48 +02:00
|
|
|
* `subnet_id` - (Optional) The VPC Subnet ID to launch in.
|
2014-07-29 14:12:43 +02:00
|
|
|
* `associate_public_ip_address` - (Optional) Associate a public ip address with an instance in a VPC.
|
2014-09-01 10:06:39 +02:00
|
|
|
* `private_ip` - (Optional) Private IP address to associate with the
|
2014-08-22 02:17:50 +02:00
|
|
|
instance in a VPC.
|
2014-07-23 23:41:48 +02:00
|
|
|
* `source_dest_check` - (Optional) Controls if traffic is routed to the instance when
|
2014-09-16 13:40:16 +02:00
|
|
|
the destination address does not match the instance. Used for NAT or VPNs. Defaults true.
|
2014-07-23 23:41:48 +02:00
|
|
|
* `user_data` - (Optional) The user data to provide when launching the instance.
|
2014-09-23 20:06:30 +02:00
|
|
|
* `iam_instance_profile` - (Optional) The IAM Instance Profile to
|
|
|
|
launch the instance with.
|
2014-10-13 22:55:59 +02:00
|
|
|
* `tags` - (Optional) A mapping of tags to assign to the resource.
|
providers/aws: add root_block_device to aws_instance
AWS provides a single `BlockDeviceMapping` to manage three different
kinds of block devices:
(a) The root volume
(b) Ephemeral storage
(c) Additional EBS volumes
Each of these types has slightly different semantics [1].
(a) The root volume is defined by the AMI; it can only be customized
with `volume_size`, `volume_type`, and `delete_on_termination`.
(b) Ephemeral storage is made available based on instance type [2]. It's
attached automatically if _no_ block device mappings are specified, and
must otherwise be defined with block device mapping entries that contain
only DeviceName set to a device like "/dev/sdX" and VirtualName set to
"ephemeralN".
(c) Additional EBS volumes are controlled by mappings that omit
`virtual_name` and can specify `volume_size`, `volume_type`,
`delete_on_termination`, `snapshot_id`, and `encryption`.
After deciding to ignore root block devices to fix #859, we had users
with configurations that were attempting to manage the root block device chime
in on #913.
Terraform does not have the primitives to be able to properly handle a
single collection of resources that is partially managed and partially
computed, so our strategy here is to break out logical sub-resources for
Terraform and hide the BlockDeviceMapping inside the provider
implementation.
Now (a) is supported by the `root_block_device` sub-resource, and (b)
and (c) are still both merged together under `block_device`, though I
have yet to see ephemeral block devices working properly.
Looking into possibly separating out `ephemeral_block_device` and
`ebs_block_device` sub-resources as well, which seem like the logical
next step. We'll wait until the next big release for this, though, since
it will break backcompat.
[1] http://bit.ly/ec2bdmap
[2] http://bit.ly/instancestorebytype
Fixes #913
Refs #858
2015-02-18 18:45:30 +01:00
|
|
|
* `root_block_device` - (Optional) Customize details about the root block
|
2015-02-24 18:00:22 +01:00
|
|
|
device of the instance. See [Block Devices](#block-devices) below for details.
|
|
|
|
* `ebs_block_device` - (Optional) Additional EBS block devices to attach to the
|
|
|
|
instance. See [Block Devices](#block-devices) below for details.
|
|
|
|
* `ephemeral_block_device` - (Optional) Customize Ephemeral (also known as
|
|
|
|
"Instance Store") volumes on the instance. See [Block Devices](#block-devices) below for details.
|
2014-11-20 00:59:29 +01:00
|
|
|
|
|
|
|
|
2015-02-24 18:00:22 +01:00
|
|
|
<a id="block-devices"></a>
|
|
|
|
## Block devices
|
|
|
|
|
|
|
|
Each of the `*_block_device` attributes controls a portion of the AWS
|
|
|
|
Instance's "Block Device Mapping". It's a good idea to familiarize yourself with [AWS's Block Device
|
|
|
|
Mapping docs](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html)
|
|
|
|
to understand the implications of using these attributes.
|
2014-07-23 23:41:48 +02:00
|
|
|
|
providers/aws: add root_block_device to aws_instance
AWS provides a single `BlockDeviceMapping` to manage three different
kinds of block devices:
(a) The root volume
(b) Ephemeral storage
(c) Additional EBS volumes
Each of these types has slightly different semantics [1].
(a) The root volume is defined by the AMI; it can only be customized
with `volume_size`, `volume_type`, and `delete_on_termination`.
(b) Ephemeral storage is made available based on instance type [2]. It's
attached automatically if _no_ block device mappings are specified, and
must otherwise be defined with block device mapping entries that contain
only DeviceName set to a device like "/dev/sdX" and VirtualName set to
"ephemeralN".
(c) Additional EBS volumes are controlled by mappings that omit
`virtual_name` and can specify `volume_size`, `volume_type`,
`delete_on_termination`, `snapshot_id`, and `encryption`.
After deciding to ignore root block devices to fix #859, we had users
with configurations that were attempting to manage the root block device chime
in on #913.
Terraform does not have the primitives to be able to properly handle a
single collection of resources that is partially managed and partially
computed, so our strategy here is to break out logical sub-resources for
Terraform and hide the BlockDeviceMapping inside the provider
implementation.
Now (a) is supported by the `root_block_device` sub-resource, and (b)
and (c) are still both merged together under `block_device`, though I
have yet to see ephemeral block devices working properly.
Looking into possibly separating out `ephemeral_block_device` and
`ebs_block_device` sub-resources as well, which seem like the logical
next step. We'll wait until the next big release for this, though, since
it will break backcompat.
[1] http://bit.ly/ec2bdmap
[2] http://bit.ly/instancestorebytype
Fixes #913
Refs #858
2015-02-18 18:45:30 +01:00
|
|
|
The `root_block_device` mapping supports the following:
|
|
|
|
|
2015-02-24 18:00:22 +01:00
|
|
|
* `volume_type` - (Optional) The type of volume. Can be `"standard"`, `"gp2"`,
|
|
|
|
or `"io1"`. (Default: `"standard"`).
|
providers/aws: add root_block_device to aws_instance
AWS provides a single `BlockDeviceMapping` to manage three different
kinds of block devices:
(a) The root volume
(b) Ephemeral storage
(c) Additional EBS volumes
Each of these types has slightly different semantics [1].
(a) The root volume is defined by the AMI; it can only be customized
with `volume_size`, `volume_type`, and `delete_on_termination`.
(b) Ephemeral storage is made available based on instance type [2]. It's
attached automatically if _no_ block device mappings are specified, and
must otherwise be defined with block device mapping entries that contain
only DeviceName set to a device like "/dev/sdX" and VirtualName set to
"ephemeralN".
(c) Additional EBS volumes are controlled by mappings that omit
`virtual_name` and can specify `volume_size`, `volume_type`,
`delete_on_termination`, `snapshot_id`, and `encryption`.
After deciding to ignore root block devices to fix #859, we had users
with configurations that were attempting to manage the root block device chime
in on #913.
Terraform does not have the primitives to be able to properly handle a
single collection of resources that is partially managed and partially
computed, so our strategy here is to break out logical sub-resources for
Terraform and hide the BlockDeviceMapping inside the provider
implementation.
Now (a) is supported by the `root_block_device` sub-resource, and (b)
and (c) are still both merged together under `block_device`, though I
have yet to see ephemeral block devices working properly.
Looking into possibly separating out `ephemeral_block_device` and
`ebs_block_device` sub-resources as well, which seem like the logical
next step. We'll wait until the next big release for this, though, since
it will break backcompat.
[1] http://bit.ly/ec2bdmap
[2] http://bit.ly/instancestorebytype
Fixes #913
Refs #858
2015-02-18 18:45:30 +01:00
|
|
|
* `volume_size` - (Optional) The size of the volume in gigabytes.
|
2015-02-24 18:00:22 +01:00
|
|
|
* `iops` - (Optional) The amount of provisioned
|
|
|
|
[IOPS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-io-characteristics.html).
|
|
|
|
This must be set with a `volume_type` of `"io1"`.
|
|
|
|
* `delete_on_termination` - (Optional) Whether the volume should be destroyed
|
|
|
|
on instance termination (Default: `true`).
|
|
|
|
|
|
|
|
Modifying any of the `root_block_device` settings requires resource
|
|
|
|
replacement.
|
|
|
|
|
|
|
|
Each `ebs_block_device` supports the following:
|
|
|
|
|
|
|
|
* `device_name` - The name of the device to mount.
|
|
|
|
* `snapshot_id` - (Optional) The Snapshot ID to mount.
|
|
|
|
* `volume_type` - (Optional) The type of volume. Can be `"standard"`, `"gp2"`,
|
|
|
|
or `"io1"`. (Default: `"standard"`).
|
|
|
|
* `volume_size` - (Optional) The size of the volume in gigabytes.
|
|
|
|
* `iops` - (Optional) The amount of provisioned
|
|
|
|
[IOPS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-io-characteristics.html).
|
|
|
|
This must be set with a `volume_type` of `"io1"`.
|
|
|
|
* `delete_on_termination` - (Optional) Whether the volume should be destroyed
|
|
|
|
on instance termination (Default: `true`).
|
|
|
|
* `encrypted` - (Optional) Enables [EBS
|
|
|
|
encryption](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html)
|
|
|
|
on the volume (Default: `false`).
|
|
|
|
|
|
|
|
Modifying any `ebs_block_device` currently requires resource replacement.
|
|
|
|
|
|
|
|
Each `ephemeral_block_device` supports the following:
|
|
|
|
|
|
|
|
* `device_name` - The name of the block device to mount on the instance.
|
|
|
|
* `virtual_name` - The [Instance Store Device
|
|
|
|
Name](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html#InstanceStoreDeviceNames)
|
|
|
|
(e.g. `"ephemeral0"`)
|
|
|
|
|
|
|
|
Each AWS Instance type has a different set of Instance Store block devices
|
|
|
|
available for attachment. AWS [publishes a
|
|
|
|
list](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html#StorageOnInstanceTypes)
|
|
|
|
of which ephemeral devices are available on each type. The devices are always
|
|
|
|
identified by the `virtual_name` in the format `"ephemeral{0..N}"`.
|
|
|
|
|
2015-04-08 00:05:00 +02:00
|
|
|
~> **NOTE:** Currently, changes to `*_block_device` configuration of _existing_
|
|
|
|
resources cannot be automatically detected by Terraform. After making updates
|
|
|
|
to block device configuration, resource recreation can be manually triggered by
|
|
|
|
using the [`taint` command](/docs/commands/taint.html).
|
providers/aws: add root_block_device to aws_instance
AWS provides a single `BlockDeviceMapping` to manage three different
kinds of block devices:
(a) The root volume
(b) Ephemeral storage
(c) Additional EBS volumes
Each of these types has slightly different semantics [1].
(a) The root volume is defined by the AMI; it can only be customized
with `volume_size`, `volume_type`, and `delete_on_termination`.
(b) Ephemeral storage is made available based on instance type [2]. It's
attached automatically if _no_ block device mappings are specified, and
must otherwise be defined with block device mapping entries that contain
only DeviceName set to a device like "/dev/sdX" and VirtualName set to
"ephemeralN".
(c) Additional EBS volumes are controlled by mappings that omit
`virtual_name` and can specify `volume_size`, `volume_type`,
`delete_on_termination`, `snapshot_id`, and `encryption`.
After deciding to ignore root block devices to fix #859, we had users
with configurations that were attempting to manage the root block device chime
in on #913.
Terraform does not have the primitives to be able to properly handle a
single collection of resources that is partially managed and partially
computed, so our strategy here is to break out logical sub-resources for
Terraform and hide the BlockDeviceMapping inside the provider
implementation.
Now (a) is supported by the `root_block_device` sub-resource, and (b)
and (c) are still both merged together under `block_device`, though I
have yet to see ephemeral block devices working properly.
Looking into possibly separating out `ephemeral_block_device` and
`ebs_block_device` sub-resources as well, which seem like the logical
next step. We'll wait until the next big release for this, though, since
it will break backcompat.
[1] http://bit.ly/ec2bdmap
[2] http://bit.ly/instancestorebytype
Fixes #913
Refs #858
2015-02-18 18:45:30 +01:00
|
|
|
|
2014-07-23 23:41:48 +02:00
|
|
|
## Attributes Reference
|
|
|
|
|
|
|
|
The following attributes are exported:
|
|
|
|
|
|
|
|
* `id` - The instance ID.
|
|
|
|
* `availability_zone` - The availability zone of the instance.
|
|
|
|
* `key_name` - The key name of the instance
|
|
|
|
* `private_dns` - The Private DNS name of the instance
|
|
|
|
* `private_ip` - The private IP address.
|
|
|
|
* `public_dns` - The public DNS name of the instance
|
|
|
|
* `public_ip` - The public IP address.
|
|
|
|
* `security_groups` - The associated security groups.
|
|
|
|
* `subnet_id` - The VPC subnet ID.
|