id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
7f7cbb4076df-1 | ```
aws ec2 describe-instance-credit-specifications --instance-id i-1234567890abcdef0
```
The following is example output:
```
{
"InstanceCreditSpecifications": [
{
"InstanceId": "i-1234567890abcdef0",
"CpuCredits": "unlimited"
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
a59981f59775-0 | You can switch the credit specification of a running or stopped instance at any time between `unlimited` and `standard`\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
6aa6b58c0860-0 | **To modify the credit specification of a burstable performance instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the left navigation pane, choose **Instances**\.
1. Select the instance\. To modify the credit specification for several instances at one time, select all applicable instances\.
1. Choose **Actions**, **Instance settings**, **Change credit specification**\. This option is enabled only if you selected a burstable performance instance\.
1. To change the credit specification to `unlimited`, select the check box next to the instance ID\. To change the credit specification to `standard`, clear the check box next to the instance ID\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
ca2eaf066f29-0 | **To modify the credit specification of a burstable performance instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the left navigation pane, choose **Instances**\.
1. Select the instance\. To modify the credit specification for several instances at one time, select all applicable instances\.
1. Choose **Actions**, **Instance Settings**, **Change T2/T3 Unlimited**\. This option is enabled only if you selected a burstable performance instance\.
1. The current credit specification appears in parentheses after the instance ID\. To change the credit specification to `unlimited`, choose **Enable**\. To change the credit specification to `standard`, choose **Disable**\.
------
**To modify the credit specification of a burstable performance instance \(AWS CLI\)**
Use the [modify\-instance\-credit\-specification](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-credit-specification.html) command\. Specify the instance and its credit specification using the `--instance-credit-specification` parameter\. Valid credit specifications are `unlimited` and `standard`\.
**Example**
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
ca2eaf066f29-1 | **Example**
```
aws ec2 modify-instance-credit-specification --region us-east-1 --instance-credit-specification "InstanceId=i-1234567890abcdef0,CpuCredits=unlimited"
```
The following is example output:
```
{
"SuccessfulInstanceCreditSpecifications": [
{
"InstanceId": "i- 1234567890abcdef0"
}
],
"UnsuccessfulInstanceCreditSpecifications": []
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
f51be9531d5d-0 | You can set the default credit specification at the account level per AWS Region\. You specify the default credit specification per instance family \(for example, T2 or T3\)\.
If you use the Launch Instance Wizard in the AWS Management Console to launch instances, the value you select for the credit specification overrides the account\-level default credit specification\. If you use the AWS CLI to launch instances, all new burstable performance instances in the account launch using the default credit option\. The credit specification for existing running or stopped instances is not affected\.
The `modify-default-credit-specification` API is an asynchronous operation, which works at an AWS Region level and modifies the credit option for each Availability Zone\. All zones in a Region are updated within five minutes\. But if instances are launched during this operation, they might not get the new credit option until the zone is updated\. To verify whether the update has occurred, you can call `get-default-credit-specification` and check the default credit specification for updates\. For more information, see [Viewing the default credit specification](#burstable-performance-instances-get-default-credit-specification)\.
**Consideration**
The default credit specification for an instance family can be modified only once in a rolling 5\-minute period, and up to four times in a rolling 24\-hour period\.
**To set the default credit specification at the account level \(AWS CLI\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
f51be9531d5d-1 | **To set the default credit specification at the account level \(AWS CLI\)**
Use the [modify\-default\-credit\-specification](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-default-credit-specification.html) command\. Specify the AWS Region, instance family, and the default credit specification using the `--cpu-credits` parameter\. Valid default credit specifications are `unlimited` and `standard`\.
```
aws ec2 modify-default-credit-specification --region us-east-1 --instance-family t2 --cpu-credits unlimited
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
86f5e7e00df1-0 | You can view the default credit specification of a burstable performance instance family at the account level per AWS Region\.
**To view the default credit specification at the account level \(AWS CLI\)**
Use the [get\-default\-credit\-specification](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-default-credit-specification.html) command\. Specify the AWS Region and instance family\.
```
aws ec2 get-default-credit-specification --region us-east-1 --instance-family t2
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-how-to.md |
67c6e5f3b69e-0 | AMIs that are backed by Amazon EBS snapshots can take advantage of Amazon EBS encryption\. Snapshots of both data and root volumes can be encrypted and attached to an AMI\. You can launch instances and copy images with full EBS encryption support included\. Encryption parameters for these operations are supported in all Regions where AWS KMS is available\.
EC2 instances with encrypted EBS volumes are launched from AMIs in the same way as other instances\. In addition, when you launch an instance from an AMI backed by unencrypted EBS snapshots, you can encrypt some or all of the volumes during launch\.
Like EBS volumes, snapshots in AMIs can be encrypted by either your default AWS Key Management Service customer master key \(CMK\), or to a customer managed key that you specify\. You must in all cases have permission to use the selected key\.
AMIs with encrypted snapshots can be shared across AWS accounts\. For more information, see [Shared AMIs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharing-amis.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
50a0f28155a8-0 | Amazon EC2 instances are launched from AMIs using the `RunInstances` action with parameters supplied through block device mapping, either by means of the AWS Management Console or directly using the Amazon EC2 API or CLI\. For more information about block device mapping, see [Block device mapping](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/block-device-mapping-concepts.html)\. For examples of controlling block device mapping from the AWS CLI, see [Launch, List, and Terminate EC2 Instances](https://docs.aws.amazon.com/cli/latest/userguide/cli-services-ec2-instances.html)\.
By default, without explicit encryption parameters, a `RunInstances` action maintains the existing encryption state of an AMI's source snapshots while restoring EBS volumes from them\. If [Encryption by default](EBSEncryption.md#encryption-by-default) is enabled, all volumes created from the AMI \(whether from encrypted or unencrypted snapshots\) will be encrypted\. If encryption by default is not enabled, then the instance maintains the encryption state of the AMI\.
You can also launch an instance and simultaneously apply a new encryption state to the resulting volumes by supplying encryption parameters\. Consequently, the following behaviors are observed:
**Launch with no encryption parameters**
+ An unencrypted snapshot is restored to an unencrypted volume, unless encryption by default is enabled, in which case all the newly created volumes will be encrypted\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
50a0f28155a8-1 | + An encrypted snapshot that you own is restored to a volume that is encrypted to the same CMK\.
+ An encrypted snapshot that you do not own \(for example, the AMI is shared with you\) is restored to a volume that is encrypted by your AWS account's default CMK\.
The default behaviors can be overridden by supplying encryption parameters\. The available parameters are `Encrypted` and `KmsKeyId`\. Setting only the `Encrypted` parameter results in the following:
**Instance launch behaviors with `Encrypted` set, but no `KmsKeyId` specified**
+ An unencrypted snapshot is restored to an EBS volume that is encrypted by your AWS account's default CMK\.
+ An encrypted snapshot that you own is restored to an EBS volume encrypted by the same CMK\. \(In other words, the `Encrypted` parameter has no effect\.\)
+ An encrypted snapshot that you do not own \(i\.e\., the AMI is shared with you\) is restored to a volume that is encrypted by your AWS account's default CMK\. \(In other words, the `Encrypted` parameter has no effect\.\)
Setting both the `Encrypted` and `KmsKeyId` parameters allows you to specify a non\-default CMK for an encryption operation\. The following behaviors result: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
50a0f28155a8-2 | **Instance with both `Encrypted` and `KmsKeyId` set**
+ An unencrypted snapshot is restored to an EBS volume encrypted by the specified CMK\.
+ An encrypted snapshot is restored to an EBS volume encrypted not to the original CMK, but instead to the specified CMK\.
Submitting a `KmsKeyId` without also setting the `Encrypted` parameter results in an error\.
The following sections provide examples of launching instances from AMIs using non\-default encryption parameters\. In each of these scenarios, parameters supplied to the `RunInstances` action result in a change of encryption state during restoration of a volume from a snapshot\.
**Note**
For detailed console procedures to launch an instance from an AMI, see [Launch Your Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html)\.
For documentation of the `RunInstances` API, see [RunInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RunInstances.html)\.
For documentation of the `run-instances` command in the AWS Command Line Interface, see [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
077173c5adbd-0 | In this example, an AMI backed by an unencrypted snapshot is used to launch an EC2 instance with an encrypted EBS volume\.
![\[Launch instance and encrypt volume on the fly\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami-launch-convert.png)
The `Encrypted` parameter alone results in the volume for this instance being encrypted\. Providing a `KmsKeyId` parameter is optional\. If no key ID is specified, the AWS account's default CMK is used to encrypt the volume\. To encrypt the volume to a different CMK that you own, supply the `KmsKeyId` parameter\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
f015b4bcef3a-0 | In this example, an AMI backed by an encrypted snapshot is used to launch an EC2 instance with an EBS volume encrypted by a new CMK\.
![\[Launch instance and re-encrypt volume on the fly\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami-launch-encrypted.png)
If you own the AMI and supply no encryption parameters, the resulting instance has a volume encrypted by the same key as the snapshot\. If the AMI is shared rather than owned by you, and you supply no encryption parameters, the volume is encrypted by your default CMK\. With encryption parameters supplied as shown, the volume is encrypted by the specified CMK\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
861693187cb1-0 | In this more complex example, an AMI backed by multiple snapshots \(each with its own encryption state\) is used to launch an EC2 instance with a newly encrypted volume and a re\-encrypted volume\.
![\[Encrypt and re-encrypt multiple volumes during launch\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami-launch-mixed.png)
In this scenario, the `RunInstances` action is supplied with encryption parameters for each of the source snapshots\. When all possible encryption parameters are specified, the resulting instance is the same regardless of whether you own the AMI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
36312d0ece81-0 | Amazon EC2 AMIs are copied using the `CopyImage` action, either through the AWS Management Console or directly using the Amazon EC2 API or CLI\.
By default, without explicit encryption parameters, a `CopyImage` action maintains the existing encryption state of an AMI's source snapshots during copy\. You can also copy an AMI and simultaneously apply a new encryption state to its associated EBS snapshots by supplying encryption parameters\. Consequently, the following behaviors are observed:
**Copy with no encryption parameters**
+ An unencrypted snapshot is copied to another unencrypted snapshot, unless encryption by default is enabled, in which case all the newly created snapshots will be encrypted\.
+ An encrypted snapshot that you own is copied to a snapshot encrypted with the same key\.
+ An encrypted snapshot that you do not own \(that is, the AMI is shared with you\) is copied to a snapshot that is encrypted by your AWS account's default CMK\.
All of these default behaviors can be overridden by supplying encryption parameters\. The available parameters are `Encrypted` and `KmsKeyId`\. Setting only the `Encrypted` parameter results in the following:
**Copy\-image behaviors with `Encrypted` set, but no `KmsKeyId` specified**
+ An unencrypted snapshot is copied to a snapshot encrypted by the AWS account's default CMK\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
36312d0ece81-1 | + An unencrypted snapshot is copied to a snapshot encrypted by the AWS account's default CMK\.
+ An encrypted snapshot is copied to a snapshot encrypted by the same CMK\. \(In other words, the `Encrypted` parameter has no effect\.\)
+ An encrypted snapshot that you do not own \(i\.e\., the AMI is shared with you\) is copied to a volume that is encrypted by your AWS account's default CMK\. \(In other words, the `Encrypted` parameter has no effect\.\)
Setting both the `Encrypted` and `KmsKeyId` parameters allows you to specify a customer managed CMK for an encryption operation\. The following behaviors result:
**Copy\-image behaviors with both `Encrypted` and `KmsKeyId` set**
+ An unencrypted snapshot is copied to a snapshot encrypted by the specified CMK\.
+ An encrypted snapshot is copied to a snapshot encrypted not to the original CMK, but instead to the specified CMK\.
Submitting a `KmsKeyId` without also setting the `Encrypted` parameter results in an error\.
The following section provides an example of copying an AMI using non\-default encryption parameters, resulting in a change of encryption state\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
36312d0ece81-2 | The following section provides an example of copying an AMI using non\-default encryption parameters, resulting in a change of encryption state\.
**Note**
For detailed console procedures to copy an AMI, see [Copying an AMI](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/CopyingAMIs.html)\.
For documentation of the `CopyImage` API, see [CopyImage](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CopyImage.html)\.
For documentation of the command `copy-image` in the AWS Command Line Interface, see [copy\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/copy-image.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
15ea0ba10dd0-0 | In this scenario, an AMI backed by an unencrypted root snapshot is copied to an AMI with an encrypted root snapshot\. The `CopyImage` action is invoked with two encryption parameters, including a CMK\. As a result, the encryption status of the root snapshot changes, so that the target AMI is backed by a root snapshot containing the same data as the source snapshot, but encrypted using the specified key\. You incur storage costs for the snapshots in both AMIs, as well as charges for any instances you launch from either AMI\.
**Note**
Enabling [encryption by default](EBSEncryption.md#encryption-by-default) has the same effect as setting the `Encrypted` parameter to `true` for all snapshots in the AMI\.
![\[Copy AMI and encrypt snapshot on the fly\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami-to-ami-convert.png)
Setting the `Encrypted` parameter encrypts the single snapshot for this instance\. If you do not specify the `KmsKeyId` parameter, the default CMK is used to encrypt the snapshot copy\.
**Note**
You can also copy an image with multiple snapshots and configure the encryption state of each individually\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIEncryption.md |
12363757fd93-0 | You can use the following methods to troubleshoot an unreachable instance\.
**Topics**
+ [Instance reboot](#instance-console-rebooting)
+ [Instance console output](#instance-console-console-output)
+ [Capture a screenshot of an unreachable instance](#instance-console-screenshot)
+ [Instance recovery when a host computer fails](#instance-machine-failure) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-console.md |
cc8aa7f52802-0 | The ability to reboot instances that are otherwise unreachable is valuable for both troubleshooting and general instance management\.
Just as you can reset a computer by pressing the reset button, you can reset EC2 instances using the Amazon EC2 console, CLI, or API\. For more information, see [Reboot your instance](ec2-instance-reboot.md)\.
**Warning**
For Windows instances, this operation performs a hard reboot that might result in data corruption\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-console.md |
e59e83867ba6-0 | Console output is a valuable tool for problem diagnosis\. It is especially useful for troubleshooting kernel problems and service configuration issues that could cause an instance to terminate or become unreachable before its SSH daemon can be started\.
For Linux/Unix, the instance console output displays the exact console output that would normally be displayed on a physical monitor attached to a computer\. The console output returns buffered information that was posted shortly after an instance transition state \(start, stop, reboot, and terminate\)\. The posted output is not continuously updated; only when it is likely to be of the most value\.
For Windows instances, the instance console output includes the last three system event log errors\.
You can optionally retrieve the latest serial console output at any time during the instance lifecycle\. This option is only supported on [Instances built on the Nitro System](instance-types.md#ec2-nitro-instances)\. It is not supported through the Amazon EC2 console\.
**Note**
Only the most recent 64 KB of posted output is stored, which is available for at least 1 hour after the last posting\.
Only the instance owner can access the console output\. You can retrieve the console output for your instances using the console or the command line\.
**To get console output using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the left navigation pane, choose **Instances**, and select the instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-console.md |
e59e83867ba6-1 | 1. In the left navigation pane, choose **Instances**, and select the instance\.
1. Choose **Actions**, **Instance Settings**, **Get System Log**\.
**To get console output using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [get\-console\-output](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-console-output.html) \(AWS CLI\)
+ [Get\-EC2ConsoleOutput](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ConsoleOutput.html) \(AWS Tools for Windows PowerShell\)
For more information about common system log errors, see [Troubleshooting system log errors for Linux\-based instances](TroubleshootingInstances.md#system-log-errors-linux)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-console.md |
879b0c3980b0-0 | If you are unable to reach your instance via SSH or RDP, you can capture a screenshot of your instance and view it as an image\. The image can provide visibility as to the status of the instance, and allows for quicker troubleshooting\. You can generate screenshots while the instance is running or after it has crashed\. There is no data transfer cost for this screenshot\. The image is generated in JPG format and is no larger than 100 kb\. This feature is not supported when the instance is using an NVIDIA GRID driver, is on bare metal instances \(instances of type `*.metal`\), or is powered by Arm\-based Graviton or Graviton 2 processors\. This feature is available in the following Regions:
+ US East \(N\. Virginia\) Region
+ US East \(Ohio\) Region
+ US West \(Oregon\) Region
+ US West \(N\. California\) Region
+ Europe \(Ireland\) Region
+ Europe \(Frankfurt\) Region
+ Asia Pacific \(Tokyo\) Region
+ Asia Pacific \(Seoul\) Region
+ Asia Pacific \(Singapore\) Region
+ Asia Pacific \(Sydney\) Region\)
+ South America \(São Paulo\) Region\)
+ Asia Pacific \(Mumbai\) Region
+ Canada \(Central\) Region\)
+ Europe \(London\) Region
+ Europe \(Paris\) Region
**To access the instance console** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-console.md |
879b0c3980b0-1 | + Europe \(London\) Region
+ Europe \(Paris\) Region
**To access the instance console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the left navigation pane, choose **Instances**\.
1. Select the instance to capture\.
1. Choose **Actions**, **Instance Settings**\.
1. Choose **Get Instance Screenshot**\.
Right\-click on the image to download and save it\.
**To capture a screenshot using the command line**
You can use one of the following commands\. The returned content is base64\-encoded\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [get\-console\-screenshot](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-console-screenshot.html) \(AWS CLI\)
+ [GetConsoleScreenshot](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-GetConsoleScreenshot.html) \(Amazon EC2 Query API\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-console.md |
f9a90da4c0c4-0 | If there is an unrecoverable issue with the hardware of an underlying host computer, AWS may schedule an instance stop event\. You are notified of such an event ahead of time by email\.
**To recover an Amazon EBS\-backed instance running on a host computer that failed**
1. Back up any important data on your instance store volumes to Amazon EBS or Amazon S3\.
1. Stop the instance\.
1. Start the instance\.
1. Restore any important data\.
For more information, see [Stop and start your instance](Stop_Start.md)\.
**To recover an instance store\-backed instance running on a host computer that failed**
1. Create an AMI from the instance\.
1. Upload the image to Amazon S3\.
1. Back up important data to Amazon EBS or Amazon S3\.
1. Terminate the instance\.
1. Launch a new instance from the AMI\.
1. Restore any important data to the new instance\.
For more information, see [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-console.md |
ee3588d8a4b4-0 | Idempotency ensures that an API request completes only once\. With an idempotent request, if the original request completes successfully\. The subsequent retries return the result from the original successful request and they have no additional effect\.
The [ StartSnapshot](https://docs.aws.amazon.com/ebs/latest/APIReference/API_StartSnapshot.html) API supports idempotency using a *client token*\. A client token is a unique string that you specify when you make an API request\. If you retry an API request with the same client token and the same request parameters after it has completed successfully, the result of the original request is returned\. If you retry a request with the same client token, but change one or more of the request parameters, the `ConflictException` error is returned\.
If you do not specify your own client token, the AWS SDKs automatically generates a client token for the request to ensure that it is idempotent\.
A client token can be any string that includes up to up to 64 ASCII characters\. You should not reuse the same client tokens for different requests\.
**To make an idempotent StartSnapshot request with your own client token using the API**
Specify the `ClientToken` request parameter\.
```
POST /snapshots HTTP/1.1
Host: ebs.us-east-2.amazonaws.com
Accept-Encoding: identity
User-Agent: <User agent parameter>
X-Amz-Date: 20200618T040724Z | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-direct-api-idempotency.md |
ee3588d8a4b4-1 | User-Agent: <User agent parameter>
X-Amz-Date: 20200618T040724Z
Authorization: <Authentication parameter>
{
"VolumeSize": 8,
"ParentSnapshot": snap-123EXAMPLE1234567,
"ClientToken": "550e8400-e29b-41d4-a716-446655440000",
"Timeout": 60
}
```
**To make an idempotent StartSnapshot request with your own client token using the AWS CLI**
Specify the `client-token` request parameter\.
```
$ aws ebs start-snapshot --region us-east-2 --volume-size 8 --parent-snapshot snap-123EXAMPLE1234567 --timeout 60 --client-token 550e8400-e29b-41d4-a716-446655440000
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-direct-api-idempotency.md |
f030212c1290-0 | An *elastic network interface* is a logical networking component in a VPC that represents a virtual network card\. It can include the following attributes:
+ A primary private IPv4 address from the IPv4 address range of your VPC
+ One or more secondary private IPv4 addresses from the IPv4 address range of your VPC
+ One Elastic IP address \(IPv4\) per private IPv4 address
+ One public IPv4 address
+ One or more IPv6 addresses
+ One or more security groups
+ A MAC address
+ A source/destination check flag
+ A description
You can create and configure network interfaces in your account and attach them to instances in your VPC\. Your account might also have *requester\-managed* network interfaces, which are created and managed by AWS services to enable you to use other resources and services\. You cannot manage these network interfaces yourself\. For more information, see [Requester\-managed network interfaces](requester-managed-eni.md)\.
This AWS resource is referred to as a *network interface* in the AWS Management Console and the Amazon EC2 API\. Therefore, we use "network interface" in this documentation instead of "elastic network interface"\. The term "network interface" in this documentation always means "elastic network interface"\.
**Topics**
+ [Network interface basics](#eni-basics)
+ [IP addresses per network interface per instance type](#AvailableIpPerENI)
+ [Scenarios for network interfaces](#scenarios-enis) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
f030212c1290-1 | + [IP addresses per network interface per instance type](#AvailableIpPerENI)
+ [Scenarios for network interfaces](#scenarios-enis)
+ [Best practices for configuring network interfaces](#best-practices-for-configuring-network-interfaces)
+ [Working with network interfaces](#working-with-enis)
+ [Requester\-managed network interfaces](requester-managed-eni.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
fd6086077397-0 | You can create a network interface, attach it to an instance, detach it from an instance, and attach it to another instance\. The attributes of a network interface follow it as it's attached or detached from an instance and reattached to another instance\. When you move a network interface from one instance to another, network traffic is redirected to the new instance\.
You can also modify the attributes of your network interface, including changing its security groups and managing its IP addresses\.
Every instance in a VPC has a default network interface, called the *primary network interface*\. You cannot detach a primary network interface from an instance\. You can create and attach additional network interfaces\. The maximum number of network interfaces that you can use varies by instance type\. For more information, see [IP addresses per network interface per instance type](#AvailableIpPerENI)\.
**Public IPv4 addresses for network interfaces**
In a VPC, all subnets have a modifiable attribute that determines whether network interfaces created in that subnet \(and therefore instances launched into that subnet\) are assigned a public IPv4 address\. For more information, see [IP Addressing Behavior for Your Subnet](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html#vpc-ip-addressing-subnet) in the *Amazon VPC User Guide*\. The public IPv4 address is assigned from Amazon's pool of public IPv4 addresses\. When you launch an instance, the IP address is assigned to the primary network interface that's created\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
fd6086077397-1 | When you create a network interface, it inherits the public IPv4 addressing attribute from the subnet\. If you later modify the public IPv4 addressing attribute of the subnet, the network interface keeps the setting that was in effect when it was created\. If you launch an instance and specify an existing network interface as the primary network interface, the public IPv4 address attribute is determined by this network interface\.
For more information, see [Public IPv4 addresses and external DNS hostnames](using-instance-addressing.md#concepts-public-addresses)\.
**IPv6 addresses for network interfaces**
You can associate an IPv6 CIDR block with your VPC and subnet, and assign one or more IPv6 addresses from the subnet range to a network interface\.
All subnets have a modifiable attribute that determines whether network interfaces created in that subnet \(and therefore instances launched into that subnet\) are automatically assigned an IPv6 address from the range of the subnet\. For more information, see [IP Addressing Behavior for Your Subnet](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html#vpc-ip-addressing-subnet) in the *Amazon VPC User Guide*\. When you launch an instance, the IPv6 address is assigned to the primary network interface that's created\.
For more information, see [IPv6 addresses](using-instance-addressing.md#ipv6-addressing)\.
**Monitoring IP traffic** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
fd6086077397-2 | **Monitoring IP traffic**
You can enable a VPC flow log on your network interface to capture information about the IP traffic going to and from a network interface\. After you've created a flow log, you can view and retrieve its data in Amazon CloudWatch Logs\. For more information, see [VPC Flow Logs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html) in the *Amazon VPC User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-0 | The following table lists the maximum number of network interfaces per instance type, and the maximum number of private IPv4 addresses and IPv6 addresses per network interface\. The limit for IPv6 addresses is separate from the limit for private IPv4 addresses per network interface\. Not all instance types support IPv6 addressing\. Network interfaces, multiple private IPv4 addresses, and IPv6 addresses are only available for instances running in a VPC\. IPv6 addresses are public and reachable over the Internet\. For more information, see [Multiple IP addresses](MultipleIP.md)\. For more information about IPv6 in VPC, see [IP Addressing in Your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html) in the *Amazon VPC User Guide*\.
| Instance type | Maximum network interfaces | Private IPv4 addresses per interface | IPv6 addresses per interface |
| --- | --- | --- | --- |
| a1\.medium | 2 | 4 | 4 |
| a1\.large | 3 | 10 | 10 |
| a1\.xlarge | 4 | 15 | 15 |
| a1\.2xlarge | 4 | 15 | 15 |
| a1\.4xlarge | 8 | 30 | 30 |
| a1\.metal | 8 | 30 | 30 |
| c1\.medium | 2 | 6 | IPv6 not supported |
| c1\.xlarge | 4 | 15 | IPv6 not supported | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-1 | | c1\.medium | 2 | 6 | IPv6 not supported |
| c1\.xlarge | 4 | 15 | IPv6 not supported |
| c3\.large | 3 | 10 | 10 |
| c3\.xlarge | 4 | 15 | 15 |
| c3\.2xlarge | 4 | 15 | 15 |
| c3\.4xlarge | 8 | 30 | 30 |
| c3\.8xlarge | 8 | 30 | 30 |
| c4\.large | 3 | 10 | 10 |
| c4\.xlarge | 4 | 15 | 15 |
| c4\.2xlarge | 4 | 15 | 15 |
| c4\.4xlarge | 8 | 30 | 30 |
| c4\.8xlarge | 8 | 30 | 30 |
| c5\.large | 3 | 10 | 10 |
| c5\.xlarge | 4 | 15 | 15 |
| c5\.2xlarge | 4 | 15 | 15 |
| c5\.4xlarge | 8 | 30 | 30 |
| c5\.9xlarge | 8 | 30 | 30 |
| c5\.12xlarge | 8 | 30 | 30 |
| c5\.18xlarge | 15 | 50 | 50 |
| c5\.24xlarge | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-2 | | c5\.18xlarge | 15 | 50 | 50 |
| c5\.24xlarge | 15 | 50 | 50 |
| c5\.metal | 15 | 50 | 50 |
| c5a\.large | 3 | 10 | 10 |
| c5a\.xlarge | 4 | 15 | 15 |
| c5a\.2xlarge | 4 | 15 | 15 |
| c5a\.4xlarge | 8 | 30 | 30 |
| c5a\.8xlarge | 8 | 30 | 30 |
| c5a\.12xlarge | 8 | 30 | 30 |
| c5a\.16xlarge | 15 | 50 | 50 |
| c5a\.24xlarge | 15 | 50 | 50 |
| c5ad\.large | 3 | 10 | 10 |
| c5ad\.xlarge | 4 | 15 | 15 |
| c5ad\.2xlarge | 4 | 15 | 15 |
| c5ad\.4xlarge | 8 | 30 | 30 |
| c5ad\.8xlarge | 8 | 30 | 30 |
| c5ad\.12xlarge | 8 | 30 | 30 |
| c5ad\.16xlarge | 15 | 50 | 50 |
| c5ad\.24xlarge | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-3 | | c5ad\.16xlarge | 15 | 50 | 50 |
| c5ad\.24xlarge | 15 | 50 | 50 |
| c5d\.large | 3 | 10 | 10 |
| c5d\.xlarge | 4 | 15 | 15 |
| c5d\.2xlarge | 4 | 15 | 15 |
| c5d\.4xlarge | 8 | 30 | 30 |
| c5d\.9xlarge | 8 | 30 | 30 |
| c5d\.12xlarge | 8 | 30 | 30 |
| c5d\.18xlarge | 15 | 50 | 50 |
| c5d\.24xlarge | 15 | 50 | 50 |
| c5d\.metal | 15 | 50 | 50 |
| c5n\.large | 3 | 10 | 10 |
| c5n\.xlarge | 4 | 15 | 15 |
| c5n\.2xlarge | 4 | 15 | 15 |
| c5n\.4xlarge | 8 | 30 | 30 |
| c5n\.9xlarge | 8 | 30 | 30 |
| c5n\.18xlarge | 15 | 50 | 50 |
| c5n\.metal | 15 | 50 | 50 |
| c6g\.medium | 2 | 4 | 4 |
| c6g\.large | 3 | 10 | 10 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-4 | | c6g\.medium | 2 | 4 | 4 |
| c6g\.large | 3 | 10 | 10 |
| c6g\.xlarge | 4 | 15 | 15 |
| c6g\.2xlarge | 4 | 15 | 15 |
| c6g\.4xlarge | 8 | 30 | 30 |
| c6g\.8xlarge | 8 | 30 | 30 |
| c6g\.12xlarge | 8 | 30 | 30 |
| c6g\.16xlarge | 15 | 50 | 50 |
| c6g\.metal | 15 | 50 | 50 |
| c6gd\.medium | 2 | 4 | 4 |
| c6gd\.large | 3 | 10 | 10 |
| c6gd\.xlarge | 4 | 15 | 15 |
| c6gd\.2xlarge | 4 | 15 | 15 |
| c6gd\.4xlarge | 8 | 30 | 30 |
| c6gd\.8xlarge | 8 | 30 | 30 |
| c6gd\.12xlarge | 8 | 30 | 30 |
| c6gd\.16xlarge | 15 | 50 | 50 |
| c6gd\.metal | 15 | 50 | 50 |
| cc2\.8xlarge | 8 | 30 | IPv6 not supported | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-5 | | cc2\.8xlarge | 8 | 30 | IPv6 not supported |
| cr1\.8xlarge | 8 | 30 | IPv6 not supported |
| d2\.xlarge | 4 | 15 | 15 |
| d2\.2xlarge | 4 | 15 | 15 |
| d2\.4xlarge | 8 | 30 | 30 |
| d2\.8xlarge | 8 | 30 | 30 |
| f1\.2xlarge | 4 | 15 | 15 |
| f1\.4xlarge | 8 | 30 | 30 |
| f1\.16xlarge | 8 | 50 | 50 |
| g2\.2xlarge | 4 | 15 | IPv6 not supported |
| g2\.8xlarge | 8 | 30 | IPv6 not supported |
| g3s\.xlarge | 4 | 15 | 15 |
| g3\.4xlarge | 8 | 30 | 30 |
| g3\.8xlarge | 8 | 30 | 30 |
| g3\.16xlarge | 15 | 50 | 50 |
| g4dn\.xlarge | 3 | 10 | 10 |
| g4dn\.2xlarge | 3 | 10 | 10 |
| g4dn\.4xlarge | 3 | 10 | 10 |
| g4dn\.8xlarge | 4 | 15 | 15 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-6 | | g4dn\.8xlarge | 4 | 15 | 15 |
| g4dn\.12xlarge | 8 | 30 | 30 |
| g4dn\.16xlarge | 4 | 15 | 15 |
| g4dn\.metal | 15 | 50 | 50 |
| h1\.2xlarge | 4 | 15 | 15 |
| h1\.4xlarge | 8 | 30 | 30 |
| h1\.8xlarge | 8 | 30 | 30 |
| h1\.16xlarge | 15 | 50 | 50 |
| hs1\.8xlarge | 8 | 30 | IPv6 not supported |
| i2\.xlarge | 4 | 15 | 15 |
| i2\.2xlarge | 4 | 15 | 15 |
| i2\.4xlarge | 8 | 30 | 30 |
| i2\.8xlarge | 8 | 30 | 30 |
| i3\.large | 3 | 10 | 10 |
| i3\.xlarge | 4 | 15 | 15 |
| i3\.2xlarge | 4 | 15 | 15 |
| i3\.4xlarge | 8 | 30 | 30 |
| i3\.8xlarge | 8 | 30 | 30 |
| i3\.16xlarge | 15 | 50 | 50 |
| i3\.metal | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-7 | | i3\.16xlarge | 15 | 50 | 50 |
| i3\.metal | 15 | 50 | 50 |
| i3en\.large | 3 | 10 | 10 |
| i3en\.xlarge | 4 | 15 | 15 |
| i3en\.2xlarge | 4 | 15 | 15 |
| i3en\.3xlarge | 4 | 15 | 15 |
| i3en\.6xlarge | 8 | 30 | 30 |
| i3en\.12xlarge | 8 | 30 | 30 |
| i3en\.24xlarge | 15 | 50 | 50 |
| i3en\.metal | 15 | 50 | 50 |
| inf1\.xlarge | 4 | 10 | 10 |
| inf1\.2xlarge | 4 | 10 | 10 |
| inf1\.6xlarge | 8 | 30 | 30 |
| inf1\.24xlarge | 15 | 30 | 30 |
| m1\.small | 2 | 4 | IPv6 not supported |
| m1\.medium | 2 | 6 | IPv6 not supported |
| m1\.large | 3 | 10 | IPv6 not supported |
| m1\.xlarge | 4 | 15 | IPv6 not supported |
| m2\.xlarge | 4 | 15 | IPv6 not supported | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-8 | | m2\.xlarge | 4 | 15 | IPv6 not supported |
| m2\.2xlarge | 4 | 30 | IPv6 not supported |
| m2\.4xlarge | 8 | 30 | IPv6 not supported |
| m3\.medium | 2 | 6 | IPv6 not supported |
| m3\.large | 3 | 10 | IPv6 not supported |
| m3\.xlarge | 4 | 15 | IPv6 not supported |
| m3\.2xlarge | 4 | 30 | IPv6 not supported |
| m4\.large | 2 | 10 | 10 |
| m4\.xlarge | 4 | 15 | 15 |
| m4\.2xlarge | 4 | 15 | 15 |
| m4\.4xlarge | 8 | 30 | 30 |
| m4\.10xlarge | 8 | 30 | 30 |
| m4\.16xlarge | 8 | 30 | 30 |
| m5\.large | 3 | 10 | 10 |
| m5\.xlarge | 4 | 15 | 15 |
| m5\.2xlarge | 4 | 15 | 15 |
| m5\.4xlarge | 8 | 30 | 30 |
| m5\.8xlarge | 8 | 30 | 30 |
| m5\.12xlarge | 8 | 30 | 30 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-9 | | m5\.8xlarge | 8 | 30 | 30 |
| m5\.12xlarge | 8 | 30 | 30 |
| m5\.16xlarge | 15 | 50 | 50 |
| m5\.24xlarge | 15 | 50 | 50 |
| m5\.metal | 15 | 50 | 50 |
| m5a\.large | 3 | 10 | 10 |
| m5a\.xlarge | 4 | 15 | 15 |
| m5a\.2xlarge | 4 | 15 | 15 |
| m5a\.4xlarge | 8 | 30 | 30 |
| m5a\.8xlarge | 8 | 30 | 30 |
| m5a\.12xlarge | 8 | 30 | 30 |
| m5a\.16xlarge | 15 | 50 | 50 |
| m5a\.24xlarge | 15 | 50 | 50 |
| m5ad\.large | 3 | 10 | 10 |
| m5ad\.xlarge | 4 | 15 | 15 |
| m5ad\.2xlarge | 4 | 15 | 15 |
| m5ad\.4xlarge | 8 | 30 | 30 |
| m5ad\.8xlarge | 8 | 30 | 30 |
| m5ad\.12xlarge | 8 | 30 | 30 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-10 | | m5ad\.8xlarge | 8 | 30 | 30 |
| m5ad\.12xlarge | 8 | 30 | 30 |
| m5ad\.16xlarge | 15 | 50 | 50 |
| m5ad\.24xlarge | 15 | 50 | 50 |
| m5d\.large | 3 | 10 | 10 |
| m5d\.xlarge | 4 | 15 | 15 |
| m5d\.2xlarge | 4 | 15 | 15 |
| m5d\.4xlarge | 8 | 30 | 30 |
| m5d\.8xlarge | 8 | 30 | 30 |
| m5d\.12xlarge | 8 | 30 | 30 |
| m5d\.16xlarge | 15 | 50 | 50 |
| m5d\.24xlarge | 15 | 50 | 50 |
| m5d\.metal | 15 | 50 | 50 |
| m5dn\.large | 3 | 10 | 10 |
| m5dn\.xlarge | 4 | 15 | 15 |
| m5dn\.2xlarge | 4 | 15 | 15 |
| m5dn\.4xlarge | 8 | 30 | 30 |
| m5dn\.8xlarge | 8 | 30 | 30 |
| m5dn\.12xlarge | 8 | 30 | 30 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-11 | | m5dn\.12xlarge | 8 | 30 | 30 |
| m5dn\.16xlarge | 15 | 50 | 50 |
| m5dn\.24xlarge | 15 | 50 | 50 |
| m5n\.large | 3 | 10 | 10 |
| m5n\.xlarge | 4 | 15 | 15 |
| m5n\.2xlarge | 4 | 15 | 15 |
| m5n\.4xlarge | 8 | 30 | 30 |
| m5n\.8xlarge | 8 | 30 | 30 |
| m5n\.12xlarge | 8 | 30 | 30 |
| m5n\.16xlarge | 15 | 50 | 50 |
| m5n\.24xlarge | 15 | 50 | 50 |
| m6g\.medium | 2 | 4 | 4 |
| m6g\.large | 3 | 10 | 10 |
| m6g\.xlarge | 4 | 15 | 15 |
| m6g\.2xlarge | 4 | 15 | 15 |
| m6g\.4xlarge | 8 | 30 | 30 |
| m6g\.8xlarge | 8 | 30 | 30 |
| m6g\.12xlarge | 8 | 30 | 30 |
| m6g\.16xlarge | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-12 | | m6g\.12xlarge | 8 | 30 | 30 |
| m6g\.16xlarge | 15 | 50 | 50 |
| m6g\.metal | 15 | 50 | 50 |
| m6gd\.medium | 2 | 4 | 4 |
| m6gd\.large | 3 | 10 | 10 |
| m6gd\.xlarge | 4 | 15 | 15 |
| m6gd\.2xlarge | 4 | 15 | 15 |
| m6gd\.4xlarge | 8 | 30 | 30 |
| m6gd\.8xlarge | 8 | 30 | 30 |
| m6gd\.12xlarge | 8 | 30 | 30 |
| m6gd\.16xlarge | 15 | 50 | 50 |
| m6gd\.metal | 15 | 50 | 50 |
| p2\.xlarge | 4 | 15 | 15 |
| p2\.8xlarge | 8 | 30 | 30 |
| p2\.16xlarge | 8 | 30 | 30 |
| p3\.2xlarge | 4 | 15 | 15 |
| p3\.8xlarge | 8 | 30 | 30 |
| p3\.16xlarge | 8 | 30 | 30 |
| p3dn\.24xlarge | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-13 | | p3\.16xlarge | 8 | 30 | 30 |
| p3dn\.24xlarge | 15 | 50 | 50 |
| r3\.large | 3 | 10 | 10 |
| r3\.xlarge | 4 | 15 | 15 |
| r3\.2xlarge | 4 | 15 | 15 |
| r3\.4xlarge | 8 | 30 | 30 |
| r3\.8xlarge | 8 | 30 | 30 |
| r4\.large | 3 | 10 | 10 |
| r4\.xlarge | 4 | 15 | 15 |
| r4\.2xlarge | 4 | 15 | 15 |
| r4\.4xlarge | 8 | 30 | 30 |
| r4\.8xlarge | 8 | 30 | 30 |
| r4\.16xlarge | 15 | 50 | 50 |
| r5\.large | 3 | 10 | 10 |
| r5\.xlarge | 4 | 15 | 15 |
| r5\.2xlarge | 4 | 15 | 15 |
| r5\.4xlarge | 8 | 30 | 30 |
| r5\.8xlarge | 8 | 30 | 30 |
| r5\.12xlarge | 8 | 30 | 30 |
| r5\.16xlarge | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-14 | | r5\.12xlarge | 8 | 30 | 30 |
| r5\.16xlarge | 15 | 50 | 50 |
| r5\.24xlarge | 15 | 50 | 50 |
| r5\.metal | 15 | 50 | 50 |
| r5a\.large | 3 | 10 | 10 |
| r5a\.xlarge | 4 | 15 | 15 |
| r5a\.2xlarge | 4 | 15 | 15 |
| r5a\.4xlarge | 8 | 30 | 30 |
| r5a\.8xlarge | 8 | 30 | 30 |
| r5a\.12xlarge | 8 | 30 | 30 |
| r5a\.16xlarge | 15 | 50 | 50 |
| r5a\.24xlarge | 15 | 50 | 50 |
| r5ad\.large | 3 | 10 | 10 |
| r5ad\.xlarge | 4 | 15 | 15 |
| r5ad\.2xlarge | 4 | 15 | 15 |
| r5ad\.4xlarge | 8 | 30 | 30 |
| r5ad\.8xlarge | 8 | 30 | 30 |
| r5ad\.12xlarge | 8 | 30 | 30 |
| r5ad\.16xlarge | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-15 | | r5ad\.12xlarge | 8 | 30 | 30 |
| r5ad\.16xlarge | 15 | 50 | 50 |
| r5ad\.24xlarge | 15 | 50 | 50 |
| r5d\.large | 3 | 10 | 10 |
| r5d\.xlarge | 4 | 15 | 15 |
| r5d\.2xlarge | 4 | 15 | 15 |
| r5d\.4xlarge | 8 | 30 | 30 |
| r5d\.8xlarge | 8 | 30 | 30 |
| r5d\.12xlarge | 8 | 30 | 30 |
| r5d\.16xlarge | 15 | 50 | 50 |
| r5d\.24xlarge | 15 | 50 | 50 |
| r5d\.metal | 15 | 50 | 50 |
| r5dn\.large | 3 | 10 | 10 |
| r5dn\.xlarge | 4 | 15 | 15 |
| r5dn\.2xlarge | 4 | 15 | 15 |
| r5dn\.4xlarge | 8 | 30 | 30 |
| r5dn\.8xlarge | 8 | 30 | 30 |
| r5dn\.12xlarge | 8 | 30 | 30 |
| r5dn\.16xlarge | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-16 | | r5dn\.16xlarge | 15 | 50 | 50 |
| r5dn\.24xlarge | 15 | 50 | 50 |
| r5n\.large | 3 | 10 | 10 |
| r5n\.xlarge | 4 | 15 | 15 |
| r5n\.2xlarge | 4 | 15 | 15 |
| r5n\.4xlarge | 8 | 30 | 30 |
| r5n\.8xlarge | 8 | 30 | 30 |
| r5n\.12xlarge | 8 | 30 | 30 |
| r5n\.16xlarge | 15 | 50 | 50 |
| r5n\.24xlarge | 15 | 50 | 50 |
| r6g\.medium | 2 | 4 | 4 |
| r6g\.large | 3 | 10 | 10 |
| r6g\.xlarge | 4 | 15 | 15 |
| r6g\.2xlarge | 4 | 15 | 15 |
| r6g\.4xlarge | 8 | 30 | 30 |
| r6g\.8xlarge | 8 | 30 | 30 |
| r6g\.12xlarge | 8 | 30 | 30 |
| r6g\.16xlarge | 15 | 50 | 50 |
| r6g\.metal | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-17 | | r6g\.16xlarge | 15 | 50 | 50 |
| r6g\.metal | 15 | 50 | 50 |
| r6gd\.medium | 2 | 4 | 4 |
| r6gd\.large | 3 | 10 | 10 |
| r6gd\.xlarge | 4 | 15 | 15 |
| r6gd\.2xlarge | 4 | 15 | 15 |
| r6gd\.4xlarge | 8 | 30 | 30 |
| r6gd\.8xlarge | 8 | 30 | 30 |
| r6gd\.12xlarge | 8 | 30 | 30 |
| r6gd\.16xlarge | 15 | 50 | 50 |
| r6gd\.metal | 15 | 50 | 50 |
| t1\.micro | 2 | 2 | IPv6 not supported |
| t2\.nano | 2 | 2 | 2 |
| t2\.micro | 2 | 2 | 2 |
| t2\.small | 3 | 4 | 4 |
| t2\.medium | 3 | 6 | 6 |
| t2\.large | 3 | 12 | 12 |
| t2\.xlarge | 3 | 15 | 15 |
| t2\.2xlarge | 3 | 15 | 15 |
| t3\.nano | 2 | 2 | 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-18 | | t2\.2xlarge | 3 | 15 | 15 |
| t3\.nano | 2 | 2 | 2 |
| t3\.micro | 2 | 2 | 2 |
| t3\.small | 3 | 4 | 4 |
| t3\.medium | 3 | 6 | 6 |
| t3\.large | 3 | 12 | 12 |
| t3\.xlarge | 4 | 15 | 15 |
| t3\.2xlarge | 4 | 15 | 15 |
| t3a\.nano | 2 | 2 | 2 |
| t3a\.micro | 2 | 2 | 2 |
| t3a\.small | 2 | 4 | 4 |
| t3a\.medium | 3 | 6 | 6 |
| t3a\.large | 3 | 12 | 12 |
| t3a\.xlarge | 4 | 15 | 15 |
| t3a\.2xlarge | 4 | 15 | 15 |
| t4g\.nano | 2 | 2 | 2 |
| t4g\.micro | 2 | 2 | 2 |
| t4g\.small | 2 | 4 | 4 |
| t4g\.medium | 3 | 6 | 6 |
| t4g\.large | 3 | 12 | 12 |
| t4g\.xlarge | 4 | 15 | 15 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-19 | | t4g\.large | 3 | 12 | 12 |
| t4g\.xlarge | 4 | 15 | 15 |
| t4g\.2xlarge | 4 | 15 | 15 |
| u\-6tb1\.metal | 5 | 30 | 30 |
| u\-9tb1\.metal | 5 | 30 | 30 |
| u\-12tb1\.metal | 5 | 30 | 30 |
| u\-18tb1\.metal | 15 | 50 | 50 |
| u\-24tb1\.metal | 15 | 50 | 50 |
| x1\.16xlarge | 8 | 30 | 30 |
| x1\.32xlarge | 8 | 30 | 30 |
| x1e\.xlarge | 3 | 10 | 10 |
| x1e\.2xlarge | 4 | 15 | 15 |
| x1e\.4xlarge | 4 | 15 | 15 |
| x1e\.8xlarge | 4 | 15 | 15 |
| x1e\.16xlarge | 8 | 30 | 30 |
| x1e\.32xlarge | 8 | 30 | 30 |
| z1d\.large | 3 | 10 | 10 |
| z1d\.xlarge | 4 | 15 | 15 |
| z1d\.2xlarge | 4 | 15 | 15 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e24daf0e25a5-20 | | z1d\.xlarge | 4 | 15 | 15 |
| z1d\.2xlarge | 4 | 15 | 15 |
| z1d\.3xlarge | 8 | 30 | 30 |
| z1d\.6xlarge | 8 | 30 | 30 |
| z1d\.12xlarge | 15 | 50 | 50 |
| z1d\.metal | 15 | 50 | 50 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
7948f1534e66-0 | Attaching multiple network interfaces to an instance is useful when you want to:
+ Create a management network\.
+ Use network and security appliances in your VPC\.
+ Create dual\-homed instances with workloads/roles on distinct subnets\.
+ Create a low\-budget, high\-availability solution\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
47ce487db15b-0 | You can create a management network using network interfaces\. In this scenario, the primary network interface \(eth0\) on the instance handles public traffic and the secondary network interface \(eth1\) handles backend management traffic and is connected to a separate subnet in your VPC that has more restrictive access controls\. The public interface, which may or may not be behind a load balancer, has an associated security group that allows access to the server from the internet \(for example, allow TCP port 80 and 443 from `0.0.0.0/0`, or from the load balancer\) while the private facing interface has an associated security group allowing SSH access only from an allowed range of IP addresses either within the VPC or from the internet, a private subnet within the VPC or a virtual private gateway\.
To ensure failover capabilities, consider using a secondary private IPv4 for incoming traffic on a network interface\. In the event of an instance failure, you can move the interface and/or secondary private IPv4 address to a standby instance\.
![\[Creating a Management Network\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/EC2_ENI_management_network.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
e1b0683cf832-0 | Some network and security appliances, such as load balancers, network address translation \(NAT\) servers, and proxy servers prefer to be configured with multiple network interfaces\. You can create and attach secondary network interfaces to instances in a VPC that are running these types of applications and configure the additional interfaces with their own public and private IP addresses, security groups, and source/destination checking\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
0bf82869fa23-0 | You can place a network interface on each of your web servers that connects to a mid\-tier network where an application server resides\. The application server can also be dual\-homed to a backend network \(subnet\) where the database server resides\. Instead of routing network packets through the dual\-homed instances, each dual\-homed instance receives and processes requests on the front end, initiates a connection to the backend, and then sends requests to the servers on | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
0bf82869fa23-1 | and then sends requests to the servers on the backend network\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
dd757815e1d0-0 | If one of your instances serving a particular function fails, its network interface can be attached to a replacement or hot standby instance pre\-configured for the same role in order to rapidly recover the service\. For example, you can use a network interface as your primary or secondary network interface to a critical service such as a database instance or a NAT instance\. If the instance fails, you \(or more likely, the code running on your behalf\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
dd757815e1d0-1 | likely, the code running on your behalf\) can attach the network interface to a hot standby instance\. Because the interface maintains its private IP addresses, Elastic IP addresses, and MAC address, network traffic begins flowing to the standby instance as soon as you attach the network interface to the replacement instance\. Users experience a brief loss of connectivity between the time the instance fails and the time that the network interface is attached to the standby instance, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
dd757815e1d0-2 | network interface is attached to the standby instance, but no changes to the VPC route table or your DNS server are required\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
43bd829b1e4a-0 | + You can attach a network interface to an instance when it's running \(hot attach\), when it's stopped \(warm attach\), or when the instance is being launched \(cold attach\)\.
+ You can detach secondary network interfaces when the instance is running or stopped\. However, you can't detach the primary network interface\.
+ You can move a network interface from one instance to another, if the instances are in the same Availability Zone and VPC but in different subnets\.
+ When launching an instance using the CLI, API, or an SDK, you can specify the primary network interface and additional network interfaces\.
+ Launching an Amazon Linux or Windows Server instance with multiple network interfaces automatically configures interfaces, private IPv4 addresses, and route tables on the operating system of the instance\.
+ A warm or hot attach of an additional network interface may require you to manually bring up the second interface, configure the private IPv4 address, and modify the route table accordingly\. Instances running Amazon Linux or Windows Server automatically recognize the warm or hot attach and configure themselves\.
+ Attaching another network interface to an instance \(for example, a NIC teaming configuration\) cannot be used as a method to increase or double the network bandwidth to or from the dual\-homed instance\.
+ If you attach two or more network interfaces from the same subnet to an instance, you may encounter networking issues such as asymmetric routing\. If possible, use a secondary private IPv4 address on the primary network interface instead\. For more information, see [Assigning a secondary private IPv4 address](MultipleIP.md#ManageMultipleIP)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
f6c51c683653-0 | Amazon Linux AMIs may contain additional scripts installed by AWS, known as ec2\-net\-utils\. These scripts optionally automate the configuration of your network interfaces\. These scripts are available for Amazon Linux only\.
Use the following command to install the package on Amazon Linux if it's not already installed, or update it if it's installed and additional updates are available:
```
$ yum install ec2-net-utils
```
The following components are part of ec2\-net\-utils:
udev rules \(`/etc/udev/rules.d`\)
Identifies network interfaces when they are attached, detached, or reattached to a running instance, and ensures that the hotplug script runs \(`53-ec2-network-interfaces.rules`\)\. Maps the MAC address to a device name \(`75-persistent-net-generator.rules`, which generates `70-persistent-net.rules`\)\.
hotplug script
Generates an interface configuration file suitable for use with DHCP \(`/etc/sysconfig/network-scripts/ifcfg-eth`*N*\)\. Also generates a route configuration file \(`/etc/sysconfig/network-scripts/route-eth`*N*\)\.
DHCP script | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
f6c51c683653-1 | DHCP script
Whenever the network interface receives a new DHCP lease, this script queries the instance metadata for Elastic IP addresses\. For each Elastic IP address, it adds a rule to the routing policy database to ensure that outbound traffic from that address uses the correct network interface\. It also adds each private IP address to the network interface as a secondary address\.
ec2ifup eth*N*
Extends the functionality of the standard ifup\. After this script rewrites the configuration files `ifcfg-eth`*N* and `route-eth`*N*, it runs ifup\.
ec2ifdown eth*N*
Extends the functionality of the standard ifdown\. After this script removes any rules for the network interface from the routing policy database, it runs ifdown\.
ec2ifscan
Checks for network interfaces that have not been configured and configures them\.
This script isn't available in the initial release of ec2\-net\-utils\.
To list any configuration files that were generated by ec2\-net\-utils, use the following command:
```
$ ls -l /etc/sysconfig/network-scripts/*-eth?
```
To disable the automation on a per\-instance basis, you can add `EC2SYNC=no` to the corresponding `ifcfg-eth`*N* file\. For example, use the following command to disable the automation for the eth1 interface:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
f6c51c683653-2 | ```
$ sed -i -e 's/^EC2SYNC=yes/EC2SYNC=no/' /etc/sysconfig/network-scripts/ifcfg-eth1
```
To disable the automation completely, you can remove the package using the following command:
```
$ yum remove ec2-net-utils
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
fcf986a48a91-0 | You can work with network interfaces using the Amazon EC2 console or the command line\.
**Topics**
+ [Creating a network interface](#create_eni)
+ [Deleting a network interface](#delete_eni)
+ [Viewing details about a network interface](#view_eni_details)
+ [Attaching a network interface when launching an instance](#attach_eni_launch)
+ [Attaching a network interface to a stopped or running instance](#attach_eni_running_stopped)
+ [Detaching a network interface from an instance](#detach_eni)
+ [Changing the security group](#eni_security_group)
+ [Changing the source or destination checking](#change_source_dest_check)
+ [Associating an Elastic IP address \(IPv4\)](#associate_eip)
+ [Disassociating an Elastic IP address \(IPv4\)](#disassociate_eip)
+ [Assigning an IPv6 address](#eni-assign-ipv6)
+ [Unassigning an IPv6 address](#eni-unassign-ipv6)
+ [Changing termination behavior](#change_term_behavior)
+ [Adding or editing a description](#add_edit_description)
+ [Adding or editing tags](#eni_add_edit_tags) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
9f0c4d2ea555-0 | You can create a network interface in a subnet\. You can't move the network interface to another subnet after it's created, and you can only attach the network interface to instances in the same Availability Zone\.
**To create a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Choose **Create Network Interface**\.
1. For **Description**, enter a descriptive name\.
1. For **Subnet**, select the subnet\.
1. For **Private IP** \(or **IPv4 Private IP**\), enter the primary private IPv4 address\. If you don't specify an IPv4 address, we select an available private IPv4 address from within the selected subnet\.
1. \(IPv6 only\) If you selected a subnet that has an associated IPv6 CIDR block, you can optionally specify an IPv6 address in the **IPv6 IP** field\.
1. To create an Elastic Fabric Adapter, select **Elastic Fabric Adapter**\.
1. For **Security groups**, select one or more security groups\.
1. \(Optional\) **Choose Add Tag** and enter a tag key and a tag value\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
9f0c4d2ea555-1 | 1. \(Optional\) **Choose Add Tag** and enter a tag key and a tag value\.
1. Choose **Yes, Create**\.
**To create a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [create\-network\-interface](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-network-interface.html) \(AWS CLI\)
+ [New\-EC2NetworkInterface](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2NetworkInterface.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
3227ad3fafe8-0 | To delete an instance, you must first detach the network interface\. Deleting a network interface releases all attributes associated with the interface and releases any private IP addresses or Elastic IP addresses to be used by another instance\.
**To delete a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select a network interface and choose **Delete**\.
1. In the **Delete Network Interface** dialog box, choose **Yes, Delete**\.
**To delete a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [delete\-network\-interface](https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-network-interface.html) \(AWS CLI\)
+ [Remove\-EC2NetworkInterface](https://docs.aws.amazon.com/powershell/latest/reference/items/Remove-EC2NetworkInterface.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
0917a1995035-0 | You can view all the network interfaces in your account\.
**To describe a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface\.
1. To view the details, choose **Details**\.
**To describe a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [describe\-network\-interfaces](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-network-interfaces.html) \(AWS CLI\)
+ [Get\-EC2NetworkInterface](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2NetworkInterface.html) \(AWS Tools for Windows PowerShell\)
**To describe a network interface attribute using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
0917a1995035-1 | + [describe\-network\-interface\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-network-interface-attribute.html) \(AWS CLI\)
+ [Get\-EC2NetworkInterfaceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2NetworkInterfaceAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b50561861feb-0 | You can specify an existing network interface or attach an additional network interface when you launch an instance\.
**Note**
If an error occurs when attaching a network interface to your instance, this causes the instance launch to fail\.
**To attach a network interface when launching an instance using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Launch Instance**\.
1. Select an AMI and instance type and choose **Next: Configure Instance Details**\.
1. On the **Configure Instance Details** page, select a VPC for **Network**, and a subnet for **Subnet**\.
1. In the **Network Interfaces** section, the console enables you to specify up to two network interfaces \(new, existing, or a combination\) when you launch an instance\. You can also enter a primary IPv4 address and one or more secondary IPv4 addresses for any new interface\.
You can add additional network interfaces to the instance after you launch it\. The total number of network interfaces that you can attach varies by instance type\. For more information, see [IP addresses per network interface per instance type](#AvailableIpPerENI)\.
**Note**
If you specify more than one network interface, you cannot auto\-assign a public IPv4 address to your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b50561861feb-1 | **Note**
If you specify more than one network interface, you cannot auto\-assign a public IPv4 address to your instance\.
1. \(IPv6 only\) If you're launching an instance into a subnet that has an associated IPv6 CIDR block, you can specify IPv6 addresses for any network interfaces that you attach\. Under **IPv6 IPs**, choose **Add IP**\. To add a secondary IPv6 address, choose **Add IP** again\. You can enter an IPv6 address from the range of the subnet, or leave the default **Auto\-assign** value to let Amazon choose an IPv6 address from the subnet for you\.
1. Choose **Next: Add Storage**\.
1. On the **Add Storage** page, you can specify volumes to attach to the instance besides the volumes specified by the AMI \(such as the root device volume\), and then choose **Next: Add Tags**\.
1. On the **Add Tags** page, specify tags for the instance, such as a user\-friendly name, and then choose **Next: Configure Security Group**\.
1. On the **Configure Security Group** page, you can select a security group or create a new one\. Choose **Review and Launch**\.
**Note**
If you specified an existing network interface in step 5, the instance is associated with the security group for that network interface, regardless of any option that you select in this step\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b50561861feb-2 | If you specified an existing network interface in step 5, the instance is associated with the security group for that network interface, regardless of any option that you select in this step\.
1. On the **Review Instance Launch** page, details about the primary and additional network interface are displayed\. Review the settings, and then choose **Launch** to choose a key pair and launch your instance\. If you're new to Amazon EC2 and haven't created any key pairs, the wizard prompts you to create one\.
**To attach a network interface when launching an instance using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) \(AWS CLI\)
+ [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
cf9e2bbf6fc9-0 | You can attach a network interface to any of your stopped or running instances in your VPC, using either the **Instances** or **Network Interfaces** pages of the Amazon EC2 console\.
**Note**
If the public IPv4 address on your instance is released, it does not receive a new one if there is more than one network interface attached to the instance\. For more information about the behavior of public IPv4 addresses, see [Public IPv4 addresses and external DNS hostnames](using-instance-addressing.md#concepts-public-addresses)\.
**To attach a network interface to an instance using the Instances page**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Choose **Actions**, **Networking**, **Attach Network Interface**\.
1. In the **Attach Network Interface** dialog box, select the network interface and choose **Attach**\.
**To attach a network interface to an instance using the Network Interfaces page**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
cf9e2bbf6fc9-1 | 1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and choose **Attach**\.
1. In the **Attach Network Interface** dialog box, select the instance and choose **Attach**\.
**To attach a network interface to an instance using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [attach\-network\-interface](https://docs.aws.amazon.com/cli/latest/reference/ec2/attach-network-interface.html) \(AWS CLI\)
+ [Add\-EC2NetworkInterface](https://docs.aws.amazon.com/powershell/latest/reference/items/Add-EC2NetworkInterface.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
9b77a411df73-0 | You can detach a secondary network interface that is attached to an EC2 instance at any time, using either the **Instances** or **Network Interfaces** page of the Amazon EC2 console\.
**To detach a network interface from an instance using the Instances page**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Choose **Actions**, **Networking**, **Detach Network Interface**\.
1. In the **Detach Network Interface** dialog box, select the network interface and choose **Detach**\.
You can't use the Amazon EC2 console to detach a network interface that is attached to a resource from another service, such as an Elastic Load Balancing load balancer, a Lambda function, a WorkSpace, or a NAT gateway\. The network interfaces for those resources will be deleted when the resource is deleted\.
**To detach a network interface from an instance using the Network Interfaces page**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
9b77a411df73-1 | 1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and check the description to verify that the network interface is attached to an instance, not another type of resource\. If the resource is an EC2 instance, choose **Detach**\.
If the network interface is the primary network interface for the instance, the **Detach** button is disabled\.
1. When prompted for confirmation, choose **Yes, Detach**\.
1. If the network interface fails to detach from the instance, choose **Force detachment** and then try again\. We recommend that you choose this option only as a last resort\. Forcing a detachment can prevent you from attaching a different network interface on the same index until you restart the instance\. It can also prevent the instance metadata from reflecting that the network interface was detached until you restart the instance\.
**To detach a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [detach\-network\-interface](https://docs.aws.amazon.com/cli/latest/reference/ec2/detach-network-interface.html) \(AWS CLI\)
+ [Dismount\-EC2NetworkInterface](https://docs.aws.amazon.com/powershell/latest/reference/items/Dismount-EC2NetworkInterface.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
2fe6a3502a01-0 | You can change the security groups that are associated with a network interface\. When you create the security group, be sure to specify the same VPC as the subnet for the network interface\.
**Note**
To change security group membership for interfaces owned by other services, such as Elastic Load Balancing, use the console or command line interface for that service\.
**To change the security group of a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and choose **Actions**, **Change Security Groups**\.
1. In the **Change Security Groups** dialog box, select the security groups to use, and choose **Save**\.
**To change the security group of a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [modify\-network\-interface\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-network-interface-attribute.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
2fe6a3502a01-1 | + [Edit\-EC2NetworkInterfaceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2NetworkInterfaceAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
a5ecc49a92cc-0 | The Source/Destination Check attribute controls whether source/destination checking is enabled on the instance\. Disabling this attribute enables an instance to handle network traffic that isn't specifically destined for the instance\. For example, instances running services such as network address translation, routing, or a firewall should set this value to `disabled`\. The default value is `enabled`\.
**To change source/destination checking for a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and choose **Actions**, **Change Source/Dest Check**\.
1. In the dialog box, choose **Enabled** \(if enabling\) or **Disabled** \(if disabling\), and **Save**\.
**To change source/destination checking for a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [modify\-network\-interface\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-network-interface-attribute.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
a5ecc49a92cc-1 | + [Edit\-EC2NetworkInterfaceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2NetworkInterfaceAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
ac1b280c596f-0 | If you have an Elastic IP address \(IPv4\), you can associate it with one of the private IPv4 addresses for the network interface\. You can associate one Elastic IP address with each private IPv4 address\.
You can associate an Elastic IP address using the Amazon EC2 console or the command line\.
**To associate an Elastic IP address using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and choose **Actions**, **Associate Address**\.
1. In the **Associate Elastic IP Address** dialog box, select the Elastic IP address from the **Address** list\.
1. For **Associate to private IP address**, select the private IPv4 address to associate with the Elastic IP address\.
1. Choose **Allow reassociation** to allow the Elastic IP address to be associated with the specified network interface if it's currently associated with another instance or network interface, and then choose **Associate Address**\.
**To associate an Elastic IP address using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
ac1b280c596f-1 | + [associate\-address](https://docs.aws.amazon.com/cli/latest/reference/ec2/associate-address.html) \(AWS CLI\)
+ [Register\-EC2Address](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Address.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b2f0ee7bb9cc-0 | If the network interface has an Elastic IP address \(IPv4\) associated with it, you can disassociate the address, and then either associate it with another network interface or release it back to the address pool\. This is the only way to associate an Elastic IP address with an instance in a different subnet or VPC using a network interface, as network interfaces are specific to a particular subnet\.
You can disassociate an Elastic IP address using the Amazon EC2 console or the command line\.
**To disassociate an Elastic IP address using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and choose **Actions**, **Disassociate Address**\.
1. In the **Disassociate IP Address** dialog box, choose **Yes, Disassociate**\.
**To disassociate an Elastic IP address using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b2f0ee7bb9cc-1 | + [disassociate\-address](https://docs.aws.amazon.com/cli/latest/reference/ec2/disassociate-address.html) \(AWS CLI\)
+ [Unregister\-EC2Address](https://docs.aws.amazon.com/powershell/latest/reference/items/Unregister-EC2Address.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
99867bde8dc4-0 | You can assign one or more IPv6 addresses to a network interface\. The network interface must be in a subnet that has an associated IPv6 CIDR block\. To assign a specific IPv6 address to the network interface, ensure that the IPv6 address is not already assigned to another network interface\.
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces** and select the network interface\.
1. Choose **Actions**, **Manage IP Addresses**\.
1. Under **IPv6 Addresses**, choose **Assign new IP**\. Specify an IPv6 address from the range of the subnet\. To let AWS choose an address for you, leave the **Auto\-assign** value\.
1. Choose **Yes, Update**\.
**To assign an IPv6 address to a network interface using the command line**
+ You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [assign\-ipv6\-addresses](https://docs.aws.amazon.com/cli/latest/reference/ec2/assign-ipv6-addresses.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
99867bde8dc4-1 | + [Register\-EC2Ipv6AddressList](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Ipv6AddressList.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b56d929d9cf0-0 | You can unassign an IPv6 address from a network interface using the Amazon EC2 console\.
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces** and select the network interface\.
1. Choose **Actions**, **Manage IP Addresses**\.
1. Under **IPv6 Addresses**, choose **Unassign** for the IPv6 address to remove\.
1. Choose **Yes, Update**\.
**To unassign an IPv6 address from a network interface using the command line**
+ You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [unassign\-ipv6\-addresses](https://docs.aws.amazon.com/cli/latest/reference/ec2/unassign-ipv6-addresses.html) \(AWS CLI\)
+ [Unregister\-EC2Ipv6AddressList](https://docs.aws.amazon.com/powershell/latest/reference/items/Unregister-EC2Ipv6AddressList.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b978e2bc653d-0 | You can set the termination behavior for a network interface that's attached to an instance\. You can specify whether the network interface should be automatically deleted when you terminate the instance to which it's attached\.
You can change the terminating behavior for a network interface using the Amazon EC2 console or the command line\.
**To change the termination behavior for a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and choose **Actions**, **Change Termination Behavior**\.
1. In the **Change Termination Behavior** dialog box, select the **Delete on termination** check box if you want the network interface to be deleted when you terminate an instance\.
**To change the termination behavior for a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [modify\-network\-interface\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-network-interface-attribute.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b978e2bc653d-1 | + [Edit\-EC2NetworkInterfaceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2NetworkInterfaceAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
a01079dbcbe8-0 | You can change the description for a network interface using the Amazon EC2 console or the command line\.
**To change the description for a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface and choose **Actions**, **Change Description**\.
1. In the **Change Description** dialog box, enter a description for the network interface, and then choose **Save**\.
**To change the description for a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [modify\-network\-interface\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-network-interface-attribute.html) \(AWS CLI\)
+ [Edit\-EC2NetworkInterfaceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2NetworkInterfaceAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b898e1ebf5a7-0 | Tags are metadata that you can add to a network interface\. Tags are private and are only visible to your account\. Each tag consists of a key and an optional value\. For more information about tags, see [Tagging your Amazon EC2 resources](Using_Tags.md)\.
**To add or edit tags for a network interface using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Network Interfaces**\.
1. Select the network interface\.
1. In the details pane, choose **Tags**, **Add/Edit Tags**\.
1. In the **Add/Edit Tags** dialog box, choose **Create Tag** for each tag to create, and enter a key and optional value\. When you're done, choose **Save**\.
**To add or edit tags for a network interface using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [create\-tags](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-tags.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
b898e1ebf5a7-1 | + [New\-EC2Tag](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Tag.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-eni.md |
2dd62cbd7e69-0 | Amazon EC2 provides the following networking features\.
**Topics**
+ [Amazon EC2 instance IP addressing](using-instance-addressing.md)
+ [Bring your own IP addresses \(BYOIP\) in Amazon EC2](ec2-byoip.md)
+ [Elastic IP addresses](elastic-ip-addresses-eip.md)
+ [Elastic network interfaces](using-eni.md)
+ [Enhanced networking on Linux](enhanced-networking.md)
+ [Elastic Fabric Adapter](efa.md)
+ [Placement groups](placement-groups.md)
+ [Network maximum transmission unit \(MTU\) for your EC2 instance](network_mtu.md)
+ [Virtual private clouds](using-vpc.md)
+ [EC2\-Classic](ec2-classic-platform.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-networking.md |
91d59a807301-0 | Reserved Instances provide you with significant savings on your Amazon EC2 costs compared to On\-Demand Instance pricing\. Reserved Instances are not physical instances, but rather a billing discount applied to the use of On\-Demand Instances in your account\. These On\-Demand Instances must match certain attributes, such as instance type and Region, in order to benefit from the billing discount\.
Savings Plans also offer significant savings on your Amazon EC2 costs compared to On\-Demand Instance pricing\. With Savings Plans, you make a commitment to a consistent usage amount, measured in USD per hour\. This provides you with the flexibility to use the instance configurations that best meet your needs and continue to save money, instead of making a commitment to a specific instance configuration\. For more information, see the [AWS Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/)\.
**Topics**
+ [Reserved Instance overview](#ri-overview)
+ [Key variables that determine Reserved Instance pricing](#ri-key-pricing-variables)
+ [Reserved Instance limits](#ri-limits)
+ [Regional and zonal Reserved Instances \(scope\)](reserved-instances-scope.md)
+ [Types of Reserved Instances \(offering classes\)](reserved-instances-types.md)
+ [How Reserved Instances are applied](apply_ri.md)
+ [How you are billed](concepts-reserved-instances-application.md)
+ [Buying Reserved Instances](ri-market-concepts-buying.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-reserved-instances.md |
91d59a807301-1 | + [Buying Reserved Instances](ri-market-concepts-buying.md)
+ [Reserved Instance Marketplace](ri-market-general.md)
+ [Modifying Reserved Instances](ri-modifying.md)
+ [Exchanging Convertible Reserved Instances](ri-convertible-exchange.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-reserved-instances.md |
3c55d2fb59c5-0 | The following diagram shows a basic overview of purchasing and using Reserved Instances\.
![\[Purchasing Reserved Instances\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-basics.png)
In this scenario, you have a running On\-Demand Instance \(T2\) in your account, for which you're currently paying On\-Demand rates\. You purchase a Reserved Instance that matches the attributes of your running instance, and the billing benefit is immediately applied\. Next, you purchase a Reserved Instance for a C4 instance\. You do not have any running instances in your account that match the attributes of this Reserved Instance\. In the final step, you launch an instance that matches the attributes of the C4 Reserved Instance, and the billing benefit is immediately applied\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-reserved-instances.md |
22cc9292c2fb-0 | The Reserved Instance pricing is determined by the following key variables\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-reserved-instances.md |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.