AWS Workspaces require use of specific AZ ids about terraform-aws-vpc-nfw HOT 3 OPEN

would it make sense to add a workspaces subnet input type to the module instead? that way any time workspaces is spun up it'll use the specific AZs its supposed to? I can add something like that too.

from terraform-aws-vpc-nfw.

That should work. It just would likely need to be noted somewhere in documentation (README or otherwise) that Workspaces is something that needs to be carefully considered when building the VPC subnets and ruled out in future architecture. Just because I'd imagine it's not easy (or possible?) if someone deploys in say, us-east-1a, us-east-1b, us-east-1c thinking they don't ever need Workspaces, but then a few years later they want/need to add Workspaces but the subnets are in the wrong AZ IDs for the account.

from terraform-aws-vpc-nfw.

synced with @herman-wong-cf on the tech sync, i didn't understand correctly that the AZ IDs can vary per account per region, so the mapping isn't consistent per region, its consistent per account only. Will work to update this on the backside.

from terraform-aws-vpc-nfw.