PuppyIP Resource Center
Network & Connection Troubleshooting 5 min Published 2026-11-19

AWS Transit Gateway GWLB attachment pending acceptance? Check access, AZs, and routes

When an AWS Transit Gateway Gateway Load Balancer attachment shows pendingAcceptance, check whether the endpoint service requires approval. If it does, the Gateway Load Balancer endpoint service owner accepts the connections. After the attachment becomes available, verify the Transit Gateway route and actual firewall traffic separately.

AWS Transit Gateway Gateway Load Balancer GWLB pendingAcceptance Network troubleshooting

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The Transit Gateway owner creates the attachment. For cross-account setup, the endpoint service owner grants that account permission first.
  • When acceptance is required, the service owner identifies and accepts the pending endpoint connections by attachment ID.
  • Each Availability Zone must be supported by both Transit Gateway and the endpoint service. AWS excludes use1-az3.
  • After the attachment becomes available, check the static route in the applicable route table and verify traffic inspection and the return path.

Check the accounts, Region, and endpoint service first

AWS announced native Gateway Load Balancer (GWLB) integration on November 17. The Transit Gateway owner creates a Network function attachment using the GWLB VPC endpoint service that fronts the firewall appliances. Verify healthy appliance targets and the endpoint service’s association with the load balancer. Transit Gateway creates endpoints in the selected Availability Zones.

For a cross-account attachment, the endpoint service owner grants the Transit Gateway owner’s account the transit-gateway-attachment permission type. The principal creating the attachment also needs ec2:DescribeVpcEndpointServices. The launch covers commercial Regions where both services operate, excluding Bahrain and the United Arab Emirates. AWS also lists both US GovCloud Regions.

Check Availability Zones and encryption state if creation fails

Confirm the Region and the specific Availability Zone IDs. Select zones supported by both sides. AWS’s documentation explicitly excludes use1-az3. Compare AZ IDs when working across accounts. If the service is inaccessible during creation, check its name, Region, and account permissions.

AWS currently requires Transit Gateway Encryption Support to be disabled at creation. A state of enabled, enabling, or disabling results in rejection. If your gateway must retain that encryption capability, evaluate deployment options against your organization’s network design and requirements before adopting this attachment.

Have the endpoint service owner handle pending connections

If the create request succeeded and the state is pendingAcceptance, see whether the GWLB endpoint service requires acceptance. When it does, the service owner opens the service in the VPC console under Endpoint services, selects Endpoint connections, and identifies and accepts all pending connections for the Transit Gateway attachment ID. Automatic acceptance requires no manual action.

During handoff, record the Region, GWLB endpoint service ID, and Transit Gateway attachment ID. Verify that the requests belong to the intended gateway and authorized account before accepting. Return to the gateway account and check that the attachment becomes available.

Verify the static route and inspected traffic after acceptance

Network function attachments use static routes. Identify the Transit Gateway route table associated with the ingress attachment, then verify that the destination CIDR points to the intended firewall attachment. Compare the existing route with the planned change and check the test prefix for unintended effects on other sources.

Send an authorized test connection that the firewall should inspect. Check the corresponding traffic and verdict at the firewall, then verify destination reachability, the return path, and the application response. If the attachment is available and no packets reach the firewall, start with the route-table association and the matching static route.

Sources

Frequently Asked Questions

Who accepts a pending GWLB attachment?

When manual acceptance is required, the GWLB endpoint service owner accepts the connections for the matching attachment ID under the service’s Endpoint connections tab.

Why can I see the service but still fail to create the attachment?

Check whether the error points to the Availability Zone or Transit Gateway encryption state, and confirm that the creating principal can call ec2:DescribeVpcEndpointServices. For cross-account setup, also check the permission type.

Does available mean traffic is already inspected?

Available means the attachment is ready. Traffic inspection still depends on the Transit Gateway static route, route-table association, and verification in both directions.