AWS AWSEC2 documentation change
Summary
Simplified title, removed SQL Server conversion details, restructured requirements section, and updated CLI example formatting. Removed console workflow steps while keeping constraints.
Security assessment
Changes focus on content reorganization and clarity improvements. No security vulnerabilities addressed or security features documented.
Diff
diff --git a/AWSEC2/latest/UserGuide/dedicated-change-tenancy.md b/AWSEC2/latest/UserGuide/dedicated-change-tenancy.md index 7bb0e89ec..196a16563 100644 --- a/AWSEC2/latest/UserGuide/dedicated-change-tenancy.md +++ b/AWSEC2/latest/UserGuide/dedicated-change-tenancy.md @@ -5 +5 @@ -# Change the tenancy of an Amazon EC2 instance +# Change the tenancy of an EC2 instance @@ -9,2 +8,0 @@ You can change the tenancy of a stopped instance after launch. The changes that -The operating system details of your instance—and whether SQL Server is installed—affect what conversions are supported. For more information about the tenancy conversion paths available to your instance, see [Tenancy conversion](https://docs.aws.amazon.com/license-manager/latest/userguide/conversion-tenancy.html) in the _License Manager User Guide_. - @@ -15,6 +13 @@ Alternatively, you can change the tenancy of your virtual private cloud (VPC). F - * For T3 instances, you must launch the instance on a Dedicated Host to use a tenancy of `host`. You can't change the tenancy from `host` to `dedicated` or `default`. Attempting to make one of these unsupported tenancy changes results in an `InvalidRequest` error code. - - - - -Console + * You can't change the tenancy of an instance using the AWS Management Console. @@ -21,0 +15 @@ Console + * The instance must be in the `stopped` state. @@ -23 +17 @@ Console -###### To change the tenancy of an instance using the console + * The operating system details of your instance—and whether SQL Server is installed—affect what conversions are supported. For more information about the tenancy conversion paths available to your instance, see [Tenancy conversion](https://docs.aws.amazon.com/license-manager/latest/userguide/conversion-tenancy.html) in the _License Manager User Guide_. @@ -25,9 +19 @@ Console - 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). - - 2. In the navigation pane, choose **Instances** and select your instance. - - 3. Choose **Instance state** , **Stop instance** , **Stop**. - - 4. Choose **Actions** , **Instance settings** , **Modify instance placement**. - - 5. For **Tenancy** , choose whether to run your instance on dedicated hardware or on a Dedicated Host. Choose **Save**. + * For T3 instances, you must launch the instance on a Dedicated Host to use a tenancy of `host`. You can't change the tenancy from `host` to `dedicated` or `default`. Attempting to make one of these unsupported tenancy changes results in an `InvalidRequest` error code. @@ -46 +32,3 @@ Use the [ modify-instance-placement](https://awscli.amazonaws.com/v2/documentati - aws ec2 modify-instance-placement --instance-id i-1234567890abcdef0 --tenancy dedicated + aws ec2 modify-instance-placement \ + --instance-id i-1234567890abcdef0 \ + --tenancy dedicated @@ -51 +39 @@ PowerShell -###### To modify the tenancy value of an instance using the AWS CLI +###### To modify the tenancy value of an instance using the Tools for PowerShell @@ -64 +52 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Launch Dedicated Instances into VPC +Launch Dedicated Instances