- Newest
- Most votes
- Most comments
This scenario is achievable with AWS Cloud WAN's service insertion feature using Network Function Groups (NFGs). You can set up your inspection in eu-west-1 and configure the service insertion policy to route all cross-segment traffic through this region for inspection before reaching its destination, regardless of the source or destination region.
To implement this, you would create an NFG in eu-west-1 that includes your inspection VPC or security appliances. Then, in your Cloud WAN policy, you would use the "send-via" segment action with the "single-hop" mode. This configuration allows you to specify eu-west-1 as the preferred region for inspection.
Your policy might look something like this:
"segment-actions": [ { "action": "send-via", "segment": "*", "mode": "single-hop", "when-sent-to": { "segments": "*" }, "via": { "network-function-groups": ["InspectionNFG"] } } ]
In this configuration, you would also set an ordered list of regions with eu-west-1 as the preferred region for inspection.
Regarding potential issues:
-
Session timeouts: While this setup doesn't inherently cause session timeouts, you should be aware that routing traffic to eu-west-1 for inspection before reaching its destination in other regions (like us-east-1 or ap-south-1) will introduce some latency. This additional latency could potentially lead to timeouts if your applications have very strict timeout settings.
-
Asynchronous routing: AWS Cloud WAN is designed to handle complex routing scenarios, so asynchronous routing shouldn't be a significant concern. The service manages route propagation automatically based on your policy.
However, it's important to note that this centralized inspection model might introduce increased latency for traffic between us-east-1 and ap-south-1, as it would need to travel to eu-west-1 for inspection before reaching its destination. This could impact application performance, especially for latency-sensitive applications.
To optimize this setup, you might consider:
- Ensuring your inspection appliances in eu-west-1 are properly sized to handle the global traffic load.
- Monitoring network performance and adjusting your configuration if needed.
- For latency-sensitive applications, you might explore using Cloud WAN's capability to set up multiple NFGs in different regions and use policy-based routing to balance between centralized and distributed inspection models.
While this setup is achievable and can simplify your global security inspection, it's crucial to carefully consider the trade-offs between centralized security control and potential performance impacts, especially for geographically distant regions.
Sources
Simplify global security inspection with AWS Cloud WAN Service Insertion | Networking & Content Delivery
AWS Cloud WAN service insertion - AWS Network Manager
AWS Cloud WAN introduces Service Insertion to simplify security inspection at global scale - AWS
answered a year ago
The Network Function Group (NFG) feature will allow you to steer network traffic as you describe.
The NFG allows you to specify which segments or pairs of segments should have their traffic redirected through the network functions defined within the NFG.
NFG consumes one global segment, so you can associate a network attachment from any AWS region that's part of your core network to the NFG. So, if your core network spans three regions (us-east-1, eu-west-1, and ap-west-1), you can include the inspection or firewall VPC from any of those regions in the NFG.
However, it's important to consider the impact on network latency based on this path you are forcing. Ideally, it's recommended to have an inspection VPC located in each region where traffic originates. That way, if traffic needs to travel from us-east-1 to ap-south-1, it can be inspected locally in the us-east-1 region before being routed to its final destination. Returning traffic can follow the same path.
But in your scenario, traffic from us-east-1 to ap-south-1 would need to be redirected to eu-west-1 just for inspection, same for returning traffic, which depending on your latency requirements, might not be ideal.
Yes,you are right! It will give an additional latency to other region due to inspection.
Adding inspection PA firewalls in other 2 regions is not cost-effective since AP-South-1 and US-East-1 have significantly less traffic compared to EU-West-1. Additionally, EU-West-1 has VPCs from different organizations, requiring us to place a PA firewall for inspection. but Cross-segment traffic without inspection is also a concern, even though all VPCs within AP-South-1 and US-East-1 belong to my organization.I have PA firewall and Cisco Viptela for WAN overlay in each region. Can I use the same PA SDWAN firewall in each region for WAN overlay traffic and Inspection by implementing two different Virtual router in PA firewall?
Relevant content
asked a year ago
asked 2 years ago
asked 2 years ago

Yes, I understand that this setup introduces latency.
Currently, my existing setup is TGW-based, with EU-West-1 egress connected to PA SD-WAN and Viptela in AWS, serving as a WAN solution to connect Venlo Data Center and other locations across the globe.
For US-East-1 and AP-South-1, we have IPsec tunnels connected to Windsor DC and MUM ( India) DC, respectively. Setting up Direct Connect for each region to its respective plant location or deploying Viptela and PA SD-WAN in every region would significantly increase costs.
As we plan to migrate to AWS Cloud WAN, our goal is to achieve this transition without substantial additional investment.