AWS Transit Gateway

[fwmike]

Hello,

Is there planned AWS Transit Gateway integration? There is mention but no detail in this video:

https://www.youtube.com/watch?v=6fhwoAwYrug

Other than operational ease, the Transit Gateway advantages appear limited. Traffic between VPCs is not encrypted. VPC segmentation is via routing and does not traverse a firewall.

[Cdchamberlin]

Hi @jperry1 ,

My concern with this design is the VPC attachment from TGW SN to the TGW. Rather than using ECMP VPN links 'that I have been unable to find documentation on', the data sent across that connection will be in the clear; right? 

What are your thoughts on that? 

[buzor.okoye]

Fantastic documentation here in the manual build https://github.com/PaloAltoNetworks/TransitGatewayDeployment, I think you left out one thing. A need to add default route on FW2 pointing to eth1, otherwise the outbound traffic will be dropped by the firewall.

[DewhirstR]

I am on my third or fourth attempt to walk through the Manual build guide and every time I reach Page 22, step 8, the TGW Attachment "attach-spoke1" is not available as a target.  Only the tgw-security gateway.

[jmeurer]

Please switch the deployment guide and reference architecture here. 

https://www.paloaltonetworks.com/resources/reference-architectures/aws

[Cdchamberlin]

Hi @DewhirstR ,

Hope all is well and you get this worked out.

Take a look at page 13-15 and verify the VPC attachments for both spokes to the TGW. Verify Associations in the TGW Route Table for the VPCs.