AWS Amazon EC2 Attachment

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

aws_network_interface_attachment (Terraform)

The Attachment in Amazon EC2 can be configured in Terraform with the resource name aws_network_interface_attachment. The following sections describe 1 example of how to use the resource and its parameters.

Example Usage from GitHub

middle-ec2-instances.tf#L16
resource "aws_network_interface_attachment" "eni_subnet_03" {
  count                = local.instances_middle_per_subnet
  instance_id          = aws_instance.middle_subnet_0[count.index].id
  network_interface_id = aws_network_interface.eni_subnet_03[count.index].id
  device_index         = 1
}

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

Attach an Elastic network interface (ENI) resource with EC2 instance.

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.

AWS::EC2::NetworkInterfaceAttachment (CloudFormation)

The NetworkInterfaceAttachment in EC2 can be configured in CloudFormation with the resource name AWS::EC2::NetworkInterfaceAttachment. The following sections describe 10 examples of how to use the resource and its parameters.

Example Usage from GitHub

ec2.yml#L77
      Type: AWS::EC2::NetworkInterfaceAttachment
      Properties:
        InstanceId:
          Ref: MyEC2Instance
        NetworkInterfaceId:
          Ref: Eth1
ec2-with-existing-resources.yml#L54
    Type: AWS::EC2::NetworkInterfaceAttachment
    Properties:
      DeviceIndex: 1
      InstanceId: !Ref VM01
      NetworkInterfaceId: !FindInMap [ prd, ServerName, NetworkInterfaceMgrId ]
################################
cloudformation.yml#L389
    Type: AWS::EC2::NetworkInterfaceAttachment
    Properties:
      InstanceId: !Ref PANec2Instance
      NetworkInterfaceId: !Ref PublicENI
      DeviceIndex: 1

CFN.yml#L187
   Type: AWS::EC2::NetworkInterfaceAttachment
   Properties:
       InstanceId:
           Ref: EC2Instance1
       NetworkInterfaceId:
           Ref: Instance1ENI1
e07.yml#L145
    Type: AWS::EC2::NetworkInterfaceAttachment
    Properties:
      DeviceIndex: 1
      InstanceId: !Ref HelloInstance
      NetworkInterfaceId: !Ref HelloEni

AWS-Create-Stack-PaloAlto-bkp.json#L527
      "Type": "AWS::EC2::NetworkInterfaceAttachment",
      "Properties": {
        "DeviceIndex": "3",
        "NetworkInterfaceId": {
          "Ref": "AWSNetworkInterfacePaloAlto3"
        },
AWS-Create-Stack-PaloAlto-bkp.json#L527
      "Type": "AWS::EC2::NetworkInterfaceAttachment",
      "Properties": {
        "DeviceIndex": "3",
        "NetworkInterfaceId": {
          "Ref": "AWSNetworkInterfacePaloAlto3"
        },
vpc-sg-igw-subnet-ec2-rt-config.json#L259
            "Type": "AWS::EC2::NetworkInterfaceAttachment",
            "Properties": {
                "InstanceId": {
                    "Ref": "Ec2Instance"
                },
                "NetworkInterfaceId": {
vpc-sg-igw-subnet-ec2-rt.json#L256
            "Type": "AWS::EC2::NetworkInterfaceAttachment",
            "Properties": {
                "InstanceId": {
                    "Ref": "Ec2Instance"
                },
                "NetworkInterfaceId": {
avaya-aura-template.json#L1227
      "Type" : "AWS::EC2::NetworkInterfaceAttachment",
      "Condition": "SBCSeparateServer",
      "Properties" : {
          "DeleteOnTermination" : "true",
          "DeviceIndex" : "1",
          "InstanceId" : {"Ref" : "EMSInstance"},

Parameters

Explanation in CloudFormation Registry

Attaches an elastic network interface (ENI) to an Amazon EC2 instance. You can use this resource type to attach additional network interfaces to an instance without interruption.

Frequently asked questions

What is AWS Amazon EC2 Attachment?

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

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

For Terraform, the indeni/cloudrail-knowledge source code example is useful. See the Terraform Example section for further details.

For CloudFormation, the libert-xyz/cloudformation-templates, m-oka-system/aws-cloudformation and wpacket/pan-aws-cf source code examples are useful. See the CloudFormation Example section for further details.