diff --git a/roadmaps/cloud-computing/content/core-networking@Yim9sxfbsQBiM6HTB3xaW.md b/roadmaps/cloud-computing/content/core-networking@Yim9sxfbsQBiM6HTB3xaW.md index 4995a13e8..5e48baec9 100644 --- a/roadmaps/cloud-computing/content/core-networking@Yim9sxfbsQBiM6HTB3xaW.md +++ b/roadmaps/cloud-computing/content/core-networking@Yim9sxfbsQBiM6HTB3xaW.md @@ -1,3 +1,9 @@ # Core Networking -Core networking covers the fundamental building blocks of a cloud network: isolated virtual networks, subnet segmentation, routing, and address management. These are configured before any workload is deployed and form the foundation that all other networking features build on. \ No newline at end of file +Core networking covers the fundamental building blocks of a cloud network: isolated virtual networks, subnet segmentation, routing, and address management. These are configured before any workload is deployed and form the foundation that all other networking features build on. + +Visit the following resources to learn more: + +- [@article@What is cloud networking? - Cloudflare](https://www.cloudflare.com/en-gb/learning/cloud/what-is-cloud-networking/) +- [@article@What is cloud networking? - Cisco](https://www.cisco.com/site/us/en/learn/topics/cloud-networking/what-is-cloud-networking.html) +- [@video@Cloud Networking Explained](https://www.youtube.com/playlist?list=PLOspHqNVtKAA_5N3pI49wkH4WsTkeZ_iQ) diff --git a/roadmaps/cloud-computing/content/dns-in-the-cloud@6MDgQ61_A4HbS9Kv5BXnX.md b/roadmaps/cloud-computing/content/dns-in-the-cloud@6MDgQ61_A4HbS9Kv5BXnX.md index a132547a9..77f2bf7ee 100644 --- a/roadmaps/cloud-computing/content/dns-in-the-cloud@6MDgQ61_A4HbS9Kv5BXnX.md +++ b/roadmaps/cloud-computing/content/dns-in-the-cloud@6MDgQ61_A4HbS9Kv5BXnX.md @@ -1,3 +1,8 @@ # DNS in the Cloud -Cloud DNS services resolve domain names to cloud resources and go beyond basic A record management. They support latency-based routing (directing users to the nearest region), geolocation routing, weighted routing for gradual traffic shifts, and health-check-based failover that automatically removes unhealthy endpoints. Route 53, Cloud DNS, and Azure DNS integrate directly with load balancers, CDNs, and other cloud services to enable these traffic patterns. \ No newline at end of file +Cloud DNS services resolve domain names to cloud resources and go beyond basic A record management. They support latency-based routing (directing users to the nearest region), geolocation routing, weighted routing for gradual traffic shifts, and health-check-based failover that automatically removes unhealthy endpoints. Route 53, Cloud DNS, and Azure DNS integrate directly with load balancers, CDNs, and other cloud services to enable these traffic patterns. + +Visit the following resources to learn more: + +- [@article@What is DNS? | How DNS works](https://www.cloudflare.com/learning/dns/what-is-dns/) +- [@video@How a DNS Server (Domain Name System) works.](https://www.youtube.com/watch?v=mpQZVYPuDGU) diff --git a/roadmaps/cloud-computing/content/encryption@EalIN2w9Lc_gc0Du3VrUk.md b/roadmaps/cloud-computing/content/encryption@EalIN2w9Lc_gc0Du3VrUk.md index 835ab717c..e4b4af588 100644 --- a/roadmaps/cloud-computing/content/encryption@EalIN2w9Lc_gc0Du3VrUk.md +++ b/roadmaps/cloud-computing/content/encryption@EalIN2w9Lc_gc0Du3VrUk.md @@ -1,3 +1,8 @@ # Encryption -Encryption protects data by transforming it into an unreadable format that can only be decoded with the correct key. Encryption at rest protects stored data (in databases, object storage, disk volumes) from unauthorized access if physical or logical storage is compromised. Encryption in transit protects data moving over networks using TLS, preventing interception. Cloud providers encrypt managed services by default and offer key management services (AWS KMS, Cloud KMS, Azure Key Vault) for managing and rotating encryption keys. \ No newline at end of file +Encryption protects data by transforming it into an unreadable format that can only be decoded with the correct key. Encryption at rest protects stored data (in databases, object storage, disk volumes) from unauthorized access if physical or logical storage is compromised. Encryption in transit protects data moving over networks using TLS, preventing interception. Cloud providers encrypt managed services by default and offer key management services (AWS KMS, Cloud KMS, Azure Key Vault) for managing and rotating encryption keys. + +Visit the following resources to learn more: + +- [@course@Encryption Course](https://www.internetsociety.org/learning/encryption/) +- [@article@What is encryption?](https://www.cloudflare.com/learning/ssl/what-is-encryption/) diff --git a/roadmaps/cloud-computing/content/firewalls--security-groups@sAt-dQwgeATknlYeDIwxG.md b/roadmaps/cloud-computing/content/firewalls--security-groups@sAt-dQwgeATknlYeDIwxG.md index d4c9eea1e..0cfea1be4 100644 --- a/roadmaps/cloud-computing/content/firewalls--security-groups@sAt-dQwgeATknlYeDIwxG.md +++ b/roadmaps/cloud-computing/content/firewalls--security-groups@sAt-dQwgeATknlYeDIwxG.md @@ -1,3 +1,9 @@ # Firewalls & Security Groups -Security groups are stateful virtual firewalls attached to individual instances or network interfaces. They define which inbound and outbound traffic is allowed by port, protocol, and source IP or security group. Network ACLs (Access Control Lists) operate at the subnet level and are stateless, requiring explicit rules for both directions. Together they form the primary traffic filtering layer in a VPC, controlling what can reach your instances and what your instances can reach. \ No newline at end of file +Security groups are stateful virtual firewalls attached to individual instances or network interfaces. They define which inbound and outbound traffic is allowed by port, protocol, and source IP or security group. Network ACLs (Access Control Lists) operate at the subnet level and are stateless, requiring explicit rules for both directions. Together they form the primary traffic filtering layer in a VPC, controlling what can reach your instances and what your instances can reach. + +Visit the following resources to learn more: + +- [@article@What is a firewall? How network firewalls work](https://www.cloudflare.com/en-gb/learning/security/what-is-a-firewall/) +- [@video@What is a Firewall?](https://www.youtube.com/watch?v=kDEX1HXybrU) +- [@video@AWS Security Groups Simply Explained: A Step-by-Step Tutorial for Beginners](https://www.youtube.com/watch?v=uYDT2SsHImQ) diff --git a/roadmaps/cloud-computing/content/infrastructure-as-code@GVNifuoultxXmOyoY3Ecr.md b/roadmaps/cloud-computing/content/infrastructure-as-code@GVNifuoultxXmOyoY3Ecr.md index 0e54ace80..6efa4d47c 100644 --- a/roadmaps/cloud-computing/content/infrastructure-as-code@GVNifuoultxXmOyoY3Ecr.md +++ b/roadmaps/cloud-computing/content/infrastructure-as-code@GVNifuoultxXmOyoY3Ecr.md @@ -1,3 +1,9 @@ # Infrastructure as Code -Infrastructure as Code treats cloud resources the same way software treats application logic: defined in files, stored in version control, reviewed through pull requests, and applied through automated tooling. It replaces manual console clicks with reproducible, diffable configuration and is the foundation of consistent multi-environment deployments. \ No newline at end of file +Infrastructure as Code treats cloud resources the same way software treats application logic: defined in files, stored in version control, reviewed through pull requests, and applied through automated tooling. It replaces manual console clicks with reproducible, diffable configuration and is the foundation of consistent multi-environment deployments. + +Visit the following resources to learn more: + +- [@article@What Is Infrastructure as Code?](https://www.cisco.com/site/us/en/learn/topics/computing/what-is-iac.html) +- [@article@Infrastructure-as-Code (IaC): Benefits And Best Practices](https://www.fortinet.com/resources/cyberglossary/infrastructure-as-code) +- [@video@What is Infrastructure as Code?](https://www.youtube.com/watch?v=zWw2wuiKd5o) diff --git a/roadmaps/cloud-computing/content/latency--throughput@YcSsXeZxpoDlV83vGcYXu.md b/roadmaps/cloud-computing/content/latency--throughput@YcSsXeZxpoDlV83vGcYXu.md index 7efbabbe3..fa8eda771 100644 --- a/roadmaps/cloud-computing/content/latency--throughput@YcSsXeZxpoDlV83vGcYXu.md +++ b/roadmaps/cloud-computing/content/latency--throughput@YcSsXeZxpoDlV83vGcYXu.md @@ -1,3 +1,9 @@ # Latency & Throughput -Latency is the time it takes for a single request to travel from sender to receiver and back. Throughput is the amount of data or number of requests a system can handle per unit of time. Both are used to measure and design cloud system performance: low-latency systems respond quickly to individual requests, while high-throughput systems handle large volumes of work efficiently. \ No newline at end of file +Latency is the time it takes for a single request to travel from sender to receiver and back. Throughput is the amount of data or number of requests a system can handle per unit of time. Both are used to measure and design cloud system performance: low-latency systems respond quickly to individual requests, while high-throughput systems handle large volumes of work efficiently. + +Visit the following resources to learn more: + +- [@article@What is Network Latency?](https://aws.amazon.com/what-is/latency/) +- [@article@What’s the Difference Between Throughput and Latency?](https://aws.amazon.com/compare/the-difference-between-throughput-and-latency/) +- [@video@What is Latency? (In about a minute)](https://www.youtube.com/watch?v=S0NKk86HRdg) diff --git a/roadmaps/cloud-computing/content/load-balancers@YXpKsHX1YX40NlezjO6Ut.md b/roadmaps/cloud-computing/content/load-balancers@YXpKsHX1YX40NlezjO6Ut.md index 435866523..748c37eb6 100644 --- a/roadmaps/cloud-computing/content/load-balancers@YXpKsHX1YX40NlezjO6Ut.md +++ b/roadmaps/cloud-computing/content/load-balancers@YXpKsHX1YX40NlezjO6Ut.md @@ -5,3 +5,5 @@ A load balancer distributes incoming traffic across multiple backend instances t Visit the following resources to learn more: - [@article@API gateway vs. Load balancer: Do you need one or both?](https://roadmap.sh/network-engineer/api-gateway-vs-load-balancer) +- [@article@What is Network Load Balancing? Understanding Traffic Distribution](https://www.digitalocean.com/resources/articles/network-load-balancing) +- [@video@Load Balancer Explained](https://www.youtube.com/watch?v=1fN2UDbtGDQ) diff --git a/roadmaps/cloud-computing/content/nat--ip-management@ag58krahDzkHzCZzBdxp-.md b/roadmaps/cloud-computing/content/nat--ip-management@ag58krahDzkHzCZzBdxp-.md index 07b61733d..68accb7e0 100644 --- a/roadmaps/cloud-computing/content/nat--ip-management@ag58krahDzkHzCZzBdxp-.md +++ b/roadmaps/cloud-computing/content/nat--ip-management@ag58krahDzkHzCZzBdxp-.md @@ -1,3 +1,8 @@ # NAT & IP Management -Resources in private subnets often need to make outbound requests to the internet (to download updates, call external APIs) without being reachable from outside. A NAT gateway handles this by translating private IP addresses to a public one for outbound traffic. IP management in cloud environments also covers elastic IP allocation (static public IPs), IPv4 vs IPv6 planning, and CIDR block sizing to avoid address space exhaustion as a VPC grows. \ No newline at end of file +Resources in private subnets often need to make outbound requests to the internet (to download updates, call external APIs) without being reachable from outside. A NAT gateway handles this by translating private IP addresses to a public one for outbound traffic. IP management in cloud environments also covers elastic IP allocation (static public IPs), IPv4 vs IPv6 planning, and CIDR block sizing to avoid address space exhaustion as a VPC grows. + +Visit the following resources to learn more: + +- [@article@Static vs Dynamic NAT: What’s the Difference?](https://www.h2kinfosys.com/blog/static-vs-dynamic-nat-whats-the-difference/) +- [@video@NAT Explained - Network Address Translation](https://www.youtube.com/watch?v=FTUV0t6JaDA) diff --git a/roadmaps/cloud-computing/content/network-topology@ePXTBUCFKWMC2xStg4QHF.md b/roadmaps/cloud-computing/content/network-topology@ePXTBUCFKWMC2xStg4QHF.md index b1046e460..f676e699d 100644 --- a/roadmaps/cloud-computing/content/network-topology@ePXTBUCFKWMC2xStg4QHF.md +++ b/roadmaps/cloud-computing/content/network-topology@ePXTBUCFKWMC2xStg4QHF.md @@ -1,3 +1,9 @@ # Network Topology -A data center's internal network connects thousands of servers and must handle massive volumes of east-west traffic (between servers) in addition to north-south traffic (between servers and the internet). Modern data center networks are designed to be non-blocking, highly redundant, and software-configurable to support the dynamic workloads cloud environments demand. \ No newline at end of file +A data center's internal network connects thousands of servers and must handle massive volumes of east-west traffic (between servers) in addition to north-south traffic (between servers and the internet). Modern data center networks are designed to be non-blocking, highly redundant, and software-configurable to support the dynamic workloads cloud environments demand. + +Visit the following resources to learn more: + +- [@article@What is spine-leaf architecture?](https://www.hpe.com/emea_africa/en/what-is/spine-leaf-architecture.html) +- [@article@A Guide to Simple Two-Tier, Three-Tier, and Spine-Leaf Designs](https://learningnetwork.cisco.com/s/question/0D56e0000EBtd2dCQB/a-guide-to-simple-twotier-threetier-and-spineleaf-designs) +- [@video@Cisco Spine-leaf Network Topology](https://www.youtube.com/watch?v=IPaU-N7p4L0) diff --git a/roadmaps/cloud-computing/content/networking-basics@8y280d5BPXrDZwtsHZCaX.md b/roadmaps/cloud-computing/content/networking-basics@8y280d5BPXrDZwtsHZCaX.md index c618800b3..af159b9d8 100644 --- a/roadmaps/cloud-computing/content/networking-basics@8y280d5BPXrDZwtsHZCaX.md +++ b/roadmaps/cloud-computing/content/networking-basics@8y280d5BPXrDZwtsHZCaX.md @@ -6,3 +6,7 @@ Visit the following resources to learn more: - [@roadmap@Visit the Dedicated Network Engineer Roadmap](https://roadmap.sh/network-engineer) - [@article@WebSocket vs. HTTP: Which protocol should you use?](https://roadmap.sh/network-engineer/websocket-vs-http) +- [@article@How does the internet work?](https://roadmap.sh/guides/what-is-internet) +- [@article@What is the OSI Model?](https://www.cloudflare.com/en-gb/learning/ddos/glossary/open-systems-interconnection-model-osi/) +- [@article@What Is an IP Address?](https://www.coursera.org/articles/ip-address) +- [@video@What is TCP/IP?](https://www.youtube.com/watch?v=PpsEaqJV_A0) diff --git a/roadmaps/cloud-computing/content/shell--bash@uxm_BIAyhfFmcE94k9i9J.md b/roadmaps/cloud-computing/content/shell--bash@uxm_BIAyhfFmcE94k9i9J.md index 524345934..2f21a36b7 100644 --- a/roadmaps/cloud-computing/content/shell--bash@uxm_BIAyhfFmcE94k9i9J.md +++ b/roadmaps/cloud-computing/content/shell--bash@uxm_BIAyhfFmcE94k9i9J.md @@ -5,3 +5,4 @@ Bash is the default shell on most Linux systems and the primary language for wri Visit the following resources to learn more: - [@roadmap@Visit the Dedicated Shell/Bash Roadmap](https://roadmap.sh/shell-bash) +- [@video@Shell Scripting Tutorial for Beginners 1 - Introduction](https://www.youtube.com/watch?v=cQepf9fY6cE) diff --git a/roadmaps/cloud-computing/content/subnets--routing@OAEFYuE5sD3U47Kiex4Bo.md b/roadmaps/cloud-computing/content/subnets--routing@OAEFYuE5sD3U47Kiex4Bo.md index e9e484800..f08336b9e 100644 --- a/roadmaps/cloud-computing/content/subnets--routing@OAEFYuE5sD3U47Kiex4Bo.md +++ b/roadmaps/cloud-computing/content/subnets--routing@OAEFYuE5sD3U47Kiex4Bo.md @@ -1,3 +1,10 @@ # Subnets & Routing -A VPC is divided into subnets, each assigned a CIDR block and typically tied to a specific availability zone. Public subnets have a route to an internet gateway, making resources in them reachable from the internet. Private subnets have no direct internet route and are used for databases, internal services, and anything that should not be publicly accessible. Routing tables define how traffic moves between subnets, to the internet, or to connected on-premises networks. \ No newline at end of file +A VPC is divided into subnets, each assigned a CIDR block and typically tied to a specific availability zone. Public subnets have a route to an internet gateway, making resources in them reachable from the internet. Private subnets have no direct internet route and are used for databases, internal services, and anything that should not be publicly accessible. Routing tables define how traffic moves between subnets, to the internet, or to connected on-premises networks. + +Visit the following resources to learn more: + +- [@article@What is a subnet? | How subnetting works](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-a-subnet/) +- [@article@What is CIDR?](https://aws.amazon.com/what-is/cidr/) +- [@video@Subnetting Explained: Networking Basics](https://www.youtube.com/watch?v=hbdT_Q9DM8w) +- [@video@What is CIDR (Classless Inter Domain Routing)?](https://www.youtube.com/watch?v=KiWXRL-2TnY) diff --git a/roadmaps/cloud-computing/content/terraform@BaaSRLtKgCAOBtfnKdQhZ.md b/roadmaps/cloud-computing/content/terraform@BaaSRLtKgCAOBtfnKdQhZ.md index db11b53ba..7e9d92e6b 100644 --- a/roadmaps/cloud-computing/content/terraform@BaaSRLtKgCAOBtfnKdQhZ.md +++ b/roadmaps/cloud-computing/content/terraform@BaaSRLtKgCAOBtfnKdQhZ.md @@ -6,3 +6,5 @@ Visit the following resources to learn more: - [@roadmap@Visit the Dedicated Terraform Roadmap](https://roadmap.sh/terraform) - [@article@Terraform Backend: How it Works and How to Configure it](https://roadmap.sh/terraform/backend) +- [@official@Terraform Docs](https://developer.hashicorp.com/terraform/docs) +- [@video@Terraform explained in 15 mins | Terraform Tutorial for Beginners](https://www.youtube.com/watch?v=l5k1ai_GBDE) diff --git a/roadmaps/cloud-computing/content/upstream-connectivity@gIza15GnIgZo3bHc-VHjb.md b/roadmaps/cloud-computing/content/upstream-connectivity@gIza15GnIgZo3bHc-VHjb.md index f3b2cf427..33ae53ae0 100644 --- a/roadmaps/cloud-computing/content/upstream-connectivity@gIza15GnIgZo3bHc-VHjb.md +++ b/roadmaps/cloud-computing/content/upstream-connectivity@gIza15GnIgZo3bHc-VHjb.md @@ -1,3 +1,8 @@ # Upstream Connectivity -Upstream connectivity is how a data center connects to the public internet. Providers maintain multiple redundant fiber connections to upstream ISPs and peer directly with other networks at internet exchange points (IXPs) to reduce latency and transit costs. Redundant upstream links ensure that a single cable cut or ISP outage does not take a data center offline. \ No newline at end of file +Upstream connectivity is how a data center connects to the public internet. Providers maintain multiple redundant fiber connections to upstream ISPs and peer directly with other networks at internet exchange points (IXPs) to reduce latency and transit costs. Redundant upstream links ensure that a single cable cut or ISP outage does not take a data center offline. + +Visit the following resources to learn more: + +- [@article@What is BGP? | BGP routing explained](https://www.cloudflare.com/en-gb/learning/security/glossary/what-is-bgp/) +- [@video@MicroNugget: What is BGP and BGP Configuration Explained](https://www.youtube.com/watch?v=z8INzy9E628) diff --git a/roadmaps/cloud-computing/content/virtual-private-cloud@Q4Ttb6uMZr35fVj7Bubqe.md b/roadmaps/cloud-computing/content/virtual-private-cloud@Q4Ttb6uMZr35fVj7Bubqe.md index 87ea5444a..abfd45a9c 100644 --- a/roadmaps/cloud-computing/content/virtual-private-cloud@Q4Ttb6uMZr35fVj7Bubqe.md +++ b/roadmaps/cloud-computing/content/virtual-private-cloud@Q4Ttb6uMZr35fVj7Bubqe.md @@ -1,3 +1,9 @@ # Virtual Private Cloud (VPC) -A VPC (Virtual Private Cloud) is a logically isolated network you define within a cloud provider's infrastructure. Your cloud resources run inside it, invisible to other customers on the same physical hardware. You control the IP address range, subnets, routing tables, and gateways. Every cloud deployment starts with a VPC; it is the network boundary that everything else sits inside. \ No newline at end of file +A VPC (Virtual Private Cloud) is a logically isolated network you define within a cloud provider's infrastructure. Your cloud resources run inside it, invisible to other customers on the same physical hardware. You control the IP address range, subnets, routing tables, and gateways. Every cloud deployment starts with a VPC; it is the network boundary that everything else sits inside. + +Visit the following resources to learn more: + +- [@article@What is a Virtual Network? How it Works and Its Types?](https://www.pynetlabs.com/what-is-a-virtual-network/) +- [@video@Virtual Private Cloud (VPC) Explained](https://www.youtube.com/watch?v=2fPgKvDBfbs) +- [@video@Amazon Virtual Private Cloud (VPC) Routing Deep Dive](https://www.youtube.com/watch?v=LJNNMTicv1c) diff --git a/roadmaps/cloud-computing/content/vlans--vxlan@ztCFSoR4a5qQiGrHyoroM.md b/roadmaps/cloud-computing/content/vlans--vxlan@ztCFSoR4a5qQiGrHyoroM.md index 62d37a919..ade231bcc 100644 --- a/roadmaps/cloud-computing/content/vlans--vxlan@ztCFSoR4a5qQiGrHyoroM.md +++ b/roadmaps/cloud-computing/content/vlans--vxlan@ztCFSoR4a5qQiGrHyoroM.md @@ -1,3 +1,10 @@ # VLANs & VXLAN -VLANs (Virtual Local Area Networks) segment a physical network into isolated logical networks at Layer 2. In large-scale cloud environments, VLANs alone cannot provide enough isolation across distributed data centers. VXLAN (Virtual Extensible LAN) extends Layer 2 networks over a Layer 3 IP fabric by encapsulating Ethernet frames inside UDP packets. It is the underlying technology that enables VPCs and tenant network isolation to scale across thousands of physical hosts. \ No newline at end of file +VLANs (Virtual Local Area Networks) segment a physical network into isolated logical networks at Layer 2. In large-scale cloud environments, VLANs alone cannot provide enough isolation across distributed data centers. VXLAN (Virtual Extensible LAN) extends Layer 2 networks over a Layer 3 IP fabric by encapsulating Ethernet frames inside UDP packets. It is the underlying technology that enables VPCs and tenant network isolation to scale across thousands of physical hosts. + +Visit the following resources to learn more: + +- [@article@Guide to VLANs](https://www.cbtnuggets.com/blog/technology/networking/what-is-a-vlan-and-how-they-work) +- [@article@What is VXLAN?](https://www.hpe.com/emea_europe/en/what-is/vxlan.html) +- [@video@VLAN Explained](https://www.youtube.com/watch?v=jC6MJTh9fRE) +- [@video@VXLAN - What is VXLAN?](https://www.youtube.com/watch?v=Jv0IqaM9KOs) diff --git a/roadmaps/cloud-computing/content/vpn--direct-connect@jLeK4ZrgzX2mrIVg-g-bV.md b/roadmaps/cloud-computing/content/vpn--direct-connect@jLeK4ZrgzX2mrIVg-g-bV.md index 680d53b1b..c890310a7 100644 --- a/roadmaps/cloud-computing/content/vpn--direct-connect@jLeK4ZrgzX2mrIVg-g-bV.md +++ b/roadmaps/cloud-computing/content/vpn--direct-connect@jLeK4ZrgzX2mrIVg-g-bV.md @@ -1,3 +1,9 @@ # VPN & Direct Connect -VPN (Virtual Private Network) tunnels encrypted traffic between an on-premises network and a cloud VPC over the public internet. It is quick to set up and low cost but shares bandwidth with internet traffic. Direct Connect (AWS), Cloud Interconnect (GCP), and ExpressRoute (Azure) provide dedicated private circuits between on-premises infrastructure and the cloud, offering lower and more consistent latency, higher throughput, and no exposure to public internet congestion. Direct connections are used for production hybrid architectures where VPN performance is insufficient. \ No newline at end of file +VPN (Virtual Private Network) tunnels encrypted traffic between an on-premises network and a cloud VPC over the public internet. It is quick to set up and low cost but shares bandwidth with internet traffic. Direct Connect (AWS), Cloud Interconnect (GCP), and ExpressRoute (Azure) provide dedicated private circuits between on-premises infrastructure and the cloud, offering lower and more consistent latency, higher throughput, and no exposure to public internet congestion. Direct connections are used for production hybrid architectures where VPN performance is insufficient. + +Visit the following resources to learn more: + +- [@article@What is a VPN (virtual private network)?](https://azure.microsoft.com/en-us/resources/cloud-computing-dictionary/what-is-vpn) +- [@article@What Is a Cloud VPN? | Cloud-Based Remote Access VPNs Explained](https://www.paloaltonetworks.com/cyberpedia/what-is-a-cloud-vpn) +- [@video@VPN (Virtual Private Network) Explained](https://www.youtube.com/watch?v=R-JUOpCgTZc) diff --git a/roadmaps/cloud-computing/content/zero-trust@O_HEtoFuv7NOgAbtGvFIC.md b/roadmaps/cloud-computing/content/zero-trust@O_HEtoFuv7NOgAbtGvFIC.md index 92577b5bb..d86583dac 100644 --- a/roadmaps/cloud-computing/content/zero-trust@O_HEtoFuv7NOgAbtGvFIC.md +++ b/roadmaps/cloud-computing/content/zero-trust@O_HEtoFuv7NOgAbtGvFIC.md @@ -1,3 +1,8 @@ # Zero Trust -Zero Trust is a security model based on the principle of never trust, always verify. No user or system is trusted by default, even if they are inside the corporate network. Every request is authenticated, authorized, and validated against policy before access is granted. In cloud environments, Zero Trust is implemented through strong identity verification, least-privilege IAM policies, network micro-segmentation, and continuous monitoring rather than relying on network perimeter as a trust boundary. \ No newline at end of file +Zero Trust is a security model based on the principle of never trust, always verify. No user or system is trusted by default, even if they are inside the corporate network. Every request is authenticated, authorized, and validated against policy before access is granted. In cloud environments, Zero Trust is implemented through strong identity verification, least-privilege IAM policies, network micro-segmentation, and continuous monitoring rather than relying on network perimeter as a trust boundary. + +Visit the following resources to learn more: + +- [@article@What is zero trust?](https://www.ibm.com/think/topics/zero-trust) +- [@video@Cybersecurity and Zero Trust](https://www.youtube.com/watch?v=FMMWSLIcaME)