<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VPC on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/vpc/</link><description>Recent content in VPC on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 30 Apr 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/vpc/index.xml" rel="self" type="application/rss+xml"/><item><title>Alibaba Cloud Full Stack (3): VPC, SLB, and the Network Layer</title><link>https://www.chenk.top/en/aliyun-fullstack/03-vpc-networking/</link><pubDate>Thu, 30 Apr 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/aliyun-fullstack/03-vpc-networking/</guid><description>&lt;p>Every outage I have debugged in the cloud ultimately traced back to networking. Bad CIDR planning that ran out of IPs six months in. Missing routes that silently dropped traffic between tiers. Security groups that were either wide open (hello, port 22 to &lt;code>0.0.0.0/0&lt;/code>) or so locked down that health checks failed and the load balancer kept draining healthy instances. Getting the network layer right is the single most important thing you can do before deploying anything else, and it is the single most painful thing to fix retroactively because changing a VPC CIDR means recreating everything inside it.&lt;/p></description></item><item><title>Terraform for AI Agents (3): A Reusable VPC and Security Baseline</title><link>https://www.chenk.top/en/terraform-agents/03-vpc-and-security-baseline/</link><pubDate>Mon, 16 Mar 2026 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/terraform-agents/03-vpc-and-security-baseline/</guid><description>&lt;p>This article builds the single most copied piece of Terraform in my agent projects: a &lt;code>vpc-baseline&lt;/code> module that gives every later component (ECS, RDS, OpenSearch, ACK) a sane place to land. It&amp;rsquo;s about 200 lines of HCL all-in. Worth typing once, refer to it forever.&lt;/p>
&lt;p>By the end you&amp;rsquo;ll have:&lt;/p>
&lt;ul>
&lt;li>A VPC across three availability zones in one region&lt;/li>
&lt;li>Six vSwitches (one public + one private per zone) with non-overlapping CIDRs&lt;/li>
&lt;li>A NAT Gateway with EIP for private-subnet outbound to LLM APIs&lt;/li>
&lt;li>Three security groups stacked by tier (ALB → agent runtime → memory)&lt;/li>
&lt;li>Three KMS customer master keys, one per data domain (memory, secrets, logs)&lt;/li>
&lt;li>A clean module interface: &lt;code>name + CIDR + zones&lt;/code> in, IDs out&lt;/li>
&lt;li>Drift detection in CI, semver-pinned module references, and a per-line cost model&lt;/li>
&lt;/ul>
&lt;hr>
&lt;h2 id="the-mental-model" class="heading-anchor">The mental model&lt;a href="#the-mental-model" class="heading-link" aria-label="Permalink to this section" title="Copy link to this section">#&lt;/a>
&lt;/h2>&lt;p>Before code, the picture:&lt;/p></description></item><item><title>Cloud Computing (5): Cloud Network Architecture and SDN</title><link>https://www.chenk.top/en/cloud-computing/networking-sdn/</link><pubDate>Tue, 18 Apr 2023 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/cloud-computing/networking-sdn/</guid><description>&lt;p>&lt;figure class="article-figure">
 &lt;img src="https://blog-pic-ck.oss-cn-beijing.aliyuncs.com/posts/en/cloud-computing/networking-sdn/illustration_1.png" alt="Cloud Computing (5): Cloud Network Architecture and SDN — Chapter overview" loading="lazy" decoding="async" class="content-image">
 
&lt;/figure>
&lt;/p>
&lt;p>A cloud platform is essentially a network with attached computers. The compute layer scales by adding servers; the storage layer scales by adding disks; the &lt;em>network&lt;/em> layer integrates these into a single, coherent system. Get the network right, and the rest of the stack feels effortless. Get it wrong — a missing route, a 5-tuple mismatch in a security group, or an under-provisioned load balancer — and the whole platform goes dark.&lt;/p></description></item></channel></rss>