AWS Builder Center
The VPC Settings Panel You Probably Never Clicked

The VPC Settings Panel You Probably Never Clicked

Four links sit in the VPC dashboard Settings panel. Two of them change security posture for every VPC in the region. A walkthrough of account-level encryption control, Block Public Access, Zones, and Console Experiments in ap-south-2.

Cloud @ Sudo | 14x AWS Certified | 2x Claude Certified | 2x Oracle | 2x CNCF(KCNA , KCSA)
Open the VPC dashboard. Look at the right side, under Settings.
There are four links sitting there:
  • Account-level encryption control
  • Block Public Access
  • Zones
  • Console Experiments

Most of us go straight to Your VPCs, Subnets, Route Tables and never touch this panel. But two of these change security posture for every VPC in the region, not just one. Worth ten minutes.
I clicked through all four in  ap-south-2  (Hyderabad). Here is what each one actually does.



1. Account-level encryption control

This governs the encryption control mode for all VPCs in the region owned by your account.
By default it is Unmanaged. That means encryption is handled per VPC, individually. Nothing is centrally enforced.
VPC encryption control enforces that traffic in and out of your VPC is encrypted in transit, not at rest. Monitor mode flags resources and connections that would carry unencrypted traffic (peering links, TGW attachments, VPN, endpoints); enforce mode blocks creation of them outright.
Hit Switch mode and you get three options:
Mode
What it does
Unmanaged
Current behaviour. Each VPC managed on its own.
Attempt monitor mode
Moves all VPCs to monitor. Flags unencrypted resources but does not block anything.
Attempt enforce mode
Moves all VPCs to enforce. Blocks creation of unencrypted resources.
Three things the console tells you before you confirm, and all three matter:
  1. The mode applies to all VPCs in the region and may override individual VPC settings.
  1. While account-level control is active, you cannot change modes at the individual VPC level.
  1. There is an "Additional charges apply" link right at the top. Read it before you flip anything.

That second point is the one that bites. If a team has a VPC deliberately set differently, account-level control takes the wheel and they lose the ability to change it locally.

Practical order: monitor first, look at what gets flagged, fix it, then enforce. Going straight to enforce in an account with running workloads is how you find out which pipeline creates unencrypted resources, at the worst possible time.



2. Block Public Access

Same idea, different control. This one is about internet traffic.
Default status is Off. The console spells it out: internet traffic to and from all VPCs in the region is not restricted.

Turn it on and you block internet traffic to and/or from every VPC in the region, with an Exclusions table for the resources you want to keep reachable.
Two useful details:
  • Internet gateway block direction lets you choose whether you block both directions or only ingress. Ingress-only is the softer setting: outbound stays alive, so patching and API calls keep working.
  • Exclusions allowed was set to Allowed in my account. If it were not, nobody could carve out an exception, which is exactly what you want in a locked-down environment.
  • Managed by: Account. In an Organization this can be managed centrally instead, and then the member account cannot override it.
My exclusions table was empty because the feature was off. The right sequence is the opposite: create your exclusions for the load balancers and public subnets you genuinely need, then switch it on.
This is a real safety net. One misconfigured route table plus one wide-open security group is the whole story behind a lot of exposure incidents. This blocks it at the region boundary.



3. Zones

This one is read-only from here. It shows the Availability Zones in the region, with the ID, the name, and the opt-in status.
In  ap-south-2  I have three:
Zone ID
Zone Name
State
Opt-in
aps2-az1
ap-south-2a
Available
Enabled by default
aps2-az2
ap-south-2b
Available
Enabled by default
aps2-az3
ap-south-2c
Available
Enabled by default
The important column is Zone ID, not Zone Name.  ap-south-2a  in my account and  ap-south-2a  in your account are almost certainly different physical zones. AWS shuffles the name-to-hardware mapping per account so everyone does not pile into "a". The Zone ID ( aps2-az1 ) is consistent across accounts.

If you are doing cross-account VPC sharing or trying to keep two accounts' resources in the same physical zone to avoid cross-AZ data charges, you match on Zone ID. This is also why the page now points you to the AWS Global View console to actually view and update Zones.
Local Zones and Wavelength Zones show up here too, and those need explicit opt-in.



4. Console Experiments

Purely cosmetic, and I like it.
Right now the available experiment is Compact row tables, which reduces row height in resource tables so more resources fit on screen. It applies only to the current Region, and experiments are only available in limited regions.
I opted in. If you spend your day scrolling through subnet and route table lists, it is a genuine quality-of-life change.
Fair warning from AWS itself: these are still in development and might change or be removed.

Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article