AWS AWSEC2 documentation change
Summary
Updated managed resource visibility documentation: added WorkSpaces Core to supported services, clarified default visibility behavior, and modified console instructions.
Security assessment
The changes refine visibility settings for AWS-managed resources but don't address vulnerabilities or security weaknesses. Modifications are operational improvements without security implications.
Diff
diff --git a/AWSEC2/latest/UserGuide/amazon-ec2-managed-instances.md b/AWSEC2/latest/UserGuide/amazon-ec2-managed-instances.md index fbe3b4b8f..d768d8fbd 100644 --- a//AWSEC2/latest/UserGuide/amazon-ec2-managed-instances.md +++ b//AWSEC2/latest/UserGuide/amazon-ec2-managed-instances.md @@ -127 +127 @@ You can control whether resources that AWS services provision on your behalf app -AWS services such as Amazon EKS, Amazon ECS, Workspaces, and AWS Lambda provision and operate Amazon EC2 instances directly within your account. These services assume responsibility for scaling, OS patches, security updates, and lifecycle management. The resulting Amazon EC2 instances, Amazon EC2 launch templates, Amazon EBS volumes, and network interfaces (ENIs) appear alongside your customer-managed resources in the Amazon EC2 console and APIs. Managed resource visibility settings give you control over whether these managed resources surface in your resource views. +AWS services such as Amazon EKS, Amazon ECS, WorkSpaces Core, and AWS Lambda provision and operate Amazon EC2 instances directly within your account. These services assume responsibility for scaling, OS patches, security updates, and lifecycle management. The resulting Amazon EC2 instances, Amazon EC2 launch templates, Amazon EBS volumes, and network interfaces (ENIs) appear alongside your customer-managed resources in the Amazon EC2 console and APIs. Managed resource visibility settings give you control over whether these managed resources surface in your resource views. @@ -134,3 +134,3 @@ Amazon EC2 instances | Amazon EKS worker nodes, Amazon ECS container instances, -Amazon EC2 launch templates | Amazon EKS, Amazon ECS | Launch templates created by managed services -Amazon EBS volumes | Amazon EKS, Amazon ECS | Volumes attached to managed instances -Network interfaces (ENIs) | Amazon EKS, Amazon ECS, Lambda | Network interfaces provisioned for managed workloads +Amazon EC2 launch templates | Amazon EKS, Amazon ECS, Amazon WorkSpaces Core | Launch templates created by managed services +Amazon EBS volumes | Amazon EKS, Amazon ECS, Amazon WorkSpaces Core | Volumes attached to managed instances +Network interfaces (ENIs) | Amazon EKS, Amazon ECS, AWS Lambda, Amazon WorkSpaces Core | Network interfaces provisioned for managed workloads @@ -140 +140 @@ Network interfaces (ENIs) | Amazon EKS, Amazon ECS, Lambda | Network interfaces -By default, new managed resources are hidden. Existing managed resources already created in your account by managed instance offerings (such as Amazon EKS Auto Mode, Amazon ECS managed instances, or Lambda managed instances) remain visible. You can change visibility settings at any time. +By default, Amazon EC2 hides managed resources for accounts that did not have managed resources before visibility settings became available. For accounts that already had managed resources, Amazon EC2 sets the visibility setting to **Visible** to preserve existing workflows. The visibility setting applies to all managed resources in a Region, regardless of when they were created. You can change visibility settings at any time. @@ -163 +163 @@ Visibility settings control resource display in AWS console views and API list o -You can configure managed resource visibility by using the Amazon EC2 console or the AWS CLI. +You can configure the visibility of managed resources by using the Amazon EC2 console or the AWS CLI. @@ -172 +172 @@ Console - 3. On the **Account attributes** card, under **Settings** , choose **Managed resource visibility**. + 3. On the **Account attributes** card, under **Settings** , choose **Managed resources**. @@ -174 +174 @@ Console - 4. Choose **Manage**. + 4. Choose **Modify**. @@ -176 +176 @@ Console - 5. Toggle visibility on or off for managed instances. + 5. Under **Default visibility** , choose one of the following options: @@ -178 +178,5 @@ Console - 6. Choose **Save changes**. + * **Hidden (default)** – Hides all managed resources. + + * **Visible** – Shows all managed resources. + + 6. Choose **Modify visibility**.