# AWS adds private network controls to IAM Identity Center

> IAM Identity Center now supports PrivateLink VPC endpoints and network access controls in commercial AWS Regions and GovCloud, at no extra cost.

Oossa · 2026-11-16 · https://oossa.com/en/aws-adds-private-network-controls-to-iam-identity-center

AWS now lets customers route IAM Identity Center sign-in and API traffic through interface VPC endpoints using AWS PrivateLink, rather than public endpoints. Endpoint policies can limit which organizations, accounts and resources are reachable. A separate, optional network access control setting can require endpoint traffic, allow trusted IP ranges or VPCs, and restrict SCIM provisioning to specified IP ranges. Controls are disabled by default, and specific applications can be excluded from enforcement.

## The facts

- Available in all commercial AWS Regions and AWS GovCloud (US) Regions at no additional cost.
- Network access controls are configured through the IAM Identity Center API and are disabled by default.

## Why it matters

AWS customers that need to limit identity-service access to approved networks can now do so without additional service charges; the announcement does not specify how existing deployments should migrate.

## Sources & references

1. [IAM Identity Center now supports VPC endpoints and network access controls](https://aws.amazon.com/about-aws/whats-new/2026/11/iam-identity-center-vpc-endpoints/) – AWS, 2026-11-16

Last updated: 2026-11-16
