<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud on maateen</title><link>https://maateen.me/tags/cloud/</link><description>Recent content in Cloud on maateen</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 02 Jul 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://maateen.me/tags/cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS VPC 101: Virtual Private Cloud Architecture</title><link>https://maateen.me/posts/aws-vpc-101/</link><pubDate>Thu, 02 Jul 2020 00:00:00 +0000</pubDate><guid>https://maateen.me/posts/aws-vpc-101/</guid><description>&lt;p&gt;AWS VPC is the foundation of cloud infrastructure in AWS. When we start architecting infrastructure, we start by designing the VPCs. Whatever we need to launch, EC2/EKS/RDS, we have to launch within the VPC. If we don&amp;rsquo;t plan it well, soon we will be running out the IP address or facing subnet collision while setting up network connectivity with internal/external networks. So, we will try to have a high-level idea over AWS VPC in this blog.&lt;/p&gt;</description></item></channel></rss>