id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
a84bdbf364af-0 | An IAM policy is a JSON document that consists of one or more statements\. Each statement is structured as follows\.
```
{
"Statement":[{
"Effect":"effect",
"Action":"action",
"Resource":"arn",
"Condition":{
"condition":{
"key":"value"
}
}
}
]
}
```
There are various elements that make up a statement:
+ **Effect:** The *effect* can be `Allow` or `Deny`\. By default, IAM users don't have permission to use resources and API actions, so all requests are denied\. An explicit allow overrides the default\. An explicit deny overrides any allows\.
+ **Action**: The *action* is the specific API action for which you are granting or denying permission\. To learn about specifying *action*, see [Actions for Amazon EC2](#UsingWithEC2_Actions)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
a84bdbf364af-1 | + **Resource**: The resource that's affected by the action\. Some Amazon EC2 API actions allow you to include specific resources in your policy that can be created or modified by the action\. You specify a resource using an Amazon Resource Name \(ARN\) or using the wildcard \(\*\) to indicate that the statement applies to all resources\. For more information, see [Supported resource\-level permissions for Amazon EC2 API actions](#ec2-supported-iam-actions-resources)\.
+ **Condition**: Conditions are optional\. They can be used to control when your policy is in effect\. For more information about specifying conditions for Amazon EC2, see [Condition keys for Amazon EC2](#amazon-ec2-keys)\.
For more information about example IAM policy statements for Amazon EC2, see [Example policies for working with the AWS CLI or an AWS SDK](ExamplePolicies_EC2.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
c060454b6525-0 | In an IAM policy statement, you can specify any API action from any service that supports IAM\. For Amazon EC2, use the following prefix with the name of the API action: `ec2:`\. For example: `ec2:RunInstances` and `ec2:CreateImage`\.
To specify multiple actions in a single statement, separate them with commas as follows:
```
"Action": ["ec2:action1", "ec2:action2"]
```
You can also specify multiple actions using wildcards\. For example, you can specify all actions whose name begins with the word "Describe" as follows:
```
"Action": "ec2:Describe*"
```
To specify all Amazon EC2 API actions, use the \* wildcard as follows:
```
"Action": "ec2:*"
```
For a list of Amazon EC2 actions, see [Actions](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-apis.html) in the *Amazon EC2 API Reference*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
b7af2567c30f-0 | *Resource\-level permissions* refers to the ability to specify which resources users are allowed to perform actions on\. Amazon EC2 has partial support for resource\-level permissions\. This means that for certain Amazon EC2 actions, you can control when users are allowed to use those actions based on conditions that have to be fulfilled, or specific resources that users are allowed to use\. For example, you can grant users permissions to launch instances, but only of a specific type, and only using a specific AMI\.
To specify a resource in an IAM policy statement, use its Amazon Resource Name \(ARN\)\. For more information about specifying the ARN value, see [Amazon Resource Names \(ARNs\) for Amazon EC2](#EC2_ARN_Format)\. If an API action does not support individual ARNs, you must use a wildcard \(\*\) to specify that all resources can be affected by the action\.
To see tables that identify which Amazon EC2 API actions support resource\-level permissions, and the ARNs and condition keys that you can use in a policy, see [Actions, Resources, and Condition Keys for Amazon EC2](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonec2.html) in the *IAM User Guide*\. Condition keys for Amazon EC2 are also further explained in a later section\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
b7af2567c30f-1 | Keep in mind that you can apply tag\-based resource\-level permissions in the IAM policies you use for Amazon EC2 API actions\. This gives you better control over which resources a user can create, modify, or use\. For more information, see [Granting permission to tag resources during creation](supported-iam-actions-tagging.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
24538cf3da56-0 | Each IAM policy statement applies to the resources that you specify using their ARNs\.
An ARN has the following general syntax:
```
arn:aws:[service]:[region]:[account]:resourceType/resourcePath
```
*service*
The service \(for example, `ec2`\)\.
*region*
The Region for the resource \(for example, `us-east-1`\)\.
*account*
The AWS account ID, with no hyphens \(for example, `123456789012`\)\.
*resourceType*
The type of resource \(for example, `instance`\)\.
*resourcePath*
A path that identifies the resource\. You can use the \* wildcard in your paths\.
For example, you can indicate a specific instance \(`i-1234567890abcdef0`\) in your statement using its ARN as follows\.
```
"Resource": "arn:aws:ec2:us-east-1:123456789012:instance/i-1234567890abcdef0"
```
You can specify all instances that belong to a specific account by using the \* wildcard as follows\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
24538cf3da56-1 | ```
You can specify all instances that belong to a specific account by using the \* wildcard as follows\.
```
"Resource": "arn:aws:ec2:us-east-1:123456789012:instance/*"
```
You can also specify all Amazon EC2 resources that belong to a specific account by using the \* wildcard as follows\.
```
"Resource": "arn:aws:ec2:us-east-1:123456789012:*"
```
To specify all resources, or if a specific API action does not support ARNs, use the \* wildcard in the `Resource` element as follows\.
```
"Resource": "*"
```
Many Amazon EC2 API actions involve multiple resources\. For example, `AttachVolume` attaches an Amazon EBS volume to an instance, so an IAM user must have permissions to use the volume and the instance\. To specify multiple resources in a single statement, separate their ARNs with commas, as follows\.
```
"Resource": ["arn1", "arn2"]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
24538cf3da56-2 | ```
"Resource": ["arn1", "arn2"]
```
For a list of ARNs for Amazon EC2 resources, see [Resource Types Defined by Amazon EC2](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonec2.html#amazonec2-resources-for-iam-policies) in the *IAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
d86ec2762314-0 | In a policy statement, you can optionally specify conditions that control when it is in effect\. Each condition contains one or more key\-value pairs\. Condition keys are not case\-sensitive\. We've defined AWS\-wide condition keys, plus additional service\-specific condition keys\.
For a list of service\-specific condition keys for Amazon EC2, see [ Condition Keys for Amazon EC2](https://docs.aws.amazon.com/IAM/latest/UserGuide/list_amazonec2.html#amazonec2-policy-keys) in the *IAM User Guide*\. Amazon EC2 also implements the AWS\-wide condition keys\. For more information, see [Information Available in All Requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_variables.html#policy-vars-infoallreqs) in the *IAM User Guide*\.
To use a condition key in your IAM policy, use the `Condition` statement\. For example, the following policy grants users permission to add and remove inbound and outbound rules for any security group\. It uses the `ec2:Vpc` condition key to specify that these actions can only be performed on security groups in a specific VPC\.
```
{
"Version": "2012-10-17",
"Statement":[{
"Effect":"Allow",
"Action": [
"ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
d86ec2762314-1 | "ec2:AuthorizeSecurityGroupIngress",
"ec2:AuthorizeSecurityGroupEgress",
"ec2:RevokeSecurityGroupIngress",
"ec2:RevokeSecurityGroupEgress"],
"Resource": "arn:aws:ec2:region:account:security-group/*",
"Condition": {
"StringEquals": {
"ec2:Vpc": "arn:aws:ec2:region:account:vpc/vpc-11223344556677889"
}
}
}
]
}
```
If you specify multiple conditions, or multiple keys in a single condition, we evaluate them using a logical AND operation\. If you specify a single condition with multiple values for one key, we evaluate the condition using a logical OR operation\. For permissions to be granted, all conditions must be met\.
You can also use placeholders when you specify conditions\. For example, you can grant an IAM user permission to use resources with a tag that specifies his or her IAM user name\. For more information, see [Policy Variables](https://docs.aws.amazon.com/IAM/latest/UserGuide/PolicyVariables.html) in the *IAM User Guide*\.
**Important** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
d86ec2762314-2 | **Important**
Many condition keys are specific to a resource, and some API actions use multiple resources\. If you write a policy with a condition key, use the `Resource` element of the statement to specify the resource to which the condition key applies\. If not, the policy may prevent users from performing the action at all, because the condition check fails for the resources to which the condition key does not apply\. If you do not want to specify a resource, or if you've written the `Action` element of your policy to include multiple API actions, then you must use the `...IfExists` condition type to ensure that the condition key is ignored for resources that do not use it\. For more information, see [\.\.\.IfExists Conditions](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements.html#Conditions_IfExists) in the *IAM User Guide*\.
All Amazon EC2 actions support the `aws:RequestedRegion` and `ec2:Region` condition keys\. For more information, see [Example: Restricting access to a specific Region](ExamplePolicies_EC2.md#iam-example-region)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
d86ec2762314-3 | The `ec2:SourceInstanceARN` key can be used for conditions that specify the ARN of the instance from which a request is made\. This condition key is available AWS\-wide and is not service\-specific\. For policy examples, see [Allows an EC2 Instance to Attach or Detach Volumes](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_examples_ec2_volumes-instance.html) and [Example: Allowing a specific instance to view resources in other AWS services](ExamplePolicies_EC2.md#iam-example-source-instance)\. The `ec2:SourceInstanceARN` key cannot be used as a variable to populate the ARN for the `Resource` element in a statement\.
For example policy statements for Amazon EC2, see [Example policies for working with the AWS CLI or an AWS SDK](ExamplePolicies_EC2.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
02bf732243a1-0 | After you've created an IAM policy, we recommend that you check whether it grants users the permissions to use the particular API actions and resources they need before you put the policy into production\.
First, create an IAM user for testing purposes, and then attach the IAM policy that you created to the test user\. Then, make a request as the test user\.
If the Amazon EC2 action that you are testing creates or modifies a resource, you should make the request using the `DryRun` parameter \(or run the AWS CLI command with the `--dry-run` option\)\. In this case, the call completes the authorization check, but does not complete the operation\. For example, you can check whether the user can terminate a particular instance without actually terminating it\. If the test user has the required permissions, the request returns `DryRunOperation`; otherwise, it returns `UnauthorizedOperation`\.
If the policy doesn't grant the user the permissions that you expected, or is overly permissive, you can adjust the policy as needed and retest until you get the desired results\.
**Important**
It can take several minutes for policy changes to propagate before they take effect\. Therefore, we recommend that you allow five minutes to pass before you test your policy updates\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
02bf732243a1-1 | It can take several minutes for policy changes to propagate before they take effect\. Therefore, we recommend that you allow five minutes to pass before you test your policy updates\.
If an authorization check fails, the request returns an encoded message with diagnostic information\. You can decode the message using the `DecodeAuthorizationMessage` action\. For more information, see [DecodeAuthorizationMessage](https://docs.aws.amazon.com/STS/latest/APIReference/API_DecodeAuthorizationMessage.html) in the *AWS Security Token Service API Reference*, and [decode\-authorization\-message](https://docs.aws.amazon.com/cli/latest/reference/sts/decode-authorization-message.html) in the *AWS CLI Command Reference*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/iam-policy-structure.md |
5aad5908ebd8-0 | When your needs change, you can modify your Standard or Convertible Reserved Instances and continue to benefit from the billing benefit\. You can modify attributes such as the Availability Zone, instance size \(within the same instance family\), and scope of your Reserved Instance\.
**Note**
You can also exchange a Convertible Reserved Instance for another Convertible Reserved Instance with a different configuration\. For more information, see [Exchanging Convertible Reserved Instances](ri-convertible-exchange.md)\.
You can modify all or a subset of your Reserved Instances\. You can separate your original Reserved Instances into two or more new Reserved Instances\. For example, if you have a reservation for 10 instances in `us-east-1a` and decide to move 5 instances to `us-east-1b`, the modification request results in two new reservations: one for 5 instances in `us-east-1a` and the other for 5 instances in `us-east-1b`\.
You can also *merge* two or more Reserved Instances into a single Reserved Instance\. For example, if you have four `t2.small` Reserved Instances of one instance each, you can merge them to create one `t2.large` Reserved Instance\. For more information, see [Support for modifying instance sizes](#ri-modification-instancemove)\.
After modification, the benefit of the Reserved Instances is applied only to instances that match the new parameters\. For example, if you change the Availability Zone of a reservation, the capacity reservation and pricing benefits are automatically applied to instance usage in the new Availability Zone\. Instances that no longer match the new parameters are charged at the On\-Demand rate, unless your account has other applicable reservations\.
If your modification request succeeds: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
5aad5908ebd8-1 | If your modification request succeeds:
+ The modified reservation becomes effective immediately and the pricing benefit is applied to the new instances beginning at the hour of the modification request\. For example, if you successfully modify your reservations at 9:15PM, the pricing benefit transfers to your new instance at 9:00PM\. You can get the effective date of the modified Reserved Instances by using the [describe\-reserved\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances.html) command\.
+ The original reservation is retired\. Its end date is the start date of the new reservation, and the end date of the new reservation is the same as the end date of the original Reserved Instance\. If you modify a three\-year reservation that had 16 months left in its term, the resulting modified reservation is a 16\-month reservation with the same end date as the original one\.
+ The modified reservation lists a $0 fixed price and not the fixed price of the original reservation\.
+ The fixed price of the modified reservation does not affect the discount pricing tier calculations applied to your account, which are based on the fixed price of the original reservation\.
If your modification request fails, your Reserved Instances maintain their original configuration, and are immediately available for another modification request\.
There is no fee for modification, and you do not receive any new bills or invoices\.
You can modify your reservations as frequently as you like, but you cannot change or cancel a pending modification request after you submit it\. After the modification has completed successfully, you can submit another modification request to roll back any changes you made, if needed\.
**Topics** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
5aad5908ebd8-2 | **Topics**
+ [Requirements and restrictions for modification](#ri-modification-limits)
+ [Support for modifying instance sizes](#ri-modification-instancemove)
+ [Submitting modification requests](#ri-modification-process)
+ [Troubleshooting modification requests](#ri-modification-process-messages) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
516007602469-0 | You can modify these attributes as follows\.
| Modifiable attribute | Supported platforms | Limitations |
| --- | --- | --- |
| Change **Availability Zones** within the same Region | Linux and Windows | \- |
| Change the **scope** from Availability Zone to Region and vice versa | Linux and Windows | If you change the scope from Availability Zone to Region, you lose the capacity reservation benefit\. If you change the scope from Region to Availability Zone, you lose Availability Zone flexibility and instance size flexibility \(if applicable\)\. For more information, see [How Reserved Instances are applied](apply_ri.md)\. |
| Change the **instance size** within the same instance family | Linux/UNIX only Instance size flexibility is not available for Reserved Instances on the other platforms, which include Linux with SQL Server Standard, Linux with SQL Server Web, Linux with SQL Server Enterprise, Red Hat Enterprise Linux, SUSE Linux, Windows, Windows with SQL Standard, Windows with SQL Server Enterprise, and Windows with SQL Server Web\. | The reservation must use default tenancy\. Some instance families are not supported, because there are no other sizes available\. For more information, see [Support for modifying instance sizes](#ri-modification-instancemove)\. |
| Change the **network** from EC2\-Classic to Amazon VPC and vice versa | Linux and Windows | The network platform must be available in your AWS account\. If you created your AWS account after 2013\-12\-04, it does not support EC2\-Classic\. |
**Requirements** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
516007602469-1 | **Requirements**
Amazon EC2 processes your modification request if there is sufficient capacity for your target configuration \(if applicable\), and if the following conditions are met:
+ The Reserved Instance cannot be modified before or at the same time that you purchase it
+ The Reserved Instance must be active
+ There cannot be a pending modification request
+ The Reserved Instance is not listed in the Reserved Instance Marketplace
+ There must be a match between the instance size footprint of the active reservation and the target configuration\. For more information, see [Support for modifying instance sizes](#ri-modification-instancemove)\.
+ The input Reserved Instances are all Standard Reserved Instances or all Convertible Reserved Instances, not some of each type
+ The input Reserved Instances must expire within the same hour, if they are Standard Reserved Instances
+ The Reserved Instance is not a G4 instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
4e1d3ccbf053-0 | You can modify the instance size of a Reserved Instance if the following requirements are met\.
**Requirements**
+ The platform is Linux/UNIX\.
+ You must select another instance size in the same instance family\. For example, you cannot modify an Reserved Instance from `t2` to `t3`, whether you use the same size or a different size\.
You cannot modify the instance size of Reserved Instances for the following instances, because each of these instance families has only one size:
+ `cc2.8xlarge`
+ `cr1.8xlarge`
+ `hs1.8xlarge`
+ `t1.micro`
+ The original and modified Reserved Instance must have the same instance size footprint\.
**Topics**
+ [Instance size footprint](#ri-modification-instance-size-footprint)
+ [Normalization factors for bare metal instances](#ri-normalization-factor-bare-metal-2) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
1b1c15b76112-0 | Each Reserved Instance has an *instance size footprint*, which is determined by the normalization factor of the instance size and the number of instances in the reservation\. When you modify the instance sizes in an Reserved Instance, the footprint of the target configuration must match that of the original configuration, otherwise the modification request is not processed\.
To calculate the instance size footprint of a Reserved Instance, multiply the number of instances by the normalization factor\. In the Amazon EC2 console, the normalization factor is measured in units\. The following table describes the normalization factor for the instance sizes in an instance family\. For example, `t2.medium` has a normalization factor of 2, so a reservation for four `t2.medium` instances has a footprint of 8 units\.
| Instance size | Normalization factor |
| --- | --- |
| nano | 0\.25 |
| micro | 0\.5 |
| small | 1 |
| medium | 2 |
| large | 4 |
| xlarge | 8 |
| 2xlarge | 16 |
| 4xlarge | 32 |
| 8xlarge | 64 |
| 9xlarge | 72 |
| 10xlarge | 80 |
| 12xlarge | 96 |
| 16xlarge | 128 |
| 18xlarge | 144 |
| 24xlarge | 192 |
| 32xlarge | 256 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
1b1c15b76112-1 | | 18xlarge | 144 |
| 24xlarge | 192 |
| 32xlarge | 256 |
You can allocate your reservations into different instance sizes across the same instance family as long as the instance size footprint of your reservation remains the same\. For example, you can divide a reservation for one `t2.large` \(1 @ 4 units\) instance into four `t2.small` \(4 @ 1 unit\) instances\. Similarly, you can combine a reservation for four `t2.small` instances into one `t2.large` instance\. However, you cannot change your reservation for two `t2.small` instances into one `t2.large` instance because the footprint of the modified reservation \(4 units\) is larger than the footprint of the existing reservation \(2 units\)\.
In the following example, you have a reservation with two `t2.micro` instances \(1 unit\) and a reservation with one `t2.small` instance \(1 unit\)\. If you merge both of these reservations to a single reservation with one `t2.medium` instance \(2 units\), the footprint of the modified reservation equals the footprint of the combined reservations\.
![\[Modifying Reserved Instances\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-modify-merge.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
1b1c15b76112-2 | You can also modify a reservation to divide it into two or more reservations\. In the following example, you have a reservation with a `t2.medium` instance \(2 units\)\. You can divide the reservation into two reservations, one with two `t2.nano` instances \(\.5 units\) and the other with three `t2.micro` instances \(1\.5 units\)\.
![\[Modifying Reserved Instances\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ri-modify-divide.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
dce4434f119b-0 | You can modify a reservation with `metal` instances using other sizes within the same instance family\. Similarly, you can modify a reservation with instances other than bare metal instances using the `metal` size within the same instance family\. Generally, a bare metal instance is the same size as the largest available instance size within the same instance family\. For example, an `i3.metal` instance is the same size as an `i3.16xlarge` instance, so they have the same normalization factor\.
The following table describes the normalization factor for the bare metal instance sizes in the instance families that have bare metal instances\. The normalization factor for `metal` instances depends on the instance family, unlike the other instance sizes\.
| Bare metal instance size | Normalization factor |
| --- | --- |
| c5\.metal | 192 |
| i3\.metal | 128 |
| r5\.metal | 192 |
| r5d\.metal | 192 |
| z1d\.metal | 96 |
| m5\.metal | 192 |
| m5d\.metal | 192 |
For example, an `i3.metal` instance has a normalization factor of 128\. If you purchase an `i3.metal` default tenancy Amazon Linux/Unix Reserved Instance, you can divide the reservation as follows: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
dce4434f119b-1 | + An `i3.16xlarge` is the same size as an `i3.metal` instance, so its normalization factor is 128 \(128/1\)\. The reservation for one `i3.metal` instance can be modified into one `i3.16xlarge` instance\.
+ An `i3.8xlarge` is half the size of an `i3.metal` instance, so its normalization factor is 64 \(128/2\)\. The reservation for one `i3.metal` instance can be divided into two `i3.8xlarge` instances\.
+ An `i3.4xlarge` is a quarter the size of an `i3.metal` instance, so its normalization factor is 32 \(128/4\)\. The reservation for one `i3.metal` instance can be divided into four `i3.4xlarge` instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
6e031aa83b8e-0 | Before you modify your Reserved Instances, ensure that you have read the applicable [restrictions](#ri-modification-limits)\. Before you modify the instance size, calculate the total [instance size footprint](#ri-modification-instancemove) of the reservations that you want to modify and ensure that it matches the total instance size footprint of your target configurations\.
**To modify your Reserved Instances using the AWS Management Console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. On the **Reserved Instances** page, select one or more Reserved Instances to modify, and choose **Actions**, **Modify Reserved Instances**\.
**Note**
If your Reserved Instances are not in the active state or cannot be modified, **Modify Reserved Instances** is disabled\.
1. The first entry in the modification table displays attributes of selected Reserved Instances, and at least one target configuration beneath it\. The **Units** column displays the total instance size footprint\. Choose **Add** for each new configuration to add\. Modify the attributes as needed for each configuration, and then choose **Continue**:
+ **Scope**: Choose whether the configuration applies to an Availability Zone or to the whole Region\.
+ **Availability Zone**: Choose the required Availability Zone\. Not applicable for regional Reserved Instances\.
+ **Instance Type**: Select the required instance type\. The combined configurations must equal the instance size footprint of your original configurations\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
6e031aa83b8e-1 | + **Instance Type**: Select the required instance type\. The combined configurations must equal the instance size footprint of your original configurations\.
+ **Count**: Specify the number of instances\. To split the Reserved Instances into multiple configurations, reduce the count, choose **Add**, and specify a count for the additional configuration\. For example, if you have a single configuration with a count of 10, you can change its count to 6 and add a configuration with a count of 4\. This process retires the original Reserved Instance after the new Reserved Instances are activated\.
1. To confirm your modification choices when you finish specifying your target configurations, choose **Submit Modifications**\.
1. You can determine the status of your modification request by looking at the **State** column in the Reserved Instances screen\. The following are the possible states\.
+ **active* \(pending modification\)*** — Transition state for original Reserved Instances
+ **retired* \(pending modification\)*** — Transition state for original Reserved Instances while new Reserved Instances are being created
+ **retired** — Reserved Instances successfully modified and replaced
+ **active** — One of the following:
+ New Reserved Instances created from a successful modification request
+ Original Reserved Instances after a failed modification request
**To modify your Reserved Instances using the command line**
1. To modify your Reserved Instances, you can use one of the following commands: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
6e031aa83b8e-2 | **To modify your Reserved Instances using the command line**
1. To modify your Reserved Instances, you can use one of the following commands:
+ [modify\-reserved\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-reserved-instances.html) \(AWS CLI\)
+ [Edit\-EC2ReservedInstance](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2ReservedInstance.html) \(AWS Tools for Windows PowerShell\)
1. To get the status of your modification request \(`processing`, `fulfilled`, or `failed`\), use one of the following commands:
+ [describe\-reserved\-instances\-modifications](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-reserved-instances-modifications.html) \(AWS CLI\)
+ [Get\-EC2ReservedInstancesModification](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2ReservedInstancesModification.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
15de0daf672a-0 | If the target configuration settings that you requested were unique, you receive a message that your request is being processed\. At this point, Amazon EC2 has only determined that the parameters of your modification request are valid\. Your modification request can still fail during processing due to unavailable capacity\.
In some situations, you might get a message indicating incomplete or failed modification requests instead of a confirmation\. Use the information in such messages as a starting point for resubmitting another modification request\. Ensure that you have read the applicable [restrictions](#ri-modification-limits) before submitting the request\.
**Not all selected Reserved Instances can be processed for modification**
Amazon EC2 identifies and lists the Reserved Instances that cannot be modified\. If you receive a message like this, go to the **Reserved Instances** page in the Amazon EC2 console and check the information for the Reserved Instances\.
**Error in processing your modification request**
You submitted one or more Reserved Instances for modification and none of your requests can be processed\. Depending on the number of reservations you are modifying, you can get different versions of the message\.
Amazon EC2 displays the reasons why your request cannot be processed\. For example, you might have specified the same target configuration—a combination of Availability Zone and platform—for one or more subsets of the Reserved Instances you are modifying\. Try submitting the modification requests again, but ensure that the instance details of the reservations match, and that the target configurations for all subsets being modified are unique\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ri-modifying.md |
8946bb5b974d-0 | Amazon EC2 instances support multithreading, which enables multiple threads to run concurrently on a single CPU core\. Each thread is represented as a virtual CPU \(vCPU\) on the instance\. An instance has a default number of CPU cores, which varies according to instance type\. For example, an `m5.xlarge` instance type has two CPU cores and two threads per core by default—four vCPUs in total\.
**Note**
Each vCPU is a thread of a CPU core, except for T2 instances and instances powered by AWS Graviton2 processors\.
In most cases, there is an Amazon EC2 instance type that has a combination of memory and number of vCPUs to suit your workloads\. However, you can specify the following CPU options to optimize your instance for specific workloads or business needs:
+ **Number of CPU cores**: You can customize the number of CPU cores for the instance\. You might do this to potentially optimize the licensing costs of your software with an instance that has sufficient amounts of RAM for memory\-intensive workloads but fewer CPU cores\.
+ **Threads per core**: You can disable multithreading by specifying a single thread per CPU core\. You might do this for certain workloads, such as high performance computing \(HPC\) workloads\.
You can specify these CPU options during instance launch\. There is no additional or reduced charge for specifying CPU options\. You're charged the same as instances that are launched with default CPU options\.
**Topics**
+ [Rules for specifying CPU options](#instance-cpu-options-rules) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
8946bb5b974d-1 | **Topics**
+ [Rules for specifying CPU options](#instance-cpu-options-rules)
+ [CPU cores and threads per CPU core per instance type](#cpu-options-supported-instances-values)
+ [Specifying CPU options for your instance](#instance-specify-cpu-options)
+ [Viewing the CPU options for your instance](#view-cpu-options) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
75a408ba4083-0 | To specify the CPU options for your instance, be aware of the following rules:
+ CPU options can only be specified during instance launch and cannot be modified after launch\.
+ When you launch an instance, you must specify both the number of CPU cores and threads per core in the request\. For example requests, see [Specifying CPU options for your instance](#instance-specify-cpu-options)\.
+ The number of vCPUs for the instance is the number of CPU cores multiplied by the threads per core\. To specify a custom number of vCPUs, you must specify a valid number of CPU cores and threads per core for the instance type\. You cannot exceed the default number of vCPUs for the instance\. For more information, see [CPU cores and threads per CPU core per instance type](#cpu-options-supported-instances-values)\.
+ To disable multithreading, specify one thread per core\.
+ When you [change the instance type](ec2-instance-resize.md) of an existing instance, the CPU options automatically change to the default CPU options for the new instance type\.
+ The specified CPU options persist after you stop, start, or reboot an instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-0 | The following tables list the instance types that support specifying CPU options\. For each type, the table shows the default and supported number of CPU cores and threads per core\.
**Accelerated computing instances**
| Instance type | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core |
| --- | --- | --- | --- | --- | --- |
| f1\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| f1\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| f1\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| g3\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| g3\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| g3\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-1 | | g3s\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| g4dn\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| g4dn\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| g4dn\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| g4dn\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| g4dn\.12xlarge | 48 | 24 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| g4dn\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| inf1\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| inf1\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| inf1\.6xlarge | 24 | 12 | 2 | 2, 4, 6, 8, 10, 12 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-2 | | inf1\.6xlarge | 24 | 12 | 2 | 2, 4, 6, 8, 10, 12 | 1, 2 |
| inf1\.24xlarge | 96 | 48 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| p2\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| p2\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| p2\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| p3\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| p3\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| p3\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-3 | | p3dn\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
**Compute optimized instances**
| Instance type | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core |
| --- | --- | --- | --- | --- | --- |
| c4\.large | 2 | 1 | 2 | 1 | 1, 2 |
| c4\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| c4\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| c4\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| c4\.8xlarge | 36 | 18 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18 | 1, 2 |
| c5\.large | 2 | 1 | 2 | 1 | 1, 2 |
| c5\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| c5\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-4 | | c5\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| c5\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| c5\.9xlarge | 36 | 18 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18 | 1, 2 |
| c5\.12xlarge | 48 | 24 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| c5\.18xlarge | 72 | 36 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36 | 1, 2 |
| c5\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| c5a\.large | 2 | 1 | 2 | 1 | 1, 2 |
| c5a\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| c5a\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| c5a\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 8 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-5 | | c5a\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 8 | 1, 2 |
| c5a\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 8, 12, 16 | 1, 2 |
| c5a\.12xlarge | 48 | 24 | 2 | 1, 2, 3, 4, 8, 12, 16, 20, 24 | 1, 2 |
| c5a\.16xlarge | 64 | 32 | 2 | 1, 2, 3, 4, 8, 12, 16, 20, 24, 28, 32 | 1, 2 |
| c5a\.24xlarge | 96 | 48 | 2 | 1, 2, 3, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48 | 1, 2 |
| c5ad\.large | 2 | 1 | 2 | 1 | 1, 2 |
| c5ad\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| c5ad\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| c5ad\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 8 | 1, 2 |
| c5ad\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 8, 12, 16 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-6 | | c5ad\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 8, 12, 16 | 1, 2 |
| c5ad\.12xlarge | 48 | 24 | 2 | 1, 2, 3, 4, 8, 12, 16, 20, 24 | 1, 2 |
| c5ad\.16xlarge | 64 | 32 | 2 | 1, 2, 3, 4, 8, 12, 16, 20, 24, 28, 32 | 1, 2 |
| c5ad\.24xlarge | 96 | 48 | 2 | 1, 2, 3, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48 | 1, 2 |
| c5d\.large | 2 | 1 | 2 | 1 | 1, 2 |
| c5d\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| c5d\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| c5d\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| c5d\.9xlarge | 36 | 18 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18 | 1, 2 |
| c5d\.12xlarge | 48 | 24 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-7 | | c5d\.18xlarge | 72 | 36 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36 | 1, 2 |
| c5d\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| c5n\.large | 2 | 1 | 2 | 1 | 1, 2 |
| c5n\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| c5n\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| c5n\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| c5n\.9xlarge | 36 | 18 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18 | 1, 2 |
| c5n\.18xlarge | 72 | 36 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36 | 1, 2 |
**General purpose instances**
| Instance type | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-8 | | Instance type | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core |
| --- | --- | --- | --- | --- | --- |
| m5\.large | 2 | 1 | 2 | 1 | 1, 2 |
| m5\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| m5\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| m5\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| m5\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| m5\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| m5\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| m5\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-9 | | m5a\.large | 2 | 1 | 2 | 1 | 1, 2 |
| m5a\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| m5a\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| m5a\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| m5a\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| m5a\.12xlarge | 48 | 24 | 2 | 6, 12, 18, 24 | 1, 2 |
| m5a\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| m5a\.24xlarge | 96 | 48 | 2 | 12, 18, 24, 36, 48 | 1, 2 |
| m5ad\.large | 2 | 1 | 2 | 1 | 1, 2 |
| m5ad\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| m5ad\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| m5ad\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-10 | | m5ad\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| m5ad\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| m5ad\.12xlarge | 48 | 24 | 2 | 6, 12, 18, 24 | 1, 2 |
| m5ad\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| m5ad\.24xlarge | 96 | 48 | 2 | 12, 18, 24, 36, 48 | 1, 2 |
| m5d\.large | 2 | 1 | 2 | 1 | 1, 2 |
| m5d\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| m5d\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| m5d\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| m5d\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| m5d\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-11 | | m5d\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| m5d\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| m5dn\.large | 2 | 1 | 2 | 1 | 1, 2 |
| m5dn\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| m5dn\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| m5dn\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| m5dn\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| m5dn\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| m5dn\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-12 | | m5dn\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| m5n\.large | 2 | 1 | 2 | 1 | 1, 2 |
| m5n\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| m5n\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| m5n\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| m5n\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| m5n\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| m5n\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| m5n\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-13 | | t3\.nano | 2 | 1 | 2 | 1 | 1, 2 |
| t3\.micro | 2 | 1 | 2 | 1 | 1, 2 |
| t3\.small | 2 | 1 | 2 | 1 | 1, 2 |
| t3\.medium | 2 | 1 | 2 | 1 | 1, 2 |
| t3\.large | 2 | 1 | 2 | 1 | 1, 2 |
| t3\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| t3\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| t3a\.nano | 2 | 1 | 2 | 1 | 1, 2 |
| t3a\.micro | 2 | 1 | 2 | 1 | 1, 2 |
| t3a\.small | 2 | 1 | 2 | 1 | 1, 2 |
| t3a\.medium | 2 | 1 | 2 | 1 | 1, 2 |
| t3a\.large | 2 | 1 | 2 | 1 | 1, 2 |
| t3a\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| t3a\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
**Memory optimized instances**
| Instance type | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-14 | | Instance type | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core |
| --- | --- | --- | --- | --- | --- |
| r4\.large | 2 | 1 | 2 | 1 | 1, 2 |
| r4\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| r4\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| r4\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| r4\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| r4\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| r5\.large | 2 | 1 | 2 | 1 | 1, 2 |
| r5\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| r5\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-15 | | r5\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| r5\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| r5\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| r5\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| r5\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| r5\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| r5a\.large | 2 | 1 | 2 | 1 | 1, 2 |
| r5a\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| r5a\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| r5a\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-16 | | r5a\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| r5a\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| r5a\.12xlarge | 48 | 24 | 2 | 6, 12, 18, 24 | 1, 2 |
| r5a\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| r5a\.24xlarge | 96 | 48 | 2 | 12, 18, 24, 36, 48 | 1, 2 |
| r5ad\.large | 2 | 1 | 2 | 1 | 1, 2 |
| r5ad\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| r5ad\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| r5ad\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| r5ad\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| r5ad\.12xlarge | 48 | 24 | 2 | 6, 12, 18, 24 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-17 | | r5ad\.12xlarge | 48 | 24 | 2 | 6, 12, 18, 24 | 1, 2 |
| r5ad\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| r5ad\.24xlarge | 96 | 48 | 2 | 12, 18, 24, 36, 48 | 1, 2 |
| r5d\.large | 2 | 1 | 2 | 1 | 1, 2 |
| r5d\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| r5d\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| r5d\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| r5d\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| r5d\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| r5d\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-18 | | r5d\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| r5dn\.large | 2 | 1 | 2 | 1 | 1, 2 |
| r5dn\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| r5dn\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| r5dn\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| r5dn\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| r5dn\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| r5dn\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-19 | | r5dn\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 |
| r5n\.large | 2 | 1 | 2 | 1 | 1, 2 |
| r5n\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| r5n\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| r5n\.4xlarge | 16 | 8 | 2 | 2, 4, 6, 8 | 1, 2 |
| r5n\.8xlarge | 32 | 16 | 2 | 2, 4, 6, 8, 10, 12, 14, 16 | 1, 2 |
| r5n\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
| r5n\.16xlarge | 64 | 32 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| r5n\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-20 | | x1\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| x1\.32xlarge | 128 | 64 | 2 | 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64 | 1, 2 |
| x1e\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| x1e\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| x1e\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| x1e\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| x1e\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| x1e\.32xlarge | 128 | 64 | 2 | 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-21 | | z1d\.large | 2 | 1 | 2 | 1 | 1, 2 |
| z1d\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| z1d\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| z1d\.3xlarge | 12 | 6 | 2 | 2, 4, 6 | 1, 2 |
| z1d\.6xlarge | 24 | 12 | 2 | 2, 4, 6, 8, 10, 12 | 1, 2 |
| z1d\.12xlarge | 48 | 24 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 |
**Storage optimized instances**
| Instance type | Default vCPUs | Default CPU cores | Default threads per core | Valid number of CPU cores | Valid number of threads per core |
| --- | --- | --- | --- | --- | --- |
| d2\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| d2\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| d2\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-22 | | d2\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| d2\.8xlarge | 36 | 18 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18 | 1, 2 |
| h1\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| h1\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| h1\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| h1\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| i3\.large | 2 | 1 | 2 | 1 | 1, 2 |
| i3\.xlarge | 4 | 2 | 2 | 1, 2 | 1, 2 |
| i3\.2xlarge | 8 | 4 | 2 | 1, 2, 3, 4 | 1, 2 |
| i3\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-23 | | i3\.4xlarge | 16 | 8 | 2 | 1, 2, 3, 4, 5, 6, 7, 8 | 1, 2 |
| i3\.8xlarge | 32 | 16 | 2 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 | 1, 2 |
| i3\.16xlarge | 64 | 32 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32 | 1, 2 |
| i3en\.large | 2 | 1 | 2 | 1 | 1, 2 |
| i3en\.xlarge | 4 | 2 | 2 | 2 | 1, 2 |
| i3en\.2xlarge | 8 | 4 | 2 | 2, 4 | 1, 2 |
| i3en\.3xlarge | 12 | 6 | 2 | 2, 4, 6 | 1, 2 |
| i3en\.6xlarge | 24 | 12 | 2 | 2, 4, 6, 8, 10, 12 | 1, 2 |
| i3en\.12xlarge | 48 | 24 | 2 | 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
854a10dbabe1-24 | | i3en\.24xlarge | 96 | 48 | 2 | 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48 | 1, 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
7aa5490f2033-0 | You can specify CPU options during instance launch\. The following examples are for an `r4.4xlarge` instance type, which has the following [default values](#cpu-options-mem-optimized):
+ Default CPU cores: 8
+ Default threads per core: 2
+ Default vCPUs: 16 \(8 \* 2\)
+ Valid number of CPU cores: 1, 2, 3, 4, 5, 6, 7, 8
+ Valid number of threads per core: 1, 2 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
6f74396847e2-0 | To disable multithreading, specify one thread per core\.
**To disable multithreading during instance launch \(console\)**
1. Follow the [Launching an instance using the Launch Instance Wizard](launching-instance.md) procedure\.
1. On the **Configure Instance Details** page, for **CPU options**, choose **Specify CPU options**\.
1. For **Core count**, choose the number of required CPU cores\. In this example, to specify the default CPU core count for an `r4.4xlarge` instance, choose `8`\.
1. To disable multithreading, for **Threads per core**, choose **1**\.
1. Continue as prompted by the wizard\. When you've finished reviewing your options on the **Review Instance Launch** page, choose **Launch**\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\.
**To disable multithreading during instance launch \(AWS CLI\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
6f74396847e2-1 | **To disable multithreading during instance launch \(AWS CLI\)**
Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) AWS CLI command and specify a value of `1` for `ThreadsPerCore` for the `--cpu-options` parameter\. For `CoreCount`, specify the number of CPU cores\. In this example, to specify the default CPU core count for an `r4.4xlarge` instance, specify a value of `8`\.
```
aws ec2 run-instances --image-id ami-1a2b3c4d --instance-type r4.4xlarge --cpu-options "CoreCount=8,ThreadsPerCore=1" --key-name MyKeyPair
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
0279367265a4-0 | You can customize the number of CPU cores and threads per core for the instance\.
**To specify a custom number of vCPUs during instance launch \(console\)**
The following example launches an `r4.4xlarge` instance with six vCPUs\.
1. Follow the [Launching an instance using the Launch Instance Wizard](launching-instance.md) procedure\.
1. On the **Configure Instance Details** page, for **CPU options**, choose **Specify CPU options**\.
1. To get six vCPUs, specify three CPU cores and two threads per core, as follows:
+ For **Core count**, choose **3**\.
+ For **Threads per core**, choose **2**\.
1. Continue as prompted by the wizard\. When you've finished reviewing your options on the **Review Instance Launch** page, choose **Launch**\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\.
**To specify a custom number of vCPUs during instance launch \(AWS CLI\)**
The following example launches an `r4.4xlarge` instance with six vCPUs\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
0279367265a4-1 | The following example launches an `r4.4xlarge` instance with six vCPUs\.
Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) AWS CLI command and specify the number of CPU cores and number of threads in the `--cpu-options` parameter\. You can specify three CPU cores and two threads per core to get six vCPUs\.
```
aws ec2 run-instances --image-id ami-1a2b3c4d --instance-type r4.4xlarge --cpu-options "CoreCount=3,ThreadsPerCore=2" --key-name MyKeyPair
```
Alternatively, specify six CPU cores and one thread per core \(disable multithreading\) to get six vCPUs:
```
aws ec2 run-instances --image-id ami-1a2b3c4d --instance-type r4.4xlarge --cpu-options "CoreCount=6,ThreadsPerCore=1" --key-name MyKeyPair
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
2ce2f59518c0-0 | You can view the CPU options for an existing instance in the Amazon EC2 console or by describing the instance using the AWS CLI\.
**To view the CPU options for an instance \(console\)**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the left navigation pane, choose **Instances**, and select the instance\.
1. Choose **Description** and view the **Number of vCPUs** field\.
1. To view the core count and threads per core, choose the **Number of vCPUs** field value\.
**To view the CPU options for an instance \(AWS CLI\)**
Use the [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) command\.
```
aws ec2 describe-instances --instance-ids i-123456789abcde123
```
```
...
"Instances": [
{
"Monitoring": {
"State": "disabled"
},
"PublicDnsName": "ec2-198-51-100-5.eu-central-1.compute.amazonaws.com", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
2ce2f59518c0-1 | "PublicDnsName": "ec2-198-51-100-5.eu-central-1.compute.amazonaws.com",
"State": {
"Code": 16,
"Name": "running"
},
"EbsOptimized": false,
"LaunchTime": "2018-05-08T13:40:33.000Z",
"PublicIpAddress": "198.51.100.5",
"PrivateIpAddress": "172.31.2.206",
"ProductCodes": [],
"VpcId": "vpc-1a2b3c4d",
"CpuOptions": {
"CoreCount": 34,
"ThreadsPerCore": 1
},
"StateTransitionReason": "",
...
}
]
...
```
In the output that's returned, the `CoreCount` field indicates the number of cores for the instance\. The `ThreadsPerCore` field indicates the number of threads per core\.
Alternatively, connect to your instance and use a tool such as lscpu to view the CPU information for your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
2ce2f59518c0-2 | Alternatively, connect to your instance and use a tool such as lscpu to view the CPU information for your instance\.
You can use AWS Config to record, assess, audit, and evaluate configuration changes for instances, including terminated instances\. For more information, see [Getting Started with AWS Config](https://docs.aws.amazon.com/config/latest/developerguide/getting-started.html) in the *AWS Config Developer Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-optimize-cpu.md |
96e76755a950-0 | With On\-Demand Instances, you pay for compute capacity by the second with no long\-term commitments\. You have full control over its lifecycle—you decide when to launch, stop, hibernate, start, reboot, or terminate it\.
There is no long\-term commitment required when you purchase On\-Demand Instances\. You pay only for the seconds that your On\-Demand Instances are in the `running` state\. The price per second for a running On\-Demand Instance is fixed, and is listed on the [Amazon EC2 Pricing, On\-Demand Pricing page](http://aws.amazon.com/ec2/pricing/on-demand/)\.
We recommend that you use On\-Demand Instances for applications with short\-term, irregular workloads that cannot be interrupted\.
For significant savings over On\-Demand Instances, use [AWS Savings Plans](http://aws.amazon.com/savingsplans/), [Spot Instances](using-spot-instances.md), or [Reserved Instances](ec2-reserved-instances.md)\.
**Contents**
+ [Working with On\-Demand Instances](#working-with-on-demand-instances)
+ [On\-Demand Instance limits](#ec2-on-demand-instances-limits)
+ [Calculating how many vCPUs you need](#vcpu-limits-calculator)
+ [Requesting a limit increase](#vcpu-limits-request-increase)
+ [Monitoring On\-Demand Instance limits and usage](#monitoring-on-demand-limits) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
96e76755a950-1 | + [Monitoring On\-Demand Instance limits and usage](#monitoring-on-demand-limits)
+ [Querying the prices of AWS services](#query-aws-price-list) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
8fde8ba39cbf-0 | You can work with On\-Demand Instances in the following ways:
+ [Launch your instance](LaunchingAndUsingInstances.md)
+ [Connect to your Linux instance](AccessingInstances.md)
+ [Stop and start your instance](Stop_Start.md)
+ [Hibernate your Linux instance](Hibernate.md)
+ [Reboot your instance](ec2-instance-reboot.md)
+ [Instance retirement](instance-retirement.md)
+ [Terminate your instance](terminating-instances.md)
+ [Recover your instance](ec2-instance-recover.md)
+ [Configuring your Amazon Linux instance](Configure_Instance.md)
+ [Identify EC2 Linux instances](identify_ec2_instances.md)
If you're new to Amazon EC2, see [How to get started with Amazon EC2](concepts.md#how-to-get-started)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
527a00aa8bc2-0 | There is a limit on the number of running On\-Demand Instances per AWS account per Region\. On\-Demand Instance limits are managed in terms of the *number of virtual central processing units \(vCPUs\)* that your running On\-Demand Instances are using, regardless of the instance type\.
There are five On\-Demand Instance limits, listed in the following table\. Each limit specifies the vCPU limit for one or more instance families\. For information about the different instance families, generations, and sizes, see [Amazon EC2 Instance Types](http://aws.amazon.com/ec2/instance-types/)\.
| On\-Demand Instance limit name | Default vCPU limit |
| --- | --- |
| Running On\-Demand Standard \(A, C, D, H, I, M, R, T, and Z\) instances | 1152 vCPUs |
| Running On\-Demand F instances | 128 vCPUs |
| Running On\-Demand G instances | 128 vCPUs |
| Running On\-Demand Inf instances | 128 vCPUs |
| Running On\-Demand P instances | 128 vCPUs |
| Running On\-Demand X instances | 128 vCPUs |
**Note**
New AWS accounts may start with limits that are lower than the limits described here\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
527a00aa8bc2-1 | **Note**
New AWS accounts may start with limits that are lower than the limits described here\.
With vCPU limits, you can use your limit in terms of the number of vCPUs required to launch any combination of instance types that meet your changing application needs\. For example, with a Standard instance limit of 256 vCPUs, you could launch 32 `m5.2xlarge` instances \(32 x 8 vCPUs\) or 16 `c5.4xlarge` instances \(16 x 16 vCPUs\), or a combination of any Standard instance types and sizes that total 256 vCPUs\. For more information, see [EC2 On\-Demand Instance limits](http://aws.amazon.com/ec2/faqs/#EC2_On-Demand_Instance_limits)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
23b62f28db2f-0 | You can use the vCPU limits calculator to determine the number of vCPUs that you require for your application needs\.
When using the calculator, keep the following in mind: The calculator assumes that you have reached your current limit\. The value that you enter for **Instance count** is the number of instances that you need to launch *in addition* to what is permitted by your current limit\. The calculator adds your current limit to the **Instance count** to arrive at a new limit\.
The following screenshot shows the vCPU limits calculator\.
![\[The vCPU limit calculator in the Amazon EC2 console.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/vCPU-limit-calculator.png)
You can view and use the following controls and information:
+ **Instance type** – The instance types that you add to the vCPU limits calculator\.
+ **Instance count** – The number of instances that you require for the selected instance type\.
+ **vCPU count** – The number of vCPUs that corresponds to the **Instance count**\.
+ **Current limit** – Your current limit for the limit type to which the instance type belongs\. The limit applies to all instance types of the same limit type\. For example, in the preceding screenshot, the current limit for `m5.2xlarge` and `c5.4xlarge` is 1,920 vCPUs, which is the limit for all the instance types that belong to the All Standard instances limit\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
23b62f28db2f-1 | + **New limit** – The new limit, in number of vCPUs, which is calculated by adding **vCPU count** and **Current limit**\.
+ **X** – Choose the **X** to remove the row\.
+ **Add instance type** – Choose **Add instance type** to add another instance type to the calculator\.
+ **Limits calculation** – Displays the current limit, vCPUs needed, and new limit for the limit types\.
+ **Instance limit name** – The limit type for the instance types that you selected\.
+ **Current limit** – The current limit for the limit type\.
+ **vCPUs needed** – The number of vCPUs that corresponds to the number of instances that you specified in **Instance count**\. For the All Standard instances limit type, the vCPUs needed is calculated by adding the values for **vCPU count** for all the instance types of this limit type\.
+ **New limit** – The new limit is calculated by adding **Current limit** and **vCPUs needed**\.
+ **Options** – Choose **Request limit increase** to request a limit increase for the corresponding limit type\.
**To calculate the number of required vCPUs**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the navigation bar, select a Region\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
23b62f28db2f-2 | 1. From the navigation bar, select a Region\.
1. From the left navigator, choose **Limits**\.
1. Choose **Calculate vCPU limit**\.
1. Choose **Add instance type**, choose the required instance type, and specify the required number of instances\. To add more instance types, choose **Add instance type** again\.
1. View **Limits calculation** for the required new limit\.
1. When you've finished using the calculator, choose **Close**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
235eec4683a0-0 | You can request a limit increase for each On\-Demand Instance limit type from the [Limits page](https://console.aws.amazon.com/ec2/#Limits) or the vCPU limits calculator in the Amazon EC2 console\. Complete the required fields on the AWS Support Center [limit increase form](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-ec2-instances) with your use case\. For **Primary Instance Type**, select the limit type that corresponds to the **Instance limit name** in the vCPU limits | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
235eec4683a0-1 | **Instance limit name** in the vCPU limits calculator\. For the new limit value, use the value that appears in the **New limit** column in the vCPU limits calculator\. For more information about requesting a limit increase, see [Amazon EC2 service quotas](ec2-resource-limits.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
b09415ec03a9-0 | You can view and manage your On\-Demand Instance limits using the following:
+ The [Limits page](https://console.aws.amazon.com/ec2/#Limits) in the Amazon EC2 console
+ The Amazon EC2 [Services quotas page](https://console.aws.amazon.com/servicequotas/#!/services/ec2/quotas) in the Service Quotas console
+ The [get\-service\-quota](https://docs.aws.amazon.com/cli/latest/reference/service-quotas/get-service-quota.html) AWS CLI
+ The [Service Limits page](https://console.aws.amazon.com/trustedadvisor/home?#/category/service-limits) in the AWS Trusted Advisor console
For more information, see [Amazon EC2 service quotas](ec2-resource-limits.md) in the *Amazon EC2 User Guide for Linux Instances*, [Viewing a Service Quota](https://docs.aws.amazon.com/servicequotas/latest/userguide/gs-request-quota.html) in the *Service Quotas User Guide*, and [AWS Trusted Advisor](http://aws.amazon.com/premiumsupport/technology/trusted-advisor/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
b09415ec03a9-1 | With Amazon CloudWatch metrics integration, you can monitor EC2 usage against limits\. You can also configure alarms to warn about approaching limits\. For more information, see [Using Amazon CloudWatch Alarms](https://docs.aws.amazon.com/servicequotas/latest/userguide/configure-cloudwatch.html) in the *Service Quotas User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
2620aaec5600-0 | You can use the Price List Service API or the AWS Price List API to query the prices of On\-Demand Instances\. For more information, see [Using the AWS Price List API](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/price-changes.html) in the *AWS Billing and Cost Management User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-on-demand-instances.md |
6f40fe66020d-0 | When you launch an instance in Amazon EC2, you have the option of passing user data to the instance that can be used to perform common automated configuration tasks and even run scripts after the instance starts\. You can pass two types of user data to Amazon EC2: shell scripts and cloud\-init directives\. You can also pass this data into the launch wizard as plain text, as a file \(this is useful for launching instances using the command line tools\), or as base64\-encoded text \(for API calls\)\.
If you are interested in more complex automation scenarios, consider using AWS CloudFormation and AWS OpsWorks\. For more information, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/) and the [AWS OpsWorks User Guide](https://docs.aws.amazon.com/opsworks/latest/userguide/)\.
For information about running commands on your Windows instance at launch, see [Running Commands on Your Windows Instance at Launch](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-windows-user-data.html) and [Managing Windows Instance Configuration](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-configuration-manage.html) in the *Amazon EC2 User Guide for Windows Instances*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
6f40fe66020d-1 | In the following examples, the commands from the [Install a LAMP Web Server on Amazon Linux 2](ec2-lamp-amazon-linux-2.md) are converted to a shell script and a set of cloud\-init directives that executes when the instance launches\. In each example, the following tasks are executed by the user data:
+ The distribution software packages are updated\.
+ The necessary web server, `php`, and `mariadb` packages are installed\.
+ The `httpd` service is started and turned on via systemctl\.
+ The `ec2-user` is added to the apache group\.
+ The appropriate ownership and file permissions are set for the web directory and the files contained within it\.
+ A simple web page is created to test the web server and PHP engine\.
**Topics**
+ [Prerequisites](#user-data-requirements)
+ [User data and shell scripts](#user-data-shell-scripts)
+ [User data and the console](#user-data-console)
+ [User data and cloud\-init directives](#user-data-cloud-init)
+ [User data and the AWS CLI](#user-data-api-cli) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
2f9d568ec38c-0 | The following examples assume that your instance has a public DNS name that is reachable from the Internet\. For more information, see [Step 1: Launch an instance](EC2_GetStarted.md#ec2-launch-instance)\. You must also configure your security group to allow SSH \(port 22\), HTTP \(port 80\), and HTTPS \(port 443\) connections\. For more information about these prerequisites, see [Setting up with Amazon EC2](get-set-up-for-amazon-ec2.md)\.
Also, these instructions are intended for use with Amazon Linux 2, and the commands and directives may not work for other Linux distributions\. For more information about other distributions, such as their support for cloud\-init, see their specific documentation\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d18f7c8a2dc-0 | If you are familiar with shell scripting, this is the easiest and most complete way to send instructions to an instance at launch\. Adding these tasks at boot time adds to the amount of time it takes to boot the instance\. You should allow a few minutes of extra time for the tasks to complete before you test that the user script has finished successfully\.
**Important**
By default, user data scripts and cloud\-init directives run only during the boot cycle when you first launch an instance\. You can update your configuration to ensure that your user data scripts and cloud\-init directives run every time you restart your instance\. For more information, see [How can I execute user data with every restart of my EC2 instance?](https://aws.amazon.com/premiumsupport/knowledge-center/execute-user-data-ec2/) in the AWS Knowledge Center\.
User data shell scripts must start with the `#!` characters and the path to the interpreter you want to read the script \(commonly /bin/bash\)\. For a great introduction on shell scripting, see [the BASH Programming HOW\-TO](http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html) at the Linux Documentation Project \([tldp\.org](http://tldp.org)\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d18f7c8a2dc-1 | Scripts entered as user data are executed as the `root` user, so do not use the sudo command in the script\. Remember that any files you create will be owned by `root`; if you need non\-root users to have file access, you should modify the permissions accordingly in the script\. Also, because the script is not run interactively, you cannot include commands that require user feedback \(such as yum update without the `-y` flag\)\.
If you use an AWS API, including the AWS CLI, in a user data script, you must use an instance profile when launching the instance\. An instance profile provides the appropriate AWS credentials required by the user data script to execute the API call\. For more information, see [Using instance profiles](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_use_switch-role-ec2_instance-profiles.html) in the IAM User Guide\. The permissions you assign to the IAM role depend on which services you are calling with the API\. For more information, see [IAM roles for Amazon EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html)\.
The cloud\-init output log file \(`/var/log/cloud-init-output.log`\) captures console output so it is easy to debug your scripts following a launch if the instance does not behave the way you intended\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d18f7c8a2dc-2 | When a user data script is processed, it is copied to and executed from `/var/lib/cloud/instances/instance-id/`\. The script is not deleted after it is run\. Be sure to delete the user data scripts from `/var/lib/cloud/instances/instance-id/` before you create an AMI from the instance\. Otherwise, the script will exist in this directory on any instance launched from the AMI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
14d73ece5fb3-0 | You can specify instance user data when you launch the instance\. If the root volume of the instance is an EBS volume, you can also stop the instance and update its user data\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
2ca69b28c277-0 | Follow the procedure for launching an instance at [Launching an instance using the Launch Instance Wizard](launching-instance.md), but when you get to [Step 3: Configure Instance Details](launching-instance.md#configure_instance_details_step) in that procedure, copy your shell script in the **User data** field, and then complete the launch procedure\.
In the example script below, the script creates and configures our web server\.
```
#!/bin/bash
yum update -y
amazon-linux-extras install -y lamp-mariadb10.2-php7.2 php7.2
yum install -y httpd mariadb-server
systemctl start httpd
systemctl enable httpd
usermod -a -G apache ec2-user
chown -R ec2-user:apache /var/www
chmod 2775 /var/www
find /var/www -type d -exec chmod 2775 {} \;
find /var/www -type f -exec chmod 0664 {} \;
echo "<?php phpinfo(); ?>" > /var/www/html/phpinfo.php
```
Allow enough time for the instance to launch and execute the commands in your script, and then check to see that your script has completed the tasks that you intended\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
2ca69b28c277-1 | Allow enough time for the instance to launch and execute the commands in your script, and then check to see that your script has completed the tasks that you intended\.
For our example, in a web browser, enter the URL of the PHP test file the script created\. This URL is the public DNS address of your instance followed by a forward slash and the file name\.
```
http://my.public.dns.amazonaws.com/phpinfo.php
```
You should see the PHP information page\. If you are unable to see the PHP information page, check that the security group you are using contains a rule to allow HTTP \(port 80\) traffic\. For more information, see [Adding rules to a security group](working-with-security-groups.md#adding-security-group-rule)\.
\(Optional\) If your script did not accomplish the tasks you were expecting it to, or if you just want to verify that your script completed without errors, examine the cloud\-init output log file at `/var/log/cloud-init-output.log` and look for error messages in the output\.
For additional debugging information, you can create a Mime multipart archive that includes a cloud\-init data section with the following directive:
```
output : { all : '| tee -a /var/log/cloud-init-output.log' }
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
2ca69b28c277-2 | output : { all : '| tee -a /var/log/cloud-init-output.log' }
```
This directive sends command output from your script to `/var/log/cloud-init-output.log`\. For more information about cloud\-init data formats and creating Mime multi part archive, see [cloud\-init Formats](http://cloudinit.readthedocs.org/en/latest/topics/format.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
ddc1d893b8dc-0 | **To modify instance user data**
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 the instance and choose **Actions**, **Instance State**, **Stop**\.
**Warning**
When you stop an instance, the data on any instance store volumes is erased\. To keep data from instance store volumes, be sure to back it up to persistent storage\.
1. When prompted for confirmation, choose **Yes, Stop**\. It can take a few minutes for the instance to stop\.
1. With the instance still selected, choose **Actions**, **Instance Settings**, **View/Change User Data**\. You can't change the user data if the instance is running, but you can view it\.
1. In the **View/Change User Data** dialog box, update the user data, and then choose **Save**\.
1. Restart the instance\. The new user data is visible on your instance after you restart it; however, user data scripts are not executed\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
d3cb0e10fa79-0 | The cloud\-init package configures specific aspects of a new Amazon Linux instance when it is launched; most notably, it configures the `.ssh/authorized_keys` file for the ec2\-user so you can log in with your own private key\. For more information, see [cloud\-init](amazon-linux-ami-basics.md#amazon-linux-cloud-init)\.
The cloud\-init user directives can be passed to an instance at launch the same way that a script is passed, although the syntax is different\. For more information about cloud\-init, go to [http://cloudinit\.readthedocs\.org/en/latest/index\.html](http://cloudinit.readthedocs.org/en/latest/index.html)\.
**Important**
By default, user data scripts and cloud\-init directives run only during the boot cycle when you first launch an instance\. You can update your configuration to ensure that your user data scripts and cloud\-init directives run every time you restart your instance\. For more information, see [How can I execute user data with every restart of my EC2 instance?](https://aws.amazon.com/premiumsupport/knowledge-center/execute-user-data-ec2/) in the AWS Knowledge Center\.
Adding these tasks at boot time adds to the amount of time it takes to boot an instance\. You should allow a few minutes of extra time for the tasks to complete before you test that your user data directives have completed\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
d3cb0e10fa79-1 | **To pass cloud\-init directives to an instance with user data**
1. Follow the procedure for launching an instance at [Launching an instance using the Launch Instance Wizard](launching-instance.md), but when you get to [Step 3: Configure Instance Details](launching-instance.md#configure_instance_details_step) in that procedure, enter your cloud\-init directive text in the **User data** field, and then complete the launch procedure\.
In the example below, the directives create and configure a web server on Amazon Linux 2\. The `#cloud-config` line at the top is required in order to identify the commands as cloud\-init directives\.
```
#cloud-config
repo_update: true
repo_upgrade: all
packages:
- httpd
- mariadb-server
runcmd:
- [ sh, -c, "amazon-linux-extras install -y lamp-mariadb10.2-php7.2 php7.2" ]
- systemctl start httpd
- sudo systemctl enable httpd
- [ sh, -c, "usermod -a -G apache ec2-user" ]
- [ sh, -c, "chown -R ec2-user:apache /var/www" ]
- chmod 2775 /var/www | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
d3cb0e10fa79-2 | - [ sh, -c, "chown -R ec2-user:apache /var/www" ]
- chmod 2775 /var/www
- [ find, /var/www, -type, d, -exec, chmod, 2775, {}, \; ]
- [ find, /var/www, -type, f, -exec, chmod, 0664, {}, \; ]
- [ sh, -c, 'echo "<?php phpinfo(); ?>" > /var/www/html/phpinfo.php' ]
```
1. Allow enough time for the instance to launch and execute the directives in your user data, and then check to see that your directives have completed the tasks you intended\.
For our example, in a web browser, enter the URL of the PHP test file the directives created\. This URL is the public DNS address of your instance followed by a forward slash and the file name\.
```
http://my.public.dns.amazonaws.com/phpinfo.php
```
You should see the PHP information page\. If you are unable to see the PHP information page, check that the security group you are using contains a rule to allow HTTP \(port 80\) traffic\. For more information, see [Adding rules to a security group](working-with-security-groups.md#adding-security-group-rule)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
d3cb0e10fa79-3 | 1. \(Optional\) If your directives did not accomplish the tasks you were expecting them to, or if you just want to verify that your directives completed without errors, examine the output log file at `/var/log/cloud-init-output.log` and look for error messages in the output\. For additional debugging information, you can add the following line to your directives:
```
output : { all : '| tee -a /var/log/cloud-init-output.log' }
```
This directive sends runcmd output to `/var/log/cloud-init-output.log`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d2ef2a295ff-0 | You can use the AWS CLI to specify, modify, and view the user data for your instance\. For information about viewing user data from your instance using instance metadata, see [Retrieve instance user data](instancedata-add-user-data.md#instancedata-user-data-retrieval)\.
On Windows, you can use the AWS Tools for Windows PowerShell instead of using the AWS CLI\. For more information, see [User Data and the Tools for Windows PowerShell](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-windows-user-data.html#user-data-powershell) in the *Amazon EC2 User Guide for Windows Instances*\.
**Example: Specify user data at launch**
To specify user data when you launch your instance, use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command with the `--user-data` parameter\. With run\-instances, the AWS CLI performs base64 encoding of the user data for you\.
The following example shows how to specify a script as a string on the command line:
```
aws ec2 run-instances --image-id ami-abcd1234 --count 1 --instance-type m3.medium \
--key-name my-key-pair --subnet-id subnet-abcd1234 --security-group-ids sg-abcd1234 \
--user-data echo user data
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d2ef2a295ff-1 | --user-data echo user data
```
The following example shows how to specify a script using a text file\. Be sure to use the `file://` prefix to specify the file\.
```
aws ec2 run-instances --image-id ami-abcd1234 --count 1 --instance-type m3.medium \
--key-name my-key-pair --subnet-id subnet-abcd1234 --security-group-ids sg-abcd1234 \
--user-data file://my_script.txt
```
The following is an example text file with a shell script\.
```
#!/bin/bash
yum update -y
service httpd start
chkconfig httpd on
```
**Example: Modify the user data of a stopped instance**
You can modify the user data of a stopped instance using the [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) command\. With modify\-instance\-attribute, the AWS CLI does not perform base64 encoding of the user data for you\.
+ On a **Linux** computer, use the base64 command to encode the user data\.
```
base64 my_script.txt >my_script_base64.txt | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d2ef2a295ff-2 | ```
base64 my_script.txt >my_script_base64.txt
```
+ On a **Windows** computer, use the certutil command to encode the user data\. Before you can use this file with the AWS CLI, you must remove the first \(BEGIN CERTIFICATE\) and last \(END CERTIFICATE\) lines\.
```
certutil -encode my_script.txt my_script_base64.txt
notepad my_script_base64.txt
```
Use the `--attribute` and `--value` parameters to use the encoded text file to specify the user data\. Be sure to use the `file://` prefix to specify the file\.
```
aws ec2 modify-instance-attribute --instance-id i-1234567890abcdef0 --attribute userData --value file://my_script_base64.txt
```
**Example: Clear the user data of a stopped instance**
To delete the existing user data, use the [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) command as follows:
```
aws ec2 modify-instance-attribute --instance-id i-1234567890abcdef0 --user-data Value=
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d2ef2a295ff-3 | ```
**Example: View user data**
To retrieve the user data for an instance, use the [describe\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-attribute.html) command\. With describe\-instance\-attribute, the AWS CLI does not perform base64 decoding of the user data for you\.
```
aws ec2 describe-instance-attribute --instance-id i-1234567890abcdef0 --attribute userData
```
The following is example output with the user data base64 encoded\.
```
{
"UserData": {
"Value": "IyEvYmluL2Jhc2gKeXVtIHVwZGF0ZSAteQpzZXJ2aWNlIGh0dHBkIHN0YXJ0CmNoa2NvbmZpZyBodHRwZCBvbg=="
},
"InstanceId": "i-1234567890abcdef0"
}
```
+ On a **Linux** computer , use the `--query` option to get the encoded user data and the base64 command to decode it\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
5d2ef2a295ff-4 | ```
aws ec2 describe-instance-attribute --instance-id i-1234567890abcdef0 --attribute userData --output text --query "UserData.Value" | base64 --decode
```
+ On a **Windows** computer, use the `--query` option to get the coded user data and the certutil command to decode it\. Note that the encoded output is stored in a file and the decoded output is stored in another file\.
```
aws ec2 describe-instance-attribute --instance-id i-1234567890abcdef0 --attribute userData --output text --query "UserData.Value" >my_output.txt
certutil -decode my_output.txt my_output_decoded.txt
type my_output_decoded.txt
```
The following is example output\.
```
#!/bin/bash
yum update -y
service httpd start
chkconfig httpd on
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/user-data.md |
b893499adfe4-0 | -----
*****Copyright © 2020 Amazon Web Services, Inc. and/or its affiliates. All rights reserved.*****
-----
Amazon's trademarks and trade dress may not be used in
connection with any product or service that is not Amazon's,
in any manner that is likely to cause confusion among customers,
or in any manner that disparages or discredits Amazon. All other
trademarks not owned by Amazon are the property of their respective
owners, who may or may not be affiliated with, connected to, or
sponsored by Amazon.
----- | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
819155de5278-0 | + [What is Amazon EC2?](concepts.md)
+ [Instances and AMIs](ec2-instances-and-amis.md)
+ [Regions and Zones](using-regions-availability-zones.md)
+ [Amazon EC2 root device volume](RootDeviceStorage.md)
+ [Setting up with Amazon EC2](get-set-up-for-amazon-ec2.md)
+ [Tutorial: Getting started with Amazon EC2 Linux instances](EC2_GetStarted.md)
+ [Best practices for Amazon EC2](ec2-best-practices.md)
+ [Tutorials for Amazon EC2 Instances Running Linux](ec2-tutorials.md)
+ [Tutorial: Install a LAMP web server on Amazon Linux 2](ec2-lamp-amazon-linux-2.md)
+ [Tutorial: Install a LAMP web server with the Amazon Linux AMI](install-LAMP.md)
+ [Tutorial: Hosting a WordPress blog with Amazon Linux](hosting-wordpress.md)
+ [Tutorial: Configure SSL/TLS on Amazon Linux 2](SSL-on-amazon-linux-2.md)
+ [Tutorial: Configure SSL/TLS on Amazon Linux](SSL-on-amazon-linux-ami.md)
+ [Tutorial: Increase the availability of your application on Amazon EC2](ec2-increase-availability.md)
+ [Amazon Machine Images (AMI)](AMIs.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/index.md |
Subsets and Splits