Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Design and (where possible) build an automated, cloud-connected network that combines the fundamentals with modern tooling. Requirements: (1) design a CLOUD network — a VPC (AWS/Azure/GCP free tier, or Terraform plan) with public and private SUBNETS, route tables, an internet/NAT gateway, and SECURITY GROUPS enforcing least privilege (e.g. web tier reachable on 443; database only from the web tier); (2) apply AUTOMATION — express the network as code (Terraform for the cloud VPC, and/or an Ansible playbook or Python/Netmiko script to configure devices in a simulator) so it is idempotent and version-controlled in Git; (3) include a DEFENSIVE security design — segmentation, a documented firewall/security-group policy, and how remote access would be secured (VPN/zero-trust principles); (4) add an OPERATIONS plan — what you would MONITOR (bandwidth/latency/loss, key metrics), baselines/alerts, and a layered TROUBLESHOOTING runbook for a common failure; (5) document the architecture, the IaC, the security rationale, and the ops plan. Everything defensive and on infrastructure you own.
A VPC with public/private subnets, route tables, gateways, and least-privilege security groups; correct addressing.
The network expressed as version-controlled, idempotent code (Terraform and/or Ansible/Python); reproducible.
Defensive segmentation + documented firewall policy and secure remote access; a monitoring + layered troubleshooting plan.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# An automated, cloud-connected network ## Goal Design and (where possible) build an automated, cloud-connected network that combines the fundamentals with modern tooling. Requirements: (1) design a CLOUD network — a VPC (AWS/Azure/GCP free tier, or Terraform plan) with public and private SUBNETS, route tables, an internet/NAT gateway, and SECURITY GROUPS enforcing least privilege (e.g. web tier reachable on 443; database only from the web tier); (2) apply AUTOMATION — express the network as code (Terraform for the cloud VPC, and/or an Ansible playbook or Python/Netmiko script to configure devices in a simulator) so it is idempotent and version-controlled in Git; (3) include a DEFENSIVE security design — segmentation, a documented firewall/security-group policy, and how remote access would be secured (VPN/zero-trust principles); (4) add an OPERATIONS plan — what you would MONITOR (bandwidth/latency/loss, key metrics), baselines/alerts, and a layered TROUBLESHOOTING runbook for a common failure; (5) document the architecture, the IaC, the security rationale, and the ops plan. Everything defensive and on infrastructure you own. ## Acceptance criteria - [ ] Cloud network design: A VPC with public/private subnets, route tables, gateways, and least-privilege security groups; correct addressing. - [ ] Automation (IaC): The network expressed as version-controlled, idempotent code (Terraform and/or Ansible/Python); reproducible. - [ ] Security & operations: Defensive segmentation + documented firewall policy and secure remote access; a monitoring + layered troubleshooting plan. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.