id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
92509c03a951-0 | Use the following procedure to delete a snapshot\.
**To delete a snapshot using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Snapshots** in the navigation pane\.
1. Select a snapshot and then choose **Delete** from the **Actions** list\.
1. Choose **Yes, Delete**\.
**To delete a snapshot using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [delete\-snapshot](https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-snapshot.html) \(AWS CLI\)
+ [Remove\-EC2Snapshot](https://docs.aws.amazon.com/powershell/latest/reference/items/Remove-EC2Snapshot.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-deleting-snapshot.md |
8538a0b84082-0 | To delete multi\-volume snapshots, retrieve all of the snapshots for your multi\-volume group using the tag you applied to the group when you created the snapshots\. Then, delete the snapshots individually\. You will not be prevented from deleting individual snapshots in the multi\-volume snapshots group\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-deleting-snapshot.md |
b5484f4afa06-0 | Amazon FSx for Windows File Server provides fully managed Windows file servers, backed by a fully–native Windows file system with the features, performance, and compatibility to easily lift and shift enterprise applications to AWS\.
Amazon FSx supports a broad set of enterprise Windows workloads with fully managed file storage built on Microsoft Windows Server\. Amazon FSx has native support for Windows file system features and for the industry\-standard Server Message Block \(SMB\) protocol to access file storage over a network\. Amazon FSx is optimized for enterprise applications in the AWS Cloud, with native Windows compatibility, enterprise performance and features, and consistent sub\-millisecond latencies\.
With file storage on Amazon FSx, the code, applications, and tools that Windows developers and administrators use today can continue to work unchanged\. The Windows applications and workloads that are ideal for Amazon FSx include business applications, home directories, web serving, content management, data analytics, software build setups, and media processing workloads\.
As a fully managed service, Amazon FSx for Windows File Server eliminates the administrative overhead of setting up and provisioning file servers and storage volumes\. Additionally, it keeps Windows software up to date, detects and addresses hardware failures, and performs backups\. It also provides rich integration with other AWS services, including AWS Directory Service for Microsoft Active Directory, Amazon WorkSpaces, AWS Key Management Service, and AWS CloudTrail\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage_fsx.md |
b5484f4afa06-1 | For more information, see the [Amazon FSx for Windows File Server User Guide](https://docs.aws.amazon.com/fsx/latest/WindowsGuide/)\. For pricing information, see [Amazon FSx for Windows File Server Pricing](http://aws.amazon.com/fsx/windows/pricing/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage_fsx.md |
01549b4143c6-0 | To start using Capacity Reservations, you create the capacity reservation in the required Availability Zone\. Then, you can launch instances into the reserved capacity, view its capacity utilization in real time, and increase or decrease its capacity as needed\.
By default, Capacity Reservations automatically match new instances and running instances that have matching attributes \(instance type, platform, and Availability Zone\)\. This means that any instance with matching attributes automatically runs in the Capacity Reservation\. However, you can also target a Capacity Reservation for specific workloads\. This enables you to explicitly control which instances are allowed to run in that reserved capacity\.
You can specify how the reservation ends\. You can choose to manually cancel the Capacity Reservation or end it automatically at a specified time\. If you specify an end time, the Capacity Reservation is canceled within an hour of the specified time\. For example, if you specify 5/31/2019, 13:30:55, the Capacity Reservation is guaranteed to end between 13:30:55 and 14:30:55 on 5/31/2019\. After a reservation ends, you can no longer target instances to the Capacity Reservation\. Instances running in the reserved capacity continue to run uninterrupted\. If instances targeting a Capacity Reservation are stopped, you cannot restart them until you remove their Capacity Reservation targeting preference or configure them to target a different Capacity Reservation\.
**Contents**
+ [Creating a Capacity Reservation](#capacity-reservations-create)
+ [Working with Capacity Reservation groups](#create-cr-group)
+ [Launching instances into an existing Capacity Reservation](#capacity-reservations-launch)
+ [Modifying a Capacity Reservation](#capacity-reservations-modify) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
01549b4143c6-1 | + [Launching instances into an existing Capacity Reservation](#capacity-reservations-launch)
+ [Modifying a Capacity Reservation](#capacity-reservations-modify)
+ [Modifying an instance's Capacity Reservation settings](#capacity-reservations-modify-instance)
+ [Viewing a Capacity Reservation](#capacity-reservations-view)
+ [Canceling a Capacity Reservation](#capacity-reservations-release) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
5ad4e31e39fd-0 | After you create the Capacity Reservation, the capacity is available immediately\. The capacity remains reserved for your use as long as the Capacity Reservation is active, and you can launch instances into it at any time\. If the Capacity Reservation is open, new instances and existing instances that have matching attributes automatically run in the capacity of the Capacity Reservation\. If the Capacity Reservation is `targeted`, instances must specifically target it to run in the reserved capacity\.
Your request to create a Capacity Reservation could fail if one of the following is true:
+ Amazon EC2 does not have sufficient capacity to fulfill the request\. Either try again at a later time, try a different Availability Zone, or try a smaller capacity\. If your application is flexible across instance types and sizes, try different instance attributes\.
+ The requested quantity exceeds your On\-Demand Instance limit for the selected instance family\. Increase your On\-Demand Instance limit for the instance family and try again\. For more information, see [On\-Demand Instance limits](ec2-on-demand-instances.md#ec2-on-demand-instances-limits)\.
**To create a Capacity Reservation using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Capacity Reservations**, and then choose **Create Capacity Reservation**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
5ad4e31e39fd-1 | 1. Choose **Capacity Reservations**, and then choose **Create Capacity Reservation**\.
1. On the Create a Capacity Reservation page, configure the following settings in the **Instance details** section\. The instance type, platform, and Availability Zone of the instances that you launch must match the instance type, platform, and Availability Zone that you specify here or the Capacity Reservation is not applied\. For example, if an open Capacity Reservation doesn't match, an instance launch that targets that Capacity Reservation explicitly will fail\.
1. **Instance Type**—The type of instance to launch into the reserved capacity\.
1. **Launch EBS\-optimized instances**—Specify whether to reserve the capacity for EBS\-optimized instances\. This option is selected by default for some instance types\. For more information about EBS\-optimized instances, see [Amazon Elastic Block Store \(Amazon EBS\)](AmazonEBS.md)\.
1. **Attach instance store at launch**—Specify whether instances launched into the Capacity Reservation use temporary block\-level storage\. The data on an instance store volume persists only during the life of the associated instance\.
1. **Platform**—The operating system for your instances\. For more information, see [Supported platforms](ec2-capacity-reservations.md#capacity-reservations-platforms)\. For more information about the supported Windows platforms, see [ Supported platforms](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-capacity-reservations.html#capacity-reservations-platforms) in the *Amazon EC2 User Guide for Windows Instances*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
5ad4e31e39fd-2 | 1. **Availability Zone**—The Availability Zone in which to reserve the capacity\.
1. **Tenancy**—Specify whether to run on shared hardware \(default\) or a dedicated instance\.
1. **Quantity**—The number of instances for which to reserve capacity\. If you specify a quantity that exceeds your remaining On\-Demand Instance limit for the selected instance type, the request is denied\.
1. Configure the following settings in the **Reservation details** section:
1. **Reservation Ends**—Choose one of the following options:
+ **Manually**—Reserve the capacity until you explicitly cancel it\.
+ **Specific time**—Cancel the capacity reservation automatically at the specified date and time\.
1. **Instance eligibility**—Choose one of the following options:
+ **open**—\(Default\) The Capacity Reservation matches any instance that has matching attributes \(instance type, platform, and Availability Zone\)\. If you launch an instance with matching attributes, it is placed into the reserved capacity automatically\.
+ **targeted**—The Capacity Reservation only accepts instances that have matching attributes \(instance type, platform, and Availability Zone\), and that explicitly target the reservation\.
1. Choose **Request reservation**\.
**To create a Capacity Reservation using the AWS CLI** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
5ad4e31e39fd-3 | 1. Choose **Request reservation**\.
**To create a Capacity Reservation using the AWS CLI**
Use the [create\-capacity\-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-capacity-reservation.html) command\. For more information, see [Supported platforms](ec2-capacity-reservations.md#capacity-reservations-platforms)\. For more information about the supported Windows platforms, see [ Supported platforms](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-capacity-reservations.html#capacity-reservations-platforms) in the *Amazon EC2 User Guide for Windows Instances*\.
For example, the following command creates a Capacity Reservation that reserves capacity for three `m5.2xlarge` instances running Red Hat Enterprise Linux AMIs in the `us-east-1a` Availability Zone\.
```
aws ec2 create-capacity-reservation --instance-type m5.2xlarge --instance-platform Red Hat Enterprise Linux --availability-zone us-east-1a --instance-count 3
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-0 | You can use AWS Resource Groups to create logical collections of Capacity Reservations, called *resource groups*\. A resource group is a logical grouping of AWS resources that are all in the same AWS Region\. You can include multiple Capacity Reservations that have different attributes \(instance type, platform, and Availability Zone\) in a single resource group\.
When you create resource groups for your Capacity Reservations, you can target instances to a group of Capacity Reservations instead of an individual Capacity Reservation\. Instances that target a group of Capacity Reservations match with any Capacity Reservation in the group that has matching attributes \(instance type, platform, and Availability Zone\) and available capacity\. If the group does not have a Capacity Reservation with matching attributes and available capacity, the instances run using On\-Demand capacity\. If a matching Capacity Reservation is added to the targeted group at a later stage, the instance is automatically matched with and moved into its reserved capacity\.
To prevent unintended use of Capacity Reservations in a group, configure the Capacity Reservations in the group to accept only instances that explicitly target the capacity reservation\. To do this, set **Instance eligibility** to **targeted** \(old console\) or **Only instances that specify this reservation** \(new console\) when creating the Capacity Reservation using the Amazon EC2 console\. When using the AWS CLI, specify `--instance-match-criteria targeted` when creating the Capacity Reservation\. Doing this ensures that only instances that explicitly target the group, or a Capacity Reservation in the group, can run in the group\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-1 | If a Capacity Reservation in a group is canceled or expires while it has running instances, the instances are automatically moved to another Capacity Reservation in the group that has matching attributes and available capacity\. If there are no remaining Capacity Reservations in the group that have matching attributes and available capacity, the instances run in On\-Demand capacity\. If a matching Capacity Reservation is added to the targeted group at a later stage, the instance is automatically moved into its reserved capacity\.
**To create a group for your Capacity Reservations**
Use the [create\-group](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/create-group.html) AWS CLI command\. For `name`, provide a descriptive name for the group, and for `configuration`, specify two `Type` request parameters:
+ `AWS::EC2::CapacityReservationPool` to ensure that the resource group can be targeted for instance launches
+ `AWS::ResourceGroups::Generic` with `allowed-resource-types` set to `AWS::EC2::CapacityReservation` to ensure that the resource group accepts Capacity Reservations only
For example, the following command creates a group named `MyCRGroup`\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-2 | For example, the following command creates a group named `MyCRGroup`\.
```
$ aws resource-groups create-group --name MyCRGroup --configuration '{"Type":"AWS::EC2::CapacityReservationPool"}' '{"Type":"AWS::ResourceGroups::Generic", "Parameters": [{"Name": "allowed-resource-types", "Values": ["AWS::EC2::CapacityReservation"]}]}'
```
The following shows example output\.
```
{
"GroupConfiguration": {
"Status": "UPDATE_COMPLETE",
"Configuration": [
{
"Type": "AWS::EC2::CapacityReservationPool"
},
{
"Type": "AWS::ResourceGroups::Generic",
"Parameters": [
{
"Values": [
"AWS::EC2::CapacityReservation"
],
"Name": "allowed-resource-types"
}
]
}
]
},
"Group": {
"GroupArn": "arn:aws:resource-groups:sa-east-1:123456789012:group/MyCRGroup", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-3 | "GroupArn": "arn:aws:resource-groups:sa-east-1:123456789012:group/MyCRGroup",
"Name": "MyCRGroup"
}
}
```
**To add a Capacity Reservation to a group**
Use the [group\-resources](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/group-resources.html) AWS CLI command\. For `group`, specify the name of the group to which to add the Capacity Reservations, and for `resources`, specify ARNs of the Capacity Reservations to add\. To add multiple Capacity Reservations, separate the ARNs with a space\.
For example, the following command adds two Capacity Reservations to a group named `MyCRGroup`\.
```
$ aws resource-groups group-resources --group MyCRGroup --resource-arns arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-1234567890abcdef1 arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890
```
The following shows example output\.
```
{
"Failed": [],
"Succeeded": [ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-4 | ```
{
"Failed": [],
"Succeeded": [
"arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-1234567890abcdef1",
"arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890"
]
}
```
**To view the Capacity Reservations in a specific group**
Use the [list\-group\-resources](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/list-group-resources.html) AWS CLI command\. For `group`, specify the name of the group\.
For example, the following command lists the Capacity Reservations in a group named `MyCRGroup`\.
```
$ aws resource-groups list-group-resources --group MyCRGroup
```
The following shows example output\.
```
{
"QueryErrors": [],
"ResourceIdentifiers": [
{
"ResourceType": "AWS::EC2::CapacityReservation", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-5 | "ResourceIdentifiers": [
{
"ResourceType": "AWS::EC2::CapacityReservation",
"ResourceArn": "arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-1234567890abcdef1"
},
{
"ResourceType": "AWS::EC2::CapacityReservation",
"ResourceArn": "arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890"
}
]
}
```
**To view the groups to which a specific Capacity Reservation has been added \(AWS CLI\)**
Use the [get\-groups\-for\-capacity\-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-groups-for-capacity-reservation.html) AWS CLI command\.
For example, the following command lists the groups to which Capacity Reservation `cr-1234567890abcdef1` has been added\.
```
$ aws ec2 get-groups-for-capacity-reservation --capacity-reservation-id cr-1234567890abcdef1
```
The following shows example output\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-6 | ```
The following shows example output\.
```
{
"CapacityReservationGroups": [
{
"OwnerId": "123456789012",
"GroupArn": "arn:aws:resource-groups:sa-east-1:123456789012:group/MyCRGroup"
}
]
}
```
**To view the groups to which a specific Capacity Reservation has been added \(console\)**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Capacity Reservations**, select the Capacity Reservation to view, and then choose **View**\.
The groups to which the Capacity Reservation has been added are listed in the **Groups** card\.
**To remove a Capacity Reservation from a group**
Use the [ungroup\-resources](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/ungroup-resources.html) AWS CLI command\. For `group`, specify the ARN of the group from which to remove the Capacity Reservation, and for `resources` specify the ARNs of the Capacity Reservations to remove\. To remove multiple Capacity Reservations, separate the ARNs with a space\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-7 | The following example removes two Capacity Reservations from a group named `MyCRGroup`\.
```
$ aws resource-groups ungroup-resources --group MyCRGroup --resource-arns arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-0e154d26a16094dd arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890
```
The following shows example output\.
```
{
"Failed": [],
"Succeeded": [
"arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-0e154d26a16094dd",
"arn:aws:ec2:sa-east-1:123456789012:capacity-reservation/cr-54321abcdef567890"
]
}
```
**To delete a group**
Use the [delete\-group](https://docs.aws.amazon.com/cli/latest/reference/resource-groups/delete-group.html) AWS CLI command\. For `group`, provide the name of the group to delete\.
For example, the following command deletes a group named `MyCRGroup`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
45e72ce28e70-8 | For example, the following command deletes a group named `MyCRGroup`\.
```
$ aws resource-groups delete-group --group MyCRGroup
```
The following shows example output\.
```
{
"Group": {
"GroupArn": "arn:aws:resource-groups:sa-east-1:123456789012:group/MyCRGroup",
"Name": "MyCRGroup"
}
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
1594b584945f-0 | When you launch an instance, you can specify whether to launch the instance into any `open` Capacity Reservation, into a specific Capacity Reservation, or into a group of Capacity Reservations\. You can only launch an instance into a Capacity Reservation that has matching attributes \(instance type, platform, and Availability Zone\) and sufficient capacity\. Alternatively, you can configure the instance to avoid running in a Capacity Reservation, even if you have an `open` Capacity Reservation that has matching attributes and available capacity\.
Launching an instance into a Capacity Reservation reduces its available capacity by the number of instances launched\. For example, if you launch three instances, the available capacity of the Capacity Reservation is reduced by three\.
**To launch instances into an existing Capacity Reservation using the console**
1. Open the Launch Instance wizard by choosing **Launch Instances** from **Dashboard** or **Instances**\.
1. Select an Amazon Machine Image \(AMI\) and an instance type\.
1. Complete the **Configure Instance Details** page\. For **Capacity Reservation**, choose one of the following options:
+ **None** — Prevents the instances from launching into a Capacity Reservation\. The instances run in On\-Demand capacity\.
+ **Open** — Launches the instances into any Capacity Reservation that has matching attributes and sufficient capacity for the number of instances you selected\. If there is no matching Capacity Reservation with sufficient capacity, the instance uses On\-Demand capacity\.
+ **Target by ID** — Launches the instances into the selected Capacity Reservation\. If the selected Capacity Reservation does not have sufficient capacity for the number of instances you selected, the instance launch fails\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
1594b584945f-1 | + **Target by group** — Launches the instances into any Capacity Reservation with matching attributes and available capacity in the selected Capacity Reservation group\. If the selected group does not have a Capacity Reservation with matching attributes and available capacity, the instances launch into On\-Demand capacity\.
1. Complete the remaining steps to launch the instances\.
**To launch an instance into an existing Capacity Reservation using the AWS CLI**
Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command and specify the `--capacity-reservation-specification` parameter\.
The following example launches a `t2.micro` instance into any open Capacity Reservation that has matching attributes and available capacity:
```
aws ec2 run-instances --image-id ami-abc12345 --count 1 --instance-type t2.micro --key-name MyKeyPair --subnet-id subnet-1234567890abcdef1 --capacity-reservation-specification CapacityReservationPreference=open
```
The following example launches a `t2.micro` instance into a `targeted` Capacity Reservation:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
1594b584945f-2 | ```
The following example launches a `t2.micro` instance into a `targeted` Capacity Reservation:
```
aws ec2 run-instances --image-id ami-abc12345 --count 1 --instance-type t2.micro --key-name MyKeyPair --subnet-id subnet-1234567890abcdef1 --capacity-reservation-specification CapacityReservationTarget={CapacityReservationId=cr-a1234567}
```
The following example launches a `t2.micro` instance into a Capacity Reservation group:
```
aws ec2 run-instances --image-id ami-abc12345 --count 1 --instance-type t2.micro --key-name MyKeyPair --subnet-id subnet-1234567890abcdef1 --capacity-reservation-specification CapacityReservationTarget={CapacityReservationResourceGroupArn=arn:aws:resource-groups:us-west-1:123456789012:group/my-cr-group}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
de6e7416d79c-0 | You can change the attributes of an active Capacity Reservation after you have created it\. You cannot modify a Capacity Reservation after it has expired or after you have explicitly canceled it\.
When modifying a Capacity Reservation, you can only increase or decrease the quantity and change the way in which it is released\. You cannot change the instance type, EBS optimization, instance store settings, platform, Availability Zone, or instance eligibility of a Capacity Reservation\. If you need to modify any of these attributes, we recommend that you cancel the reservation, and then create a new one with the required attributes\.
If you specify a new quantity that exceeds your remaining On\-Demand Instance limit for the selected instance type, the update fails\.
**To modify a Capacity Reservation using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Capacity Reservations**, select the Capacity Reservation to modify, and then choose **Edit**\.
1. Modify the **Quantity** or **Reservation ends** options as needed, and choose **Save changes**\.
**To modify a Capacity Reservation using the AWS CLI**
Use the [modify\-capacity\-reservations](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-capacity-reservations.html) command:
For example, the following command modifies a Capacity Reservation to reserve capacity for eight instances\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
de6e7416d79c-1 | For example, the following command modifies a Capacity Reservation to reserve capacity for eight instances\.
```
aws ec2 modify-capacity-reservation --capacity-reservation-id cr-1234567890abcdef0 --instance-count 8
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
b913b40a6a83-0 | You can modify the following Capacity Reservation settings for a stopped instance at any time:
+ Start in any Capacity Reservation that has matching attributes \(instance type, platform, and Availability Zone\) and available capacity\.
+ Start the instance in a specific Capacity Reservation\.
+ Start the in any Capacity Reservation that has matching attributes and available capacity in a Capacity Reservation group
+ Prevent the instance from starting in a Capacity Reservation\.
**To modify an instance's Capacity Reservation settings using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Instances** and select the instance to modify\. Stop the instance if it is not already stopped\.
1. Choose **Actions**, **Modify Capacity Reservation Settings**\.
1. For **Capacity Reservation**, choose one of the following options:
+ **Open** — Launches the instances into any Capacity Reservation that has matching attributes and sufficient capacity for the number of instances you selected\. If there is no matching Capacity Reservation with sufficient capacity, the instance uses On\-Demand capacity\.
+ **None** — Prevents the instances from launching into a Capacity Reservation\. The instances run in On\-Demand capacity\.
+ **Specify Capacity Reservation** — Launches the instances into the selected Capacity Reservation\. If the selected Capacity Reservation does not have sufficient capacity for the number of instances you selected, the instance launch fails\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
b913b40a6a83-1 | + **Specify Capacity Reservation group** — Launches the instances into any Capacity Reservation with matching attributes and available capacity in the selected Capacity Reservation group\. If the selected group does not have a Capacity Reservation with matching attributes and available capacity, the instances launch into On\-Demand capacity\.
**To modify an instance's Capacity Reservation settings using the AWS CLI**
Use the [modify\-instance\-capacity\-reservation\-attributes](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-capacity-reservation-attributes.html) command\.
For example, the following command changes an instance's Capacity Reservation setting to `open` or `none`\.
```
aws ec2 modify-instance-capacity-reservation-attributes --instance-id i-1234567890abcdef0 --capacity-reservation-specification CapacityReservationPreference=none|open
```
For example, the following command modifies an instance to target a specific Capacity Reservation\.
```
aws ec2 modify-instance-capacity-reservation-attributes --instance-id i-1234567890abcdef0 --capacity-reservation-specification CapacityReservationTarget={CapacityReservationId=cr-1234567890abcdef0}
```
For example, the following command modifies an instance to target a specific Capacity Reservation group\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
b913b40a6a83-2 | ```
For example, the following command modifies an instance to target a specific Capacity Reservation group\.
```
aws ec2 modify-instance-capacity-reservation-attributes --instance-id i-1234567890abcdef0 --capacity-reservation-specification CapacityReservationTarget={CapacityReservationResourceGroupArn=arn:aws:resource-groups:us-west-1:123456789012:group/my-cr-group}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
8dd26508d420-0 | Capacity Reservations have the following possible states:
+ `active`—The capacity is available for use\.
+ `expired`—The Capacity Reservation expired automatically at the date and time specified in your reservation request\. The reserved capacity is no longer available for your use\.
+ `cancelled`—The Capacity Reservation was manually canceled\. The reserved capacity is no longer available for your use\.
+ `pending`—The Capacity Reservation request was successful but the capacity provisioning is still pending\.
+ `failed`—The Capacity Reservation request has failed\. A request can fail due to invalid request parameters, capacity constraints, or instance limit constraints\. You can view a failed request for 60 minutes\.
**To view your Capacity Reservations using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Capacity Reservations** and select a Capacity Reservation to view\.
1. Choose **View launched instances for this reservation**\.
**To view your Capacity Reservations using the AWS CLI**
Use the [describe\-capacity\-reservations](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-capacity-reservations.html) command:
For example, the following command describes all Capacity Reservations\.
```
aws ec2 describe-capacity-reservations
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
25cbf0f413e8-0 | You can cancel a Capacity Reservation at any time if you no longer need the reserved capacity\. When you cancel a Capacity Reservation, the capacity is released immediately, and it is no longer reserved for your use\.
You can cancel empty Capacity Reservations and Capacity Reservations that have running instances\. If you cancel a Capacity Reservation that has running instances, the instances continue to run normally outside of the capacity reservation at standard On\-Demand Instance rates or at a discounted rate if you have a matching Savings Plan or regional Reserved Instance\.
After you cancel a Capacity Reservation, instances that target it can no longer launch\. Modify these instances so that they either target a different Capacity Reservation, launch into any open Capacity Reservation with matching attributes and sufficient capacity, or avoid launching into a Capacity Reservation\. For more information, see [Modifying an instance's Capacity Reservation settings](#capacity-reservations-modify-instance)\.
**To cancel a Capacity Reservation using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Capacity Reservations** and select the Capacity Reservation to cancel\.
1. Choose **Cancel reservation**, **Cancel reservation**\.
**To cancel a Capacity Reservation using the AWS CLI**
Use the [cancel\-capacity\-reservation](https://docs.aws.amazon.com/cli/latest/reference/ec2/cancel-capacity-reservation.html) command: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
25cbf0f413e8-1 | For example, the following command cancels a Capacity Reservation with an ID of `cr-1234567890abcdef0`\.
```
aws ec2 cancel-capacity-reservation --capacity-reservation-id cr-1234567890abcdef0
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/capacity-reservations-using.md |
302c7f837a46-0 | By default, your instance is enabled for basic monitoring\. You can optionally enable detailed monitoring\. After you enable detailed monitoring, the Amazon EC2 console displays monitoring graphs with a 1\-minute period for the instance\.
The following describes the data interval and charge for basic and detailed monitoring for instances\.
Basic monitoring
Data is available automatically in 5\-minute periods at no charge\.
Detailed monitoring
Data is available in 1\-minute periods for an additional charge\.
To get this level of data, you must specifically enable it for the instance\. For the instances where you've enabled detailed monitoring, you can also get aggregated data across groups of similar instances\.
**Charges for detailed monitoring**
If you enable detailed monitoring, you are charged per metric that is sent to CloudWatch\. You are not charged for data storage\. For more information about pricing for detailed monitoring, see **Paid tier** on the [Amazon CloudWatch pricing page](https://aws.amazon.com/cloudwatch/pricing/)\. For a pricing example, see **Example 1 \- EC2 Detailed Monitoring** on the [Amazon CloudWatch pricing page](https://aws.amazon.com/cloudwatch/pricing/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-cloudwatch-new.md |
62fe17234ecd-0 | You can enable detailed monitoring on an instance as you launch it or after the instance is running or stopped\. Enabling detailed monitoring on an instance does not affect the monitoring of the EBS volumes attached to the instance\. For more information, see [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md)\.
**To enable detailed monitoring for an existing instance \(console\)**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Select the instance and choose **Actions**, **CloudWatch Monitoring**, **Enable Detailed Monitoring**\.
1. In the **Enable Detailed Monitoring** dialog box, choose **Yes, Enable**\.
1. Choose **Close**\.
**To enable detailed monitoring when launching an instance \(console\)**
When launching an instance using the AWS Management Console, select the **Monitoring** check box on the **Configure Instance Details** page\.
**To enable detailed monitoring for an existing instance \(AWS CLI\)**
Use the following [monitor\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/monitor-instances.html) command to enable detailed monitoring for the specified instances\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-cloudwatch-new.md |
62fe17234ecd-1 | ```
aws ec2 monitor-instances --instance-ids i-1234567890abcdef0
```
**To enable detailed monitoring when launching an instance \(AWS CLI\)**
Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command with the `--monitoring` flag to enable detailed monitoring\.
```
aws ec2 run-instances --image-id ami-09092360 --monitoring Enabled=true...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-cloudwatch-new.md |
ba2fcb8be5e0-0 | You can disable detailed monitoring on an instance as you launch it or after the instance is running or stopped\.
**To disable detailed monitoring \(console\)**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Select the instance and choose **Actions**, **CloudWatch Monitoring**, **Disable Detailed Monitoring**\.
1. In the **Disable Detailed Monitoring** dialog box, choose **Yes, Disable**\.
1. Choose **Close**\.
**To disable detailed monitoring \(AWS CLI\)**
Use the following [unmonitor\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/unmonitor-instances.html) command to disable detailed monitoring for the specified instances\.
```
aws ec2 unmonitor-instances --instance-ids i-1234567890abcdef0
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-cloudwatch-new.md |
cb77bf802204-0 | An Amazon EC2 Dedicated Host is a physical server with EC2 instance capacity fully dedicated to your use\. Dedicated Hosts allow you to use your existing per\-socket, per\-core, or per\-VM software licenses, including Windows Server, Microsoft SQL Server, SUSE, and Linux Enterprise Server\.
For information about the configurations supported on Dedicated Hosts, see the [Dedicated Hosts Configuration Table](http://aws.amazon.com/ec2/dedicated-hosts/pricing/#host-configuration)\.
**Topics**
+ [Differences between Dedicated Hosts and Dedicated Instances](#dedicated-hosts-dedicated-instances)
+ [Bring your own license](#dedicated-hosts-BYOL)
+ [Dedicated Host instance capacity](#dedicated-hosts-limits)
+ [Dedicated Hosts restrictions](#dedicated-hosts-limitations)
+ [Pricing and billing](#dedicated-hosts-billing)
+ [Working with Dedicated Hosts](how-dedicated-hosts-work.md)
+ [Working with shared Dedicated Hosts](dh-sharing.md)
+ [Host recovery](dedicated-hosts-recovery.md)
+ [Tracking configuration changes](dedicated-hosts-aws-config.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
ecbb529b7f41-0 | Dedicated Hosts and Dedicated Instances can both be used to launch Amazon EC2 instances onto physical servers that are dedicated for your use\.
There are no performance, security, or physical differences between Dedicated Instances and instances on Dedicated Hosts\. However, there are some differences between the two\. The following table highlights some of the key differences between Dedicated Hosts and Dedicated Instances:
| | Dedicated Host | Dedicated Instance |
| --- | --- | --- |
| Billing | Per\-host billing | Per\-instance billing |
| Visibility of sockets, cores, and host ID | Provides visibility of the number of sockets and physical cores | No visibility |
| Host and instance affinity | Allows you to consistently deploy your instances to the same physical server over time | Not supported |
| Targeted instance placement | Provides additional visibility and control over how instances are placed on a physical server | Not supported |
| Automatic instance recovery | Supported\. For more information, see [Host recovery](dedicated-hosts-recovery.md)\. | Supported |
| Bring Your Own License \(BYOL\) | Supported | Not supported | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
28972db7f24b-0 | Dedicated Hosts allow you to use your existing per\-socket, per\-core, or per\-VM software licenses\. When you bring your own license, you are responsible for managing your own licenses\. However, Amazon EC2 has features that help you maintain license compliance, such as instance affinity and targeted placement\.
These are the general steps to follow in order to bring your own volume licensed machine image into Amazon EC2\.
1. Verify that the license terms controlling the use of your machine images allow usage in a virtualized cloud environment\.
1. After you have verified that your machine image can be used within Amazon EC2, import it using VM Import/Export\. For information about how to import your machine image, see the [ VM Import/Export User Guide](https://docs.aws.amazon.com/vm-import/latest/userguide/)\.
1. After you import your machine image, you can launch instances from it onto active Dedicated Hosts in your account\.
1. When you run these instances, depending on the operating system, you might be required to activate these instances against your own KMS server\.
**Note**
To track how your images are used in AWS, enable host recording in AWS Config\. You can use AWS Config to record configuration changes to a Dedicated Host and use the output as a data source for license reporting\. For more information, see [Tracking configuration changes](dedicated-hosts-aws-config.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
da0e86beb3f7-0 | Support for multiple instance types on the same Dedicated Host is available for the following instance families: `c5`, `m5`, `r5`, `c5n`, `r5n`, and `m5n`\. For example, when you allocate an `r5` Dedicated Host, you can use a host with 2 sockets and 48 physical cores on which you can run different instance types, such as `r5.2xlarge` and `r5.4xlarge`\. You can run any number of instances up to the core capacity associated with the host\. For example, the table below shows the different instance type combinations you can run on a Dedicated Host\.
| Instance family | Example instance type combinations |
| --- | --- |
| R5 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-overview.html) |
| C5 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-overview.html) |
| M5 | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-overview.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
da0e86beb3f7-1 | Other instance families support only a single instance type on the same Dedicated Host\. For more information about the instance families and instance type configurations supported on Dedicated Hosts see [Amazon EC2 Dedicated Host Pricing](http://aws.amazon.com/ec2/dedicated-hosts/pricing/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
45dc3ff22ef1-0 | Before you allocate Dedicated Hosts, take note of the following limitations and restrictions:
+ To run RHEL, SUSE Linux, and SQL Server on Dedicated Hosts, you must bring your own AMIs\. RHEL, SUSE Linux, and SQL Server AMIs that are offered by AWS or that are available on AWS Marketplace can't be used with Dedicated Hosts\. For more information on how to create your own AMI, see [Bring your own license](#dedicated-hosts-BYOL)\.
+ Up to two On\-Demand Dedicated Hosts per instance family, per Region can be allocated\. It is possible to request a limit increase: [Request to Raise Allocation Limit on Amazon EC2 Dedicated Hosts](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=)\.
+ The instances that run on a Dedicated Host can only be launched in a VPC\.
+ Auto Scaling groups are supported when using a launch template that specifies a host resource group\. For more information, see [ Creating a Launch Template for an Auto Scaling Group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html) in the *Amazon EC2 Auto Scaling User Guide*\.
+ Amazon RDS instances are not supported\.
+ The AWS Free Usage tier is not available for Dedicated Hosts\.
+ Instance placement control refers to managing instance launches onto Dedicated Hosts\. You cannot launch Dedicated Hosts into placement groups\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
0bf276da0cbc-0 | The price for a Dedicated Host varies by payment option\.
**Topics**
+ [On\-Demand Dedicated Hosts](#on-demand-dedicated-hosts)
+ [Dedicated Host Reservations](#dedicated-host-reservations)
+ [Savings Plans](#dedicated-hosts-savings-plans)
+ [Pricing for Windows Server on Dedicated Hosts](#dh-win-billing) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
2adb31c4a57b-0 | On\-Demand billing is automatically activated when you allocate a Dedicated Host to your account\.
The On\-Demand price for a Dedicated Host varies by instance family and Region\. You pay per second \(with a minimum of 60 seconds\) for active Dedicated Host, regardless of the quantity or the size of instances that you choose to launch on it\. For more information about On\-Demand pricing, see [Amazon EC2 Dedicated Hosts On\-Demand Pricing](http://aws.amazon.com/ec2/dedicated-hosts/pricing/#on-demand)\.
You can release an On\-Demand Dedicated Host at any time to stop accruing charges for it\. For information about releasing a Dedicated Host, see [Releasing Dedicated Hosts](how-dedicated-hosts-work.md#dedicated-hosts-releasing)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
113387113f66-0 | Dedicated Host Reservations provide a billing discount compared to running On\-Demand Dedicated Hosts\. Reservations are available in three payment options:
+ **No Upfront**—No Upfront Reservations provide you with a discount on your Dedicated Host usage over a term and do not require an upfront payment\. Available for a one\-year term only\.
+ **Partial Upfront**—A portion of the reservation must be paid upfront and the remaining hours in the term are billed at a discounted rate\. Available in one\-year and three\-year terms\.
+ **All Upfront**—Provides the lowest effective price\. Available in one\-year and three\-year terms and covers the entire cost of the term upfront, with no additional future charges\.
You must have active Dedicated Hosts in your account before you can purchase reservations\. Each reservation covers a single, specific Dedicated Host in your account\. Reservations are applied to the instance family on the host, not the instance size\. If you have three Dedicated Hosts with different instances sizes \(`m4.xlarge`, `m4.medium`, and `m4.large`\) you can associate a single `m4` reservation with all those Dedicated Hosts\. The instance family and Region of the reservation must match that of the Dedicated Hosts you want to associate it with\.
When a reservation is associated with a Dedicated Host, the Dedicated Host can't be released until the reservation's term is over\.
For more information about reservation pricing, see [Amazon EC2 Dedicated Hosts Pricing](https://aws.amazon.com/ec2/dedicated-hosts/pricing/#reservations)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
09e1733a02da-0 | Savings Plans are a flexible pricing model that offers significant savings over On\-Demand Instances\. With Savings Plans, you make a commitment to a consistent amount of usage, in USD per hour, for a term of one or three years\. This provides you with the flexibility to use the Dedicated Hosts that best meet your needs and continue to save money, instead of making a commitment to a specific Dedicated Host\. For more information, see the [AWS Savings | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
09e1733a02da-1 | For more information, see the [AWS Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
6dae4ec8b677-0 | Subject to Microsoft licensing terms, you can bring your existing Windows Server and SQL Server licenses to Dedicated Hosts\. There is no additional charge for software usage if you choose to bring your own licenses\.
In addition, you can also use Windows Server AMIs provided by Amazon to run the latest versions of Windows Server on Dedicated Hosts\. This is common for scenarios where you have existing SQL Server licenses eligible to run on Dedicated Hosts, but need Windows Server to run the SQL Server workload\. Windows Server AMIs provided by Amazon are supported on [ current generation instance types](instance-types.md#AvailableInstanceTypes) only\. For more information, see [ Amazon EC2 Dedicated Hosts Pricing](http://aws.amazon.com/ec2/dedicated-hosts/pricing#windows-dh)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dedicated-hosts-overview.md |
e72f12178b58-0 | The [FPGA Developer AMI](https://aws.amazon.com/marketplace/pp/B06VVYBLZZ) provides the tools for developing, testing, and building AFIs\. You can use the FPGA Developer AMI on any EC2 instance with at least 32 GB of system memory \(for example, C5, M4, and R4 instances\)\.
For more information, see the documentation for the [AWS FPGA Hardware Development Kit](https://github.com/aws/aws-fpga/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/fpga-getting-started.md |
185e9fed11ef-0 | The following procedures help you install an Apache web server with PHP and MySQL support on your Amazon Linux instance \(sometimes called a LAMP web server or LAMP stack\)\. You can use this server to host a static website or deploy a dynamic PHP application that reads and writes information to a database\.
**Important**
To set up a LAMP web server on Amazon Linux 2, see [Tutorial: Install a LAMP web server on Amazon Linux 2](ec2-lamp-amazon-linux-2.md)\.
If you are trying to set up a LAMP web server on an Ubuntu or Red Hat Enterprise Linux instance, this tutorial will not work for you\. For more information about other distributions, see their specific documentation\. For information about LAMP web servers on Ubuntu, see the Ubuntu community documentation [ApacheMySQLPHP](https://help.ubuntu.com/community/ApacheMySQLPHP) topic\.
**Option: Complete this tutorial using automation**
To complete this tutorial using AWS Systems Manager Automation instead of the following tasks, run the [AWSDocs\-InstallALAMPServer\-AL](https://console.aws.amazon.com/systems-manager/automation/execute/AWSDocs-InstallALAMPServer-AL) Automation document\.
**Topics**
+ [Step 1: Prepare the LAMP server](#prepare-lamp-server-alami)
+ [Step 2: Test your Lamp server](#test-lamp-server-alami) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
185e9fed11ef-1 | + [Step 2: Test your Lamp server](#test-lamp-server-alami)
+ [Step 3: Secure the database server](#secure-mysql-lamp-server)
+ [Step 4: \(Optional\) Install phpMyAdmin](#install-phpmyadmin-lamp-server-alami)
+ [Troubleshooting](#lamp-troubleshooting-alami)
+ [Related topics](#lamp-more-info-alami) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-0 | **Prerequisites**
This tutorial assumes that you have already launched a new instance using the Amazon Linux AMI, with 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 have configured your security group to allow SSH \(port 22\), HTTP \(port 80\), and HTTPS \(port 443\) connections\. For more information about these prerequisites, see [Authorizing inbound traffic for your Linux instances](authorizing-access-to-an-instance.md)\.
**To install and start the LAMP web server with the Amazon Linux AMI**
1. [Connect to your instance](EC2_GetStarted.md#ec2-connect-to-instance-linux)\.
1. To ensure that all of your software packages are up to date, perform a quick software update on your instance\. This process may take a few minutes, but it is important to make sure that you have the latest security updates and bug fixes\.
The `-y` option installs the updates without asking for confirmation\. If you would like to examine the updates before installing, you can omit this option\.
```
[ec2-user ~]$ sudo yum update -y
```
1. Now that your instance is current, you can install the Apache web server, MySQL, and PHP software packages\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-1 | 1. Now that your instance is current, you can install the Apache web server, MySQL, and PHP software packages\.
**Note**
Some applications may not be compatible with the following recommended software environment\. Before installing these packages, check whether your LAMP applications are compatible with them\. If there is a problem, you may need to install an alternative environment\. For more information, see [The application software I want to run on my server is incompatible with the installed PHP version or other software](#software-versions-alami)
Use the yum install command to install multiple software packages and all related dependencies at the same time\.
```
[ec2-user ~]$ sudo yum install -y httpd24 php72 mysql57-server php72-mysqlnd
```
**Note**
If you receive the error `No package package-name available`, then your instance was not launched with the Amazon Linux AMI \(perhaps you are using Amazon Linux 2 instead\)\. You can view your version of Amazon Linux with the following command\.
```
cat /etc/system-release
```
1. Start the Apache web server\.
```
[ec2-user ~]$ sudo service httpd start
Starting httpd: [ OK ]
```
1. Use the chkconfig command to configure the Apache web server to start at each system boot\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-2 | 1. Use the chkconfig command to configure the Apache web server to start at each system boot\.
```
[ec2-user ~]$ sudo chkconfig httpd on
```
The chkconfig command does not provide any confirmation message when you successfully use it to enable a service\.
You can verify that httpd is on by running the following command:
```
[ec2-user ~]$ chkconfig --list httpd
httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
```
Here, httpd is `on` in runlevels 2, 3, 4, and 5 \(which is what you want to see\)\.
1. Add a security rule to allow inbound HTTP \(port 80\) connections to your instance if you have not already done so\. By default, a **launch\-wizard\-*N*** security group was set up for your instance during initialization\. This group contains a single rule to allow SSH connections\.
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Instances** and select your instance\.
1. Under **Security groups**, choose **view inbound rules**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-3 | 1. Under **Security groups**, choose **view inbound rules**\.
1. You should see the following list of rules in your default security group:
```
Security Groups associated with i-1234567890abcdef0
Ports Protocol Source launch-wizard-N
22 tcp 0.0.0.0/0 ✔
```
Using the procedures in [Adding rules to a security group](working-with-security-groups.md#adding-security-group-rule), add a new inbound security rule with the following values:
+ **Type**: HTTP
+ **Protocol**: TCP
+ **Port Range**: 80
+ **Source**: Custom
1. Test your web server\. In a web browser, type the public DNS address \(or the public IP address\) of your instance\. If there is no content in `/var/www/html`, you should see the Apache test page\. You can get the public DNS for your instance using the Amazon EC2 console \(check the **Public DNS** column; if this column is hidden, choose **Show/Hide Columns** \(the gear\-shaped icon\) and choose **Public DNS**\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-4 | If you are unable to see the Apache test page, check that the security group you are using contains a rule to allow HTTP \(port 80\) traffic\. For information about adding an HTTP rule to your security group, see [Adding rules to a security group](working-with-security-groups.md#adding-security-group-rule)\.
**Important**
If you are not using Amazon Linux, you may also need to configure the firewall on your instance to allow these connections\. For more information about how to configure the firewall, see the documentation for your specific distribution\.
![\[Apache test page\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/apache_test_page2.4.png)
**Note**
This test page appears only when there is no content in `/var/www/html`\. When you add content to the document root, your content appears at the public DNS address of your instance instead of this test page\.
Apache httpd serves files that are kept in a directory called the Apache document root\. The Amazon Linux Apache document root is `/var/www/html`, which by default is owned by root\.
```
[ec2-user ~]$ ls -l /var/www
total 16
drwxr-xr-x 2 root root 4096 Jul 12 01:00 cgi-bin
drwxr-xr-x 3 root root 4096 Aug 7 00:02 error | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-5 | drwxr-xr-x 3 root root 4096 Aug 7 00:02 error
drwxr-xr-x 2 root root 4096 Jan 6 2012 html
drwxr-xr-x 3 root root 4096 Aug 7 00:02 icons
drwxr-xr-x 2 root root 4096 Aug 7 21:17 noindex
```
To allow the `ec2-user` account to manipulate files in this directory, you must modify the ownership and permissions of the directory\. There are many ways to accomplish this task\. In this tutorial, you add `ec2-user` to the `apache` group, to give the `apache` group ownership of the `/var/www` directory and assign write permissions to the group\.
**To set file permissions**
1. Add your user \(in this case, `ec2-user`\) to the `apache` group\.
```
[ec2-user ~]$ sudo usermod -a -G apache ec2-user
```
1. Log out and then log back in again to pick up the new group, and then verify your membership\.
1. Log out \(use the exit command or close the terminal window\):
```
[ec2-user ~]$ exit
```
1. To verify your membership in the `apache` group, reconnect to your instance, and then run the following command:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-6 | 1. To verify your membership in the `apache` group, reconnect to your instance, and then run the following command:
```
[ec2-user ~]$ groups
ec2-user wheel apache
```
1. Change the group ownership of `/var/www` and its contents to the `apache` group\.
```
[ec2-user ~]$ sudo chown -R ec2-user:apache /var/www
```
1. To add group write permissions and to set the group ID on future subdirectories, change the directory permissions of `/var/www` and its subdirectories\.
```
[ec2-user ~]$ sudo chmod 2775 /var/www
[ec2-user ~]$ find /var/www -type d -exec sudo chmod 2775 {} \;
```
1. To add group write permissions, recursively change the file permissions of `/var/www` and its subdirectories:
```
[ec2-user ~]$ find /var/www -type f -exec sudo chmod 0664 {} \;
```
Now, `ec2-user` \(and any future members of the `apache` group\) can add, delete, and edit files in the Apache document root, enabling you to add content, such as a static website or a PHP application\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
a7efbd3d97a5-7 | **\(Optional\) Secure your web server**
A web server running the HTTP protocol provides no transport security for the data that it sends or receives\. When you connect to an HTTP server using a web browser, the URLs that you visit, the content of webpages that you receive, and the contents \(including passwords\) of any HTML forms that you submit are all visible to eavesdroppers anywhere along the network pathway\. The best practice for securing your web server is to install support for HTTPS \(HTTP Secure\), which protects your data with SSL/TLS encryption\.
For information about enabling HTTPS on your server, see [Tutorial: Configure SSL/TLS on Amazon Linux](SSL-on-amazon-linux-ami.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
b5705033a2c3-0 | If your server is installed and running, and your file permissions are set correctly, your `ec2-user` account should be able to create a PHP file in the `/var/www/html` directory that is available from the internet\.
**To test your LAMP web server**
1. Create a PHP file in the Apache document root\.
```
[ec2-user ~]$ echo "<?php phpinfo(); ?>" > /var/www/html/phpinfo.php
```
If you get a "Permission denied" error when trying to run this command, try logging out and logging back in again to pick up the proper group permissions that you configured in [Step 1: Prepare the LAMP server](#prepare-lamp-server-alami)\.
1. In a web browser, type the URL of the file that you just created\. This URL is the public DNS address of your instance followed by a forward slash and the file name\. For example:
```
http://my.public.dns.amazonaws.com/phpinfo.php
```
You should see the PHP information page:
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/phpinfo7.2.10.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
b5705033a2c3-1 | If you do not see this page, verify that the `/var/www/html/phpinfo.php` file was created properly in the previous step\. You can also verify that all of the required packages were installed with the following command\. The package versions in the second column do not need to match this example output\.
```
[ec2-user ~]$ sudo yum list installed httpd24 php72 mysql57-server php72-mysqlnd
Loaded plugins: priorities, update-motd, upgrade-helper
Installed Packages
httpd24.x86_64 2.4.25-1.68.amzn1 @amzn-updates
mysql56-server.x86_64 5.6.35-1.23.amzn1 @amzn-updates
php70.x86_64 7.0.14-1.20.amzn1 @amzn-updates
php70-mysqlnd.x86_64 7.0.14-1.20.amzn1 @amzn-updates
```
If any of the required packages are not listed in your output, install them using the sudo yum install *package* command\.
1. Delete the `phpinfo.php` file\. Although this can be useful information, it should not be broadcast to the internet for security reasons\.
```
[ec2-user ~]$ rm /var/www/html/phpinfo.php
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
09f8d9dd3046-0 | The default installation of the MySQL server has several features that are great for testing and development, but they should be disabled or removed for production servers\. The mysql\_secure\_installation command walks you through the process of setting a root password and removing the insecure features from your installation\. Even if you are not planning on using the MySQL server, we recommend performing this procedure\.<a name="SecuringMySQLProcedure"></a>
**To secure the database server**
1. Start the MySQL server\.
```
[ec2-user ~]$ sudo service mysqld start
Initializing MySQL database:
...
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
...
Starting mysqld: [ OK ]
```
1. Run mysql\_secure\_installation\.
```
[ec2-user ~]$ sudo mysql_secure_installation
```
1. When prompted, type a password for the root account\.
1. Type the current root password\. By default, the root account does not have a password set\. Press Enter\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
09f8d9dd3046-1 | 1. Type the current root password\. By default, the root account does not have a password set\. Press Enter\.
1. Type **Y** to set a password, and type a secure password twice\. For more information about creating a secure password, see [https://identitysafe\.norton\.com/password\-generator/](https://identitysafe.norton.com/password-generator/)\. Make sure to store this password in a safe place\.
**Note**
Setting a root password for MySQL is only the most basic measure for securing your database\. When you build or install a database\-driven application, you typically create a database service user for that application and avoid using the root account for anything but database administration\.
1. Type **Y** to remove the anonymous user accounts\.
1. Type **Y** to disable the remote root login\.
1. Type **Y** to remove the test database\.
1. Type **Y** to reload the privilege tables and save your changes\.
1. \(Optional\) If you do not plan to use the MySQL server right away, stop it\. You can restart it when you need it again\.
```
[ec2-user ~]$ sudo service mysqld stop
Stopping mysqld: [ OK ]
```
1. \(Optional\) If you want the MySQL server to start at every boot, type the following command\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
09f8d9dd3046-2 | 1. \(Optional\) If you want the MySQL server to start at every boot, type the following command\.
```
[ec2-user ~]$ sudo chkconfig mysqld on
```
You should now have a fully functional LAMP web server\. If you add content to the Apache document root at `/var/www/html`, you should be able to view that content at the public DNS address for your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
1fe691403f29-0 | **To install phpMyAdmin**
[phpMyAdmin](https://www.phpmyadmin.net/) is a web\-based database management tool that you can use to view and edit the MySQL databases on your EC2 instance\. Follow the steps below to install and configure phpMyAdmin on your Amazon Linux instance\.
**Important**
We do not recommend using phpMyAdmin to access a LAMP server unless you have enabled SSL/TLS in Apache; otherwise, your database administrator password and other data are transmitted insecurely across the internet\. For security recommendations from the developers, see [Securing your phpMyAdmin installation](https://docs.phpmyadmin.net/en/latest/setup.html#securing-your-phpmyadmin-installation)\.
**Note**
The Amazon Linux package management system does not currently support the automatic installation of phpMyAdmin in a PHP 7 environment\. This tutorial describes how to install phpMyAdmin manually\.
1. Log in to your EC2 instance using SSH\.
1. Install the required dependencies\.
```
[ec2-user ~]$ sudo yum install php72-mbstring.x86_64 -y
```
1. Restart Apache\.
```
[ec2-user ~]$ sudo service httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
1fe691403f29-1 | Stopping httpd: [ OK ]
Starting httpd: [ OK ]
```
1. Navigate to the Apache document root at `/var/www/html`\.
```
[ec2-user ~]$ cd /var/www/html
[ec2-user html]$
```
1. Select a source package for the latest phpMyAdmin release from [https://www\.phpmyadmin\.net/downloads](https://www.phpmyadmin.net/downloads)\. To download the file directly to your instance, copy the link and paste it into a wget command, as in this example:
```
[ec2-user html]$ wget https://www.phpmyadmin.net/downloads/phpMyAdmin-latest-all-languages.tar.gz
```
1. Create a phpMyAdmin folder and extract the package into it using the following command\.
```
[ec2-user html]$ mkdir phpMyAdmin && tar -xvzf phpMyAdmin-latest-all-languages.tar.gz -C phpMyAdmin --strip-components 1
```
1. Delete the *phpMyAdmin\-latest\-all\-languages\.tar\.gz* tarball\.
```
[ec2-user html]$ rm phpMyAdmin-latest-all-languages.tar.gz | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
1fe691403f29-2 | ```
[ec2-user html]$ rm phpMyAdmin-latest-all-languages.tar.gz
```
1. \(Optional\) If the MySQL server is not running, start it now\.
```
[ec2-user ~]$ sudo service mysqld start
Starting mysqld: [ OK ]
```
1. In a web browser, type the URL of your phpMyAdmin installation\. This URL is the public DNS address \(or the public IP address\) of your instance followed by a forward slash and the name of your installation directory\. For example:
```
http://my.public.dns.amazonaws.com/phpMyAdmin
```
You should see the phpMyAdmin login page:
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/phpmyadmin_login.png)
1. Log in to your phpMyAdmin installation with the `root` user name and the MySQL root password you created earlier\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
1fe691403f29-3 | 1. Log in to your phpMyAdmin installation with the `root` user name and the MySQL root password you created earlier\.
Your installation must still be configured before you put it into service\. To configure phpMyAdmin, you can [manually create a configuration file](https://docs.phpmyadmin.net/en/latest/setup.html#manually-creating-the-file), [use the setup console](https://docs.phpmyadmin.net/en/latest/setup.html#using-setup-script), or combine both approaches\.
For information about using phpMyAdmin, see the [phpMyAdmin User Guide](http://docs.phpmyadmin.net/en/latest/user.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
bb676a6c1da5-0 | This section offers suggestions for resolving common problems you may encounter while setting up a new LAMP server\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
f333f65c90c7-0 | Perform the following checks to see if your Apache web server is running and accessible\.
+ **Is the web server running?**
You can verify that httpd is on by running the following command:
```
[ec2-user ~]$ chkconfig --list httpd
httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
```
Here, httpd is `on` in runlevels 2, 3, 4, and 5 \(which is what you want to see\)\.
If the httpd process is not running, repeat the steps described in [Step 1: Prepare the LAMP server](#prepare-lamp-server-alami)\.
+ **Is the firewall correctly configured?**
If you are unable to see the Apache test page, check that the security group you are using contains a rule to allow HTTP \(port 80\) traffic\. For information about adding an HTTP rule to your security group, 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/install-LAMP.md |
3349aadd2515-0 | This tutorial recommends installing the most up\-to\-date versions of Apache HTTP Server, PHP, and MySQL\. Before installing an additional LAMP application, check its requirements to confirm that it is compatible with your installed environment\. If the latest version of PHP is not supported, it is possible \(and entirely safe\) to downgrade to an earlier supported configuration\. You can also install more than one version of PHP in parallel, which solves certain compatibility problems with a minimum of effort\. For information about configuring a preference among multiple installed PHP versions, see [Amazon Linux AMI 2016\.09 Release Notes\.](https://aws.amazon.com/amazon-linux-ami/2016.09-release-notes/)
**How to downgrade**
The well\-tested previous version of this tutorial called for the following core LAMP packages:
+ `httpd24`
+ `php56`
+ `mysql55-server`
+ `php56-mysqlnd`
If you have already installed the latest packages as recommended at the start of this tutorial, you must first uninstall these packages and other dependencies as follows:
```
[ec2-user ~]$ sudo yum remove -y httpd24 php72 mysql57-server php72-mysqlnd perl-DBD-MySQL57
```
Next, install the replacement environment:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
3349aadd2515-1 | ```
Next, install the replacement environment:
```
[ec2-user ~]$ sudo yum install -y httpd24 php56 mysql55-server php56-mysqlnd
```
If you decide later to upgrade to the recommended environment, you must first remove the customized packages and dependencies:
```
[ec2-user ~]$ sudo yum remove -y httpd24 php56 mysql55-server php56-mysqlnd perl-DBD-MySQL56
```
Now you can install the latest packages, as described earlier\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
43705e0f0fce-0 | For more information about transferring files to your instance or installing a WordPress blog on your web server, see the following documentation:
+ [Transferring files to your Linux instance using WinSCP](putty.md#Transfer_WinSCP)
+ [Transferring files to Linux instances from Linux using SCP](AccessingInstancesLinux.md#AccessingInstancesLinuxSCP)
+ [Tutorial: Hosting a WordPress blog with Amazon Linux](hosting-wordpress.md)
For more information about the commands and software used in this tutorial, see the following webpages:
+ Apache web server: [http://httpd\.apache\.org/](http://httpd.apache.org/)
+ MySQL database server: [http://www\.mysql\.com/](http://www.mysql.com/)
+ PHP programming language: [http://php\.net/](http://php.net/)
+ The `chmod` command: [https://en\.wikipedia\.org/wiki/Chmod](https://en.wikipedia.org/wiki/Chmod)
+ The `chown` command: [https://en\.wikipedia\.org/wiki/Chown](https://en.wikipedia.org/wiki/Chown) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
43705e0f0fce-1 | For more information about registering a domain name for your web server, or transferring an existing domain name to this host, see [Creating and Migrating Domains and Subdomains to Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/creating-migrating.html) in the *Amazon Route 53 Developer Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-LAMP.md |
0d573b1a261f-0 | You can create an Amazon EBS volume and then attach it to any EC2 instance in the same Availability Zone\. If you create an encrypted EBS volume, you can only attach it to supported instance types\. For more information, see [Supported instance types](EBSEncryption.md#EBSEncryption_supported_instances)\.
If you are creating a volume for a high\-performance storage scenario, you should make sure to use a Provisioned IOPS SSD \(`io1` or `io2`\) volume and attach it to an instance with enough bandwidth to support your application, such as an EBS\-optimized instance or an instance with 10\-Gigabit network connectivity\. The same advice holds for Throughput Optimized HDD \(`st1`\) and Cold HDD \(`sc1`\) volumes\. For more information, see [Amazon EBS–optimized instances](ebs-optimized.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
0d573b1a261f-1 | Empty EBS volumes receive their maximum performance the moment that they are available and do not require initialization \(formerly known as pre\-warming\)\. However, storage blocks on volumes that were created from snapshots must be initialized \(pulled down from Amazon S3 and written to the volume\) before you can access the block\. This preliminary action takes time and can cause a significant increase in the latency of an I/O operation the first time each block is accessed\. Volume performance is achieved after all blocks have been downloaded and written to the volume\. For most applications, amortizing this cost over the lifetime of the volume is acceptable\. To avoid this initial performance hit in a production environment, you can force immediate initialization of the entire volume or enable fast snapshot restore\. For more information, see [Initializing Amazon EBS volumes](ebs-initialize.md)\.
**Methods of creating a volume**
+ Create and attach EBS volumes when you launch instances by specifying a block device mapping\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md) and [Block device mapping](block-device-mapping-concepts.md)\.
+ Create an empty EBS volume and attach it to a running instance\. For more information, see [Creating an empty volume](#ebs-create-empty-volume) below\.
+ Create an EBS volume from a previously created snapshot and attach it to a running instance\. For more information, see [Creating a volume from a snapshot](#ebs-create-volume-from-snapshot) below\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
58573cfcfd38-0 | Empty volumes receive their maximum performance the moment that they are available and do not require initialization\.
**To create a empty EBS volume using the console**
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 the Region in which you would like to create your volume\. This choice is important because some Amazon EC2 resources can be shared between Regions, while others can't\. For more information, see [Resource locations](resources.md)\.
1. In the navigation pane, choose **ELASTIC BLOCK STORE**, **Volumes**\.
1. Choose **Create Volume**\.
1. For **Volume Type**, choose a volume type\. For more information, see [Amazon EBS volume types](ebs-volume-types.md)\.
1. For **Size \(GiB\)**, type the size of the volume\. For more information, see [Constraints on the size and configuration of an EBS volume](volume_constraints.md)\.
1. With a Provisioned IOPS SSD volume, for **IOPS**, type the maximum number of input/output operations per second \(IOPS\) that the volume should support\.
1. For **Availability Zone**, choose the Availability Zone in which to create the volume\. EBS volumes can only be attached to EC2 instances within the same Availability Zone\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
58573cfcfd38-1 | 1. \(Optional\) If the instance type supports EBS encryption and you want to encrypt the volume, select **Encrypt this volume** and choose a CMK\. If encryption by default is enabled in this Region, EBS encryption is enabled and the default CMK for EBS encryption is chosen\. You can choose a different CMK from **Master Key** or paste the full ARN of any key that you can access\. For more information, see [Amazon EBS encryption](EBSEncryption.md)\.
1. \(Optional\) Choose **Create additional tags** to add tags to the volume\. For each tag, provide a tag key and a tag value\. For more information, see [Tagging your Amazon EC2 resources](Using_Tags.md)\.
1. Choose **Create Volume**\. The volume is ready for use when the volume status is **Available**\.
1. To use your new volume, attach it to an instance, format it, and mount it\. For more information, see [Attaching an Amazon EBS volume to an instance](ebs-attaching-volume.md)\.
**To create an empty EBS volume using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [create\-volume](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-volume.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
58573cfcfd38-2 | + [New\-EC2Volume](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Volume.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
15b9ed5508e3-0 | Volumes created from snapshots load lazily in the background\. This means that there is no need to wait for all of the data to transfer from Amazon S3 to your EBS volume before the instance can start accessing an attached volume and all its data\. If your instance accesses data that hasn't yet been loaded, the volume immediately downloads the requested data from Amazon S3, and then continues loading the rest of the volume data in the background\. Volume performance is achieved after all blocks are downloaded and written to the volume\. To avoid the initial performance hit in a production environment, see [Initializing Amazon EBS volumes](ebs-initialize.md)\.
New EBS volumes that are created from encrypted snapshots are automatically encrypted\. You can also encrypt a volume on\-the\-fly while restoring it from an unencrypted snapshot\. Encrypted volumes can only be attached to instance types that support EBS encryption\. For more information, see [Supported instance types](EBSEncryption.md#EBSEncryption_supported_instances)\.
Use the following procedure to create a volume from a snapshot\.
**To create an EBS volume from a snapshot using the console**
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 the Region that your snapshot is located in\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
15b9ed5508e3-1 | 1. From the navigation bar, select the Region that your snapshot is located in\.
To use the snapshot to create a volume in a different region, copy your snapshot to the new Region and then use it to create a volume in that Region\. For more information, see [Copying an Amazon EBS snapshot](ebs-copy-snapshot.md)\.
1. In the navigation pane, choose **ELASTIC BLOCK STORE**, **Volumes**\.
1. Choose **Create Volume**\.
1. For **Volume Type**, choose a volume type\. For more information, see [Amazon EBS volume types](ebs-volume-types.md)\.
1. For **Snapshot ID**, start typing the ID or description of the snapshot from which you are restoring the volume, and choose it from the list of suggested options\.
1. \(Optional\) Select **Encrypt this volume** to change the encryption state of your volume\. This is optional if [encryption by default](EBSEncryption.md#encryption-by-default) is enabled\. Select a CMK from **Master Key** to specify a CMK other than the default CMK for EBS encryption\.
1. For **Size \(GiB\)**, type the size of the volume, or verify that the default size of the snapshot is adequate\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
15b9ed5508e3-2 | 1. For **Size \(GiB\)**, type the size of the volume, or verify that the default size of the snapshot is adequate\.
If you specify both a volume size and a snapshot, the size must be equal to or greater than the snapshot size\. When you select a volume type and a snapshot, the minimum and maximum sizes for the volume are shown next to **Size**\. For more information, see [Constraints on the size and configuration of an EBS volume](volume_constraints.md)\.
1. With a Provisioned IOPS SSD volume, for **IOPS**, type the maximum number of input/output operations per second \(IOPS\) that the volume should support\.
1. For **Availability Zone**, choose the Availability Zone in which to create the volume\. EBS volumes can only be attached to EC2 instances in the same Availability Zone\.
1. \(Optional\) Choose **Create additional tags** to add tags to the volume\. For each tag, provide a tag key and a tag value\.
1. Choose **Create Volume**\.
1. To use your new volume, attach it to an instance and mount it\. For more information, see [Attaching an Amazon EBS volume to an instance](ebs-attaching-volume.md)\.
1. If you created a volume that is larger than the snapshot, you must extend the file system on the volume to take advantage of the extra space\. For more information, see [Amazon EBS Elastic Volumes](ebs-modify-volume.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
15b9ed5508e3-3 | **To create an EBS volume from a snapshot using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [create\-volume](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-volume.html) \(AWS CLI\)
+ [New\-EC2Volume](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Volume.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-creating-volume.md |
2c68d00a6cd0-0 | You can optionally verify the EFA tarball \(\.tar\.gz file\) using an MD5 or SHA256 checksum\. We recommend that you do this to verify the identity of the software publisher and to check that the application has not been altered or corrupted since it was published\.
**To verify the tarball**
Use the **md5sum** utility for the MD5 checksum, or the **sha256sum** utility for the SHA256 checksum, and specify the tarball filename\. You must run the command from the directory in which you saved the tarball file\.
+ MD5
```
$ md5sum tarball_filename.tar.gz
```
+ SHA256
```
$ sha256sum tarball_filename.tar.gz
```
The commands should return a checksum value in the following format\.
```
checksum_value tarball_filename.tar.gz
```
Compare the checksum value returned by the command with the checksum value provided in the table below\. If the checksums match, then it is safe to run the installation script\. If the checksums do not match, do not run the installation script, and contact AWS Support\.
For example, the following command verifies the EFA 1\.9\.4 tarball using the SHA256 checksum\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-verify.md |
2c68d00a6cd0-1 | For example, the following command verifies the EFA 1\.9\.4 tarball using the SHA256 checksum\.
```
$ sha256sum aws-efa-installer-1.9.4.tar.gz
```
```
1009b5182693490d908ef0ed2c1dd4f813cc310a5d2062ce9619c4c12b5a7f14 aws-efa-installer-1.9.4.tar.gz
```
The following table lists the checksums for recent versions of EFA\.
| Version | Download URL | Checksums |
| --- | --- | --- |
| EFA 1\.9\.5 | https://efa\-installer\.amazonaws\.com/aws\-efa\-installer\-1\.9\.5\.tar\.gz | **MD5: **`95edb8a209c18ba8d250409846eb6ef4` **SHA256: **`a4343308d7ea4dc943ccc21bcebed913e8868e59bfb2ac93599c61a7c87d7d25` | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-verify.md |
2c68d00a6cd0-2 | | EFA 1\.9\.4 | https://efa\-installer\.amazonaws\.com/aws\-efa\-installer\-1\.9\.4\.tar\.gz | **MD5: **`f26dd5c350422c1a985e35947fa5aa28` **SHA256: **`1009b5182693490d908ef0ed2c1dd4f813cc310a5d2062ce9619c4c12b5a7f14` |
| EFA 1\.9\.3 | https://efa\-installer\.amazonaws\.com/aws\-efa\-installer\-1\.9\.3\.tar\.gz | **MD5: **`95755765a097802d3e6d5018d1a5d3d6` **SHA256: **`46ce732d6f3fcc9edf6a6e9f9df0ad136054328e24675567f7029edab90c68f1` | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-verify.md |
2c68d00a6cd0-3 | | EFA 1\.8\.4 | https://efa\-installer\.amazonaws\.com/aws\-efa\-installer\-1\.8\.4\.tar\.gz | **MD5: **`85d594c41e831afc6c9305263140457e` **SHA256: **`0d974655a09b213d7859e658965e56dc4f23a0eee2dc44bb41b6d039cc5bab45` | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-verify.md |
1ecfbc785c9c-0 | This list of practices will help you get the maximum benefit from Amazon EC2\.
**Security**
+ Manage access to AWS resources and APIs using identity federation, IAM users, and IAM roles\. Establish credential management policies and procedures for creating, distributing, rotating, and revoking AWS access credentials\. For more information, see [IAM Best Practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/IAMBestPractices.html) in the *IAM User Guide*\.
+ Implement the least permissive rules for your security group\. For more information, see [Security group rules](ec2-security-groups.md#security-group-rules)\.
+ Regularly patch, update, and secure the operating system and applications on your instance\. For more information about updating Amazon Linux 2 or the Amazon Linux AMI, see [Managing Software on Your Linux Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-software.html) in the *Amazon EC2 User Guide for Linux Instances*\.
**Storage**
+ Understand the implications of the root device type for data persistence, backup, and recovery\. For more information, see [Storage for the root device](ComponentsAMIs.md#storage-for-the-root-device)\.
+ Use separate Amazon EBS volumes for the operating system versus your data\. Ensure that the volume with your data persists after instance termination\. For more information, see [Preserving Amazon EBS volumes on instance termination](terminating-instances.md#preserving-volumes-on-termination)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-best-practices.md |
1ecfbc785c9c-1 | + Use the instance store available for your instance to store temporary data\. Remember that the data stored in instance store is deleted when you stop or terminate your instance\. If you use instance store for database storage, ensure that you have a cluster with a replication factor that ensures fault tolerance\.
+ Encrypt EBS volumes and snapshots\. For more information, see [Amazon EBS encryption](EBSEncryption.md)\.
**Resource management**
+ Use instance metadata and custom resource tags to track and identify your AWS resources\. For more information, see [Instance metadata and user data](ec2-instance-metadata.md) and [Tagging your Amazon EC2 resources](Using_Tags.md)\.
+ View your current limits for Amazon EC2\. Plan to request any limit increases in advance of the time that you'll need them\. For more information, see [Amazon EC2 service quotas](ec2-resource-limits.md)\.
**Backup and recovery**
+ Regularly back up your EBS volumes using [Amazon EBS snapshots](EBSSnapshots.md), and create an [Amazon Machine Image \(AMI\)](AMIs.md) from your instance to save the configuration as a template for launching future instances\.
+ Deploy critical components of your application across multiple Availability Zones, and replicate your data appropriately\.
+ Design your applications to handle dynamic IP addressing when your instance restarts\. For more information, see [Amazon EC2 instance IP addressing](using-instance-addressing.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-best-practices.md |
1ecfbc785c9c-2 | + Monitor and respond to events\. For more information, see [Monitoring Amazon EC2](monitoring_ec2.md)\.
+ Ensure that you are prepared to handle failover\. For a basic solution, you can manually attach a network interface or Elastic IP address to a replacement instance\. For more information, see [Elastic network interfaces](using-eni.md)\. For an automated solution, you can use Amazon EC2 Auto Scaling\. For more information, see the [Amazon EC2 Auto Scaling User Guide](https://docs.aws.amazon.com/autoscaling/latest/userguide/)\.
+ Regularly test the process of recovering your instances and Amazon EBS volumes if they fail\.
**Networking**
+ Set the time\-to\-live \(TTL\) value for your applications to 255, for IPv4 and IPv6\. If you use a smaller value, there is a risk that the TTL will expire while application traffic is in transit, causing reachability issues for your instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-best-practices.md |
c3e62bcbbc20-0 | There is a wealth of open\-source software available on the Internet that has not been pre\-compiled and made available for download from a package repository\. You may eventually discover a software package that you need to compile yourself, from its source code\. For your system to be able to compile software, you need to install several development tools, such as make, gcc, and autoconf\.
**Important**
This information applies to Amazon Linux\. For information about other distributions, see their specific documentation\.
Because software compilation is not a task that every Amazon EC2 instance requires, these tools are not installed by default, but they are available in a package group called "Development Tools" that is easily added to an instance with the yum groupinstall command\.
```
[ec2-user ~]$ sudo yum groupinstall "Development Tools"
```
Software source code packages are often available for download \(from web sites such as [https://github\.com/](https://github.com/) and [http://sourceforge\.net/](https://sourceforge.net/)\) as a compressed archive file, called a tarball\. These tarballs will usually have the `.tar.gz` file extension\. You can decompress these archives with the tar command\.
```
[ec2-user ~]$ tar -xzf software.tar.gz
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/compile-software.md |
c3e62bcbbc20-1 | ```
[ec2-user ~]$ tar -xzf software.tar.gz
```
After you have decompressed and unarchived the source code package, you should look for a `README` or `INSTALL` file in the source code directory that can provide you with further instructions for compiling and installing the source code\.
**To retrieve source code for Amazon Linux packages**
Amazon Web Services provides the source code for maintained packages\. You can download the source code for any installed packages with the yumdownloader \-\-source command\.
+ Run the yumdownloader \-\-source *package* command to download the source code for *package*\. For example, to download the source code for the `htop` package, enter the following command\.
```
[ec2-user ~]$ yumdownloader --source htop
Loaded plugins: priorities, update-motd, upgrade-helper
Enabling amzn-updates-source repository
Enabling amzn-main-source repository
amzn-main-source | 1.9 kB 00:00:00
amzn-updates-source | 1.9 kB 00:00:00
(1/2): amzn-updates-source/latest/primary_db | 52 kB 00:00:00
(2/2): amzn-main-source/latest/primary_db | 734 kB 00:00:00 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/compile-software.md |
c3e62bcbbc20-2 | (2/2): amzn-main-source/latest/primary_db | 734 kB 00:00:00
htop-1.0.1-2.3.amzn1.src.rpm
```
The location of the source RPM is in the directory from which you ran the command\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/compile-software.md |
1bfdd27de618-0 | Amazon Elastic Block Store \(Amazon EBS\) provides block level storage volumes for use with EC2 instances\. EBS volumes behave like raw, unformatted block devices\. You can mount these volumes as devices on your instances\. EBS volumes that are attached to an instance are exposed as storage volumes that persist independently from the life of the instance\. You can create a file system on top of these volumes, or use them in any way you would use a block device \(such as a hard drive\)\. You can dynamically change the configuration of a volume attached to an instance\.
We recommend Amazon EBS for data that must be quickly accessible and requires long\-term persistence\. EBS volumes are particularly well\-suited for use as the primary storage for file systems, databases, or for any applications that require fine granular updates and access to raw, unformatted, block\-level storage\. Amazon EBS is well suited to both database\-style applications that rely on random reads and writes, and to throughput\-intensive applications that perform long, continuous reads and writes\.
With Amazon EBS, you pay only for what you use\. For more information about Amazon EBS pricing, see the Projecting Costs section of the [Amazon Elastic Block Store page](http://aws.amazon.com/ebs/)\.
**Topics**
+ [Features of Amazon EBS](#ebs-features)
+ [Amazon EBS volumes](ebs-volumes.md)
+ [Amazon EBS snapshots](EBSSnapshots.md)
+ [Amazon EBS data services](ebs-data-services.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonEBS.md |
1bfdd27de618-1 | + [Amazon EBS data services](ebs-data-services.md)
+ [Amazon EBS and NVMe on Linux instances](nvme-ebs-volumes.md)
+ [Amazon EBS–optimized instances](ebs-optimized.md)
+ [Amazon EBS volume performance on Linux instances](EBSPerformance.md)
+ [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md)
+ [Amazon CloudWatch Events for Amazon EBS](ebs-cloud-watch-events.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonEBS.md |
a2535ac5a878-0 | + EBS volumes are created in a specific Availability Zone, and can then be attached to any instances in that same Availability Zone\. To make a volume available outside of the Availability Zone, you can create a snapshot and restore that snapshot to a new volume anywhere in that Region\. You can copy snapshots to other Regions and then restore them to new volumes there, making it easier to leverage multiple AWS Regions for geographical expansion, data center migration, and disaster recovery\.
+ Amazon EBS provides the following volume types: General Purpose SSD \(`gp2`\), Provisioned IOPS SSD \(`io1` and `io2`\), Throughput Optimized HDD \(`st1`\), and Cold HDD \(`sc1`\)\. The following is a summary of performance and use cases for each volume type\.
+ General Purpose SSD volumes offer a base performance of 3 IOPS/GiB, with the ability to burst to 3,000 IOPS for extended periods of time\. These volumes are ideal for a broad range of use cases such as boot volumes, small and medium\-size databases, and development and test environments\. For more information, see [General Purpose SSD \(`gp2`\) volumes](ebs-volume-types.md#EBSVolumeTypes_gp2)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonEBS.md |
a2535ac5a878-1 | + Provisioned IOPS SSD volumes support up to 64,000 IOPS and 1,000 MiB/s of throughput\. This allows you to predictably scale to tens of thousands of IOPS per EC2 instance\. For more information, see [Provisioned IOPS SSD \(`io1` and `io2`\) volumes](ebs-volume-types.md#EBSVolumeTypes_piops)\.
+ Throughput Optimized HDD volumes provide low\-cost magnetic storage that defines performance in terms of throughput rather than IOPS\. These volumes are ideal for large, sequential workloads such as Amazon EMR, ETL, data warehouses, and log processing\. For more information, see [Throughput Optimized HDD \(`st1`\) volumes](ebs-volume-types.md#EBSVolumeTypes_st1)\.
+ Cold HDD volumes provide low\-cost magnetic storage that defines performance in terms of throughput rather than IOPS\. These volumes are ideal for large, sequential, cold\-data workloads\. If you require infrequent access to your data and are looking to save costs, these volumes provides inexpensive block storage\. For more information, see [Cold HDD \(`sc1`\) volumes](ebs-volume-types.md#EBSVolumeTypes_sc1)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonEBS.md |
a2535ac5a878-2 | + You can create your EBS volumes as encrypted volumes, in order to meet a wide range of data\-at\-rest encryption requirements for regulated/audited data and applications\. When you create an encrypted EBS volume and attach it to a supported instance type, data stored at rest on the volume, disk I/O, and snapshots created from the volume are all encrypted\. The encryption occurs on the servers that host EC2 instances, providing encryption of data\-in\-transit from EC2 instances to EBS storage\. For more information, see [Amazon EBS encryption](EBSEncryption.md)\.
+ You can create point\-in\-time snapshots of EBS volumes, which are persisted to Amazon S3\. Snapshots protect data for long\-term durability, and they can be used as the starting point for new EBS volumes\. The same snapshot can be used to instantiate as many volumes as you wish\. These snapshots can be copied across AWS Regions\. For more information, see [Amazon EBS snapshots](EBSSnapshots.md)\.
+ Performance metrics, such as bandwidth, throughput, latency, and average queue length, are available through the AWS Management Console\. These metrics, provided by Amazon CloudWatch, allow you to monitor the performance of your volumes to make sure that you are providing enough performance for your applications without paying for resources you don't need\. For more information, see [Amazon EBS volume performance on Linux instances](EBSPerformance.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonEBS.md |
70a2a52f354e-0 | Security groups enable you to control traffic to your instance, including the kind of traffic that can reach your instance\. For example, you can allow computers from only your home network to access your instance using SSH\. If your instance is a web server, you can allow all IP addresses to access your instance using HTTP or HTTPS, so that external users can browse the content on your web server\.
Your default security groups and newly created security groups include default rules that do not enable you to access your instance from the internet\. For more information, see [Default security groups](ec2-security-groups.md#default-security-group) and [Custom security groups](ec2-security-groups.md#creating-your-own-security-groups)\. To enable network access to your instance, you must allow inbound traffic to your instance\. To open a port for inbound traffic, add a rule to a security group that you associated with your instance when you launched it\.
To connect to your instance, you must set up a rule to authorize SSH traffic from your computer's public IPv4 address\. To allow SSH traffic from additional IP address ranges, add another rule for each range you need to authorize\.
If you've enabled your VPC for IPv6 and launched your instance with an IPv6 address, you can connect to your instance using its IPv6 address instead of a public IPv4 address\. Your local computer must have an IPv6 address and must be configured to use IPv6\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/authorizing-access-to-an-instance.md |
70a2a52f354e-1 | If you need to enable network access to a Windows instance, see [Authorizing inbound traffic for your Windows instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/authorizing-access-to-an-instance.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/authorizing-access-to-an-instance.md |
dbf7f3e11d93-0 | Decide who requires access to your instance; for example, a single host or a specific network that you trust such as your local computer's public IPv4 address\. The security group editor in the Amazon EC2 console can automatically detect the public IPv4 address of your local computer for you\. Alternatively, you can use the search phrase "what is my IP address" in an internet browser, or use the following service: [Check IP](http://checkip.amazonaws.com/)\. If you are connecting through an ISP or from behind your firewall without a static IP address, you need to find out the range of IP addresses used by client computers\.
**Warning**
If you use `0.0.0.0/0`, you enable all IPv4 addresses to access your instance using SSH\. If you use `::/0`, you enable all IPv6 address to access your instance\. This is acceptable for a short time in a test environment, but it's unsafe for production environments\. In production, you authorize only a specific IP address or range of addresses to access your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/authorizing-access-to-an-instance.md |
dbf7f3e11d93-1 | Decide whether you'll support SSH access to your instances using EC2 Instance Connect\. If you will not use EC2 Instance Connect, consider uninstalling it or denying the following action in your IAM policies: `ec2-instance-connect:SendSSHPublicKey`\. For more information, see [Uninstall EC2 Instance Connect](ec2-instance-connect-uninstall.md) and [Configure IAM Permissions for EC2 Instance Connect](ec2-instance-connect-set-up.md#ec2-instance-connect-configure-IAM-role)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/authorizing-access-to-an-instance.md |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.