id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
38708f39ed29-0 | When you delete a key pair, you are only deleting the Amazon EC2 copy of the public key\. Deleting a key pair doesn't affect the private key on your computer or the public key on any instances that already launched using that key pair\. You can't launch a new instance using a deleted key pair, but you can continue to connect to any instances that you launched using a deleted key pair, as long as you still have the private key \(`.pem`\) file\.
If you're using an Auto Scaling group \(for example, in an Elastic Beanstalk environment\), ensure that the key pair you're deleting is not specified in your launch configuration\. Amazon EC2 Auto Scaling launches a replacement instance if it detects an unhealthy instance; however, the instance launch fails if the key pair cannot be found\.
You can delete a key pair using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-key-pairs.md |
40daf527de6f-0 | **To delete your key pair**
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 **Key Pairs**\.
1. Select the key pair to delete and choose **Delete**\.
1. In the confirmation field, enter `Delete` and then choose **Delete**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-key-pairs.md |
36a8e3b3d67b-0 | **To delete your key pair**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, under **NETWORK & SECURITY**, choose **Key Pairs**\.
1. Select the key pair and choose **Delete**\.
1. When prompted, choose **Yes**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-key-pairs.md |
23bf8a4f2a9b-0 | **To delete your key pair**
Use the [delete\-key\-pair](https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-key-pair.html) AWS CLI command\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-key-pairs.md |
aeffbfb0e170-0 | **To delete your key pair**
Use the [Remove\-EC2KeyPair](https://docs.aws.amazon.com/powershell/latest/reference/items/Remove-EC2KeyPair.html) AWS Tools for Windows PowerShell command\.
------
If you create a Linux AMI from an instance, and then use the AMI to launch a new instance in a different Region or account, the new instance includes the public key from the original instance\. This enables you to connect to the new instance using the same private key file as your original instance\. You can remove this public key from your instance by removing its entry from the `.ssh/authorized_keys` file using a text editor of your choice\. For more information about managing users on your instance and providing remote access using a specific key pair, see [Managing user accounts on your Amazon Linux instance](managing-users.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-key-pairs.md |
7cdd46e10e8f-0 | The following table describes important additions to the Amazon EC2 documentation starting in 2019\. We also update the documentation frequently to address the feedback that you send us\.
| Change | Description | Date |
| --- |--- |--- |
| [T4g instances](#DocumentHistory) | New general purpose instances powered by AWS Graviton2 processors, which are based on 64\-bit Arm Neoverse cores and custom silicon designed by AWS for optimized performance and cost\. | September 14, 2020 |
| [Hibernation support for M5a and R5a](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Hibernate.html#hibernating-prerequisites) | You can now hibernate your newly\-launched instances running on M5a and R5a instance types\. | August 28, 2020 |
| [Provisioned IOPS SSD \(io2\) volumes for Amazon EBS](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html#EBSVolumeTypes_piops) | Provisioned IOPS SSD \(`io2`\) volumes are designed to provide 99\.999 percent volume durability with an AFR no higher than 0\.001 percent\. | August 24, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-1 | | [Instance metadata provides instance location and placement information](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html) | New instance metadata fields under the `placement` category: Region, placement group name, partition number, host ID, and Availability Zone ID\. | August 24, 2020 |
| [C5ad instances](#DocumentHistory) | New compute optimized instances featuring second\-generation AMD EYPC processors\. | August 13, 2020 |
| [Wavelength Zones](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-wavelength-zones) | A Wavelength Zone is an isolated zone in the carrier location where the Wavelength infrastructure is deployed\. | August 6, 2020 |
| [Capacity Reservation groups](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-reservations-using.html#create-cr-group) | You can use AWS Resource Groups to create logical collections of Capacity Reservations, and then target instance launches into those groups\. | July 29, 2020 |
| [C6gd, M6gd, and R6gd instances](#DocumentHistory) | New general purpose instances powered by AWS Graviton2 processors, which are based on 64\-bit Arm Neoverse cores and custom silicon designed by AWS for optimized performance and cost\. | July 27, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-2 | | [Fast snapshot restore](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-fast-snapshot-restore.html) | You can enable fast snapshot restore for snaphots that are shared with you\. | July 21, 2020 |
| [C6g and R6g instances](#DocumentHistory) | New general purpose instances powered by AWS Graviton2 processors, which are based on 64\-bit Arm Neoverse cores and custom silicon designed by AWS for optimized performance and cost\. | June 10, 2020 |
| [Bare metal instances for G4](#DocumentHistory) | New instances that provide your applications with direct access to the physical resources of the host server\. | June 5, 2020 |
| [C5a instances](#DocumentHistory) | New compute optimized instances featuring second\-generation AMD EYPC processors\. | June 4, 2020 |
| [Bring your own IPv6 addresses](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-byoip.html) | You can bring part or all of your IPv6 address range from your on\-premises network to your AWS account\. | May 21, 2020 |
| [M6g instances](#DocumentHistory) | New general purpose instances powered by AWS Graviton2 processors, which are based on 64\-bit Arm Neoverse cores and custom silicon designed by AWS for optimized performance and cost\. | May 11, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-3 | | [Launch instances using a Systems Manager parameter](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/finding-an-ami.html#using-systems-manager-parameter-to-find-AMI) | You can specify a AWS Systems Manager parameter instead of an AMI when you launch an instance\. | May 5, 2020 |
| [Customize scheduled event notifications](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html#customizing_scheduled_event_notifications) | You can customize scheduled event notifications to include tags in the email notification\. | May 4, 2020 |
| [Amazon Linux 2 Kernel Live Patching](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/al2-live-patching.html) | Kernel Live Patching for Amazon Linux 2 enables you to apply security vulnerability and critical bug patches to a running Linux kernel, without reboots or disruptions to running applications\. | April 28, 2020 |
| [Amazon EBS Multi\-Attach](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volumes-multi.html) | You can now attach a single Provisioned IOPS SSD \(io1\) volume to up to 16 Nitro\-based instances that are in the same Availability Zone\. | February 14, 2020 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-4 | | [Stop and start a Spot Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-requests.html#stopping-a-spot-instance) | You can now stop your Spot Instances backed by Amazon EBS and start them at will, instead of relying on the stop interruption behavior\. | January 13, 2020 |
| [Resource tagging](#DocumentHistory) | You can tag egress\-only internet gateways, local gateways, local gateway route tables, local gateway virtual interfaces, local gateway virtual interface groups, local gateway route table VPC associations, and local gateway route table virtual interface group associations\. | January 10, 2020 |
| [Connect to your instance using Session Manager](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/session-manager.html) | You can start a Session Manager session with an instance from the Amazon EC2 console\. | December 18, 2019 |
| [Inf1 instances](#DocumentHistory) | New instances featuring AWS Inferentia, a machine learning inference chip designed to deliver high performance at a low cost\. | December 3, 2019 |
| [Dedicated Hosts and host resource groups](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/how-dedicated-hosts-work.html#launching-hrg-instances) | Dedicated Hosts can now be used with host resource groups\. | December 2, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-5 | | [Dedicated Host sharing](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dh-sharing.html) | You can now share your Dedicated Hosts across AWS accounts\. | December 2, 2019 |
| [Default credit specification at the account level](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-how-to.html#burstable-performance-instance-set-default-credit-specification-for-account) | You can set the default credit specification per burstable performance instance family at the account level per AWS Region\. | November 25, 2019 |
| [Instance type discovery](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-discovery.html) | You can find an instance type that meets your needs\. | November 22, 2019 |
| [Dedicated Hosts](#DocumentHistory) | You can now configure a Dedicated Host to support multiple instance types in an instance family\. | November 21, 2019 |
| [Amazon EBS fast snapshot restores](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-fast-snapshot-restore.html) | You can enable fast snapshot restores on an EBS snapshot to ensure that EBS volumes created from the snapshot are fully\-initialized at creation and instantly deliver all of their provisioned performance\. | November 20, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-6 | | [Instance Metadata Service Version 2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-instance-metadata-service.html) | You can use Instance Metadata Service Version 2, which is a session\-oriented method for requesting instance metadata\. | November 19, 2019 |
| [Elastic Fabric Adapter](#DocumentHistory) | Elastic Fabric Adapters can now be used with Intel MPI 2019 Update 6\. | November 15, 2019 |
| [Queued purchases of Reserved Instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ri-market-concepts-buying.html#ri-queued-purchase) | You can queue the purchase of a Reserved Instance up to three years in advance\. | October 4, 2019 |
| [G4 instances](#DocumentHistory) | New instances featuring NVIDIA Tesla GPUs\. | September 19, 2019 |
| [Diagnostic interrupt](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/diagnostic-interrupt.html) | You can send a diagnostic interrupt to an unreachable or unresponsive instance to trigger a kernel panic\. | August 14, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-7 | | [Capacity optimized allocation strategy](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet-configuration-strategies.html#ec2-fleet-strategy-capacity-optimized) | Using EC2 Fleet or Spot Fleet, you can now launch Spot Instances from Spot pools with optimal capacity for the number of instances that are launching\. | August 12, 2019 |
| [On\-Demand Capacity Reservation sharing](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/capacity-reservation-sharing.html) | You can now share your Capacity Reservations across AWS accounts\. | July 29, 2019 |
| [Elastic Fabric Adapter](#DocumentHistory) | EFA now supports Open MPI 3\.1\.4 and Intel MPI 2019 Update 4\. | July 26, 2019 |
| [Resource tagging](#DocumentHistory) | You can tag launch templates on creation\. | July 24, 2019 |
| [EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Connect-using-EC2-Instance-Connect.html) | EC2 Instance Connect is a simple and secure way to connect to your instances using Secure Shell \(SSH\)\. | June 27, 2019 |
| [Host recovery](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-recovery.html) | Automatically restart your instances on a new host in the event of an unexpected hardware failure on a Dedicated Host\. | June 5, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-8 | | [Amazon EBS multi\-volume snapshots](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html#ebs-create-snapshot-multi-volume) | You can take exact point\-in\-time, data coordinated, and crash\-consistent snapshots across multiple EBS volumes attached to an EC2 instance\. | May 29, 2019 |
| [Resource tagging](#DocumentHistory) | You can tag Dedicated Host Reservations\. | May 27, 2019 |
| [Amazon EBS encryption by default](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html#encryption-by-default) | After you enable encryption by default in a Region, all new EBS volumes you create in the Region are encrypted using the default CMK for EBS encryption\. | May 23, 2019 |
| [Resource tagging](#DocumentHistory) | You can tag VPC endpoints, endpoint services, and endpoint service configurations\. | May 13, 2019 |
| [Windows to Linux Replatforming Assistant for Microsoft SQL Server Databases](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/replatform-sql-server.html) | Move existing Microsoft SQL Server workloads from a Windows to a Linux operating system\. | May 8, 2019 |
| [I3en instances](#DocumentHistory) | New I3en instances can utilize up to 100 Gbps of network bandwidth\. | May 8, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
7cdd46e10e8f-9 | | [I3en instances](#DocumentHistory) | New I3en instances can utilize up to 100 Gbps of network bandwidth\. | May 8, 2019 |
| [Elastic Fabric Adapter](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/efa-start.html) | You can attach an Elastic Fabric Adapter to your instances to accelerate High Performance Computing \(HPC\) applications\. | April 29, 2019 |
| [T3a instances](#DocumentHistory) | New instances featuring AMD EYPC processors\. | April 24, 2019 |
| [M5ad and R5ad instances](#DocumentHistory) | New instances featuring AMD EYPC processors\. | March 27, 2019 |
| [Resource tagging](#DocumentHistory) | You can assign custom tags to your Dedicated Host Reservations to categorize them in different ways\. | March 14, 2019 |
| [Bare metal instances for M5, M5d, R5, R5d, and z1d](#DocumentHistory) | New instances that provide your applications with direct access to the physical resources of the host server\. | February 13, 2019 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-0 | The following table describes important additions to the Amazon EC2 documentation in 2018 and earlier years\.
| Feature | API version | Description | Release date |
| --- | --- | --- | --- |
| <a name="history-2018"></a>Partition placement groups | 2016\-11\-15 | Partition placement groups spread instances across logical partitions, ensuring that instances in one partition do not share underlying hardware with instances in other partitions\. For more information, see [Partition placement groups](placement-groups.md#placement-groups-partition)\. | 20 December 2018 |
| p3dn\.24xlarge instances | 2016\-11\-15 | New p3dn\.24xlarge instances provide 100 Gbps of network bandwidth\. | 7 December 2018 |
| Hibernate EC2 Linux instances | 2016\-11\-15 | You can hibernate a Linux instance if it's enabled for hibernation and it meets the hibernation prerequisites\. For more information, see [Hibernate your Linux instance](Hibernate.md)\. | 28 November 2018 |
| Amazon Elastic Inference Accelerators | 2016\-11\-15 | You can attach an Amazon EI accelerator to your instances to add GPU\-powered acceleration to reduce the cost of running deep learning inference\. For more information, see [Amazon Elastic Inference](elastic-inference.md)\. | 28 November 2018 |
| Instances featuring 100 Gbps of network bandwidth | 2016\-11\-15 | New C5n instances can utilize up to 100 Gbps of network bandwidth\. | 26 November 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-1 | | Instances featuring Arm\-based Processors | 2016\-11\-15 | New A1 instances deliver significant cost savings and are ideally suited for scale\-out and Arm\-based workloads\. | 26 November 2018 |
| Spot console recommends a fleet of instances | 2016\-11\-15 | The Spot console recommends a fleet of instances based on Spot best practice \(instance diversification\) to meet the minimum hardware specifications \(vCPUs, memory, and storage\) for your application need\. For more information, see [Creating a Spot Fleet request](spot-fleet-requests.md#create-spot-fleet)\. | 20 November 2018 |
| New EC2 Fleet request type: instant | 2016\-11\-15 | EC2 Fleet now supports a new request type, instant, that you can use to synchronously provision capacity across instance types and purchase models\. The instant request returns the launched instances in the API response, and takes no further action, enabling you to control if and when instances are launched\. For more information, see [EC2 Fleet request types](ec2-fleet-configuration-strategies.md#ec2-fleet-request-type)\. | 14 November 2018 |
| Instances featuring AMD EYPC processors | 2016\-11\-15 | New general purpose \(M5a\) and memory optimized instances \(R5a\) offer lower\-priced options for microservices, small to medium databases, virtual desktops, development and test environments, business applications, and more\. | 6 November 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-2 | | Spot savings information | 2016\-11\-15 | You can view the savings made from using Spot Instances for a single Spot Fleet or for all Spot Instances\. For more information, see [Savings from purchasing Spot Instances](spot-savings.md)\. | 5 November 2018 |
| Console support for optimizing CPU options | 2016\-11\-15 | When you launch an instance, you can optimize the CPU options to suit specific workloads or business needs using the Amazon EC2 console\. For more information, see [Optimizing CPU options](instance-optimize-cpu.md)\. | 31 October 2018 |
| Console support for creating a launch template from an instance | 2016\-11\-15 | You can create a launch template using an instance as the basis for a new launch template using the Amazon EC2 console\. For more information, see [Creating a launch template](ec2-launch-templates.md#create-launch-template)\. | 30 October 2018 |
| On\-Demand Capacity Reservations | 2016\-11\-15 | You can reserve capacity for your Amazon EC2 instances in a specific Availability Zone for any duration\. This allows you to create and manage capacity reservations independently from the billing discounts offered by Reserved Instances \(RI\)\. For more information, see [On\-Demand Capacity Reservations](ec2-capacity-reservations.md)\. | 25 October 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-3 | | Bring Your Own IP Addresses \(BYOIP\) | 2016\-11\-15 | You can bring part or all of your public IPv4 address range from your on\-premises network to your AWS account\. After you bring the address range to AWS, it appears in your account as an address pool\. You can create an Elastic IP address from your address pool and use it with your AWS resources\. For more information, see [Bring your own IP addresses \(BYOIP\) in Amazon EC2](ec2-byoip.md)\. | 23 October 2018 |
| g3s\.xlarge instances | 2016\-11\-15 | Expands the range of the accelerated\-computing G3 instance family with the introduction of g3s\.xlarge instances\. | 11 October 2018 |
| Dedicated Host tag on create and console support | 2016\-11\-15 | You can tag your Dedicated Hosts on creation, and you can manage your Dedicated Host tags using the Amazon EC2 console\. For more information, see [Allocating Dedicated Hosts](how-dedicated-hosts-work.md#dedicated-hosts-allocating)\. | 08 October 2018 |
| High memory instances | 2016\-11\-15 | These instances are purpose\-built to run large in\-memory databases\. They offer bare metal performance with direct access to host hardware\. For more information, see [Memory optimized instances](memory-optimized-instances.md)\. | 27 September 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-4 | | f1\.4xlarge instances | 2016\-11\-15 | Expands the range of the accelerated\-computing F1 instance family with the introduction of f1\.4xlarge instances\. | 25 September 2018 |
| Console support for scheduled scaling for Spot Fleet | 2016\-11\-15 | Increase or decrease the current capacity of the fleet based on the date and time\. For more information, see [Scale Spot Fleet using scheduled scaling](spot-fleet-scheduled-scaling.md)\. | 20 September 2018 |
| T3 instances | 2016\-11\-15 | T3 instances are the next generation burstable general\-purpose instance type that provide a baseline level of CPU performance with the ability to burst CPU usage at any time for as long as required\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | 21 August 2018 |
| Allocation strategies for EC2 Fleets | 2016\-11\-15 | You can specify whether On\-Demand capacity is fulfilled by price \(lowest price first\) or priority \(highest priority first\)\. You can specify the number of Spot pools across which to allocate your target Spot capacity\. For more information, see [Allocation strategies for Spot Instances](ec2-fleet-configuration-strategies.md#ec2-fleet-allocation-strategy)\. | 26 July 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-5 | | Allocation strategies for Spot Fleets | 2016\-11\-15 | You can specify whether On\-Demand capacity is fulfilled by price \(lowest price first\) or priority \(highest priority first\)\. You can specify the number of Spot pools across which to allocate your target Spot capacity\. For more information, see [Allocation strategy for Spot Instances](spot-fleet.md#spot-fleet-allocation-strategy)\. | 26 July 2018 |
| R5 and R5d instances | 2016\-11\-15 | R5 and R5d instances are ideally suited for high\-performance databases, distributed in\-memory caches, and in\-memory analytics\. R5d instances come with NVMe instance store volumes\. For more information, see [Memory optimized instances](memory-optimized-instances.md)\. | 25 July 2018 |
| z1d instances | 2016\-11\-15 | These instances are designed for applications that require high per\-core performance with a large amount of memory, such as electronic design automation \(EDA\) and relational databases\. These instances come with NVME instance store volumes\. For more information, see [Memory optimized instances](memory-optimized-instances.md)\. | 25 July 2018 |
| Automate snapshot lifecycle | 2016\-11\-15 | You can use Amazon Data Lifecycle Manager to automate creation and deletion of snapshots for your EBS volumes\. For more information, see [Automating the Amazon EBS snapshot lifecycle](snapshot-lifecycle.md)\. | 12 July 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-6 | | Launch template CPU options | 2016\-11\-15 | When you create a launch template using the command line tools, you can optimize the CPU options to suit specific workloads or business needs\. For more information, see [Creating a launch template](ec2-launch-templates.md#create-launch-template)\. | 11 July 2018 |
| Tag Dedicated Hosts | 2016\-11\-15 | You can tag your Dedicated Hosts\. For more information, see [Tagging Dedicated Hosts](how-dedicated-hosts-work.md#dedicated-hosts-tagging)\. | 3 July 2018 |
| i3\.metal instances | 2016\-11\-15 | `i3.metal` instances provide your applications with direct access to the physical resources of the host server, such as processors and memory\. For more information, see [Storage optimized instances](storage-optimized-instances.md)\. | 17 May 2018 |
| Get latest console output | 2016\-11\-15 | You can retrieve the latest console output for some instance types when you use the [get\-console\-output](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-console-output.html) AWS CLI command\. | 9 May 2018 |
| Optimize CPU options | 2016\-11\-15 | When you launch an instance, you can optimize the CPU options to suit specific workloads or business needs\. For more information, see [Optimizing CPU options](instance-optimize-cpu.md)\. | 8 May 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-7 | | EC2 Fleet | 2016\-11\-15 | You can use EC2 Fleet to launch a group of instances across different EC2 instance types and Availability Zones, and across On\-Demand Instance, Reserved Instance, and Spot Instance purchasing models\. For more information, see [Launching instances using an EC2 Fleet](ec2-fleet.md)\. | 2 May 2018 |
| On\-Demand Instances in Spot Fleets | 2016\-11\-15 | You can include a request for On\-Demand capacity in your Spot Fleet request to ensure that you always have instance capacity\. For more information, see [How Spot Fleet works](spot-fleet.md)\. | 2 May 2018 |
| Tag EBS snapshots on creation | 2016\-11\-15 | You can apply tags to snapshots during creation\. For more information, see [Creating Amazon EBS snapshots](ebs-creating-snapshot.md)\. | 2 April 2018 |
| Change placement groups | 2016\-11\-15 | You can move an instance in or out of a placement group, or change its placement group\. For more information, see [Changing the placement group for an instance](placement-groups.md#change-instance-placement-group)\. | 1 March 2018 |
| Longer resource IDs | 2016\-11\-15 | You can enable the longer ID format for more resource types\. For more information, see [Resource IDs](resource-ids.md)\. | 9 February 2018 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-8 | | Network performance improvements | 2016\-11\-15 | Instances outside of a cluster placement group can now benefit from increased bandwidth when sending or receiving network traffic between other instances or Amazon S3\. For more information, see [Networking and storage features](instance-types.md#instance-networking-storage)\. | 24 January 2018 |
| <a name="history-2017"></a> Tag Elastic IP addresses | 2016\-11\-15 | You can tag your Elastic IP addresses\. For more information, see [Tagging an Elastic IP address](elastic-ip-addresses-eip.md#using-instance-addressing-eips-tagging)\. | 21 December 2017 |
| Amazon Linux 2 | 2016\-11\-15 | Amazon Linux 2 is a new version of Amazon Linux\. It provides a high performance, stable, and secure foundation for your applications\. For more information, see [Amazon Linux](amazon-linux-ami-basics.md)\. | 13 December 2017 |
| Amazon Time Sync Service | 2016\-11\-15 | You can use the Amazon Time Sync Service to keep accurate time on your instance\. For more information, see [Setting the time for your Linux instance](set-time.md)\. | 29 November 2017 |
| T2 Unlimited | 2016\-11\-15 | T2 Unlimited instances can burst above the baseline for as long as required\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | 29 November 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-9 | | Launch templates | 2016\-11\-15 | A launch template can contain all or some of the parameters to launch an instance, so that you don't have to specify them every time you launch an instance\. For more information, see [Launching an instance from a launch template](ec2-launch-templates.md)\. | 29 November 2017 |
| Spread placement | 2016\-11\-15 | Spread placement groups are recommended for applications that have a small number of critical instances that should be kept separate from each other\. For more information, see [Spread placement groups](placement-groups.md#placement-groups-spread)\. | 29 November 2017 |
| H1 instances | 2016\-11\-15 | H1 instances are designed for high\-performance big data workloads\. For more information, see [Storage optimized instances](storage-optimized-instances.md)\. | 28 November 2017 |
| M5 instances | 2016\-11\-15 | M5 instances are the next generation of general purpose compute instances\. They provide a balance of compute, memory, storage, and network resources\. | 28 November 2017 |
| Spot Instance hibernation | 2016\-11\-15 | The Spot service can hibernate Spot Instances in the event of an interruption\. For more information, see [Hibernating interrupted Spot Instances](spot-interruptions.md#hibernate-spot-instances)\. | 28 November 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-10 | | Spot Fleet target tracking | 2016\-11\-15 | You can set up target tracking scaling policies for your Spot Fleet\. For more information, see [Scale Spot Fleet using a target tracking policy](spot-fleet-target-tracking.md)\. | 17 November 2017 |
| Spot Fleet integrates with Elastic Load Balancing | 2016\-11\-15 | You can attach one or more load balancers to a Spot Fleet\. | 10 November 2017 |
| X1e instances | 2016\-11\-15 | X1e instances are ideally suited for high\-performance databases, in\-memory databases, and other memory\-intensive enterprise applications\. For more information, see [Memory optimized instances](memory-optimized-instances.md)\. | 28 November 2017 |
| C5 instances | 2016\-11\-15 | C5 instances are designed for compute\-heavy applications\. For more information, see [Compute optimized instances](compute-optimized-instances.md)\. | 6 November 2017 |
| Merge and split Convertible Reserved Instances | 2016\-11\-15 | You can exchange \(merge\) two or more Convertible Reserved Instances for a new Convertible Reserved Instance\. You can also use the modification process to split a Convertible Reserved Instance into smaller reservations\. For more information, see [Exchanging Convertible Reserved Instances](ri-convertible-exchange.md)\. | 6 November 2017 |
| P3 instances | 2016\-11\-15 | P3 instances are the next generation of compute\-optimized GPU instances\. For more information, see [Linux accelerated computing instances](accelerated-computing-instances.md)\. | 25 October 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-11 | | Modify VPC tenancy | 2016\-11\-15 | You can change the instance tenancy attribute of a VPC from `dedicated` to `default`\. For more information, see [Changing the Tenancy of a VPC](dedicated-instance.md#change-tenancy-vpc)\. | 16 October 2017 |
| Per second billing | 2016\-11\-15 | Amazon EC2 charges for Linux\-based usage by the second, with a one\-minute minimum charge\. | 2 October 2017 |
| Stop on interruption | 2016\-11\-15 | You can specify whether Amazon EC2 should stop or terminate Spot Instances when they are interrupted\. For more information, see [Interruption behaviors](spot-interruptions.md#interruption-behavior)\. | 18 September 2017 |
| Tag NAT gateways | 2016\-11\-15 | You can tag your NAT gateway\. For more information, see [Tagging your resources](Using_Tags.md#tag-resources)\. | 7 September 2017 |
| Security group rule descriptions | 2016\-11\-15 | You can add descriptions to your security group rules\. For more information, see [Security group rules](ec2-security-groups.md#security-group-rules)\. | 31 August 2017 |
| Recover Elastic IP addresses | 2016\-11\-15 | If you release an Elastic IP address for use in a VPC, you might be able to recover it\. For more information, see [Recovering an Elastic IP address](elastic-ip-addresses-eip.md#using-eip-recovering)\. | 11 August 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-12 | | Tag Spot Fleet instances | 2016\-11\-15 | You can configure your Spot Fleet to automatically tag the instances that it launches\. | 24 July 2017 |
| G3 instances | 2016\-11\-15 | G3 instances provide a cost\-effective, high\-performance platform for graphics applications using DirectX or OpenGL\. G3 instances also provide NVIDIA GRID Virtual Workstation features, supporting 4 monitors with resolutions up to 4096x2160\. For more information, see [Linux accelerated computing instances](accelerated-computing-instances.md)\. | 13 July 2017 |
| F1 instances | 2016\-11\-15 | F1 instances represent the next generation of accelerated computing instances\. For more information, see [Linux accelerated computing instances](accelerated-computing-instances.md)\. | 19 April 2017 |
| Tag resources during creation | 2016\-11\-15 | You can apply tags to instances and volumes during creation\. For more information, see [Tagging your resources](Using_Tags.md#tag-resources)\. In addition, you can use tag\-based resource\-level permissions to control the tags that are applied\. For more information see, [Granting permission to tag resources during creation](supported-iam-actions-tagging.md)\. | 28 March 2017 |
| I3 instances | 2016\-11\-15 | I3 instances represent the next generation of storage optimized instances\. For more information, see [Storage optimized instances](storage-optimized-instances.md)\. | 23 February 2017 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-13 | | Perform modifications on attached EBS volumes | 2016\-11\-15 | With most EBS volumes attached to most EC2 instances, you can modify volume size, type, and IOPS without detaching the volume or stopping the instance\. For more information, see [Amazon EBS Elastic Volumes](ebs-modify-volume.md)\. | 13 February 2017 |
| Attach an IAM role | 2016\-11\-15 | You can attach, detach, or replace an IAM role for an existing instance\. For more information, see [IAM roles for Amazon EC2](iam-roles-for-amazon-ec2.md)\. | 9 February 2017 |
| Dedicated Spot Instances | 2016\-11\-15 | You can run Spot Instances on single\-tenant hardware in a virtual private cloud \(VPC\)\. For more information, see [Specifying a tenancy for your Spot Instances](spot-requests.md#spot-instance-tenancy)\. | 19 January 2017 |
| IPv6 support | 2016\-11\-15 | You can associate an IPv6 CIDR with your VPC and subnets, and assign IPv6 addresses to instances in your VPC\. For more information, see [Amazon EC2 instance IP addressing](using-instance-addressing.md)\. | 1 December 2016 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-14 | | R4 instances | 2016\-09\-15 | R4 instances represent the next generation of memory optimized instances\. R4 instances are well\-suited for memory\-intensive, latency\-sensitive workloads such as business intelligence \(BI\), data mining and analysis, in\-memory databases, distributed web scale in\-memory caching, and applications performance real\-time processing of unstructured big data\. For more information, see [Memory optimized instances](memory-optimized-instances.md) | 30 November 2016 |
| New `t2.xlarge` and `t2.2xlarge` instance types | 2016\-09\-15 | T2 instances are designed to provide moderate base performance and the capability to burst to significantly higher performance as required by your workload\. They are intended for applications that need responsiveness, high performance for limited periods of time, and a low cost\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | 30 November 2016 |
| P2 instances | 2016\-09\-15 | P2 instances use NVIDIA Tesla K80 GPUs and are designed for general purpose GPU computing using the CUDA or OpenCL programming models\. For more information, see [Linux accelerated computing instances](accelerated-computing-instances.md)\. | 29 September 2016 |
| m4\.16xlarge instances | 2016\-04\-01 | Expands the range of the general\-purpose M4 family with the introduction of `m4.16xlarge` instances, with 64 vCPUs and 256 GiB of RAM\. | 6 September 2016 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-15 | | Automatic scaling for Spot Fleet | | You can now set up scaling policies for your Spot Fleet\. For more information, see [Automatic scaling for Spot Fleet](spot-fleet-automatic-scaling.md)\. | 1 September 2016 |
| Elastic Network Adapter \(ENA\) | 2016\-04\-01 | You can now use ENA for enhanced networking\. For more information, see [Enhanced networking types](enhanced-networking.md#supported_instances)\. | 28 June 2016 |
| Enhanced support for viewing and modifying longer IDs | 2016\-04\-01 | You can now view and modify longer ID settings for other IAM users, IAM roles, or the root user\. For more information, see [Resource IDs](resource-ids.md)\. | 23 June 2016 |
| Copy encrypted Amazon EBS snapshots between AWS accounts | 2016\-04\-01 | You can now copy encrypted EBS snapshots between AWS accounts\. For more information, see [Copying an Amazon EBS snapshot](ebs-copy-snapshot.md)\. | 21 June 2016 |
| Capture a screenshot of an instance console | 2015\-10\-01 | You can now obtain additional information when debugging instances that are unreachable\. For more information, see [Capture a screenshot of an unreachable instance](instance-console.md#instance-console-screenshot)\. | 24 May 2016 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-16 | | X1 instances | 2015\-10\-01 | Memory\-optimized instances designed for running in\-memory databases, big data processing engines, and high performance computing \(HPC\) applications\. For more information, see [Memory optimized instances](memory-optimized-instances.md)\. | 18 May 2016 |
| Two new EBS volume types | 2015\-10\-01 | You can now create Throughput Optimized HDD \(st1\) and Cold HDD \(sc1\) volumes\. For more information, see [Amazon EBS volume types](ebs-volume-types.md)\. | 19 April 2016 |
| Added new NetworkPacketsIn and NetworkPacketsOut metrics for Amazon EC2 | | Added new NetworkPacketsIn and NetworkPacketsOut metrics for Amazon EC2\. For more information, see [Instance metrics](viewing_metrics_with_cloudwatch.md#ec2-cloudwatch-metrics)\. | 23 March 2016 |
| CloudWatch metrics for Spot Fleet | | You can now get CloudWatch metrics for your Spot Fleet\. For more information, see [CloudWatch metrics for Spot Fleet](spot-fleet-cloudwatch-metrics.md)\. | 21 March 2016 |
| Scheduled Instances | 2015\-10\-01 | Scheduled Reserved Instances \(Scheduled Instances\) enable you to purchase capacity reservations that recur on a daily, weekly, or monthly basis, with a specified start time and duration\. For more information, see [Scheduled Reserved Instances](ec2-scheduled-instances.md)\. | 13 January 2016 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-17 | | Longer resource IDs | 2015\-10\-01 | We're gradually introducing longer length IDs for some Amazon EC2 and Amazon EBS resource types\. During the opt\-in period, you can enable the longer ID format for supported resource types\. For more information, see [Resource IDs](resource-ids.md)\. | 13 January 2016 |
| ClassicLink DNS support | 2015\-10\-01 | You can enable ClassicLink DNS support for your VPC so that DNS hostnames that are addressed between linked EC2\-Classic instances and instances in the VPC resolve to private IP addresses and not public IP addresses\. For more information, see [Enabling ClassicLink DNS support](vpc-classiclink.md#classiclink-enable-dns-support)\. | 11 January 2016 |
| New `t2.nano` instance type | 2015\-10\-01 | T2 instances are designed to provide moderate base performance and the capability to burst to significantly higher performance as required by your workload\. They are intended for applications that need responsiveness, high performance for limited periods of time, and a low cost\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | 15 December 2015 |
| Dedicated hosts | 2015\-10\-01 | An Amazon EC2 Dedicated host is a physical server with instance capacity dedicated for your use\. For more information, see [Dedicated Hosts](dedicated-hosts-overview.md)\. | 23 November 2015 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-18 | | Spot Instance duration | 2015\-10\-01 | You can now specify a duration for your Spot Instances\. For more information, see [Defining a duration for your Spot Instances](spot-requests.md#fixed-duration-spot-instances)\. | 6 October 2015 |
| Spot Fleet modify request | 2015\-10\-01 | You can now modify the target capacity of your Spot Fleet request\. For more information, see [Modifying a Spot Fleet request](spot-fleet-requests.md#modify-spot-fleet)\. | 29 September 2015 |
| Spot Fleet diversified allocation strategy | 2015\-04\-15 | You can now allocate Spot Instances in multiple Spot pools using a single Spot Fleet request\. For more information, see [Allocation strategy for Spot Instances](spot-fleet.md#spot-fleet-allocation-strategy)\. | 15 September 2015 |
| Spot Fleet instance weighting | 2015\-04\-15 | You can now define the capacity units that each instance type contributes to your application's performance, and adjust the amount you are willing to pay for Spot Instances for each Spot pool accordingly\. For more information, see [Spot Fleet instance weighting](spot-fleet.md#spot-instance-weighting)\. | 31 August 2015 |
| New reboot alarm action and new IAM role for use with alarm actions | | Added the reboot alarm action and new IAM role for use with alarm actions\. For more information, see [Create alarms that stop, terminate, reboot, or recover an instance](UsingAlarmActions.md)\. | 23 July 2015 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-19 | | New `t2.large` instance type | | T2 instances are designed to provide moderate base performance and the capability to burst to significantly higher performance as required by your workload\. They are intended for applications that need responsiveness, high performance for limited periods of time, and a low cost\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | 16 June 2015 |
| M4 instances | | The next generation of general\-purpose instances that provide a balance of compute, memory, and network resources\. M4 instances are powered by a custom Intel 2\.4 GHz Intel® Xeon® E5 2676v3 \(Haswell\) processor with AVX2\. | 11 June 2015 |
| Spot Fleets | 2015\-04\-15 | You can manage a collection, or fleet, of Spot Instances instead of managing separate Spot Instance requests\. For more information, see [How Spot Fleet works](spot-fleet.md)\. | 18 May 2015 |
| Migrate Elastic IP addresses to EC2\-Classic | 2015\-04\-15 | You can migrate an Elastic IP address that you've allocated for use in EC2\-Classic to be used in a VPC\. For more information, see [Migrating an Elastic IP Address from EC2\-Classic](ec2-classic-platform.md#migrating-eip)\. | 15 May 2015 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-20 | | Importing VMs with multiple disks as AMIs | 2015\-03\-01 | The VM Import process now supports importing VMs with multiple disks as AMIs\. For more information, see [Importing a VM as an Image Using VM Import/Export](https://docs.aws.amazon.com/vm-import/latest/userguide/vmimport-image-import.html) in the * VM Import/Export User Guide* \. | 23 April 2015 |
| New `g2.8xlarge` instance type | | The new `g2.8xlarge` instance is backed by four high\-performance NVIDIA GPUs, making it well suited for GPU compute workloads including large scale rendering, transcoding, machine learning, and other server\-side workloads that require massive parallel processing power\. | 7 April 2015 |
| D2 instances | | Next generation Amazon EC2 dense\-storage instances that are optimized for applications requiring sequential access to large amount of data on direct attached instance storage\. D2 instances are designed to offer best price/performance in the dense\-storage family\. Powered by 2\.4 GHz Intel® Xeon® E5 2676v3 \(Haswell\) processors, D2 instances improve on HS1 instances by providing additional compute power, more memory, and Enhanced Networking\. In addition, D2 instances are available in four instance sizes with 6TB, 12TB, 24TB, and 48TB storage options\. For more information, see [Storage optimized instances](storage-optimized-instances.md)\. | 24 March 2015 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-21 | | Automatic recovery for EC2 instances | | You can create an Amazon CloudWatch alarm that monitors an Amazon EC2 instance and automatically recovers the instance if it becomes impaired due to an underlying hardware failure or a problem that requires AWS involvement to repair\. A recovered instance is identical to the original instance, including the instance ID, IP addresses, and all instance metadata\. For more information, see [Recover your instance](ec2-instance-recover.md)\. | 12 January 2015 |
| C4 instances | | Next\-generation compute\-optimized instances that provide very high CPU performance at an economical price\. C4 instances are based on custom 2\.9 GHz Intel® Xeon® E5\-2666 v3 \(Haswell\) processors\. With additional Turbo boost, the processor clock speed in C4 instances can reach as high as 3\.5Ghz with 1 or 2 core turbo\. Expanding on the capabilities of C3 compute\-optimized instances, C4 instances offer customers the highest processor performance among EC2 instances\. These instances are ideally suited for high\-traffic web applications, ad serving, batch processing, video encoding, distributed analytics, high\-energy physics, genome analysis, and computational fluid dynamics\. For more information, see [Compute optimized instances](compute-optimized-instances.md)\. | 11 January 2015 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-22 | | ClassicLink | 2014\-10\-01 | ClassicLink enables you to link your EC2\-Classic instance to a VPC in your account\. You can associate VPC security groups with the EC2\-Classic instance, enabling communication between your EC2\-Classic instance and instances in your VPC using private IP addresses\. For more information, see [ClassicLink](vpc-classiclink.md)\. | 7 January 2015 |
| Spot Instance termination notices | | The best way to protect against Spot Instance interruption is to architect your application to be fault tolerant\. In addition, you can take advantage of Spot Instance termination notices, which provide a two\-minute warning before Amazon EC2 must terminate your Spot Instance\. For more information, see [Spot Instance interruption notices](spot-interruptions.md#spot-instance-termination-notices)\. | 5 January 2015 |
| `DescribeVolumes` pagination support | 2014\-09\-01 | The `DescribeVolumes` API call now supports the pagination of results with the `MaxResults` and `NextToken` parameters\. For more information, see [DescribeVolumes](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeVolumes.html) in the *Amazon EC2 API Reference*\. | 23 October 2014 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-23 | | T2 instances | 2014\-06\-15 | T2 instances are designed to provide moderate base performance and the capability to burst to significantly higher performance as required by your workload\. They are intended for applications that need responsiveness, high performance for limited periods of time, and a low cost\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | 30 June 2014 |
| New EC2 Service Limits page | | Use the **EC2 Service Limits** page in the Amazon EC2 console to view the current limits for resources provided by Amazon EC2 and Amazon VPC, on a per\-region basis\. | 19 June 2014 |
| Amazon EBS General Purpose SSD Volumes | 2014\-05\-01 | General Purpose SSD volumes offer cost\-effective storage that is ideal for a broad range of workloads\. These volumes deliver single\-digit millisecond latencies, the ability to burst to 3,000 IOPS for extended periods of time, and a base performance of 3 IOPS/GiB\. General Purpose SSD volumes can range in size from 1 GiB to 1 TiB\. For more information, see [General Purpose SSD \(`gp2`\) volumes](ebs-volume-types.md#EBSVolumeTypes_gp2)\. | 16 June 2014 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-24 | | Amazon EBS encryption | 2014\-05\-01 | Amazon EBS encryption offers seamless encryption of EBS data volumes and snapshots, eliminating the need to build and maintain a secure key management infrastructure\. EBS encryption enables data at rest security by encrypting your data using Amazon\-managed keys\. The encryption occurs on the servers that host EC2 instances, providing encryption of data as it moves between EC2 instances and EBS storage\. For more information, see [Amazon EBS encryption](EBSEncryption.md)\. | 21 May 2014 |
| R3 instances | 2014\-02\-01 | Next generation memory\-optimized instances with the best price point per GiB of RAM and high performance\. These instances are ideally suited for relational and NoSQL databases, in\-memory analytics solutions, scientific computing, and other memory\-intensive applications that can benefit from the high memory per vCPU, high compute performance, and enhanced networking capabilities of R3 instances\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\. | 9 April 2014 |
| New Amazon Linux AMI release | | Amazon Linux AMI 2014\.03 is released\. | 27 March 2014 |
| Amazon EC2 Usage Reports | | Amazon EC2 Usage Reports is a set of reports that shows cost and usage data of your usage of EC2\. For more information, see [Amazon EC2 usage reports](usage-reports.md)\. | 28 January 2014 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-25 | | Additional M3 instances | 2013\-10\-15 | The M3 instance sizes `m3.medium` and `m3.large` are now supported\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\. | 20 January 2014 |
| I2 instances | 2013\-10\-15 | These instances provide very high IOPS and support TRIM on Linux instances for better successive SSD write performance\. I2 instances also support enhanced networking that delivers improve inter\-instance latencies, lower network jitter, and significantly higher packet per second \(PPS\) performance\. For more information, see [Storage optimized instances](storage-optimized-instances.md)\. | 19 December 2013 |
| Updated M3 instances | 2013\-10\-15 | The M3 instance sizes, `m3.xlarge` and `m3.2xlarge` now support instance store with SSD volumes\. | 19 December 2013 |
| Importing Linux virtual machines | 2013\-10\-15 | The VM Import process now supports the importation of Linux instances\. For more information, see the [ VM Import/Export User Guide](https://docs.aws.amazon.com/vm-import/latest/userguide/)\. | 16 December 2013 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-26 | | Resource\-level permissions for RunInstances | 2013\-10\-15 | You can now create policies in AWS Identity and Access Management to control resource\-level permissions for the Amazon EC2 RunInstances API action\. For more information and example policies, see [Identity and access management for Amazon EC2](security-iam.md)\. | 20 November 2013 |
| C3 instances | 2013\-10\-15 | Compute\-optimized instances that provide very high CPU performance at an economical price\. C3 instances also support enhanced networking that delivers improved inter\-instance latencies, lower network jitter, and significantly higher packet per second \(PPS\) performance\. These instances are ideally suited for high\-traffic web applications, ad serving, batch processing, video encoding, distributed analytics, high\-energy physics, genome analysis, and computational fluid dynamics\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\. | 14 November 2013 |
| Launching an instance from the AWS Marketplace | | You can now launch an instance from the AWS Marketplace using the Amazon EC2 launch wizard\. For more information, see [Launching an AWS Marketplace instance](launch-marketplace-console.md)\. | 11 November 2013 |
| G2 instances | 2013\-10\-01 | These instances are ideally suited for video creation services, 3D visualizations, streaming graphics\-intensive applications, and other server\-side workloads requiring massive parallel processing power\. For more information, see [Linux accelerated computing instances](accelerated-computing-instances.md)\. | 4 November 2013 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-27 | | New launch wizard | | There is a new and redesigned EC2 launch wizard\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\. | 10 October 2013 |
| Modifying Instance Types of Amazon EC2 Reserved Instances | 2013\-10\-01 | You can now modify the instance type of Linux Reserved Instances within the same family \(for example, M1, M2, M3, C1\)\. For more information, see [Modifying Reserved Instances](ri-modifying.md)\. | 09 October 2013 |
| New Amazon Linux AMI release | | Amazon Linux AMI 2013\.09 is released\. | 30 September 2013 |
| Modifying Amazon EC2 Reserved Instances | 2013\-08\-15 | You can now modify Reserved Instances in a Region\. For more information, see [Modifying Reserved Instances](ri-modifying.md)\. | 11 September 2013 |
| Assigning a public IP address | 2013\-07\-15 | You can now assign a public IP address when you launch an instance in a VPC\. For more information, see [Assigning a public IPv4 address during instance launch](using-instance-addressing.md#public-ip-addresses)\. | 20 August 2013 |
| Granting resource\-level permissions | 2013\-06\-15 | Amazon EC2 supports new Amazon Resource Names \(ARNs\) and condition keys\. For more information, see [IAM policies for Amazon EC2](iam-policies-for-amazon-ec2.md)\. | 8 July 2013 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-28 | | Incremental Snapshot Copies | 2013\-02\-01 | You can now perform incremental snapshot copies\. For more information, see [Copying an Amazon EBS snapshot](ebs-copy-snapshot.md)\. | 11 June 2013 |
| New **Tags** page | | There is a new **Tags** page in the Amazon EC2 console\. For more information, see [Tagging your Amazon EC2 resources](Using_Tags.md)\. | 04 April 2013 |
| New Amazon Linux AMI release | | Amazon Linux AMI 2013\.03 is released\. | 27 March 2013 |
| Additional EBS\-optimized instance types | 2013\-02\-01 | The following instance types can now be launched as EBS\-optimized instances: `c1.xlarge`, `m2.2xlarge`, `m3.xlarge`, and `m3.2xlarge`\. For more information, see [Amazon EBS–optimized instances](ebs-optimized.md)\. | 19 March 2013 |
| Copy an AMI from one Region to another | 2013\-02\-01 | You can copy an AMI from one Region to another, enabling you to launch consistent instances in more than one AWS Region quickly and easily\. For more information, see [Copying an AMI](CopyingAMIs.md)\. | 11 March 2013 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-29 | | Launch instances into a default VPC | 2013\-02\-01 | Your AWS account is capable of launching instances into either EC2\-Classic or a VPC, or only into a VPC, on a region\-by\-region basis\. If you can launch instances only into a VPC, we create a default VPC for you\. When you launch an instance, we launch it into your default VPC, unless you create a nondefault VPC and specify it when you launch the instance\. | 11 March 2013 |
| High\-memory cluster \(cr1\.8xlarge\) instance type | 2012\-12\-01 | Have large amounts of memory coupled with high CPU and network performance\. These instances are well suited for in\-memory analytics, graph analysis, and scientific computing applications\. | 21 January 2013 |
| High storage \(`hs1.8xlarge`\) instance type | 2012\-12\-01 | High storage instances provide very high storage density and high sequential read and write performance per instance\. They are well\-suited for data warehousing, Hadoop/MapReduce, and parallel file systems\. | 20 December 2012 |
| EBS snapshot copy | 2012\-12\-01 | You can use snapshot copies to create backups of data, to create new Amazon EBS volumes, or to create Amazon Machine Images \(AMIs\)\. For more information, see [Copying an Amazon EBS snapshot](ebs-copy-snapshot.md)\. | 17 December 2012 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-30 | | Updated EBS metrics and status checks for Provisioned IOPS SSD volumes | 2012\-10\-01 | Updated the EBS metrics to include two new metrics for Provisioned IOPS SSD volumes\. For more information, see [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md)\. Also added new status checks for Provisioned IOPS SSD volumes\. For more information, see [EBS volume status checks](monitoring-volume-status.md#monitoring-volume-checks)\. | 20 November 2012 |
| Linux Kernels | | Updated AKI IDs; reorganized distribution kernels; updated PVOps section\. | 13 November 2012 |
| M3 instances | 2012\-10\-01 | There are new M3 extra\-large and M3 double\-extra\-large instance types\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\. | 31 October 2012 |
| Spot Instance request status | 2012\-10\-01 | Spot Instance request status makes it easy to determine the state of your Spot requests\. | 14 October 2012 |
| New Amazon Linux AMI release | | Amazon Linux AMI 2012\.09 is released\. | 11 October 2012 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-31 | | New Amazon Linux AMI release | | Amazon Linux AMI 2012\.09 is released\. | 11 October 2012 |
| Amazon EC2 Reserved Instance Marketplace | 2012\-08\-15 | The Reserved Instance Marketplace matches sellers who have Amazon EC2 Reserved Instances that they no longer need with buyers who are looking to purchase additional capacity\. Reserved Instances bought and sold through the Reserved Instance Marketplace work like any other Reserved Instances, except that they can have less than a full standard term remaining and can be sold at different prices\. | 11 September 2012 |
| Provisioned IOPS SSD for Amazon EBS | 2012\-07\-20 | Provisioned IOPS SSD volumes deliver predictable, high performance for I/O intensive workloads, such as database applications, that rely on consistent and fast response times\. For more information, see [Amazon EBS volume types](ebs-volume-types.md)\. | 31 July 2012 |
| High I/O instances for Amazon EC2 | 2012\-06\-15 | High I/O instances provides very high, low latency, disk I/O performance using SSD\-based local instance storage\. | 18 July 2012 |
| IAM roles on Amazon EC2 instances | 2012\-06\-01 | IAM roles for Amazon EC2 provide: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/DocumentHistory.html) | 11 June 2012 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-32 | | Spot Instance features that make it easier to get started and handle the potential of interruption\. | | You can now manage your Spot Instances as follows: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/DocumentHistory.html) | 7 June 2012 |
| EC2 instance export and timestamps for status checks for Amazon EC2 | 2012\-05\-01 | Added support for timestamps on instance status and system status to indicate the date and time that a status check failed\. | 25 May 2012 |
| EC2 instance export, and timestamps in instance and system status checks for Amazon VPC | 2012\-05\-01 | Added support for EC2 instance export to Citrix Xen, Microsoft Hyper\-V, and VMware vSphere\. Added support for timestamps in instance and system status checks\. | 25 May 2012 |
| Cluster Compute Eight Extra Large instances | 2012\-04\-01 | Added support for `cc2.8xlarge` instances in a VPC\. | 26 April 2012 |
| AWS Marketplace AMIs | 2012\-04\-01 | Added support for AWS Marketplace AMIs\. | 19 April 2012 |
| New Linux AMI release | | Amazon Linux AMI 2012\.03 is released\. | 28 March 2012 |
| New AKI version | | We've released AKI version 1\.03 and AKIs for the AWS GovCloud \(US\) region\. | 28 March 2012 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-33 | | Medium instances, support for 64\-bit on all AMIs, and a Java\-based SSH Client | 2011\-12\-15 | Added support for a new instance type and 64\-bit information\. Added procedures for using the Java\-based SSH client to connect to Linux instances\. | 7 March 2012 |
| Reserved Instance pricing tiers | 2011\-12\-15 | Added a new section discussing how to take advantage of the discount pricing that is built into the Reserved Instance pricing tiers\. | 5 March 2012 |
| Elastic Network Interfaces \(ENIs\) for EC2 instances in Amazon Virtual Private Cloud | 2011\-12\-01 | Added new section about elastic network interfaces \(ENIs\) for EC2 instances in a VPC\. For more information, see [Elastic network interfaces](using-eni.md)\. | 21 December 2011 |
| New GRU Region and AKIs | | Added information about the release of new AKIs for the SA\-East\-1 Region\. This release deprecates the AKI version 1\.01\. AKI version 1\.02 will continue to be backward compatible\. | 14 December 2011 |
| New offering types for Amazon EC2 Reserved Instances | 2011\-11\-01 | You can choose from a variety of Reserved Instance offerings that address your projected use of the instance\. | 01 December 2011 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-34 | | Amazon EC2 instance status | 2011\-11\-01 | You can view additional details about the status of your instances, including scheduled events planned by AWS that might have an impact on your instances\. These operational activities include instance reboots required to apply software updates or security patches, or instance retirements required where there are hardware issues\. For more information, see [Monitoring the status of your instances](monitoring-instances-status-check.md)\. | 16 November 2011 |
| Amazon EC2 Cluster Compute Instance Type | | Added support for Cluster Compute Eight Extra Large \(cc2\.8xlarge\) to Amazon EC2\. | 14 November 2011 |
| New PDX Region and AKIs | | Added information about the release of new AKIs for the new US\-West 2 Region\. | 8 November 2011 |
| Spot Instances in Amazon VPC | 2011\-07\-15 | Added information about the support for Spot Instances in Amazon VPC\. With this update, users can launch Spot Instances a virtual private cloud \(VPC\)\. By launching Spot Instances in a VPC, users of Spot Instances can enjoy the benefits of Amazon VPC\. | 11 October 2011 |
| New Linux AMI release | | Added information about the release of Amazon Linux AMI 2011\.09\. This update removes the beta tag from the Amazon Linux AMI, supports the ability to lock the repositories to a specific version, and provides for notification when updates are available to installed packages including security updates\. | 26 September 2011 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-35 | | Simplified VM import process for users of the CLI tools | 2011\-07\-15 | The VM Import process is simplified with the enhanced functionality of `ImportInstance` and `ImportVolume`, which now will perform the upload of the images into Amazon EC2 after creating the import task\. In addition, with the introduction of `ResumeImport`, users can restart an incomplete upload at the point the task stopped\. | 15 September 2011 |
| Support for importing in VHD file format | | VM Import can now import virtual machine image files in VHD format\. The VHD file format is compatible with the Citrix Xen and Microsoft Hyper\-V virtualization platforms\. With this release, VM Import now supports RAW, VHD and VMDK \(VMware ESX\-compatible\) image formats\. For more information, see the [ VM Import/Export User Guide](https://docs.aws.amazon.com/vm-import/latest/userguide/)\. | 24 August 2011 |
| Update to the Amazon EC2 VM Import Connector for VMware vCenter | | Added information about the 1\.1 version of the Amazon EC2 VM Import Connector for VMware vCenter virtual appliance \(Connector\)\. This update includes proxy support for Internet access, better error handling, improved task progress bar accuracy, and several bug fixes\. | 27 June 2011 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-36 | | Enabling Linux AMI to run user\-provided kernels | | Added information about the AKI version change from 1\.01 to 1\.02\. This version updates the PVGRUB to address launch failures associated with t1\.micro Linux instances\. For more information, see [User provided kernels](UserProvidedKernels.md)\. | 20 June 2011 |
| Spot Instances Availability Zone pricing changes | 2011\-05\-15 | Added information about the Spot Instances Availability Zone pricing feature\. In this release, we've added new Availability Zone pricing options as part of the information returned when you query for Spot Instance requests and Spot price history\. These additions make it easier to determine the price required to launch a Spot Instance into a particular Availability Zone\. | 26 May 2011 |
| AWS Identity and Access Management | | Added information about AWS Identity and Access Management \(IAM\), which enables users to specify which Amazon EC2 actions a user can use with Amazon EC2 resources in general\. For more information, see [Identity and access management for Amazon EC2](security-iam.md)\. | 26 April 2011 |
| Enabling Linux AMI to run user\-provided kernels | | Added information about enabling a Linux AMI to use PVGRUB Amazon Kernel Image \(AKI\) to run a user\-provided kernel\. For more information, see [User provided kernels](UserProvidedKernels.md)\. | 26 April 2011 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-37 | | Dedicated instances | | Launched within your Amazon Virtual Private Cloud \(Amazon VPC\), Dedicated Instances are instances that are physically isolated at the host hardware level\. Dedicated Instances let you take advantage of Amazon VPC and the AWS cloud, with benefits including on\-demand elastic provisioning and pay only for what you use, while isolating your Amazon EC2 compute instances at the hardware level\. For more information, see [Dedicated Instances](dedicated-instance.md)\. | 27 March 2011 |
| Reserved Instances updates to the AWS Management Console | | Updates to the AWS Management Console make it easier for users to view their Reserved Instances and purchase additional Reserved Instances, including Dedicated Reserved Instances\. For more information, see [Reserved Instances](ec2-reserved-instances.md)\. | 27 March 2011 |
| New Amazon Linux reference AMI | | The new Amazon Linux reference AMI replaces the CentOS reference AMI\. Removed information about the CentOS reference AMI, including the section named Correcting Clock Drift for Cluster Instances on CentOS 5\.4 AMI\. | 15 March 2011 |
| Metadata information | 2011\-01\-01 | Added information about metadata to reflect changes in the 2011\-01\-01 release\. For more information, see [Instance metadata and user data](ec2-instance-metadata.md) and [Instance metadata categories](instancedata-data-categories.md)\. | 11 March 2011 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-38 | | Amazon EC2 VM Import Connector for VMware vCenter | | Added information about the Amazon EC2 VM Import Connector for VMware vCenter virtual appliance \(Connector\)\. The Connector is a plug\-in for VMware vCenter that integrates with VMware vSphere Client and provides a graphical user interface that you can use to import your VMware virtual machines to Amazon EC2\. | 3 March 2011 |
| Force volume detachment | | You can now use the AWS Management Console to force the detachment of an Amazon EBS volume from an instance\. For more information, see [Detaching an Amazon EBS volume from a Linux instance](ebs-detaching-volume.md)\. | 23 February 2011 |
| Instance termination protection | | You can now use the AWS Management Console to prevent an instance from being terminated\. For more information, see [Enabling termination protection](terminating-instances.md#Using_ChangingDisableAPITermination)\. | 23 February 2011 |
| Correcting Clock Drift for Cluster Instances on CentOS 5\.4 AMI | | Added information about how to correct clock drift for cluster instances running on Amazon's CentOS 5\.4 AMI\. | 25 January 2011 |
| VM Import | 2010\-11\-15 | Added information about VM Import, which allows you to import a virtual machine or volume into Amazon EC2\. For more information, see the [ VM Import/Export User Guide](https://docs.aws.amazon.com/vm-import/latest/userguide/)\. | 15 December 2010 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-39 | | Basic monitoring for instances | 2010\-08\-31 | Added information about basic monitoring for EC2 instances\. | 12 December 2010 |
| Filters and Tags | 2010\-08\-31 | Added information about listing, filtering, and tagging resources\. For more information, see [Listing and filtering your resources](Using_Filtering.md) and [Tagging your Amazon EC2 resources](Using_Tags.md)\. | 19 September 2010 |
| Idempotent Instance Launch | 2010\-08\-31 | Added information about ensuring idempotency when running instances\. For more information, see [Ensuring Idempotency](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/Run_Instance_Idempotency.html) in the *Amazon EC2 API Reference*\. | 19 September 2010 |
| Micro instances | 2010\-06\-15 | Amazon EC2 offers the `t1.micro` instance type for certain types of applications\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | 8 September 2010 |
| AWS Identity and Access Management for Amazon EC2 | | Amazon EC2 now integrates with AWS Identity and Access Management \(IAM\)\. For more information, see [Identity and access management for Amazon EC2](security-iam.md)\. | 2 September 2010 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e6ede0a96ae7-40 | | Cluster instances | 2010\-06\-15 | Amazon EC2 offers cluster compute instances for high\-performance computing \(HPC\) applications\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\. | 12 July 2010 |
| Amazon VPC IP Address Designation | 2010\-06\-15 | Amazon VPC users can now specify the IP address to assign an instance launched in a VPC\. | 12 July 2010 |
| Amazon CloudWatch Monitoring for Amazon EBS Volumes | | Amazon CloudWatch monitoring is now automatically available for Amazon EBS volumes\. For more information, see [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md)\. | 14 June 2010 |
| High\-memory extra large instances | 2009\-11\-30 | Amazon EC2 now supports a High\-Memory Extra Large \(m2\.xlarge\) instance type\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\. | 22 February 2010 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/DocumentHistory.md |
e5dbd3fa0217-0 | Amazon EBS Multi\-Attach enables you to attach a single Provisioned IOPS SSD \(io1\) volume to up to 16 Nitro\-based instances that are in the same Availability Zone\. You can attach multiple Multi\-Attach enabled volumes to an instance or set of instances\. Each instance to which the volume is attached has full read and write permission to the shared volume\. Multi\-Attach makes it easier for you to achieve higher application availability in clustered Linux applications that manage concurrent write operations\.
**Topics**
+ [Considerations and limitations](#considerations)
+ [Performance](#perf)
+ [Working with Multi\-Attach](#working)
+ [Monitoring](#monitoring)
+ [Pricing and billing](#pricing) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
55686dae34f3-0 | + Multi\-Attach enabled volumes can be attached to up to 16 Linux instances built on the [Nitro System](instance-types.md#ec2-nitro-instances) that are in the same Availability Zone\. You can attach a volume that is Multi\-Attach enabled to Windows instances, but the operating system does not recognize the data on the volume that is shared between the instances\.
+ Multi\-Attach is supported exclusively on [Provisioned IOPS SSD \(io1\) volumes](ebs-volume-types.md#EBSVolumeTypes_piops)\. It is not supported on Provisioned IOPS SSD \(io2\) volumes\.
+ Multi\-Attach is available only in the `us-east-1`, `us-west-2`, `eu-west-1`, and `ap-northeast-2` Regions\.
+ Multi\-Attach enabled volumes do not support I/O fencing\. I/O fencing protocols control write access in a shared storage environment to maintain data consistency\. Your applications must provide write ordering for the attached instances to maintain data consistency\.
+ Multi\-Attach enabled volumes can't be created as boot volumes\.
+ Multi\-Attach enabled volumes can be attached to one block device mapping per instance\.
+ You can't enable or disable Multi\-Attach after volume creation\.
+ You can't change the volume type, size, or Provisioned IOPS of a Multi\-Attach enabled volume\.
+ Multi\-Attach can't be enabled during instance launch using either the Amazon EC2 console or RunInstances API\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
55686dae34f3-1 | + Multi\-Attach can't be enabled during instance launch using either the Amazon EC2 console or RunInstances API\.
+ Multi\-Attach enabled volumes that have an issue at the Amazon EBS infrastructure layer are unavailable to all attached instances\. Issues at the Amazon EC2 or networking layer might only impact some attached instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
c2a260751109-0 | Each attached instance is able to drive its maximum IOPS performance up to the volume's maximum provisioned performance\. However, the aggregate performance of all of the attached instances can't exceed the volume's maximum provisioned performance\. If the attached instances' demand for IOPS is higher than the volume's Provisioned IOPS, the volume will not exceed its provisioned performance\.
For example, say you create an `io1` Multi\-Attach enabled volume with `50,000` Provisioned IOPS and you attach it to an `m5.8xlarge` instance and a `c5.12xlarge` instance\. The `m5.8xlarge` and `c5.12xlarge` instances support a maximum of `30,000` and `40,000` IOPS respectively\. Each instance can drive its maximum IOPS as it is less than the volume's Provisioned IOPS of `50,000`\. However, if both instances drive I/O to the volume simultaneously, their combined IOPS can't exceed the volume's provisioned performance of `50,000 IOPS`\. The volume will not exceed `50,000` IOPS\.
To achieve consistent performance, it is best practice to balance I/O driven from attached instances across the sectors of a Multi\-Attach enabled volume\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
3d3afe2ab489-0 | Multi\-Attach enabled volumes can be managed in much the same way that you would manage any other Amazon EBS volume\. However, in order to use the Multi\-Attach functionality, you must enable it for the volume\. When you create a new volume, Multi\-Attach is disabled by default\.
**Contents**
+ [Enabling Multi\-Attach](#enable)
+ [Attaching a volume to instances](#attach)
+ [Deleting on termination](#delete) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
530d6439fbc8-0 | You can enable Multi\-Attach for an Amazon EBS volume during creation only\.
Use one of the following methods to enable Multi\-Attach for an Amazon EBS volume during creation\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
52859ed325aa-0 | **To enable Multi\-Attach during volume creation**
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 **Volumes**\.
1. Choose **Create Volume**\.
1. For **Volume Type**, choose **Provisioned IOPS SSD \(io1\)**\.
1. For **Size** and **IOPS**, choose the required volume size and the number of IOPS to provision\.
1. For **Availability Zone**, choose the same Availability Zone that the instances are in\.
1. For **Multi\-Attach**, choose **Enable**\.
1. Choose **Create Volume**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
294c429ebf02-0 | **To enable Multi\-Attach during volume creation**
Use the [create\-volume](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-volume.html) command and specify the `--multi-attach-enabled` parameter\.
```
$ aws ec2 create-volume --volume-type io1 --multi-attach-enabled --size 100 --iops 2000 --region us-west-2 --availability-zone us-west-2b
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
d927293d764c-0 | You attach a Multi\-Attach enabled volume to an instance in the same way that you attach any other EBS volume\. For more information, see [Attaching an Amazon EBS volume to an instance](ebs-attaching-volume.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
82e767dc7308-0 | Multi\-Attach enabled volumes are deleted on instance termination if the last attached instance is terminated and if that instance is configured to delete the volume on termination\. If the volume is attached to multiple instances that have different delete on termination settings in their volume block device mappings, the last attached instance's block device mapping setting determines the delete on termination behavior\.
To ensure predictable delete on termination behavior, enable or disable delete on termination for all of the instances to which the volume is attached\.
By default, when a volume is attached to an instance the delete on termination setting for the block device mapping is set to false\. If you want to turn on delete on termination for a Multi\-Attach enabled volume, modify the block device mapping\.
If you want the volume to be deleted when the attached instances are terminated, enable delete on termination in the block device mapping for all of the attached instances\. If you want to retain the volume after the attached instances have been terminated, disable delete on termination in the block device mapping for all of the attached instances\. For more information, see [Preserving Amazon EBS volumes on instance termination](terminating-instances.md#preserving-volumes-on-termination)\.
You can modify an instance's delete on termination setting at launch or after it has launched\. If you enable or disable delete on termination during instance launch, the settings apply only to volumes that are attached at launch\. If you attach a volume to an instance after launch, you must explicitly set the delete on termination behavior for that volume\.
You can modify an instance's delete on termination setting using the command line tools only\.
**To modify the delete on termination setting for an existing instance** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
82e767dc7308-1 | **To modify the delete on termination setting for an existing instance**
Use the [ modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) command and specify the `DeleteOnTermination` attribute in the `--block-device-mappings option`\.
```
aws ec2 modify-instance-attribute --instance-id i-1234567890abcdef0 --block-device-mappings file://mapping.json
```
Specify the following in `mapping.json`\.
```
[
{
"DeviceName": "/dev/sdf",
"Ebs": {
"DeleteOnTermination": true|false
}
}
]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
a287dec70ed0-0 | You can monitor a Multi\-Attach enabled volume using the CloudWatch Metrics for Amazon EBS volumes\. For more information, see [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md)\.
Data is aggregated across all of the attached instances\. You can't monitor metrics for individual attached instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
7fa38ba22741-0 | There are no additional charges for using Amazon EBS Multi\-Attach\. You are billed the standard charges that apply to Provisioned IOPS SSD \(io1\) volumes\. For more information, see [Amazon EBS pricing](http://aws.amazon.com/ebs/pricing/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes-multi.md |
bdebdd3ae1db-0 | You can use AWS Config to record configuration changes for Dedicated Hosts, and for instances that are launched, stopped, or terminated on them\. You can then use the information captured by AWS Config as a data source for license reporting\.
AWS Config records configuration information for Dedicated Hosts and instances individually, and pairs this information through relationships\. There are three reporting conditions:
+ **AWS Config recording status**—When **On**, AWS Config is recording one or more AWS resource types, which can include Dedicated Hosts and Dedicated Instances\. To capture the information required for license reporting, verify that hosts and instances are being recorded with the following fields\.
+ **Host recording status**—When **Enabled**, the configuration information for Dedicated Hosts is recorded\.
+ **Instance recording status**—When **Enabled**, the configuration information for Dedicated Instances is recorded\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-aws-config.md |
bdebdd3ae1db-1 | + **Instance recording status**—When **Enabled**, the configuration information for Dedicated Instances is recorded\.
If any of these three conditions are disabled, the icon in the **Edit Config Recording** button is red\. To derive the full benefit of this tool, ensure that all three recording methods are enabled\. When all three are enabled, the icon is green\. To edit the settings, choose **Edit Config Recording**\. You are directed to the **Set up AWS Config** page in the AWS Config console, where you can set up AWS Config and start recording for your hosts, instances, and other supported resource types\. For more information, see [Setting up AWS Config using the Console](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html) in the *AWS Config Developer Guide*\.
**Note**
AWS Config records your resources after it discovers them, which might take several minutes\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-aws-config.md |
bdebdd3ae1db-2 | **Note**
AWS Config records your resources after it discovers them, which might take several minutes\.
After AWS Config starts recording configuration changes to your hosts and instances, you can get the configuration history of any host that you have allocated or released and any instance that you have launched, stopped, or terminated\. For example, at any point in the configuration history of a Dedicated Host, you can look up how many instances are launched on that host, along with the number of sockets and cores on the host\. For any of those instances, you can also look up the ID of its Amazon Machine Image \(AMI\)\. You can use this information to report on licensing for your own server\-bound software that is licensed per\-socket or per\-core\.
You can view configuration histories in any of the following ways:
+ By using the AWS Config console\. For each recorded resource, you can view a timeline page, which provides a history of configuration details\. To view this page, choose the gray icon in the **Config Timeline** column of the **Dedicated Hosts** page\. For more information, see [Viewing Configuration Details in the AWS Config Console](https://docs.aws.amazon.com/config/latest/developerguide/view-manage-resource-console.html) in the *AWS Config Developer Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-aws-config.md |
bdebdd3ae1db-3 | + By running AWS CLI commands\. First, you can use the [list\-discovered\-resources](https://docs.aws.amazon.com/cli/latest/reference/configservice/list-discovered-resources.html) command to get a list of all hosts and instances\. Then, you can use the [get\-resource\-config\-history](https://docs.aws.amazon.com/cli/latest/reference/configservice/get-resource-config-history.html#get-resource-config-history) command to get the configuration details of a host or instance for a specific time interval\. For more information, see [View Configuration Details Using the CLI](https://docs.aws.amazon.com/config/latest/developerguide/view-manage-resource-cli.html) in the *AWS Config Developer Guide*\.
+ By using the AWS Config API in your applications\. First, you can use the [ListDiscoveredResources](https://docs.aws.amazon.com/config/latest/APIReference/API_ListDiscoveredResources.html) action to get a list of all hosts and instances\. Then, you can use the [GetResourceConfigHistory](https://docs.aws.amazon.com/config/latest/APIReference/API_GetResourceConfigHistory.html) action to get the configuration details of a host or instance for a specific time interval\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-aws-config.md |
bdebdd3ae1db-4 | For example, to get a list of all of your Dedicated Hosts from AWS Config, run a CLI command such as the following\.
```
aws configservice list-discovered-resources --resource-type AWS::EC2::Host
```
To obtain the configuration history of a Dedicated Host from AWS Config, run a CLI command such as the following\.
```
aws configservice get-resource-config-history --resource-type AWS::EC2::Instance --resource-id i-1234567890abcdef0
```
**To manage AWS Config settings using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. On the **Dedicated Hosts** page, choose **Edit Config Recording**\.
1. In the AWS Config console, follow the steps provided to turn on recording\. For more information, see [Setting up AWS Config using the Console](https://docs.aws.amazon.com/config/latest/developerguide/gs-console.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-aws-config.md |
bdebdd3ae1db-5 | For more information, see [Viewing Configuration Details in the AWS Config Console](https://docs.aws.amazon.com/config/latest/developerguide/view-manage-resource-console.html)\.
**To activate AWS Config using the command line or API**
+ AWS CLI: [Viewing Configuration Details \(AWS CLI\)](https://docs.aws.amazon.com/config/latest/developerguide/view-manage-resource-console.html#view-config-details-cli) in the *AWS Config Developer Guide*\.
+ Amazon EC2 API: [GetResourceConfigHistory](https://docs.aws.amazon.com/config/latest/APIReference/API_GetResourceConfigHistory.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-aws-config.md |
59b31de1dd9e-0 | You can use the yum search command to search the descriptions of packages that are available in your configured repositories\. This is especially helpful if you don't know the exact name of the package you want to install\. Simply append the keyword search to the command; for multiple word searches, wrap the search query with quotation marks\.
**Important**
This information applies to Amazon Linux\. For information about other distributions, see their specific documentation\.
```
[ec2-user ~]$ sudo yum search "find"
```
The following is example output for Amazon Linux 2\.
```
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
============================== N/S matched: find ===============================
findutils.x86_64 : The GNU versions of find utilities (find and xargs)
gedit-plugin-findinfiles.x86_64 : gedit findinfiles plugin
ocaml-findlib-devel.x86_64 : Development files for ocaml-findlib
perl-File-Find-Rule.noarch : Perl module implementing an alternative interface to File::Find | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/find-software.md |
59b31de1dd9e-1 | perl-File-Find-Rule.noarch : Perl module implementing an alternative interface to File::Find
robotfindskitten.x86_64 : A game/zen simulation. You are robot. Your job is to find kitten.
mlocate.x86_64 : An utility for finding files by name
ocaml-findlib.x86_64 : Objective CAML package manager and build helper
perl-Devel-Cycle.noarch : Find memory cycles in objects
perl-Devel-EnforceEncapsulation.noarch : Find access violations to blessed objects
perl-File-Find-Rule-Perl.noarch : Common rules for searching for Perl things
perl-File-HomeDir.noarch : Find your home and other directories on any platform
perl-IPC-Cmd.noarch : Finding and running system commands made easy
perl-Perl-MinimumVersion.noarch : Find a minimum required version of perl for Perl code
texlive-xesearch.noarch : A string finder for XeTeX
valgrind.x86_64 : Tool for finding memory management bugs in programs
valgrind.i686 : Tool for finding memory management bugs in programs
```
The following is example output for Amazon Linux\.
```
Loaded plugins: priorities, security, update-motd, upgrade-helper | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/find-software.md |
59b31de1dd9e-2 | ```
Loaded plugins: priorities, security, update-motd, upgrade-helper
============================== N/S Matched: find ===============================
findutils.x86_64 : The GNU versions of find utilities (find and xargs)
perl-File-Find-Rule.noarch : Perl module implementing an alternative interface to File::Find
perl-Module-Find.noarch : Find and use installed modules in a (sub)category
libpuzzle.i686 : Library to quickly find visually similar images (gif, png, jpg)
libpuzzle.x86_64 : Library to quickly find visually similar images (gif, png, jpg)
mlocate.x86_64 : An utility for finding files by name
```
Multiple word search queries in quotation marks only return results that match the exact query\. If you don't see the expected package, simplify your search to one keyword and then scan the results\. You can also try keyword synonyms to broaden your search\.
For more information about packages for Amazon Linux 2 and Amazon Linux, see the following:
+ [Package repository](amazon-linux-ami-basics.md#package-repository) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/find-software.md |
59b31de1dd9e-3 | + [Package repository](amazon-linux-ami-basics.md#package-repository)
+ [Extras library \(Amazon Linux 2\)](amazon-linux-ami-basics.md#extras-library) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/find-software.md |
1d9bee535e4d-0 | Capacity Reservation sharing enables Capacity Reservation owners to share their reserved capacity with other AWS accounts or within an AWS organization\. This enables you to create and manage Capacity Reservations centrally, and share the reserved capacity across multiple AWS accounts or within your AWS organization\.
In this model, the AWS account that owns the Capacity Reservation \(owner\) shares it with other AWS accounts \(consumers\)\. Consumers can launch instances into Capacity Reservations that are shared with them in the same way that they launch instances into Capacity Reservations that they own in their own account\. The Capacity Reservation owner is responsible for managing the Capacity Reservation and the instances that they launch into it\. Owners cannot modify instances that consumers launch into Capacity Reservations that they have shared\. Consumers are responsible for managing the instances that they launch into Capacity Reservations shared with them\. Consumers cannot view or modify instances owned by other consumers or by the Capacity Reservation owner\.
A Capacity Reservation owner can share a Capacity Reservation with:
+ Specific AWS accounts inside or outside of its AWS organization
+ An organizational unit inside its AWS organization
+ Its entire AWS organization
**Topics**
+ [Prerequisites for sharing Capacity Reservations](#sharing-cr-prereq)
+ [Related services](#cr-sharing-related)
+ [Sharing across Availability Zones](#cr-sharing-azs)
+ [Sharing a Capacity Reservation](#sharing-cr)
+ [Stop sharing a Capacity Reservation](#unsharing-cr)
+ [Identifying a shared Capacity Reservation](#identifying-shared-cr)
+ [Viewing shared Capacity Reservation usage](#shared-cr-usage) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
1d9bee535e4d-1 | + [Identifying a shared Capacity Reservation](#identifying-shared-cr)
+ [Viewing shared Capacity Reservation usage](#shared-cr-usage)
+ [Shared Capacity Reservation permissions](#shared-cr-perms)
+ [Billing and metering](#shared-cr-billing)
+ [Instance limits](#shared-cr-limits) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
9de0852c243e-0 | + To share a Capacity Reservation, you must own it in your AWS account\. You cannot share a Capacity Reservation that has been shared with you\.
+ You can only share Capacity Reservations for shared tenancy instances\. You cannot share Capacity Reservations for dedicated tenancy instances\.
+ Capacity Reservation sharing is not available to new AWS accounts or AWS accounts that have a limited billing history\. New accounts that are linked to a qualified master \(payer\) account or are linked through an AWS organization are exempt from this restriction\.
+ To share a Capacity Reservation with your AWS organization or an organizational unit in your AWS organization, you must enable sharing with AWS Organizations\. For more information, see [Enable Sharing with AWS Organizations](https://docs.aws.amazon.com/ram/latest/userguide/getting-started-sharing.html) in the *AWS RAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
8da22adabcbe-0 | Capacity Reservation sharing integrates with AWS Resource Access Manager \(AWS RAM\)\. AWS RAM is a service that enables you to share your AWS resources with any AWS account or through AWS Organizations\. With AWS RAM, you share resources that you own by creating a *resource share*\. A resource share specifies the resources to share, and the consumers with whom to share them\. Consumers can be individual AWS accounts, or organizational units or an entire organization from AWS Organizations\.
For more information about AWS RAM, see the *[AWS RAM User Guide](https://docs.aws.amazon.com/ram/latest/userguide/)*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
1514bdd162bb-0 | To ensure that resources are distributed across the Availability Zones for a Region, we independently map Availability Zones to names for each account\. This could lead to Availability Zone naming differences across accounts\. For example, the Availability Zone `us-east-1a` for your AWS account might not have the same location as `us-east-1a` for another AWS account\.
To identify the location of your Capacity Reservations relative to your accounts, you must use the *Availability Zone ID* \(AZ ID\)\. The AZ ID is a unique and consistent identifier for an Availability Zone across all AWS accounts\. For example, `use1-az1` is an AZ ID for the `us-east-1` Region and it is the same location in every AWS account\.
**To view the AZ IDs for the Availability Zones in your account**
1. Open the AWS RAM console at [https://console\.aws\.amazon\.com/ram](https://console.aws.amazon.com/ram/)\.
1. The AZ IDs for the current Region are displayed in the **Your AZ ID** panel on the right\-hand side of the screen\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
d6c19e1ac24c-0 | When you share a Capacity Reservation that you own with other AWS accounts, you enable them to launch instances into your reserved capacity\. If you share an open Capacity Reservation, keep the following in mind as it could lead to unintended Capacity Reservation usage:
+ If consumers have running instances that match the attributes of the Capacity Reservation, have the `CapacityReservationPreference` parameter set to `open`, and are not yet running in reserved capacity, they automatically use the shared Capacity Reservation\.
+ If consumers launch instances that have matching attributes \(instance type, platform, and Availability Zone\) and have the `CapacityReservationPreference` parameter set to `open`, they automatically launch into the shared Capacity Reservation\.
To share a Capacity Reservation, you must add it to a resource share\. A resource share is an AWS RAM resource that lets you share your resources across AWS accounts\. A resource share specifies the resources to share, and the consumers with whom they are shared\. When you share a Capacity Reservation using the Amazon EC2 console, you add it to an existing resource share\. To add the Capacity Reservation to a new resource share, you must create the resource share using the [AWS RAM console](https://console.aws.amazon.com/ram)\.
If you are part of an organization in AWS Organizations and sharing within your organization is enabled, consumers in your organization are automatically granted access to the shared Capacity Reservation\. Otherwise, consumers receive an invitation to join the resource share and are granted access to the shared Capacity Reservation after accepting the invitation\.
You can share a Capacity Reservation that you own using the Amazon EC2 console, AWS RAM console, or the AWS CLI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
d6c19e1ac24c-1 | You can share a Capacity Reservation that you own using the Amazon EC2 console, AWS RAM console, or the AWS CLI\.
**To share a Capacity Reservation that you own 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 **Capacity Reservations**\.
1. Choose the Capacity Reservation to share and choose **Actions**, **Share reservation**\.
1. Select the resource share to which to add the Capacity Reservation and choose **Share Capacity Reservation**\.
It could take a few minutes for consumers to get access to the shared Capacity Reservation\.
**To share a Capacity Reservation that you own using the AWS RAM console**
See [Creating a Resource Share](https://docs.aws.amazon.com/ram/latest/userguide/working-with-sharing.html#working-with-sharing-create) in the *AWS RAM User Guide*\.
**To share a Capacity Reservation that you own using the AWS CLI**
Use the [create\-resource\-share](https://docs.aws.amazon.com/cli/latest/reference/ram/create-resource-share.html) command\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
a956b04f8e38-0 | The Capacity Reservation owner can stop sharing a Capacity Reservation at any time\. The following rules apply:
+ Instances owned by consumers that were running in the shared capacity at the time sharing stops continue to run normally outside of the reserved capacity, and the capacity is restored to the Capacity Reservation subject to Amazon EC2 capacity availability\.
+ Consumers with whom the Capacity Reservation was shared can no longer launch new instances into the reserved capacity\.
To stop sharing a Capacity Reservation that you own, you must remove it from the resource share\. You can do this using the Amazon EC2 console, AWS RAM console, or the AWS CLI\.
**To stop sharing a Capacity Reservation that you own 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 **Capacity Reservations**\.
1. Select the Capacity Reservation and choose the **Sharing** tab\.
1. The **Sharing** tab lists the resource shares to which the Capacity Reservation has been added\. Select the resource share from which to remove the Capacity Reservation and choose **Remove from resource share**\.
**To stop sharing a Capacity Reservation that you own using the AWS RAM console**
See [Updating a Resource Share](https://docs.aws.amazon.com/ram/latest/userguide/working-with-sharing.html#working-with-sharing-update) in the *AWS RAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
a956b04f8e38-1 | **To stop sharing a Capacity Reservation that you own using the AWS CLI**
Use the [disassociate\-resource\-share](https://docs.aws.amazon.com/cli/latest/reference/ram/disassociate-resource-share.html) command\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
bfdf7157b796-0 | Owners and consumers can identify shared Capacity Reservations using the Amazon EC2 console and AWS CLI
**To identify a shared Capacity Reservation 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 **Capacity Reservations**\. The screen lists Capacity Reservations that you own and Capacity Reservations that are shared with you\. The **Owner** column shows the AWS account ID of the Capacity Reservation owner\. `(me)` next to the AWS account ID indicates that you are the owner\.
**To identify a shared Capacity Reservation using the AWS CLI**
Use the [describe\-capacity\-reservations](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-capacity-reservations.html) command\. The command returns the Capacity Reservations that you own and Capacity Reservations that are shared with you\. `OwnerId` shows the AWS account ID of the Capacity Reservation owner\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
89b8a40ad9db-0 | The owner of a shared Capacity Reservation can view its usage at any time using the Amazon EC2 console and the AWS CLI\.
**To view Capacity Reservation usage 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 **Capacity Reservations**\.
1. Select the Capacity Reservation for which to view the usage and choose the **Usage** tab\.
The **AWS account ID** column shows the account IDs of the consumers currently using the Capacity Reservation\. The **Launched instances** column shows the number of instances each consumer currently has running in the reserved capacity\.
**To view Capacity Reservation usage using the AWS CLI**
Use the [get\-capacity\-reservation\-usage](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-capacity-reservation-usage.html) command\. `AccountId` shows the account ID of the account using the Capacity Reservation\. `UsedInstanceCount` shows the number of instances the consumer currently has running in the reserved capacity\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
915e89dddc95-0 | Owners are responsible for managing and canceling their shared Capacity Reservations\. Owners cannot modify instances running in the shared Capacity Reservation that are owned by other accounts\. Owners remain responsible for managing instances that they launch into the shared Capacity Reservation\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
f5174f991ca4-0 | Consumers are responsible for managing their instances that are running the shared Capacity Reservation\. Consumers cannot modify the shared Capacity Reservation in any way, and they cannot view or modify instances that are owned by other consumers or the Capacity Reservation owner\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
51331c3812cd-0 | There are no additional charges for sharing Capacity Reservations\.
The Capacity Reservation owner is billed for instances that they run inside the Capacity Reservation and for unused reserved capacity\. Consumers are billed for the instances that they run inside the shared Capacity Reservation\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
44731ef74b88-0 | All Capacity Reservation usage counts toward the Capacity Reservation owner's On\-Demand Instance limits\. This includes:
+ Unused reserved capacity
+ Usage by instances owned by the Capacity Reservation owner
+ Usage by instances owned by consumers
Instances launched into the shared capacity by consumers count towards the Capacity Reservation owner's On\-Demand Instance limit\. Consumers' instance limits are a sum of their own On\-Demand Instance limits and the capacity available in the shared Capacity Reservations to which they have access\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservation-sharing.md |
b3687624f557-0 | The following examples show launch configurations that you can use with the [request\-spot\-fleet](https://docs.aws.amazon.com/cli/latest/reference/ec2/request-spot-fleet.html) command to create a Spot Fleet request\. For more information, see [Creating a Spot Fleet request](spot-fleet-requests.md#create-spot-fleet)\.
**Note**
For Spot Fleet, you can't specify an network interface ID in a launch specification\. Make sure you omit the `NetworkInterfaceID` parameter in your launch specification\.
1. [Launch Spot Instances using the lowest\-priced Availability Zone or subnet in the region](#fleet-config1)
1. [Launch Spot Instances using the lowest\-priced Availability Zone or subnet in a specified list](#fleet-config2)
1. [Launch Spot Instances using the lowest\-priced instance type in a specified list](#fleet-config3)
1. [Override the price for the request](#fleet-config4)
1. [Launch a Spot Fleet using the diversified allocation strategy](#fleet-config5)
1. [Launch a Spot Fleet using instance weighting](#fleet-config6)
1. [Launch a Spot Fleet with On\-Demand capacity](#fleet-config7) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
1cad198ac140-0 | The following example specifies a single launch specification without an Availability Zone or subnet\. The Spot Fleet launches the instances in the lowest\-priced Availability Zone that has a default subnet\. The price you pay does not exceed the On\-Demand price\.
```
{
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"KeyName": "my-key-pair",
"SecurityGroups": [
{
"GroupId": "sg-1a2b3c4d"
}
],
"InstanceType": "m3.medium",
"IamInstanceProfile": {
"Arn": "arn:aws:iam::123456789012:instance-profile/my-iam-role"
}
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
20406570ad41-0 | The following examples specify two launch specifications with different Availability Zones or subnets, but the same instance type and AMI\.
**Availability Zones**
The Spot Fleet launches the instances in the default subnet of the lowest\-priced Availability Zone that you specified\.
```
{
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"KeyName": "my-key-pair",
"SecurityGroups": [
{
"GroupId": "sg-1a2b3c4d"
}
],
"InstanceType": "m3.medium",
"Placement": {
"AvailabilityZone": "us-west-2a, us-west-2b"
},
"IamInstanceProfile": {
"Arn": "arn:aws:iam::123456789012:instance-profile/my-iam-role"
}
}
]
}
```
**Subnets** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
20406570ad41-1 | }
}
]
}
```
**Subnets**
You can specify default subnets or nondefault subnets, and the nondefault subnets can be from a default VPC or a nondefault VPC\. The Spot service launches the instances in whichever subnet is in the lowest\-priced Availability Zone\.
You can't specify different subnets from the same Availability Zone in a Spot Fleet request\.
```
{
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"KeyName": "my-key-pair",
"SecurityGroups": [
{
"GroupId": "sg-1a2b3c4d"
}
],
"InstanceType": "m3.medium",
"SubnetId": "subnet-a61dafcf, subnet-65ea5f08",
"IamInstanceProfile": {
"Arn": "arn:aws:iam::123456789012:instance-profile/my-iam-role" | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
20406570ad41-2 | "Arn": "arn:aws:iam::123456789012:instance-profile/my-iam-role"
}
}
]
}
```
If the instances are launched in a default VPC, they receive a public IPv4 address by default\. If the instances are launched in a nondefault VPC, they do not receive a public IPv4 address by default\. Use a network interface in the launch specification to assign a public IPv4 address to instances launched in a nondefault VPC\. When you specify a network interface, you must include the subnet ID and security group ID using the network interface\.
```
...
{
"ImageId": "ami-1a2b3c4d",
"KeyName": "my-key-pair",
"InstanceType": "m3.medium",
"NetworkInterfaces": [
{
"DeviceIndex": 0,
"SubnetId": "subnet-1a2b3c4d",
"Groups": [ "sg-1a2b3c4d" ],
"AssociatePublicIpAddress": true
}
],
"IamInstanceProfile": {
"Arn": "arn:aws:iam::880185128111:instance-profile/my-iam-role" | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
20406570ad41-3 | "Arn": "arn:aws:iam::880185128111:instance-profile/my-iam-role"
}
}
...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
Subsets and Splits