Your next step: cloud networking Project brief Keep the networking ideas; learn the provider rules A cloud virtual network still uses addresses, subnets, routes and access controls. In AWS, a VPC is a logically isolated virtual network, and a subnet belongs to one Availability Zone. Other cloud platforms use their own names and rules. Do not assume a cloud subnet behaves exactly like a physical Ethernet LAN. In AWS, a route table controls subnet traffic destinations. A security group is a stateful control associated with supported resources. A network ACL is a separate subnet-level control with different behaviour. An internet route alone is not enough: addressing, security policy and application state also matter. Start with a paper project, without a cloud bill Choose a VPC range such as 10.20.0.0/16. Draw an application subnet 10.20.1.0/24 and a data subnet 10.20.2.0/24. List exactly which service may talk to which port. Mark which services need inbound access and which only need outbound access. Explain routes, name resolution and logging for each path. Before deploying on a provider, review its current pricing, regional availability, reserved address rules and cleanup procedure. NAT services, public addresses and other resources may incur charges. This lesson does not create billable resources. Add Linux, identity/access management and infrastructure-as-code skills before moving to a real deployment. Evidence worksheet Goal: Audience and requirements: Devices/services and versions: Diagram and address plan: Allowed traffic (source, destination, protocol/port): Intentionally blocked traffic: Build steps: Expected result for each test: Actual result and evidence: One deliberate fault in an isolated copy: Investigation and correction: Rollback and cleanup: What I would improve next: Do not include real passwords, personal data or private company configurations. No certification or job outcome is promised. Cloud projects begin on paper; check current charges and cleanup before creating provider resources.