AWS Amazon EC2 AMI

This page shows how to write Terraform for Amazon EC2 AMI and write them securely.

aws_ami (Terraform)

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

Example Usage from GitHub

positive.tf#L2
resource "aws_ami" "positive1" {
  name                = "terraform-example"
  virtualization_type = "hvm"
  root_device_name    = "/dev/xvda"

  ebs_block_device {
ebs_block_device_encrypted.tf#L2
resource "aws_ami" "ebs_block_device_encrypted_set_to_true" {
  name = "foo"

  ebs_block_device {
    device_name = "/dev/xvda"
    volume_size = 8
ebs_block_device_encrypted.tf#L11
resource "aws_ami" "ebs_block_device_encrypted_set_to_true" {
  name = "foo"

  ebs_block_device {
    device_name = var.test_device
    volume_size = var.test_volume
positive.tf#L2
resource "aws_ami" "positive1" {
  name                = "terraform-example"
  virtualization_type = "hvm"
  root_device_name    = "/dev/xvda"

  ebs_block_device {
ebs_block_device_encrypted.tf#L2
resource "aws_ami" "ebs_block_device_encrypted_set_to_true" {
  name = "foo"

  ebs_block_device {
    device_name = "/dev/xvda"
    volume_size = 8

Review your Terraform file for AWS best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

Explanation in Terraform Registry

The AMI resource allows the creation and management of a completely-custom Amazon Machine Image (AMI). If you just want to duplicate an existing AMI, possibly copying it to another region, it's better to use aws_ami_copy instead. If you just want to share an existing AMI with another AWS account, it's better to use aws_ami_launch_permission instead.

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.

risk-label

aws_default_vpc

Ensure to avoid using default VPC

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

risk-label

aws_network_acl_rule

Ensure your network ACL rule blocks unwanted inbound traffic

It is better to block unwanted inbound traffic.

risk-label

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).

risk-label

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.

risk-label

aws_security_group

Ensure your security group blocks unwanted inbound traffic

It is better to block unwanted inbound traffic.

Review your AWS Amazon EC2 settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

CloudFormation Example

CloudFormation code does not have the related resource.

Frequently asked questions

What is AWS Amazon EC2 AMI?

AWS Amazon EC2 AMI is a resource for Amazon EC2 of Amazon Web Service. Settings can be wrote in Terraform.

Where can I find the example code for the AWS Amazon EC2 AMI?

For Terraform, the Checkmarx/kics, ffsclyh/config-lint and ffsclyh/config-lint source code examples are useful. See the Terraform Example section for further details.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.