VPN gateway must be attached and operational
Medium
AWS
General
aws-ec2-vpngateway-vpn-gateway-attached-operationa
Applies to
AWS::EC2::VPNGateway
What CGPulse checks
A resource passes this rule when state must be set true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Ensure the VPN gateway is attached to a VPC and operational for secure connectivity. In AWS Console: VPC > VPN Gateways > verify attachment state. See: https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html
Terraform
resource "aws_vpn_gateway" "{name}" {
vpc_id = aws_vpc.{name}.id
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled