Amazon EC2 announces Managed resource visibility settings
Amazon Web Services has introduced a new managed resource visibility feature for Amazon EC2 that allows users to control whether AWS-managed instances appear in their console views and API responses. The feature addresses a long-standing issue where EC2 instances provisioned by AWS services like Amazon EKS, ECS, Lambda, and WorkSpaces would appear alongside user-managed instances in the EC2 console and describe-instances API calls, despite being fully managed by AWS. By default, newly created managed resources will now be hidden from console views and API responses, better aligning with AWS's shared responsibility model where the company handles configuration, patching, and health monitoring of these instances. The change also applies to associated resources including EBS volumes, snapshots, and network interfaces that are part of managed deployments. Users can configure the visibility settings through either the Amazon EC2 console or AWS CLI, giving them flexibility to show or hide managed resources based on their operational preferences. The feature is designed to reduce console clutter and help administrators focus on resources they directly manage while maintaining the option to view the complete infrastructure when needed.
Why It Matters
This update addresses a practical pain point for AWS administrators who have struggled with console clutter from managed resources they don't directly control. It improves operational clarity by separating user-managed and AWS-managed infrastructure, potentially reducing confusion during troubleshooting and resource management. The feature also demonstrates AWS's continued refinement of the shared responsibility model, making the boundaries between customer and AWS responsibilities more visible in the user interface.
This summary is generated using AI analysis of the original press release. Always refer to the original source for complete details.