-
Notifications
You must be signed in to change notification settings - Fork 28
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.
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
Perimeter project for landing-zone-v2 #258
Comments
Dave L's Notes Related Currently in use Links
Deployment
20230124: review new documentation in https://github.com/ssc-spc-ccoe-cei/gcp-documentation |
merge main in prep (10 behind)
|
Dave, I have not been able to spend the proper amount of time on this issue yet - as I am currently busy getting 2 other projects up that will require this perimeter work. I have been working at getting the patch up through merges to the branch - but I don't want to slow down progress. All 3 projects so far require this #258 issue and I will try to find more time over this week to complete it. |
as a platform admin, I need a perimeter project that will follow the hub and spoke network design and provide the hub functionality.
so that all ingress and egress network traffic when communicating with networks outside of the landing zone is controlled, but also that traffic between spokes is controlled.
Intrusion protection service and web filtering are the features required for the MVP.
Cloud Armor and Global load balancers are also included in the network design.
Fortinet Fortigate appliances with an active-active cluster configuration is preferable
An internal load balancer is included in the network design for egress traffic coming from spokes.
A management VM should also be provisioned to allow management of the Fortigates.
The text was updated successfully, but these errors were encountered: