The proposed enhancement is to add a new optional input variable azs to allow definition of specific Availability Zones where the module should deploy AZ bound components. Currently, there is not a mechanism to specify specific a list of Availability Zones where objects (Subnets, Routes, etc.) should be deployed and a subset based on the input variable az_count is used.

The use case for this would be to deploy the VPC subnets in AZs with service endpoint or workload affinity to optimize for cost and performance (e.g. PrivateLink endpoints only available in a subset of AZs or customers deploying workloads outside this VPC in a specific subset of AZs).