Allows users to specify the subnet IDs to be used for the database
Why?
Since we don't always get to create our own VPC, the subnets associated with it are not always one or the other type. We've had issues in the past with the private subnet type not being available in the VPC (PRIVATE_ISOLATED, PRIVATE_EGRESS, etc. This allows users to specify the subnet ids so we don't rely on a specific type.
Testing?
Deployed and manually checked that the database and the ingest lambdas were associated to the subnets provided
What?
Why?
PRIVATE_ISOLATED,PRIVATE_EGRESS, etc. This allows users to specify the subnet ids so we don't rely on a specific type.Testing?