Skip to content
This repository has been archived by the owner on May 13, 2021. It is now read-only.

Support for multiple spoke accounts #30

Open
lucymhdavies opened this issue Aug 28, 2018 · 1 comment
Open

Support for multiple spoke accounts #30

lucymhdavies opened this issue Aug 28, 2018 · 1 comment

Comments

@lucymhdavies
Copy link

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.

@hnishar
Copy link

hnishar commented Sep 12, 2018

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:

https://docs.aws.amazon.com/solutions/latest/cisco-based-transit-vpc/appendix-c.html

I've noted the feature request, thanks for the feedback!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants