Transit Gateway policy table


Dear Team - As per,

To achieve dynamic routing over the Cloud WAN – Transit Gateway peering, you must associate a Transit Gateway policy table to the Transit Gateway’s peering attachment. The table contains policy rules for matching network traffic by policy attributes, and then it maps the traffic that matches the rule to a target route table. When you associate the policy table with the attachment, it populates the table automatically with the policy rules.

i dont see any option to see or configure the matching policy rule in policy table. is this policy table is really configurable ? i can see routes are rightly populated in TGW/CWAN segment but still wondering what this Transit Gateway policy table is doing which we can see ? wondering why i dont need two of the policy table for two diff route table from TGW ?

asked 2 months ago141 views
1 Answer
Accepted Answer


The policy table is not configurable, the rules are already created to make sure traffic segmentation happens through a AWS Transit Gateway - AWS Cloud WAN peering. That's why you only need 1 policy table per peering, and then you can create several Transit Gateway Route Table attachments to map Transit Gateway route tables with Cloud WAN segments.

Hope this clarifies your questions. Tell me if something is not clear. Regards,


answered 2 months ago
profile picture
reviewed a month ago
profile pictureAWS
reviewed 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions