Air-gapped systems were supposed to be untouchable. In reality, too many “air-gapped” setups in AWS are just separated by convention, not truly isolated. If the network link exists, even buried in a forgotten VPC or a misconfigured interconnect, a skilled attacker can find it. The promise of AWS access to air-gapped workloads only works when the isolation is engineered into the architecture, not just drawn on a diagram.
True air-gapping in AWS means zero inbound routes from the internet, zero outbound routes to any public endpoint, and no hidden bridge to your corporate network. Every packet path must be accounted for. That means private VPCs with no IGW, no transit gateway peering to mixed-use networks, and strict routing tables. Access must be deliberate and ephemeral, gated through secure, audited channels.
The main challenge is operational. If a workload is cut off from the world, how do you reach it for admin tasks, data sync, or critical updates? The simplest answer is often the most dangerous—persistent bastion hosts or VPN tunnels that stay up for convenience. These become the weak seam in the seal. A safer approach uses short-lived, just-in-time access with automatic teardown, backed by multi-factor auth and comprehensive logging.