id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
5eee7f8b9ba7-0 | A *default VPC* is a VPC that is configured and ready for you to use, and is only available in Regions that are VPC\-only\. For Regions that support EC2\-Classic, you can create a nondefault VPC to set up your resources\. However, you might want to use a default VPC if you prefer not to set up a VPC yourself, or if you do not have specific requirements for your VPC configuration\. For more information about default VPCs, see [Default VPC and Default Subnets](https://docs.aws.amazon.com/vpc/latest/userguide/default-vpc.html) in the *Amazon VPC User Guide*\.
The following are options for using a default VPC when you have an AWS account that supports EC2\-Classic\.
**Topics**
+ [Switch to a VPC\-only Region](#get-default-vpc-region)
+ [Create a new AWS account](#get-default-vpc-account)
+ [Convert your existing AWS account to VPC\-only](#convert-ec2-classic-account) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
ff577a50a5ef-0 | Use this option if you want to use your existing account to set up your resources in a default VPC and you do not need to use a specific Region\. To find a Region that has a default VPC, see [Detecting supported platforms](ec2-classic-platform.md#ec2-supported-platforms)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
a55407edf790-0 | New AWS accounts support VPC only\. Use this option if you want an account that has a default VPC in every Region\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
c6ebb531811a-0 | Use this option if you want a default VPC in every Region in your existing account\. Before you can convert your account, you must delete all of your EC2\-Classic resources\. You can also migrate some resources to a VPC\. For more information, see [Migrate your resources to a VPC](#full-migrate)\.
**To convert your EC2\-Classic account**
1. Delete or migrate \(if applicable\) the resources that you have created for use in EC2\-Classic\. These include the following:
+ Amazon EC2 instances
+ EC2\-Classic security groups \(excluding the default security group, which you cannot delete yourself\)
+ EC2\-Classic Elastic IP addresses
+ Classic Load Balancers
+ Amazon RDS resources
+ Amazon ElastiCache resources
+ Amazon Redshift resources
+ AWS Elastic Beanstalk resources
+ AWS Data Pipeline resources
+ Amazon EMR resources
+ AWS OpsWorks resources
1. Go to the AWS Support Center at [console\.aws\.amazon\.com/support](https://console.aws.amazon.com/support)\.
1. Choose **Create case**\.
1. Choose **Account and billing support**\.
1. For **Type**, choose **Account**\. For **Category**, choose **Convert EC2 Classic to VPC**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
c6ebb531811a-1 | 1. For **Type**, choose **Account**\. For **Category**, choose **Convert EC2 Classic to VPC**\.
1. Fill in the other details as required, and choose **Submit**\. We will review your request and contact you to guide you through the next steps\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
434955435970-0 | You can migrate or move some of your resources to a VPC\. Some resources can only be migrated from EC2\-Classic to a VPC that's in the same Region and in the same AWS account\. If the resource cannot be migrated, you must create a new resource for use in your VPC\.
**Prerequisites**
Before you begin, you must have a VPC\. If you don't have a default VPC, you can create a nondefault VPC using one of these methods:
+ In the Amazon VPC console, use the VPC wizard to create a new VPC\. For more information, see [Amazon VPC Console Wizard Configurations](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_wizard.html)\. Use this option if you want to set up a VPC quickly, using one of the available configuration options\.
+ In the Amazon VPC console, set up the components of a VPC according to your requirements\. For more information, see [VPCs and Subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html)\. Use this option if you have specific requirements for your VPC, such as a particular number of subnets\.
**Topics**
+ [Security groups](#vpc-migrate-security-group)
+ [Elastic IP addresses](#vpc-migrate-eip)
+ [AMIs and instances](#vpc-migrate-ami-instance) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
434955435970-1 | + [Elastic IP addresses](#vpc-migrate-eip)
+ [AMIs and instances](#vpc-migrate-ami-instance)
+ [Amazon RDS DB instances](#vpc-migrate-rds) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
85a316801ee2-0 | If you want your instances in your VPC to have the same security group rules as your EC2\-Classic instances, you can use the Amazon EC2 console to copy your existing EC2\-Classic security group rules to a new VPC security group\.
You can only copy security group rules to a new security group in the same AWS account in the same Region\. If you are using a different Region or a different AWS account, you must create a new security group and manually add the rules yourself\. For more information, see [Amazon EC2 security groups for Linux instances](ec2-security-groups.md)\.
**To copy your security group rules to a new security group**
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 **Security Groups**\.
1. Select the security group that's associated with your EC2\-Classic instance, then choose **Actions**, and select **Copy to new**\.
**Note**
To identify an EC2\-Classic security group, check the **VPC ID** column\. For each EC2\-Classic security group, the value in the column is blank or a `-` symbol\.
1. In the **Create Security Group** dialog box, specify a name and description for your new security group\. Select your VPC from the **VPC** list\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
85a316801ee2-1 | 1. The **Inbound** tab is populated with the rules from your EC2\-Classic security group\. You can modify the rules as required\. In the **Outbound** tab, a rule that allows all outbound traffic has automatically been created for you\. For more information about modifying security group rules, see [Amazon EC2 security groups for Linux instances](ec2-security-groups.md)\.
**Note**
If you've defined a rule in your EC2\-Classic security group that references another security group, you cannot use the same rule in your VPC security group\. Modify the rule to reference a security group in the same VPC\.
1. Choose **Create**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
363499c85585-0 | You can migrate an Elastic IP address that is allocated for use in EC2\-Classic for use with a VPC\. You cannot migrate an Elastic IP address to another Region or AWS account\. For more information, see [Migrating an Elastic IP Address from EC2\-Classic](ec2-classic-platform.md#migrating-eip)\.
**To identify an Elastic IP address that is allocated for use in EC2\-Classic**
In the Amazon EC2 console, choose **Elastic IPs** in the navigation pane\. In the **Scope** column, the value is **standard**\.
Alternatively, use the following `describe-addresses` command\.
```
aws ec2 describe-addresses --filters Name=domain,Values=standard
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
df96f4931523-0 | An AMI is a template for launching your Amazon EC2 instance\. You can create your own AMI based on an existing EC2\-Classic instance, then use that AMI to launch instances into your VPC\.
**Topics**
+ [Identify EC2\-Classic instances](#vpc-migrate-id-instances)
+ [Create an AMI](#vpc-migrate-create-ami)
+ [\(Optional\) Share or copy your AMI](#vpc-migrate-share-ami)
+ [\(Optional\) Store your data on Amazon EBS volumes](#vpc-migrate-create-volumes)
+ [Launch an instance into your VPC](#vpc-migrate-instance) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
8547989d52ad-0 | If you have instances running in both EC2\-Classic and a VPC, you can identify your EC2\-Classic instances\. In the Amazon EC2 console, choose **Instances** in the navigation pane\. In the **VPC ID** column, the value for each EC2\-Classic instance is blank or a `-` symbol\.
Alternatively, use the following `describe-instances` AWS CLI command, and use the `--query` parameter to display only instances where the value for `VpcId` is `null`\.
```
aws ec2 describe-instances --query 'Reservations[*].Instances[?VpcId==`null`]'
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
b1af57975c10-0 | After you've identified your EC2\-Classic instance, you can create an AMI from it\.
**To create a Windows AMI**
For more information, see [Creating a custom Windows AMI](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.html)\.
**To create a Linux AMI**
The method that you use to create your Linux AMI depends on the root device type of your instance, and the operating system platform on which your instance runs\. To find out the root device type of your instance, go to the **Instances** page, select your instance, and look at the information in the **Root device type** field in the **Description** tab\. If the value is `ebs`, then your instance is EBS\-backed\. If the value is `instance-store`, then your instance is instance store\-backed\. You can also use the [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) AWS CLI command to find out the root device type\.
The following table provides options for you to create your Linux AMI based on the root device type of your instance, and the software platform\.
**Important** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
b1af57975c10-1 | The following table provides options for you to create your Linux AMI based on the root device type of your instance, and the software platform\.
**Important**
Some instance types support both PV and HVM virtualization, while others support only one or the other\. If you plan to use your AMI to launch a different instance type than your current instance type, verify that the instance type supports the type of virtualization that your AMI offers\. If your AMI supports PV virtualization, and you want to use an instance type that supports HVM virtualization, you might have to reinstall your software on a base HVM AMI\. For more information about PV and HVM virtualization, see [Linux AMI virtualization types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/virtualization_types.html)\.
| Instance root device type | Action |
| --- | --- |
| EBS | Create an EBS\-backed AMI from your instance\. For more information, see [Creating an Amazon EBS\-backed Linux AMI](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html)\. |
| Instance store | Create an instance store\-backed AMI from your instance using the AMI tools\. For more information, see [Creating an instance store\-backed Linux AMI](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-instance-store.html)\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
b1af57975c10-2 | | Instance store | Convert your instance store\-backed instance to an EBS\-backed instance\. For more information, see [Converting your instance store\-backed AMI to an Amazon EBS\-backed AMI](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_ConvertingS3toEBS.html)\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
6bde6392902d-0 | To use your AMI to launch an instance in a new AWS account, you must first share the AMI with your new account\. For more information, see [Sharing an AMI with specific AWS accounts](sharingamis-explicit.md)\.
To use your AMI to launch an instance in a VPC in a different Region, you must first copy the AMI to that Region\. For more information, see [Copying an AMI](CopyingAMIs.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
7b73e5e62046-0 | You can create an Amazon EBS volume and use it to back up and store the data on your instance—like you would use a physical hard drive\. Amazon EBS volumes can be attached and detached from any instance in the same Availability Zone\. You can detach a volume from your instance in EC2\-Classic, and attach it to a new instance that you launch into your VPC in the same Availability Zone\.
For more information about Amazon EBS volumes, see the following topics:
+ [Amazon EBS volumes](ebs-volumes.md)
+ [Creating an Amazon EBS volume](ebs-creating-volume.md)
+ [Attaching an Amazon EBS volume to an instance](ebs-attaching-volume.md)
To back up the data on your Amazon EBS volume, you can take periodic snapshots of your volume\. For more information, see [Creating Amazon EBS snapshots](ebs-creating-snapshot.md)\. If you need to, you can create an Amazon EBS volume from your snapshot\. For more information, see [Creating a volume from a snapshot](ebs-creating-volume.md#ebs-create-volume-from-snapshot)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
d8a2971b720e-0 | After you've created an AMI, you can use the Amazon EC2 launch wizard to launch an instance into your VPC\. The instance will have the same data and configurations as your existing EC2\-Classic instance\.
**Note**
You can use this opportunity to [upgrade to a current generation instance type](https://aws.amazon.com/ec2/previous-generation/#Upgrade_Paths)\. However, verify that the instance type supports the type of virtualization that your AMI offers \(PV or HVM\)\. For more information about PV and HVM virtualization, see [Linux AMI virtualization types](virtualization_types.md)\.
**To launch an instance into your VPC**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. On the dashboard, choose **Launch instance**\.
1. On the **Choose an Amazon Machine Image** page, select the **My AMIs** category, and select the AMI you created\. Alternatively, if you shared an AMI from another account, in the **Ownership** filter list, choose **Shared with me**\. Select the AMI that you shared from your EC2\-Classic account\.
1. On the **Choose an Instance Type** page, select the type of instance, and choose **Next: Configure Instance Details**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
d8a2971b720e-1 | 1. On the **Choose an Instance Type** page, select the type of instance, and choose **Next: Configure Instance Details**\.
1. On the **Configure Instance Details** page, select your VPC from the **Network** list\. Select the required subnet from the **Subnet** list\. Configure any other details that you require, then go through the next pages of the wizard until you reach the **Configure Security Group** page\.
1. Select **Select an existing group**, and select the security group that you created for your VPC\. Choose **Review and Launch**\.
1. Review your instance details, then choose **Launch** to specify a key pair and launch your instance\.
For more information about the parameters that you can configure in each step of the wizard, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
559a1b9d9a11-0 | You can move your EC2\-Classic DB instance to a VPC in the same Region, in the same account\. For more information, see [Updating the VPC for a DB Instance](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.html#USER_VPC.VPC2VPC) in the *Amazon RDS User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
b7f03a3e5e98-0 | The ClassicLink feature makes it easier to manage an incremental migration to a VPC\. ClassicLink enables you to link an EC2\-Classic instance to a VPC in your account in the same Region, allowing your new VPC resources to communicate with the EC2\-Classic instance using private IPv4 addresses\. You can then migrate functionality one component at a time until your application is running fully in your VPC\.
Use this option if you cannot afford downtime during the migration, for example, if you have a multi\-tier application with processes that cannot be interrupted\.
For more information about ClassicLink, see [ClassicLink](vpc-classiclink.md)\.
**Topics**
+ [Step 1: Prepare your migration sequence](#classiclink-migrate-preparation)
+ [Step 2: Enable your VPC for ClassicLink](#classiclink-migrate-enable-vpc)
+ [Step 3: Link your EC2\-Classic instances to your VPC](#classiclink-migrate-attach-instance)
+ [Step 4: Complete the VPC migration](#classiclink-migrate-terminate-instances) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
90b8aa9873d3-0 | To use ClassicLink effectively, you must first identify the components of your application that must be migrated to the VPC, and then confirm the order in which to migrate that functionality\.
For example, you have an application that relies on a presentation web server, a backend database server, and authentication logic for transactions\. You may decide to start the migration process with the authentication logic, then the database server, and finally, the web server\.
Then, you can start migrating or recreating your resources\. For more information, see [Migrate your resources to a VPC](#full-migrate)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
8b95f2138b5c-0 | After you've configured your new VPC instances and made the functionality of your application available in the VPC, you can use ClassicLink to enable private IP communication between your new VPC instances and your EC2\-Classic instances\. First, you must enable your VPC for ClassicLink\.
**To enable a VPC for ClassicLink**
1. Open the Amazon VPC console at [https://console\.aws\.amazon\.com/vpc/](https://console.aws.amazon.com/vpc/)\.
1. In the navigation pane, choose **Your VPCs**\.
1. Select your VPC, and then choose **Actions**, **Enable ClassicLink**\.
1. Choose **Yes, Enable**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
b6a6120cd529-0 | After you've enabled ClassicLink in your VPC, you can link your EC2\-Classic instances to the VPC\.
**To link an instance to a VPC**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Select your EC2\-Classic instance, then choose **Actions**, **ClassicLink**, **Link to VPC**\.
**Note**
Verify that your instance is in the `running` state\.
1. Select your ClassicLink\-enabled VPC \(only VPCs that are enabled for ClassicLink are displayed\)\.
1. Select one or more of the VPC security groups to associate with your instance\. When you are done, choose **Link to VPC**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
e43218dbb4d5-0 | Depending on the size of your application and the functionality that must be migrated, repeat the preceding steps until you've moved all of the components of your application from EC2\-Classic into your VPC\.
After you've enabled internal communication between the EC2\-Classic and VPC instances, you must update your application to point to your migrated service in your VPC, instead of your service in the EC2\-Classic platform\. The exact steps for this depend on your application’s design\. Generally, this includes updating your destination IP addresses to point to the IP addresses of your VPC instances instead of your EC2\-Classic instances\.
After you've completed this step and you've tested that the application is functioning from your VPC, you can terminate your EC2\-Classic instances, and disable ClassicLink for your VPC\. You can also clean up any EC2\-Classic resources that you no longer need to avoid incurring charges for them\. For example, you can release Elastic IP addresses and delete the volumes that were associated with your EC2\-Classic instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
ab38a696683d-0 | In this example, you use AWS to host your gardening website\. To manage your website, you have three running instances in EC2\-Classic\. Instances A and B host your public\-facing web application, and you use Elastic Load Balancing to load balance the traffic between these instances\. You've assigned Elastic IP addresses to instances A and B so that you have static IP addresses for configuration and administration tasks on those instances\. Instance C holds your MySQL database for your website\. You've registered the domain name `www.garden.example.com`, and you've used Route 53 to create a hosted zone with an alias record set that's associated with the DNS name of your load balancer\.
![\[A web application in EC2-Classic\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/vpc-migrate-example-classic.png)
The first part of migrating to a VPC is deciding what kind of VPC architecture suits your needs\. In this case, you've decided on the following: one public subnet for your web servers, and one private subnet for your database server\. As your website grows, you can add more web servers and database servers to your subnets\. By default, instances in the private subnet cannot access the internet; however, you can enable internet access through a Network Address Translation \(NAT\) device in the public subnet\. You might want to set up a NAT device to support periodic updates and patches from the internet for your database server\. You'll migrate your Elastic IP addresses to a VPC, and create a load balancer in your public subnet to load balance the traffic between your web servers\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
ab38a696683d-1 | ![\[A web application in a VPC\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/vpc-migrate-example-vpc.png)
To migrate your web application to a VPC, you can follow these steps:
+ **Create a VPC**: In this case, you can use the VPC wizard in the Amazon VPC console to create your VPC and subnets\. The second wizard configuration creates a VPC with one private and one public subnet, and launches and configures a NAT device in your public subnet for you\. For more information, see [VPC with public and private subnets \(NAT\)](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Scenario2.html) in the *Amazon VPC User Guide*\.
+ **Configure your security groups**: In your EC2\-Classic environment, you have one security group for your web servers, and another security group for your database server\. You can use the Amazon EC2 console to copy the rules from each security group into new security groups for your VPC\. For more information, see [Security groups](#vpc-migrate-security-group)\.
**Tip**
Create the security groups that are referenced by other security groups first\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
ab38a696683d-2 | **Tip**
Create the security groups that are referenced by other security groups first\.
+ **Create AMIs and launch new instances**: Create an AMI from one of your web servers, and a second AMI from your database server\. Then, launch replacement web servers into your public subnet, and launch your replacement database server into your private subnet\. For more information, see [Create an AMI](#vpc-migrate-create-ami)\.
+ **Configure your NAT device**: If you are using a NAT instance, you must create a security group for it that allows HTTP and HTTPS traffic from your private subnet\. For more information, see [NAT instances](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html)\. If you are using a NAT gateway, traffic from your private subnet is automatically allowed\.
+ **Configure your database**: When you created an AMI from your database server in EC2\-Classic, all of the configuration information that was stored in that instance was copied to the AMI\. You might have to connect to your new database server and update the configuration details\. For example, if you configured your database to grant full read, write, and modification permissions to your web servers in EC2\-Classic, you need to update the configuration files to grant the same permissions to your new VPC web servers instead\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
ab38a696683d-3 | + **Configure your web servers**: Your web servers will have the same configuration settings as your instances in EC2\-Classic\. For example, if you configured your web servers to use the database in EC2\-Classic, update your web servers' configuration settings to point to your new database instance\.
**Note**
By default, instances launched into a nondefault subnet are not assigned a public IP address, unless you specify otherwise at launch\. Your new database server might not have a public IP address\. In this case, you can update your web servers' configuration file to use your new database server's private DNS name\. Instances in the same VPC can communicate with each other via private IP address\.
+ **Migrate your Elastic IP addresses**: Disassociate your Elastic IP addresses from your web servers in EC2\-Classic, and then migrate them to a VPC\. After you've migrated them, you can associate them with your new web servers in your VPC\. For more information, see [Migrating an Elastic IP Address from EC2\-Classic](ec2-classic-platform.md#migrating-eip)\.
+ **Create a new load balancer**: To continue using Elastic Load Balancing to load balance the traffic to your instances, make sure you understand the various ways to configure your load balancer in VPC\. For more information, see the [Elastic Load Balancing User Guide](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
ab38a696683d-4 | + **Update your DNS records**: After you've set up your load balancer in your public subnet, verify that your `www.garden.example.com` domain points to your new load balancer\. To do this, update your DNS records and your alias record set in Route 53\. For more information about using Route 53, see [Getting Started with Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started.html)\.
+ **Shut down your EC2\-Classic resources**: After you've verified that your web application is working from within the VPC architecture, you can shut down your EC2\-Classic resources to stop incurring charges for them\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/vpc-migrate.md |
35ad8acef13b-0 | Dedicated Instances are Amazon EC2 instances that run in a virtual private cloud \(VPC\) on hardware that's dedicated to a single customer\. Dedicated Instances that belong to different AWS accounts are physically isolated at a hardware level, even if those accounts are linked to a single payer account\. However, Dedicated Instances may share hardware with other instances from the same AWS account that are not Dedicated Instances\.
**Note**
A *Dedicated Host* is also a physical server that's dedicated for your use\. With a Dedicated Host, you have visibility and control over how instances are placed on the server\. For more information, see [Dedicated Hosts](dedicated-hosts-overview.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
bb860a7be407-0 | Each instance that you launch into a VPC has a tenancy attribute\. This attribute has the following values\.
| Tenancy Value | Description |
| --- | --- |
| `default` | Your instance runs on shared hardware\. |
| `dedicated` | Your instance runs on single\-tenant hardware\. |
| `host` | Your instance runs on a Dedicated Host, which is an isolated server with configurations that you can control\. |
After you launch an instance, there are some limitations to changing its tenancy\.
+ You cannot change the tenancy of an instance from `default` to `dedicated` or `host` after you've launched it\.
+ You cannot change the tenancy of an instance from `dedicated` or `host` to `default` after you've launched it\.
You can change the tenancy of an instance from `dedicated` to `host`, or from `host` to `dedicated` after you've launched it\. For more information, see [Changing the Tenancy of an Instance](#dedicated-change-tenancy)\.
Each VPC has a related instance tenancy attribute\. This attribute has the following values\.
| Tenancy Value | Description |
| --- | --- |
| `default` | An instance launched into the VPC runs on shared hardware by default, unless you explicitly specify a different tenancy during instance launch\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
bb860a7be407-1 | | `default` | An instance launched into the VPC runs on shared hardware by default, unless you explicitly specify a different tenancy during instance launch\. |
| `dedicated` | An instance launched into the VPC is a Dedicated Instance by default, unless you explicitly specify a tenancy of `host` during instance launch\. You cannot specify a tenancy of `default` during instance launch\. |
You can change the instance tenancy of a VPC from `dedicated` to `default` after you create it\. You cannot change the instance tenancy of a VPC to `dedicated`\.
To create Dedicated Instances, you can do the following:
+ Create the VPC with the instance tenancy set to `dedicated` \(all instances launched into this VPC are Dedicated Instances\)\.
+ Create the VPC with the instance tenancy set to `default`, and specify a tenancy of `dedicated` for any instances when you launch them\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
47b92af6404a-0 | Some AWS services or their features won't work with a VPC with the instance tenancy set to `dedicated`\. Check the service's documentation to confirm if there are any limitations\.
Some instance types cannot be launched into a VPC with the instance tenancy set to `dedicated`\. For more information about supported instances types, see [Amazon EC2 Dedicated Instances](https://aws.amazon.com/ec2/purchasing-options/dedicated-instances/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
872dddd5ca9b-0 | When you launch an Amazon EBS\-backed Dedicated Instance, the EBS volume doesn't run on single\-tenant hardware\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
62afdc06e57f-0 | To guarantee that sufficient capacity is available to launch Dedicated Instances, you can purchase Dedicated Reserved Instances\. For more information, see [Reserved Instances](ec2-reserved-instances.md)\.
When you purchase a Dedicated Reserved Instance, you are purchasing the capacity to launch a Dedicated Instance into a VPC at a much reduced usage fee; the price break in the usage charge applies only if you launch an instance with dedicated tenancy\. When you purchase a Reserved Instance with default tenancy, it applies only to a running instance with `default` tenancy; it would not apply to a running instance with `dedicated` tenancy\.
You can't use the modification process to change the tenancy of a Reserved Instance after you've purchased it\. However, you can exchange a Convertible Reserved Instance for a new Convertible Reserved Instance with a different tenancy\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
23a604cca3e2-0 | You can use Amazon EC2 Auto Scaling to launch Dedicated Instances\. For more information, see [Launching Auto Scaling Instances in a VPC](https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-in-vpc.html) in the *Amazon EC2 Auto Scaling User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
d5a5c8971d3d-0 | You can configure automatic recovery for a Dedicated Instances if it becomes impaired due to an underlying hardware failure or a problem that requires AWS involvement to repair\. For more information, see [Recover your instance](ec2-instance-recover.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
545b7565fe53-0 | You can run a Dedicated Spot Instance by specifying a tenancy of `dedicated` when you create a Spot Instance request\. For more information, see [Specifying a tenancy for your Spot Instances](spot-requests.md#spot-instance-tenancy)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
451616b61506-0 | Pricing for Dedicated Instances is different to pricing for On\-Demand Instances\. For more information, see the [Amazon EC2 Dedicated Instances product page](https://aws.amazon.com/dedicated-instances)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
6d7c6b543197-0 | You can leverage the benefits of running on dedicated tenancy hardware with [Burstable performance instances](burstable-performance-instances.md)\. T3 Dedicated Instances launch in unlimited mode by default, and they provide a baseline level of CPU performance with the ability to burst to a higher CPU level when required by your workload\. The T3 baseline performance and ability to burst are governed by CPU credits\. Because of the burstable nature of the T3 instance types, we recommend that you monitor how your T3 instances use the CPU resources of the dedicated hardware for the best performance\. T3 Dedicated Instances are intended for customers with diverse workloads that display random CPU behavior, but that ideally have average CPU usage at or below the baseline usages\. For more information, see [CPU credits and baseline utilization for burstable performance instances](burstable-credits-baseline-concepts.md)\.
Amazon EC2 has systems in place to identify and correct variability in performance\. However, it is still possible to experience short term variability if you launch multiple T3 Dedicated Instances that have correlated CPU usage patterns\. For these more demanding or correlated workloads, we recommend using M5 or M5a Dedicated Instances rather than T3 Dedicated Instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
b6677a23fccd-0 | You can create a VPC with an instance tenancy of `dedicated` to ensure that all instances launched into the VPC are Dedicated Instances\. Alternatively, you can specify the tenancy of the instance during launch\.
**Topics**
+ [Creating a VPC with an Instance Tenancy of Dedicated](#creatingdedicatedvpc)
+ [Launching Dedicated Instances into a VPC](#dedicatedinstancesintovpc)
+ [Displaying Tenancy Information](#dedicated-gettingpgsinfo)
+ [Changing the Tenancy of an Instance](#dedicated-change-tenancy)
+ [Changing the Tenancy of a VPC](#change-tenancy-vpc) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
bc3a1d87525e-0 | When you create a VPC, you have the option of specifying its instance tenancy\. If you're using the Amazon VPC console, you can create a VPC using the VPC wizard or the **Your VPCs** page\.
**To create a VPC with an instance tenancy of dedicated \(VPC Wizard\)**
1. Open the Amazon VPC console at [https://console\.aws\.amazon\.com/vpc/](https://console.aws.amazon.com/vpc/)\.
1. From the dashboard, choose **Start VPC Wizard**\.
1. Select a VPC configuration, and then choose **Select**\.
1. On the next page of the wizard, choose **Dedicated** from the **Hardware tenancy** list\.
1. Choose **Create VPC**\.
**To create a VPC with an instance tenancy of dedicated \(Create VPC dialog box\)**
1. Open the Amazon VPC console at [https://console\.aws\.amazon\.com/vpc/](https://console.aws.amazon.com/vpc/)\.
1. In the navigation pane, choose **Your VPCs**, and then **Create VPC**\.
1. For **Tenancy**, choose **Dedicated**\. Specify the CIDR block, and choose **Yes, Create**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
bc3a1d87525e-1 | 1. For **Tenancy**, choose **Dedicated**\. Specify the CIDR block, and choose **Yes, Create**\.
**To set the tenancy option when you create a VPC using the command line**
+ [create\-vpc](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-vpc.html) \(AWS CLI\)
+ [New\-EC2Vpc](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Vpc.html) \(AWS Tools for Windows PowerShell\)
If you launch an instance into a VPC that has an instance tenancy of `dedicated`, your instance is automatically a Dedicated Instance, regardless of the tenancy of the instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
a7526dcad6a0-0 | You can launch a Dedicated Instance using the Amazon EC2 launch instance wizard\.
**To launch a Dedicated Instance into a default tenancy VPC using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Launch Instance**\.
1. On the **Choose an Amazon Machine Image \(AMI\)** page, select an AMI and choose **Select**\.
1. On the **Choose an Instance Type** page, select the instance type and choose **Next: Configure Instance Details**\.
**Note**
Ensure that you choose an instance type that's supported as a Dedicated Instance\. For more information, see [Amazon EC2 Dedicated Instances](https://aws.amazon.com/ec2/purchasing-options/dedicated-instances/)\.
1. On the **Configure Instance Details** page, select a VPC and subnet\. Choose **Dedicated \- Run a dedicated instance** from the **Tenancy** list, and then **Next: Add Storage**\.
1. Continue as prompted by the wizard\. When you've finished reviewing your options on the **Review Instance Launch** page, choose **Launch** to choose a key pair and launch the Dedicated Instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
a7526dcad6a0-1 | For more information about launching an instance with a tenancy of `host`, see [Launching instances onto a Dedicated Host](how-dedicated-hosts-work.md#launching-dedicated-hosts-instances)\.
**To set the tenancy option for an instance during launch using the command line**
+ [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) \(AWS CLI\)
+ [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
2f8c5c0c685c-0 | **To display tenancy information for your VPC using the console**
1. Open the Amazon VPC console at [https://console\.aws\.amazon\.com/vpc/](https://console.aws.amazon.com/vpc/)\.
1. In the navigation pane, choose **Your VPCs**\.
1. Check the instance tenancy of your VPC in the **Tenancy** column\.
1. If the **Tenancy** column is not displayed, choose **Edit Table Columns** \(the gear\-shaped icon\), **Tenancy** in the **Show/Hide Columns** dialog box, and then **Close**\.
**To display tenancy information for your instance using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Check the tenancy of your instance in the **Tenancy** column\.
1. If the **Tenancy** column is not displayed, do one of the following:
+ Choose **Show/Hide Columns** \(the gear\-shaped icon\), **Tenancy** in the **Show/Hide Columns** dialog box, and then **Close**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
2f8c5c0c685c-1 | + Select the instance\. The **Description** tab in the details pane displays information about the instance, including its tenancy\.
**To describe the tenancy of your VPC using the command line**
+ [describe\-vpcs](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-vpcs.html) \(AWS CLI\)
+ [Get\-EC2Vpc](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Vpc.html) \(AWS Tools for Windows PowerShell\)
**To describe the tenancy of your instance using the command line**
+ [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) \(AWS CLI\)
+ [Get\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Instance.html) \(AWS Tools for Windows PowerShell\)
**To describe the tenancy value of a Reserved Instance using the command line**
+ [describe\-reserved\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
2f8c5c0c685c-2 | + [Get\-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstance.html) \(AWS Tools for Windows PowerShell\)
**To describe the tenancy value of a Reserved Instance offering using the command line**
+ [describe\-reserved\-instances\-offerings](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-offerings.html) \(AWS CLI\)
+ [Get\-EC2ReservedInstancesOffering](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesOffering.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
57f05b77a4ea-0 | Depending on your instance type and platform, you can change the tenancy of a stopped Dedicated Instance to `host` after launching it\. The next time the instance starts, it's started on a Dedicated Host that's allocated to your account\. For more information about allocating and working with Dedicated Hosts, and the instance types that can be used with Dedicated Hosts, see [Working with Dedicated Hosts](how-dedicated-hosts-work.md)\. Similarly, you can change the tenancy of a stopped Dedicated Host instance to `dedicated` after launching it\. The next time the instance starts, it's started on single\-tenant hardware that we control\.
**To change the tenancy of an instance using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances** and select your instance\.
1. Choose **Actions**, **Instance State**, **Stop**\.
1. Choose **Actions**, **Instance Settings**, **Modify Instance Placement**\.
1. In the **Tenancy** list, choose whether to run your instance on dedicated hardware or on a Dedicated Host\. Choose **Save**\.
**To modify the tenancy value of an instance using the command line** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
57f05b77a4ea-1 | **To modify the tenancy value of an instance using the command line**
+ [modify\-instance\-placement](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-placement.html) \(AWS CLI\)
+ [Edit\-EC2InstancePlacement](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstancePlacement.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
726766338bfd-0 | You can change the instance tenancy attribute of a VPC from `dedicated` to `default`\. Modifying the instance tenancy of the VPC does not affect the tenancy of any existing instances in the VPC\. The next time you launch an instance in the VPC, it has a tenancy of `default`, unless you specify otherwise during launch\.
You cannot change the instance tenancy attribute of a VPC to `dedicated`\.
You can modify the instance tenancy attribute of a VPC using the AWS CLI, an AWS SDK, or the Amazon EC2 API only\.
**To modify the instance tenancy attribute of a VPC using the AWS CLI**
+ Use the [modify\-vpc\-tenancy](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-vpc-tenancy.html) command to specify the ID of the VPC and instance tenancy value\. The only supported value is `default`\.
```
aws ec2 modify-vpc-tenancy --vpc-id vpc-1a2b3c4d --instance-tenancy default
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-instance.md |
9f0999ac9875-0 | The following is the recommended process of verifying the validity of the EC2Rescue for Linux package for Linux\-based operating systems\.
When you download an application from the internet, we recommend that you authenticate the identity of the software publisher and check that the application has not been altered or corrupted after it was published\. This protects you from installing a version of the application that contains a virus or other malicious code\.
If, after running the steps in this topic, you determine that the software for EC2Rescue for Linux is altered or corrupted, do not run the installation file\. Instead, contact Amazon Web Services\.
EC2Rescue for Linux files for Linux\-based operating systems are signed using GnuPG, an open\-source implementation of the Pretty Good Privacy \(OpenPGP\) standard for secure digital signatures\. GnuPG \(also known as GPG\) provides authentication and integrity checking through a digital signature\. AWS publishes a public key and signatures that you can use to verify the downloaded EC2Rescue for Linux package\. For more information about PGP and GnuPG \(GPG\), see [http://www\.gnupg\.org](http://www.gnupg.org)\.
The first step is to establish trust with the software publisher\. Download the public key of the software publisher, check that the owner of the public key is who they claim to be, and then add the public key to your keyring\. Your keyring is a collection of known public keys\. After you establish the authenticity of the public key, you can use it to verify the signature of the application\.
**Topics** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_verify.md |
9f0999ac9875-1 | **Topics**
+ [Install the GPG tools](#ec2rl_install_gpg)
+ [Authenticate and import the public key](#ec2rl_authenticate)
+ [Verify the signature of the package](#ec2rl_verify_signature) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_verify.md |
9534a3256063-0 | If your operating system is Linux or Unix, the GPG tools may already be installed\. To test whether the tools are installed on your system, enter gpg2 at a command prompt\. If the GPG tools are installed, you see a GPG command prompt\. If the GPG tools are not installed, you see an error stating that the command cannot be found\. You can install the GnuPG package from a repository\.
**To install GPG tools on Debian\-based Linux**
+ From a terminal, run the following command:
```
apt-get install gnupg2
```
**To install GPG tools on Red Hat–based Linux**
+ From a terminal, run the following command:
```
yum install gnupg2
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_verify.md |
d494d54ab35e-0 | The next step in the process is to authenticate the EC2Rescue for Linux public key and add it as a trusted key in your GPG keyring\.
**To authenticate and import the EC2Rescue for Linux public key**
1. At a command prompt, use the following command to obtain a copy of our public GPG build key:
```
curl -O https://s3.amazonaws.com/ec2rescuelinux/ec2rl.key
```
1. At a command prompt in the directory where you saved `ec2rl.key`, use the following command to import the EC2Rescue for Linux public key into your keyring:
```
gpg2 --import ec2rl.key
```
The command returns results similar to the following:
```
gpg: /home/ec2-user/.gnupg/trustdb.gpg: trustdb created
gpg: key 2FAE2A1C: public key "[email protected] <EC2 Rescue for Linux>" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_verify.md |
f88bfdfd517f-0 | After you've installed the GPG tools, authenticated and imported the EC2Rescue for Linux public key, and verified that the EC2Rescue for Linux public key is trusted, you are ready to verify the signature of the EC2Rescue for Linux installation script\.
**To verify the EC2Rescue for Linux installation script signature**
1. At a command prompt, run the following command to download the signature file for the installation script:
```
curl -O https://s3.amazonaws.com/ec2rescuelinux/ec2rl.tgz.sig
```
1. Verify the signature by running the following command at a command prompt in the directory where you saved `ec2rl.tgz.sig` and the EC2Rescue for Linux installation file\. Both files must be present\.
```
gpg2 --verify ./ec2rl.tgz.sig
```
The output should look something like the following:
```
gpg: Signature made Thu 12 Jul 2018 01:57:51 AM UTC using RSA key ID 6991ED45
gpg: Good signature from "[email protected] <EC2 Rescue for Linux>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_verify.md |
f88bfdfd517f-1 | gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: E528 BCC9 0DBF 5AFA 0F6C C36A F780 4843 2FAE 2A1C
Subkey fingerprint: 966B 0D27 85E9 AEEC 1146 7A9D 8851 1153 6991 ED45
```
If the output contains the phrase `Good signature from "[email protected] <EC2 Rescue for Linux>"`, it means that the signature has successfully been verified, and you can proceed to run the EC2Rescue for Linux installation script\.
If the output includes the phrase `BAD signature`, check whether you performed the procedure correctly\. If you continue to get this response, contact Amazon Web Services and do not run the installation file that you downloaded previously\.
The following are details about the warnings that you might see:
+ WARNING: This key is not certified with a trusted signature\! There is no indication that the signature belongs to the owner\. This refers to your personal level of trust in your belief that you possess an authentic public key for EC2Rescue for Linux\. In an ideal world, you would visit an Amazon Web Services office and receive the key in person\. However, more often you download it from a website\. In this case, the website is an Amazon Web Services website\.
+ gpg2: no ultimately trusted keys found\. This means that the specific key is not "ultimately trusted" by you \(or by other people whom you trust\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_verify.md |
f88bfdfd517f-2 | For more information, see [http://www\.gnupg\.org](http://www.gnupg.org)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_verify.md |
9a1833d24539-0 | The [MATE desktop environment](https://mate-desktop.org/) is pre\-installed and pre\-configured in the AMI with the following description: Amazon Linux 2 with \.Net Core, PowerShell, Mono, and MATE Desktop Environment\. The environment provides an intuitive graphical user interface for administering Amazon Linux 2 instances without using the command line\. The interface uses graphical representations, such as icons, windows, toolbars, folders, wallpapers, and desktop widgets\. Built\-in, GUI\-based tools are available to perform common tasks\. For example, there are tools for adding and removing software, applying updates, organizing files, launching programs, and monitoring system health\.
Complete the following procedure to use the MATE desktop environment\.
**To configure Remote Desktop Protocol \(RDP\) connections and set up a password**
1. Use the following [describe\-images](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/ec2/describe-images.html) command to get the ID of the AMI for Amazon Linux 2 that includes MATE in the AMI name\.
```
aws ec2 describe-images --filters "Name=name,Values=amzn2*MATE*" --query 'Images[*].ImageId' --output text
```
The following is example output:
```
ami-0abcdef1234567890
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-mate.md |
9a1833d24539-1 | The following is example output:
```
ami-0abcdef1234567890
```
1. Launch an EC2 instance with the AMI that you located in the previous step\. Configure the security group to allow for inbound TCP traffic to port 3389\. For more information about configuring security groups, see [Security groups for your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html)\. This configuration enables you to use an RDP client to connect to the instance\.
1. Connect to the instance using [SSH](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html)\. Run the following command to set the password for `ec2-user`\.
```
[ec2-user ~]$ sudo passwd ec2-user
```
1. Open an RDP client on the computer from which you will connect to the instance \(for example, Remote Desktop Connection on a computer running Microsoft Windows\)\. Enter `ec2-user` as the user name and enter the password that you set in the previous step\.
**To disable the MATE Desktop Environment on your EC2 instance**
You can turn off the GUI environment at any time by running one of the following commands\.
```
[ec2-user ~]$ sudo systemctl disable xrdp
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-mate.md |
9a1833d24539-2 | ```
[ec2-user ~]$ sudo systemctl disable xrdp
```
```
[ec2-user ~]$ sudo systemctl stop xrdp
```
**To enable the MATE Desktop Environment on your EC2 instance**
To turn the GUI back on, you can run one of the following commands\.
```
[ec2-user ~]$ sudo systemctl enable xrdp
```
```
[ec2-user ~]$ sudo systemctl start xrdp
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-ami-mate.md |
ebdb22c7db83-0 | You can subscribe to an AWS Marketplace product and launch an instance from the product's AMI using the Amazon EC2 launch wizard\. For more information about paid AMIs, see [Paid AMIs](paid-amis.md)\. To cancel your subscription after launch, you first have to terminate all instances running from it\. For more information, see [Managing your AWS Marketplace subscriptions](paid-amis.md#marketplace-manage-subscriptions)\.
**To launch an instance from the AWS Marketplace using the launch wizard**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the Amazon EC2 dashboard, choose **Launch instance**\.
1. On the **Choose an Amazon Machine Image \(AMI\)** page, choose the **AWS Marketplace** category on the left\. Find a suitable AMI by browsing the categories, or using the search functionality\. Choose **Select** to choose your product\.
1. A dialog displays an overview of the product you've selected\. You can view the pricing information, as well as any other information that the vendor has provided\. When you're ready, choose **Continue**\.
**Note**
You are not charged for using the product until you have launched an instance with the AMI\. Take note of the pricing for each supported instance type, as you will be prompted to select an instance type on the next page of the wizard\. Additional taxes may also apply to the product\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/launch-marketplace-console.md |
ebdb22c7db83-1 | 1. On the **Choose an Instance Type** page, select the hardware configuration and size of the instance to launch\. When you're done, choose **Next: Configure Instance Details**\.
1. On the next pages of the wizard, you can configure your instance, add storage, and add tags\. For more information about the different options you can configure, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\. Choose **Next** until you reach the **Configure Security Group** page\.
The wizard creates a new security group according to the vendor's specifications for the product\. The security group may include rules that allow all IPv4 addresses \(`0.0.0.0/0`\) access on SSH \(port 22\) on Linux or RDP \(port 3389\) on Windows\. We recommend that you adjust these rules to allow only a specific address or range of addresses to access your instance over those ports\.
When you are ready, choose **Review and Launch**\.
1. On the **Review Instance Launch** page, check the details of the AMI from which you're about to launch the instance, as well as the other configuration details you set up in the wizard\. When you're ready, choose **Launch** to select or create a key pair, and launch your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/launch-marketplace-console.md |
ebdb22c7db83-2 | 1. Depending on the product you've subscribed to, the instance may take a few minutes or more to launch\. You are first subscribed to the product before your instance can launch\. If there are any problems with your credit card details, you will be asked to update your account details\. When the launch confirmation page displays, choose **View Instances** to go to the Instances page\.
**Note**
You are charged the subscription price as long as your instance is running, even if it is idle\. If your instance is stopped, you may still be charged for storage\.
1. When your instance is in the `running` state, you can connect to it\. To do this, select your instance in the list and choose **Connect**\. Follow the instructions in the dialog\. For more information about connecting to your instance, see [Connect to your Linux instance](AccessingInstances.md)\.
**Important**
Check the vendor's usage instructions carefully, as you may need to use a specific user name to log in to the instance\. For more information about accessing your subscription details, see [Managing your AWS Marketplace subscriptions](paid-amis.md#marketplace-manage-subscriptions)\.
1. If the instance fails to launch or the state immediately goes to `terminated` instead of `running`, see [Troubleshooting instance launch issues](troubleshooting-launch.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/launch-marketplace-console.md |
0d438b20c9ca-0 | To launch instances from AWS Marketplace products using the API or command line tools, first ensure that you are subscribed to the product\. You can then launch an instance with the product's AMI ID using the following methods:
| Method | Documentation |
| --- | --- |
| AWS CLI | Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command, or see the following topic for more information: [Launching an Instance](https://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-launch.html#launching-instances)\. |
| AWS Tools for Windows PowerShell | Use the [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) command, or see the following topic for more information: [Launch an Amazon EC2 Instance Using Windows PowerShell](https://docs.aws.amazon.com/powershell/latest/userguide/pstools-ec2-launch.html) |
| Query API | Use the [RunInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-RunInstances.html) request\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/launch-marketplace-console.md |
7ef6a3a538ec-0 | A *Spot Fleet* is a collection, or fleet, of Spot Instances, and optionally On\-Demand Instances\.
The Spot Fleet attempts to launch the number of Spot Instances and On\-Demand Instances to meet the target capacity that you specified in the Spot Fleet request\. The request for Spot Instances is fulfilled if there is available capacity and the maximum price you specified in the request exceeds the current Spot price\. The Spot Fleet also attempts to maintain its target capacity fleet if your Spot Instances are interrupted\.
You can also set a maximum amount per hour that you’re willing to pay for your fleet, and Spot Fleet launches instances until it reaches the maximum amount\. When the maximum amount you're willing to pay is reached, the fleet stops launching instances even if it hasn’t met the target capacity\.
A *Spot Instance pool* is a set of unused EC2 instances with the same instance type \(for example, `m5.large`\), operating system, Availability Zone, and network platform\. When you make a Spot Fleet request, you can include multiple launch specifications, that vary by instance type, AMI, Availability Zone, or subnet\. The Spot Fleet selects the Spot Instance pools that are used to fulfill the request, based on the launch specifications included in your Spot Fleet request, and the configuration of the Spot Fleet request\. The Spot Instances come from the selected pools\.
**Topics**
+ [On\-Demand in Spot Fleet](#on-demand-in-spot)
+ [Allocation strategy for Spot Instances](#spot-fleet-allocation-strategy)
+ [Spot price overrides](#spot-price-overrides) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
7ef6a3a538ec-1 | + [Spot price overrides](#spot-price-overrides)
+ [Control spending](#spot-fleet-control-spending)
+ [Spot Fleet instance weighting](#spot-instance-weighting)
+ [Walkthrough: Using Spot Fleet with instance weighting](#instance-weighting-walkthrough) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
42fd5bbaab57-0 | To ensure that you always have instance capacity, you can include a request for On\-Demand capacity in your Spot Fleet request\. In your Spot Fleet request, you specify your desired target capacity and how much of that capacity must be On\-Demand\. The balance comprises Spot capacity, which is launched if there is available Amazon EC2 capacity and availability\. For example, if in your Spot Fleet request you specify target capacity as 10 and On\-Demand capacity as | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
42fd5bbaab57-1 | capacity as 10 and On\-Demand capacity as 8, Amazon EC2 launches 8 capacity units as On\-Demand, and 2 capacity units \(10\-8=2\) as Spot\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
92109ba5bf52-0 | When Spot Fleet attempts to fulfill your On\-Demand capacity, it defaults to launching the lowest\-priced instance type first\. If `OnDemandAllocationStrategy` is set to `prioritized`, Spot Fleet uses priority to determine which instance type to use first in fulfilling On\-Demand capacity\. The priority is assigned to the launch template override, and the highest priority is launched first\.
For example, you have configured three launch template overrides, each with a different instance type: `c3.large`, `c4.large`, and `c5.large`\. The On\-Demand price for `c5.large` is less than for `c4.large`\. `c3.large` is the cheapest\. If you do not use priority to determine the order, the fleet fulfills On\-Demand capacity by starting with `c3.large`, and then `c5.large`\. Because you often have unused Reserved Instances for `c4.large`, you can set the launch template override priority so that the order is `c4.large`, `c3.large`, and then `c5.large`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
58d8294223e6-0 | The allocation strategy for the Spot Instances in your Spot Fleet determines how it fulfills your Spot Fleet request from the possible Spot Instance pools represented by its launch specifications\. The following are the allocation strategies that you can specify in your Spot Fleet request:
`lowestPrice`
The Spot Instances come from the pool with the lowest price\. This is the default strategy\.
`diversified`
The Spot Instances are distributed across all pools\.
`capacityOptimized`
The Spot Instances come from the pool with optimal capacity for the number of instances that are launching\.
`InstancePoolsToUseCount`
The Spot Instances are distributed across the number of Spot pools that you specify\. This parameter is valid only when used in combination with `lowestPrice`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
d378bf7228a6-0 | After Spot Instances are terminated due to a change in the Spot price or available capacity of a Spot Instance pool, a Spot Fleet of type `maintain` launches replacement Spot Instances\. If the allocation strategy is `lowestPrice`, the fleet launches replacement instances in the pool where the Spot price is currently the lowest\. If the allocation strategy is `diversified`, the fleet distributes the replacement Spot Instances across the remaining pools\. If the allocation strategy is `lowestPrice` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
d378bf7228a6-1 | pools\. If the allocation strategy is `lowestPrice` in combination with `InstancePoolsToUseCount`, the fleet selects the Spot pools with the lowest price and launches Spot Instances across the number of Spot pools that you specify\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
3e70c935db35-0 | To optimize the costs for your use of Spot Instances, specify the `lowestPrice` allocation strategy so that Spot Fleet automatically deploys the least expensive combination of instance types and Availability Zones based on the current Spot price\.
For On\-Demand Instance target capacity, Spot Fleet always selects the least expensive instance type based on the public On\-Demand price, while continuing to follow the allocation strategy \(either `lowestPrice`, `capacityOptimized`, or `diversified`\) for Spot Instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
165917370a8e-0 | To create a fleet of Spot Instances that is both cheap and diversified, use the `lowestPrice` allocation strategy in combination with `InstancePoolsToUseCount`\. Spot Fleet automatically deploys the cheapest combination of instance types and Availability Zones based on the current Spot price across the number of Spot pools that you specify\. This combination can be used to avoid the most expensive Spot Instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
f247656a2fd3-0 | With Spot Instances, pricing changes slowly over time based on long\-term trends in supply and demand, but capacity fluctuates in real time\. The `capacityOptimized` strategy automatically launches Spot Instances into the most available pools by looking at real\-time capacity data and predicting which are the most available\. This works well for workloads such as big data and analytics, image and media rendering, machine learning, and high performance computing that may have a higher cost of | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
f247656a2fd3-1 | computing that may have a higher cost of interruption associated with restarting work and checkpointing\. By offering the possibility of fewer interruptions, the `capacityOptimized` strategy can lower the overall cost of your workload\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
4a9838972581-0 | You can optimize your Spot Fleets based on your use case\.
If your fleet is small or runs for a short time, the probability that your Spot Instances may be interrupted is low, even with all the instances in a single Spot Instance pool\. Therefore, the `lowestPrice` strategy is likely to meet your needs while providing the lowest cost\.
If your fleet is large or runs for a long time, you can improve the availability of your fleet by distributing the Spot Instances across multiple pools\. For example, if your Spot Fleet request specifies 10 pools and a target capacity of 100 instances, the fleet launches 10 Spot Instances in each pool\. If the Spot price for one pool exceeds your maximum price for this pool, only 10% of your fleet is affected\. Using this strategy also makes your fleet less sensitive to increases in the Spot price in any one pool over time\.
With the `diversified` strategy, the Spot Fleet does not launch Spot Instances into any pools with a Spot price that is equal to or higher than the [On\-Demand price](https://aws.amazon.com/ec2/pricing/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
4a9838972581-1 | To create a cheap and diversified fleet, use the `lowestPrice` strategy in combination with `InstancePoolsToUseCount`\. You can use a low or high number of Spot pools across which to allocate your Spot Instances\. For example, if you run batch processing, we recommend specifying a low number of Spot pools \(for example, `InstancePoolsToUseCount=2`\) to ensure that your queue always has compute capacity while maximizing savings\. If you run a web service, we recommend specifying a high number of Spot pools \(for example, `InstancePoolsToUseCount=10`\) to minimize the impact if a Spot Instance pool becomes temporarily unavailable\.
If your fleet runs workloads that may have a higher cost of interruption associated with restarting work and checkpointing, then use the `capacityOptimized` strategy\. This strategy offers the possibility of fewer interruptions, which can lower the overall cost of your workload\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
e27702ee8992-0 | Each Spot Fleet request can include a global maximum price, or use the default \(the On\-Demand price\)\. Spot Fleet uses this as the default maximum price for each of its launch specifications\.
You can optionally specify a maximum price in one or more launch specifications\. This price is specific to the launch specification\. If a launch specification includes a specific price, the Spot Fleet uses this maximum price, overriding the global maximum price\. Any other launch specifications that do not include a specific maximum price still use the global maximum price\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
14ea62489ee7-0 | Spot Fleet stops launching instances when it has either reached the target capacity or the maximum amount you’re willing to pay\. To control the amount you pay per hour for your fleet, you can specify the `SpotMaxTotalPrice` for Spot Instances and the `OnDemandMaxTotalPrice` for On\-Demand Instances\. When the maximum total price is reached, Spot Fleet stops launching instances even if it hasn’t met the target capacity\.
The following examples show two different scenarios\. In the first, Spot Fleet stops launching instances when it has met the target capacity\. In the second, Spot Fleet stops launching instances when it has reached the maximum amount you’re willing to pay\.
**Example: Stop launching instances when target capacity is reached**
Given a request for `m4.large` On\-Demand Instances, where:
+ On\-Demand Price: $0\.10 per hour
+ `OnDemandTargetCapacity`: 10
+ `OnDemandMaxTotalPrice`: $1\.50
Spot Fleet launches 10 On\-Demand Instances because the total of $1\.00 \(10 instances x $0\.10\) does not exceed the `OnDemandMaxTotalPrice` of $1\.50\.
**Example: Stop launching instances when maximum total price is reached**
Given a request for `m4.large` On\-Demand Instances, where:
+ On\-Demand Price: $0\.10 per hour
+ `OnDemandTargetCapacity`: 10 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
14ea62489ee7-1 | + On\-Demand Price: $0\.10 per hour
+ `OnDemandTargetCapacity`: 10
+ `OnDemandMaxTotalPrice`: $0\.80
If Spot Fleet launches the On\-Demand target capacity \(10 On\-Demand Instances\), the total cost per hour would be $1\.00\. This is more than the amount \($0\.80\) specified for `OnDemandMaxTotalPrice`\. To prevent spending more than you're willing to pay, Spot Fleet launches only 8 On\-Demand Instances \(below the On\-Demand target capacity\) because launching more would exceed the `OnDemandMaxTotalPrice`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
b608312406f7-0 | When you request a fleet of Spot Instances, you can define the capacity units that each instance type would contribute to your application's performance, and adjust your maximum price for each Spot Instance pool accordingly using *instance weighting*\.
By default, the price that you specify is *per instance hour*\. When you use the instance weighting feature, the price that you specify is *per unit hour*\. You can calculate your price per unit hour by dividing your price for an instance type by the number of units that it represents\. Spot Fleet calculates the number of Spot Instances to launch by dividing the target capacity by the instance weight\. If the result isn't an integer, the Spot Fleet rounds it up to the next integer, so that the size of your fleet is not below its target capacity\. Spot Fleet can select any pool that you specify in your launch specification, even if the capacity of the instances launched exceeds the requested target capacity\.
The following tables provide examples of calculations to determine the price per unit for a Spot Fleet request with a target capacity of 10\.
| Instance type | Instance weight | Price per instance hour | Price per unit hour | Number of instances launched |
| --- | --- | --- | --- | --- |
| r3\.xlarge | 2 | $0\.05 | \.025 \(\.05 divided by 2\) | 5 \(10 divided by 2\) |
| Instance type | Instance weight | Price per instance hour | Price per unit hour | Number of instances launched |
| --- | --- | --- | --- | --- | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
b608312406f7-1 | | --- | --- | --- | --- | --- |
| r3\.8xlarge | 8 | $0\.10 | \.0125 \(\.10 divided by 8\) | 2 \(10 divided by 8, result rounded up\) |
Use Spot Fleet instance weighting as follows to provision the target capacity that you want in the pools with the lowest price per unit at the time of fulfillment:
1. Set the target capacity for your Spot Fleet either in instances \(the default\) or in the units of your choice, such as virtual CPUs, memory, storage, or throughput\.
1. Set the price per unit\.
1. For each launch configuration, specify the weight, which is the number of units that the instance type represents toward the target capacity\.
**Instance weighting example**
Consider a Spot Fleet request with the following configuration:
+ A target capacity of 24
+ A launch specification with an instance type `r3.2xlarge` and a weight of 6
+ A launch specification with an instance type `c3.xlarge` and a weight of 5
The weights represent the number of units that instance type represents toward the target capacity\. If the first launch specification provides the lowest price per unit \(price for `r3.2xlarge` per instance hour divided by 6\), the Spot Fleet would launch four of these instances \(24 divided by 6\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
b608312406f7-2 | If the second launch specification provides the lowest price per unit \(price for `c3.xlarge` per instance hour divided by 5\), the Spot Fleet would launch five of these instances \(24 divided by 5, result rounded up\)\.
**Instance weighting and allocation strategy**
Consider a Spot Fleet request with the following configuration:
+ A target capacity of 30
+ A launch specification with an instance type `c3.2xlarge` and a weight of 8
+ A launch specification with an instance type `m3.xlarge` and a weight of 8
+ A launch specification with an instance type `r3.xlarge` and a weight of 8
The Spot Fleet would launch four instances \(30 divided by 8, result rounded up\)\. With the `lowestPrice` strategy, all four instances come from the pool that provides the lowest price per unit\. With the `diversified` strategy, the Spot Fleet launches one instance in each of the three pools, and the fourth instance in whichever pool provides the lowest price per unit\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
1ed4d89874d4-0 | This walkthrough uses a fictitious company called Example Corp to illustrate the process of requesting a Spot Fleet using instance weighting\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
b5fdedd40f90-0 | Example Corp, a pharmaceutical company, wants to leverage the computational power of Amazon EC2 for screening chemical compounds that might be used to fight cancer\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
e98d8aadb092-0 | Example Corp first reviews [Spot Best Practices](https://aws.amazon.com/ec2/spot/getting-started/#bestpractices)\. Next, Example Corp determines the following requirements for their Spot Fleet\.
**Instance types**
Example Corp has a compute\- and memory\-intensive application that performs best with at least 60 GB of memory and eight virtual CPUs \(vCPUs\)\. They want to maximize these resources for the application at the lowest possible price\. Example Corp decides that any of the following EC2 instance types would meet their needs:
| Instance type | Memory \(GiB\) | vCPUs |
| --- | --- | --- |
| r3\.2xlarge | 61 | 8 |
| r3\.4xlarge | 122 | 16 |
| r3\.8xlarge | 244 | 32 |
**Target capacity in units**
With instance weighting, target capacity can equal a number of instances \(the default\) or a combination of factors such as cores \(vCPUs\), memory \(GiBs\), and storage \(GBs\)\. By considering the base for their application \(60 GB of RAM and eight vCPUs\) as 1 unit, Example Corp decides that 20 times this amount would meet their needs\. So the company sets the target capacity of their Spot Fleet request to 20\.
**Instance weights** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
e98d8aadb092-1 | **Instance weights**
After determining the target capacity, Example Corp calculates instance weights\. To calculate the instance weight for each instance type, they determine the units of each instance type that are required to reach the target capacity as follows:
+ r3\.2xlarge \(61\.0 GB, 8 vCPUs\) = 1 unit of 20
+ r3\.4xlarge \(122\.0 GB, 16 vCPUs\) = 2 units of 20
+ r3\.8xlarge \(244\.0 GB, 32 vCPUs\) = 4 units of 20
Therefore, Example Corp assigns instance weights of 1, 2, and 4 to the respective launch configurations in their Spot Fleet request\.
**Price per unit hour**
Example Corp uses the [On\-Demand price](https://aws.amazon.com/ec2/pricing/) per instance hour as a starting point for their price\. They could also use recent Spot prices, or a combination of the two\. To calculate the price per unit hour, they divide their starting price per instance hour by the weight\. For example:
| Instance type | On\-Demand price | Instance weight | Price per unit hour |
| --- | --- | --- | --- |
| r3\.2xLarge | $0\.7 | 1 | $0\.7 |
| r3\.4xLarge | $1\.4 | 2 | $0\.7 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
e98d8aadb092-2 | | r3\.4xLarge | $1\.4 | 2 | $0\.7 |
| r3\.8xLarge | $2\.8 | 4 | $0\.7 |
Example Corp could use a global price per unit hour of $0\.7 and be competitive for all three instance types\. They could also use a global price per unit hour of $0\.7 and a specific price per unit hour of $0\.9 in the `r3.8xlarge` launch specification\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
de1d5ba5f7eb-0 | Before creating a Spot Fleet request, Example Corp verifies that it has an IAM role with the required permissions\. For more information, see [Spot Fleet permissions](spot-fleet-requests.md#spot-fleet-prerequisites)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
a53b021b977f-0 | Example Corp creates a file, `config.json`, with the following configuration for its Spot Fleet request:
```
{
"SpotPrice": "0.70",
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.2xlarge",
"SubnetId": "subnet-482e4972",
"WeightedCapacity": 1
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.4xlarge",
"SubnetId": "subnet-482e4972",
"WeightedCapacity": 2
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.8xlarge",
"SubnetId": "subnet-482e4972",
"SpotPrice": "0.90",
"WeightedCapacity": 4
} | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
a53b021b977f-1 | "SpotPrice": "0.90",
"WeightedCapacity": 4
}
]
}
```
Example Corp creates the Spot Fleet request using the [request\-spot\-fleet](https://docs.aws.amazon.com/cli/latest/reference/ec2/request-spot-fleet.html) command\.
```
aws ec2 request-spot-fleet --spot-fleet-request-config file://config.json
```
For more information, see [Spot Fleet requests](spot-fleet-requests.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
c8fd44cf85a1-0 | The allocation strategy determines which Spot Instance pools your Spot Instances come from\.
With the `lowestPrice` strategy \(which is the default strategy\), the Spot Instances come from the pool with the lowest price per unit at the time of fulfillment\. To provide 20 units of capacity, the Spot Fleet launches either 20 `r3.2xlarge` instances \(20 divided by 1\), 10 `r3.4xlarge` instances \(20 divided by 2\), or 5 `r3.8xlarge` instances \(20 divided by 4\)\.
If Example Corp used the `diversified` strategy, the Spot Instances would come from all three pools\. The Spot Fleet would launch 6 `r3.2xlarge` instances \(which provide 6 units\), 3 `r3.4xlarge` instances \(which provide 6 units\), and 2 `r3.8xlarge` instances \(which provide 8 units\), for a total of 20 units\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet.md |
4e38e24ccea2-0 | When you modify an EBS volume, it goes through a sequence of states\. The volume enters the `modifying` state, the `optimizing` state, and finally the `completed` state\. At this point, the volume is ready to be further modified\.
**Note**
Rarely, a transient AWS fault can result in a `failed` state\. This is not an indication of volume health; it merely indicates that the modification to the volume failed\. If this occurs, retry the volume modification\.
While the volume is in the `optimizing` state, your volume performance is in between the source and target configuration specifications\. Transitional volume performance will be no less than the source volume performance\. If you are downgrading IOPS, transitional volume performance is no less than the target volume performance\.
Volume modification changes take effect as follows:
+ Size changes usually take a few seconds to complete and take effect after a volume is in the `Optimizing` state\.
+ Performance \(IOPS\) changes can take from a few minutes to a few hours to complete and are dependent on the configuration change being made\.
+ It might take up to 24 hours for a new configuration to take effect, and in some cases more, such as when the volume has not been fully initialized\. Typically, a fully used 1\-TiB volume takes about 6 hours to migrate to a new performance configuration\.
Use one of the following methods to monitor the progress of a volume modification\.
**Topics**
+ [Monitoring the progress of a volume modification \(console\)](#console_monitoring) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
4e38e24ccea2-1 | **Topics**
+ [Monitoring the progress of a volume modification \(console\)](#console_monitoring)
+ [Monitoring the progress of a volume modification \(AWS CLI\)](#api_cli_monitoring)
+ [Monitoring the progress of a volume modification \(CloudWatch Events\)](#cwe_monitoring) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
44f1356461c5-0 | Use the following procedure to view the progress of one or more volume modifications\.
**To monitor progress of a modification using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Volumes**\.
1. Select the volume\.
1. The **State** column and the **State** field in the details pane contain information in the following format: *volume\-state* \- *modification\-state* \(*progress*%\)\. The possible volume states are **creating**, **available**, **in\-use**, **deleting**, **deleted**, and **error**\. The possible modification states are **modifying**, **optimizing**, and **completed**\. Shortly after the volume modification is completed, we remove the modification state and progress, leaving only the volume state\.
In this example, the modification state of the selected volume is **optimizing**\. The modification state of the next volume is **modifying**\.
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/monitor_modifications.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
44f1356461c5-1 | 1. Choose the text in the **State** field in the details pane to display information about the most recent modification action, as shown in the previous step\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
b74e050ffc33-0 | Use the [describe\-volumes\-modifications](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-volumes-modifications.html) command to view the progress of one or more volume modifications\. The following example describes the volume modifications for two volumes\.
```
aws ec2 describe-volumes-modifications --volume-id vol-11111111111111111 vol-22222222222222222
```
In the following example output, the volume modifications are still in the `modifying` state\. Progress is reported as a percentage\.
```
{
"VolumesModifications": [
{
"TargetSize": 200,
"TargetVolumeType": "io1",
"ModificationState": "modifying",
"VolumeId": "vol-11111111111111111",
"TargetIops": 10000,
"StartTime": "2017-01-19T22:21:02.959Z",
"Progress": 0,
"OriginalVolumeType": "gp2",
"OriginalIops": 300,
"OriginalSize": 100
},
{
"TargetSize": 2000,
"TargetVolumeType": "sc1",
"ModificationState": "modifying", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
Subsets and Splits