You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 13, 2021. It is now read-only.
Currently, the CloudFormation template for the Transit VPC account includes an AccountId parameter, which allows you to specify one additional account which should have access to the VPN Config S3 bucket.
In our case, we have many accounts we want to grant access to, so the option to provide a comma separated list of account IDs to this field would be useful.
The text was updated successfully, but these errors were encountered:
As noted, currently the solution only supports for one additional account for connecting to the transit network, additional accounts can be manually configured by following the steps outlined below:
Currently, the CloudFormation template for the Transit VPC account includes an
AccountId
parameter, which allows you to specify one additional account which should have access to the VPN Config S3 bucket.In our case, we have many accounts we want to grant access to, so the option to provide a comma separated list of account IDs to this field would be useful.
The text was updated successfully, but these errors were encountered: