<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>网络与安全 on 黄文卓 | DevOps Engineer</title><link>https://socake.github.io/categories/%E7%BD%91%E7%BB%9C%E4%B8%8E%E5%AE%89%E5%85%A8/</link><description>Recent content in 网络与安全 on 黄文卓 | DevOps Engineer</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor><webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster><copyright>© 2026 Wenzhuo Huang</copyright><lastBuildDate>Thu, 30 Apr 2026 15:30:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/categories/%E7%BD%91%E7%BB%9C%E4%B8%8E%E5%AE%89%E5%85%A8/index.xml" rel="self" type="application/rss+xml"/><item><title>Playbook：AWS Aurora 公网入口收紧的渐进路径——从 0.0.0.0/0 到零信任</title><link>https://socake.github.io/playbook/aurora-public-access-tightening/</link><pubDate>Thu, 30 Apr 2026 15:30:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/playbook/aurora-public-access-tightening/</guid><description>很多团队的生产 Aurora 长期挂着 0.0.0.0/0 全协议规则，加上几条来源不明的 IP 白名单。直接删规则会立刻打断跨 Region 服务和开发者本地调试，于是收紧工作年复一年被推迟。本文给出一条工程化路径：先用 Flow Logs + Athena + CloudTrail 摸清依赖，把跨 Region 业务切到 VPC Peering + Route53 Private Hosted Zone，再用 SSM Port Forwarding 替代开发者直连，最后原子切换 SG 并清理长尾白名单。每一步都给可直接执行的脚本和 IAM Policy。覆盖 4 个真实踩到的坑。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/playbook/aurora-public-access-tightening/featured.jpg"/></item><item><title>Playbook：自建 Headscale 零信任 Mesh，混合云内网访问的可执行落地方案</title><link>https://socake.github.io/playbook/zerotrust-mesh-headscale/</link><pubDate>Thu, 30 Apr 2026 15:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/playbook/zerotrust-mesh-headscale/</guid><description>数据库公网入口收紧后，开发调试需求仍然真实存在。SSM Port Forwarding 这类临时方案随着资源增加和团队扩大很快变得不可维护。Headscale + Tailscale 提供了一层统一的访问控制：单台 ECS 跑控制面，每个 K8s 集群部署 Subnet Router Pod，ACL 基于身份控制访问范围。本文给出从阿里云 ECS 创建命令、Caddyfile、完整 Headscale 配置、K8s 完整 manifest、运维脚本、客户端接入脚本到故障 runbook 的一整套可直接复制执行的工件，包含 5 个生产中真实踩到的坑。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/playbook/zerotrust-mesh-headscale/featured.jpg"/></item><item><title>Headscale 自建零信任 VPN：跨云多机房内网打通</title><link>https://socake.github.io/posts/headscale-zero-trust-vpn/</link><pubDate>Sun, 12 Apr 2026 14:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/headscale-zero-trust-vpn/</guid><description>从 WireGuard 协议原理到 Headscale 完整部署，包括 DERP 自建、Subnet Router 配置、K8s 集成和 ACL 策略设计，用 Mesh VPN 替代传统堡垒机的完整实操指南。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/headscale-zero-trust-vpn/featured.jpg"/></item></channel></rss>