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
Some customers want to deploy RFDK constructs into isolated subnets that have no internet access. The instances/resources deployed by the RFDK need to interact with some external sites (ex: MongoDbInstance construct accesses the MongoDB yum repository), and/or AWS services (ex: CloudFormation to signal successful startup).
The RFDK documentation should include a section on requirements for isolated subnets so that customers know which VPC Interface/Gateway endpoints they will need to deploy, and other limitations related to isolated subnets.
This is a 📕 documentation issue
The text was updated successfully, but these errors were encountered:
Some customers want to deploy RFDK constructs into isolated subnets that have no internet access. The instances/resources deployed by the RFDK need to interact with some external sites (ex: MongoDbInstance construct accesses the MongoDB yum repository), and/or AWS services (ex: CloudFormation to signal successful startup).
The RFDK documentation should include a section on requirements for isolated subnets so that customers know which VPC Interface/Gateway endpoints they will need to deploy, and other limitations related to isolated subnets.
This is a 📕 documentation issue
The text was updated successfully, but these errors were encountered: