AWS Management Console access was denied because policy conditions no longer match
My browser displays an 'access denied' error when connecting to the AWS Management Console.
AWS Management Console access can fail when IAM policies use `aws:SourceIp` or `aws:SourceVpc` conditions that no longer match how console traffic reaches AWS.
Access denied when connecting to the AWS Management Consoleauthentication
Observed message
My browser displays an 'access denied' error when connecting to the AWS Management Console.
Why it happens
IAM policy conditions using `aws:SourceIp` or `aws:SourceVpc` do not match the current console access path.
The environment uses console private access or VPC endpoints without matching policy conditions.
The policy only allows IPv4 or IPv6 while the browser prefers the other protocol.
How to fix it
Review IAM policies that use `aws:SourceIp` or `aws:SourceVpc` for console access.
Include both IPv4 and IPv6 CIDR ranges if the environment can use either.
Align console private access or VPC endpoint design with the conditions enforced by policy.
