Skip to content

docs: correct stages-aw networking description #240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
KSAGlory wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −1
Open

docs: correct stages-aw networking description #240

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion fast/stages-aw/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,9 @@ To destroy a previous FAST deployment follow the instructions detailed in cleanu
- [FedRAMP High/Moderate Compliant](/fast/stages-aw/2-networking-a-fedramp/README.md)
- [IL5/IL4 Compliant](2-networking-b-il5-ngfw/README.md)

Manages centralized network resources in a separate stage, and is typically owned by the networking team. This stage implements a hub-and-spoke design, and includes connectivity via VPN to on-premises, and YAML-based factories for firewall rules (hierarchical and VPC-level) and subnets. Currently, two networking options (IL5/IL4 and FedRAMP High/Moderate Compliant) are available.
Manages centralized network resources in a separate stage and is typically owned by the networking team. This stage implements a hub-and-spoke design. Firewall rules and subnets are configured through Terraform variables. Currently, two networking options (IL5/IL4 and FedRAMP High/Moderate Compliant) are available.

Hybrid connectivity is not deployed by either networking option and must be designed separately.

## Security (3)

Expand Down