AWS Management Console Private Access Now Supports VPCs Without Internet Connectivity

Enhanced Private Access for AWS Console

AWS has announced the general availability of AWS Management Console Private Access, which now fully supports virtual private clouds (VPCs) without internet connectivity. This update allows organizations, particularly those in regulated industries like financial services and government, to access the AWS Management Console from isolated network environments.

Previously, while AWS Management Console Private Access allowed routing console and service API calls through VPC endpoints, static assets and console-only APIs still required internet connectivity. This created a security challenge for organizations with strict network isolation requirements.

Eliminating Internet Dependencies

With this new capability, all traffic for supported service consoles, including authentication flows, static assets (JavaScript, CSS, images), console-only APIs, and AWS service API calls, can be routed entirely through AWS PrivateLink VPC endpoints. This eliminates the need for an internet gateway, NAT gateway, or any route to the public internet.

This change resolves the tension between operational convenience and network security controls, allowing operators in network-isolated environments to use the console without compromising security policies.

Operational Benefits and Availability

The updated Private Access simplifies network configurations by removing the need for proxy allowlists or TLS-intercepting proxies. It also ensures consistent access from Amazon WorkSpaces, Amazon EC2 instances, and on-premises networks connected via AWS Direct Connect or AWS Site-to-Site VPN.

This feature is available in all AWS commercial Regions for a select set of supported service consoles, providing a more secure and compliant way to manage AWS resources for organizations with stringent security requirements.