AWS Amazon EC2 From Instance

aws_ami_from_instance (Terraform)

The From Instance in Amazon EC2 can be configured in Terraform with the resource name aws_ami_from_instance. The following sections describe 5 examples of how to use the resource and its parameters.

Example Usage from GitHub

alinuxien/k8s-aws-iac

resource "aws_ami_from_instance" "controller-0-ami" {
  name               = "controller-0-ami"
  source_instance_id = aws_instance.controller-0.id
  depends_on         = [null_resource.dns-server-config]
}

rubenivanyan/epam_final_project

resource "aws_ami_from_instance" "example1" {
  name               = "serviceone"
  source_instance_id = aws_instance.ServiceOne.id
  depends_on         = [null_resource.ansibleservices]
}
#Create Image form ServiceTwo installed host

rachel-yoon59/codeherent-test-2

resource "aws_ami_from_instance" "ami_from_instance" {
  name =
  source_instance_id =
}

resource "aws_ami_from_instance" "ami_from_instance1" {

ronnie420/terraform-deployment-scripts

resource "aws_ami_from_instance" "payments_sd_cac_clone" {
  name               = "payments_sd_cac_clone_20191112"
  source_instance_id = "i-043dec12552c0a948"
  snapshot_without_reboot = true
 tags = {
    Name = "payments_sd_cac_clone_20191112"

adilogishetty/AWS-DevOps

resource "aws_ami_from_instance" "example" {
  name               = "ami2"
  source_instance_id = "i-0659f71"
}

Parameters

• architecture optional computed - string
• arn optional computed - string
• description optional - string
• ena_support optional computed - bool
• hypervisor optional computed - string
• id optional computed - string
• image_location optional computed - string
• image_owner_alias optional computed - string
• image_type optional computed - string
• kernel_id optional computed - string
• manage_ebs_snapshots optional computed - bool
• name required - string
• owner_id optional computed - string
• platform optional computed - string
• platform_details optional computed - string
• public optional computed - bool
• ramdisk_id optional computed - string
• root_device_name optional computed - string
• root_snapshot_id optional computed - string
• snapshot_without_reboot optional - bool
• source_instance_id required - string
• sriov_net_support optional computed - string
• tags optional - map from string to string
• usage_operation optional computed - string
• virtualization_type optional computed - string
• ebs_block_device set block
  • delete_on_termination optional computed - bool
  • device_name optional computed - string
  • encrypted optional computed - bool
  • iops optional computed - number
  • snapshot_id optional computed - string
  • throughput optional computed - number
  • volume_size optional computed - number
  • volume_type optional computed - string
• ephemeral_block_device set block
  • device_name optional computed - string
  • virtual_name optional computed - string
• timeouts single block
  • create optional - string
  • delete optional - string
  • update optional - string

Explanation in Terraform Registry

The "AMI from instance" resource allows the creation of an Amazon Machine Image (AMI) modelled after an existing EBS-backed EC2 instance. The created AMI will refer to implicitly-created snapshots of the instance's EBS volumes and mimick its assigned block device configuration at the time the resource is created. This resource is best applied to an instance that is stopped when this instance is created, so that the contents of the created image are predictable. When applied to an instance that is running, the instance will be stopped before taking the snapshots and then started back up again, resulting in a period of downtime. Note that the source instance is inspected only at the initial creation of this resource. Ongoing updates to the referenced instance will not be propagated into the generated AMI. Users may taint or otherwise recreate the resource in order to produce a fresh snapshot.

Tips: Best Practices for The Other AWS Amazon EC2 Resources

In addition to the aws_default_vpc, AWS Amazon EC2 has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.

aws_default_vpc

Ensure to avoid using default VPC

It is better to define the own VPC and use it.

aws_network_acl_rule

Ensure your network ACL rule blocks unwanted inbound traffic

It is better to block unwanted inbound traffic.

aws_ebs_volume

Ensure to use a customer-managed key for EBS volume encryption

It is better to use a customer-managed key for EBS volume encryption. It can be gain more control over the encryption by using customer-managed keys (CMK).

aws_instance

Ensure to avoid storing AWS access keys in user data

It is better to avoid storing AWS access keys in user data. `aws_iam_instance_profile` could be used instead.

aws_security_group

Ensure your security group blocks unwanted inbound traffic

It is better to block unwanted inbound traffic.