Skip to content
Cloud Governance Tools

Block internet gateway ingress for VPCs (declarative policy)

Block internet gateway ingress for VPCs (declarative policy) is an AWS guardrail written in declarative policies. Sets VPC Block Public Access to block_ingress for the accounts in scope, so resources in VPCs and subnets cannot receive traffic through internet gateways.

More network perimeter guardrails ยท About Declarative policies

{
  "ec2_attributes": {
    "vpc_block_public_access": {
      "internet_gateway_block": {
        "mode": {
          "@@assign": "block_ingress"
        },
        "exclusions_allowed": {
          "@@assign": "enabled"
        }
      }
    }
  }
}
Blocks
Sets VPC Block Public Access to block_ingress for the accounts in scope, so resources in VPCs and subnets cannot receive traffic through internet gateways.
Breaks
While the policy is attached, account administrators cannot change the enforced configuration; AWS lists ModifyVpcBlockPublicAccessOptions, CreateVpcBlockPublicAccessExclusion and ModifyVpcBlockPublicAccessExclusion as blocked. (source)
Test before applying
As for every Declarative policies guardrail: how to test before enforcing
Mechanism
Declarative policies: The configuration of a supported AWS service attribute in the accounts, OUs or organization they are attached to, including actions by service-linked roles.
Taken from
provider documentation, provider documentation

What the source says

"vpc_block_public_access: {" (read 10 Nov 2026).

On what it breaks: "Account administrators will not be able to modify the value of the service attribute at the individual account level."

Sources

  1. Block internet gateway ingress for VPCs (declarative policy), read 10 Nov 2026
  2. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.