- CheckMates
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- AWS Transit VPC - Multi AWS Accounts
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
AWS Transit VPC - Multi AWS Accounts
Hi,
We successfully deployed a Transit VPC in AWS using the Deployment guide, with auto-vpn provisioning for spoke VPC.
The question revolves around supporting more than TWO AWS accounts. The guide does not seem to cover this or we could not find a good reference.
Environment:
OnPrem R80.10 MDS
AWS Main account holds Transit VPC gateways (used key and secret for auth)
AWS sub-account1 has spoke VPC (auth via STS auth and role)
We have four or five more sub-accounts we would like to add to the configuration leveraging the same Transit VPC. While we see we can possibly add more "controllers" using autoprov-cfg, it is not clear if this is the right approach and even if this would build VPN tunnels back to the main transit VPC hub.
Can someone help us determine the right next steps?
-
ACI
1 -
API
1 -
architecture
4 -
Automation
3 -
Automation and APIs
1 -
Aviatrix
1 -
AWS
6 -
Azure
5 -
Azure DevOps
1 -
bash
1 -
CDT
1 -
cisco
1 -
Cisco ACI
1 -
Cloud
3 -
Cloud - Automation - Orchestration
1 -
Cloud network security
2 -
Cloud Security
1 -
cloudappsecurity
1 -
CloudGuard
4 -
CloudGuard IaaS
4 -
cloudwatch
1 -
Cluster
1 -
ClusterXL
1 -
deployment
2 -
DevSecOps
1 -
DHCP
1 -
DirectConnect
1 -
firewall
1 -
Gaia
1 -
IaC
1 -
identity
1 -
loadbalancer
1 -
MDS 80.40
1 -
multi cloud
1 -
NAT
1 -
NDR
1 -
networking
1 -
next generation firewall
1 -
NSX-T
2 -
private
1 -
public
1 -
R81
1 -
R81.10
1 -
reference
1 -
script
1 -
Site to Site VPN
1 -
Smart Console
1 -
Structura.io
1 -
technical
1 -
Terraform
3 -
TGW
1 -
VMSS
1 -
vsec_lic_cli
1
- « Previous
- Next »