点击蓝字关注雨生
这里是“雨生云计算”，如果你以为我只懂对着服务器发呆，那你可就太小看二十年老兵的觉悟了。
今天我们不聊枯燥的代码，我们来聊聊亚马逊是怎么一边用AWS掏空你的CTO预算，一边用卖内裤内衣服装掏空沃尔玛的。
# 亚马逊靠卖“基本款”干翻沃尔玛？这也太AWS了！
导语：
雨生觉得这也太魔幻了！当所有人都在盯着亚马逊re:Invent上的AI大模型时，亚马逊悄悄在另一个赛道完成了“绝杀”。
市值700亿美金的服装生意，不仅把沃尔玛拉下马，还给所有出海人上了一堂名为“这才是科技封建主义”的垄断公开课。无论你是卖货的还是写代码的，亚马逊收割你的姿势，从来都没变过。
***
雨生视角：杰夫·贝佐斯的“收租”艺术
各位出海圈的老炮儿、新贵，还有那些对着AWS账单欲哭无泪的CTO们，早啊。
我是雨生。这周大家的目光都盯着拉斯维加斯的re:Invent，等着看亚马逊云科技（AWS）又能整出什么新活儿来折磨我们的云端IT工程师。
但作为一个在云计算圈子里摸爬滚打二十年，顺便看透了出海营销套路的老兵，我发现了一条比AI更劲爆的新闻。
CNBC发了个视频，说亚马逊现在的服装销售额已经超过了沃尔玛，成了全美第一。
没错，你没听错，那个原本卖书、后来卖云的公司，现在成了全美最大的“裁缝铺”。
Shein在此欲哭无泪
这事儿看着离谱，但仔细一琢磨，这就很“亚马逊”。
你看，亚马逊做服装的逻辑，跟它做AWS简直是一个模子里刻出来的：
1. 先搭台子（Marketplace/Infrastructure）：把第三方卖家骗进来……哦不，请进来。
（市集飞轮效应）
2. 再收过路费（FBA fees/Data Transfer cost）：不管是发货还是流量，雁过拔毛。
（科技封建主义 technofeudalism）
3. 最后自己下场（Private Labels/Amazon Basics）：看谁卖得好，直接做一个“亚马逊倍思”牌的平替，价格比你低，排名比你高。
这哪是做生意啊，这是降维打击。就像AWS最近才终于承认“Unused NAT Gateways”（未使用的NAT网关）这玩意儿一直在偷偷扣你的钱一样，亚马逊的算法总是精准地卡在让你“肉疼但又离不开”的那个点上。
雨生深度解读：平台霸权的“阳谋”与卖家的“斯德哥尔摩综合症”
咱们剥开现象看本质。
亚马逊能干翻沃尔玛，
靠的不是时尚品味、不是整合营销传播
（虽然他们确实拉拢了Saks Fifth Avenue），
靠的是“极致的效率暴力和数据霸权”
1. “必要的恶”与流量毒药
新闻里提到，品牌方把亚马逊称为“necessary evil”（必要的恶）。
为什么？
因为你没得选。这就好比在云服务领域，你明知道AWS的出口流量费贵得离谱，但你还是得用它，因为你的生态都在上面。
服装品牌也是一样，为了那庞大的客流，不得不忍受5%到17%的佣金，再加上FBA的物流费，有时候一半的收入直接回流进了亚马逊的口袋。
2. “Buy Box”里的黑暗森林
98%的成交发生在那个小小的“Buy Box”（加入购物车按钮）里。如果你敢在其他网站卖得比亚马逊便宜，亚马逊就让你失去这个按钮。这招太狠了，直接把全网定价权锁死。这让我想起了AWS最近复活CodeCommit的闹剧——想杀就杀，想留就留，完全看心情，用户只能被动接受。
3. 数据驱动的“抄作业”
亚马逊推出了100多个自有品牌。Peak Design的摄影包被Amazon Basics“像素级致敬”的事儿大家都听过吧？这就是数据的力量。如果你是卖家，亚马逊既是你的裁判，又是你的运动员，手里还拿着你的训练数据。
行动指南：出海人如何在巨头的指缝里求生？
看完热闹，咱们得聊聊实战。
无论你是跨境电商卖家，
还是使用AWS的技术管理者，
面对这种巨头，我们该怎么办？
对于跨境卖家：
1. 拒绝“单吊”亚马逊：
虽然TikTok Shop现在还只是个“花哨”的发现引擎，但一定要布局。
亚马逊想做“最后的渔网”，你就得学会去别处撒鱼饵。DTC独立站是必须要有的，那是你唯一的私域避风港。
2. 品牌护城河：
别卖那种随随便便就能被Amazon Essentials替代的“白牌”货。做品牌，做溢价，做那些亚马逊算法理解不了的情感连接。
3. 精细化算账：就像我们优化云成本一样，你要盯着每一笔退货费、仓储费。
亚马逊现在取消了Try Before You Buy，把退货成本甩给卖家，你必须重新计算你的Unit Economics（单体经济模型）。
对于技术管理者（顺便吐槽下AWS）：
1. 盯着你的NAT网关：AWS终于在Compute Optimizer里推出“闲置NAT网关推荐”了。赶紧去查查，别像个冤大头一样为那些自2019年就没传过数据包的网关付费。
2. 拥抱Arm架构：Lambda用Arm64比x86便宜20%还更快，别因为懒得改一行代码就继续给亚马逊送钱。
3. 算清你的技术展单
互动环节：你的钱包还好吗？
亚马逊一边用AWS的高昂账单教育我们“云不便宜”，一边用服装市场的低价策略教育沃尔玛“你太慢了”。
我想问问在座的各位：
你在亚马逊上是赚钱了，还是赚了个寂寞？
或者，你的AWS账单里是不是也藏着几个“闲置NAT网关”这样的隐形刺客？
欢迎在评论区吐槽，说出你的血泪史。
点赞最高的，雨生我……我也不能帮你报销，但我能在精神上支持你！
别忘了关注 “雨生云计算”，我们这里不仅有穿透行业的犀利洞察，还有一个汇聚了出海精英的社群不管你是想省钱，还是想赚钱，进来聊聊，总比一个人在黑暗森林里瞎转悠强。
### 金句海报文案（建议搭配高冷极简风设计）
1. “亚马逊不是在卖衣服，它是在用算法收税。无论你是卖袜子的还是写代码的，都逃不掉。”
2. “品牌方眼里的亚马逊：必要的恶。工程师眼里的AWS：昂贵的痛。这就是垄断的滋味。”
3. “当你的利润只有一半属于你自己时，你不是老板，你只是亚马逊的高级打工仔。”
4. “出海的尽头不是IPO，而是看懂亚马逊的账单。”
5. “不要等到被Amazon Basics抄了底裤，才想起做品牌护城河。”
### 朋友圈转发文案模板
模板 1（硬核吐槽风）：
亚马逊干翻沃尔玛成了全美第一大服装零售商？看了雨生大佬的解读才明白，这哪是卖衣服，这简直就是降维打击！就像AWS收割云市场一样，亚马逊的镰刀从不留情。出海人必读，深度好文！
#雨生云计算 #出海必读
模板 2（焦虑共鸣风）：
看着每个月的FBA费用和AWS账单，真是感同身受。雨生这篇分析太犀利了，把亚马逊“既当裁判又当运动员”的逻辑扒得底裤都不剩。出海不易，且行且珍惜。强烈推荐关注！
#跨境电商 #AWS #雨生云计算
模板 3（知识分享风）：
很有意思的视角：亚马逊的Basic系列其实就是服装界的Serverless，便宜、好用、但也让你失去了控制权。如何在这个巨头的生态里活下来？这篇文章给了很实操的建议。
#知识星球 #数字化转型
***
### 粉丝增长与关注引导方案
**1. “避坑指南”诱饵：**
在文章底部设置钩子：“关注公众号，回复‘**避坑**’，获取“2025出海企业AWS成本优化与亚马逊运营避坑1:1咨询”。” 将文中提到的NAT网关优化、FBA费用陷阱等整理成Checklist，实用性极强。
***
### 新闻原文中英文对照（完整保留链接）
**The video provided, titled "How Amazon Built A $70 Billion Clothing Business" by CNBC, details how Amazon overtook Walmart to become the largest apparel retailer in the US.**
CNBC 提供的题为《亚马逊如何建立 700 亿美元的服装业务》的视频详细介绍了亚马逊如何超越沃尔玛成为美国最大的服装零售商。
**It explores the strategies Amazon used to dominate the market, the significant costs and challenges faced by third-party sellers, and the complex relationship between the e-commerce giant and fashion brands.**
视频探讨了亚马逊用于主导市场的策略、第三方卖家面临的巨大成本和挑战，以及这家电商巨头与时尚品牌之间复杂的关系。
**Here is a summary of the key points from the video:**
以下是视频要点的总结：
**1. Market Dominance**
**1. 市场主导地位**
**Rapid Growth: Fueled by the pandemic, Amazon’s clothing sales surged, solidifying its spot as the top US apparel retailer—a title held by Walmart until 2018.**
快速增长：受疫情推动，亚马逊的服装销售额激增，巩固了其作为美国顶级服装零售商的地位——这一头衔在 2018 年之前一直由沃尔玛保持。
**Scale: By 2024, nearly 13% of all US clothing sales occurred on Amazon [00:24]. Its apparel and footwear sales were more than double Walmart’s and ten times that of its closest online competitor.**
规模：到 2024 年，近 13% 的美国服装销售发生在亚马逊上 [00:24]。其服装和鞋类销售额是沃尔玛的两倍多，是其最接近的在线竞争对手的十倍。
**2. Growth Strategies**
**2. 增长策略**
**Amazon employed several strategies to build its fashion empire:**
亚马逊采用了几种策略来建立其时尚帝国：
**Third-Party Sellers: A vast portion of Amazon's inventory comes from third-party sellers. Brands feel compelled to be on the platform due to its sheer volume of customers, often describing it as a "necessary evil" [00:48].**
第三方卖家：亚马逊的大部分库存来自第三方卖家。由于平台拥有庞大的客户群，品牌感到不得不入驻，通常将其描述为“必要的恶” [00:48]。
**Private Labels: Amazon launched over 100 private label brands (e.g., Amazon Essentials, Amazon Basics). While some were cut for profitability, staples like basics remain successful because they are less seasonal and risky than high-fashion items [02:37].**
自有品牌：亚马逊推出了 100 多个自有品牌（例如 Amazon Essentials, Amazon Basics）。虽然有些为了盈利而被削减，但像基础款这样的主要产品仍然很成功，因为它们比高级时尚单品受季节影响小，风险也更低 [02:37]。
**Luxury & Partnerships: After years of struggle, Amazon has successfully courted high-end brands. In 2020, it launched a luxury storefront and recently partnered with Saks Fifth Avenue [04:01]. Even Nike, which famously left the platform in 2019, returned in 2025 to better control unauthorized listings [03:18].**
奢侈品与合作伙伴关系：经过多年的努力，亚马逊成功吸引了高端品牌。2020 年，它推出了奢侈品店面，最近还与 Saks Fifth Avenue 合作 [04:01]。甚至在 2019 年高调离开该平台的耐克，也于 2025 年回归，以更好地控制未经授权的商品列表 [03:18]。
**3. The "Seller's Dilemma": Fees and Competition**
**3. “卖家的困境”：费用与竞争**
**While Amazon provides access to millions of customers, it comes at a steep price for sellers:**
虽然亚马逊提供了接触数百万客户的机会，但卖家需要付出高昂的代价：
**High Fees: Sellers pay a referral fee (typically 5-17% for clothing) plus additional costs for "Fulfillment by Amazon" (FBA) to handle shipping and returns. Some reports suggest sellers spend up to 50% of their revenue on Amazon fees [05:54].**
高额费用：卖家支付推荐费（服装通常为 5-17%）加上“亚马逊物流”（FBA）处理运输和退货的额外费用。一些报告表明，卖家在亚马逊费用上的支出高达其收入的 50% [05:54]。
**The "Buy Box" & Pricing: 98% of sales happen through the "Buy Box" (the "Add to Cart" button). Amazon is accused of penalizing sellers who offer lower prices on other websites by removing them from this box, effectively forcing them to keep Amazon prices the lowest [09:32].**
“购买框”与定价：98% 的销售通过“购买框”（“加入购物车”按钮）发生。亚马逊被指控惩罚那些在其他网站上提供更低价格的卖家，将他们从这个框中移除，实际上迫使他们保持亚马逊价格最低 [09:32]。
**"Dupes" and Data: There are allegations that Amazon uses data from third-party sales to create its own cheaper "dupes." A specific example mentioned is Peak Design, whose popular camera bag was almost exactly copied by an Amazon Basics bag [07:35].**
“平替”与数据：有指控称亚马逊利用第三方销售数据来制造自己更便宜的“平替品”。提到的一个具体例子是 Peak Design，其受欢迎的相机包几乎被一款 Amazon Basics 包完全复制 [07:35]。
**4. The Problem of Returns**
**4. 退货问题**
**Fashion has the highest return rates in e-commerce, creating a massive logistical and financial burden:**
时尚业在电子商务中拥有最高的退货率，造成了巨大的物流和财务负担：
**Customer Behavior: Shoppers often "bracket" purchases—buying multiple sizes or colors and returning what doesn't fit. This process is so costly that sellers often lose money on these orders [11:58].**
客户行为：购物者经常“括号式”购买——购买多种尺寸或颜色，然后退回不合适的。这个过程成本很高，卖家经常在这些订单上赔钱 [11:58]。
**Waste: A significant portion of returned apparel ends up in landfills or is incinerated for energy recovery because processing it for resale is too expensive [12:16].**
浪费：很大一部分退回的服装最终进入垃圾填埋场或被焚烧以回收能量，因为处理它们以进行转售太昂贵了 [12:16]。
**Policy Changes: In 2025, Amazon ended its "Try Before You Buy" program, likely due to the unsustainable costs of covering shipping for returns, shifting that burden back to small businesses [13:11].**
政策变化：2025 年，亚马逊结束了其“先试后买”计划，这可能是由于支付退货运费的成本不可持续，从而将这种负担转嫁回小企业 [13:11]。
**5. Future Outlook**
**5. 未来展望**
**Social Commerce: As platforms like TikTok Shop rise as "glittery" discovery engines for trends, Amazon is positioning itself as the reliable "net" that captures the final purchase [15:19].**
社交电商：随着像 TikTok Shop 这样的平台作为趋势的“闪耀”发现引擎兴起，亚马逊将自己定位为捕捉最终购买的可靠“网” [15:19]。
**Continued Growth: Analysts predict Amazon’s apparel segment will grow another 7.5% in 2025, surpassing $70 billion in sales [15:33].**
持续增长：分析师预测亚马逊的服装部门将在 2025 年再增长 7.5%，销售额超过 700 亿美元 [15:33]。
**http://www.youtube.com/watch?v=SXrnZhwf9cQ**
http://www.youtube.com/watch?v=SXrnZhwf9cQ
**Last Week in AWS**
**上周 AWS 动态**
**Monday, December 1, 2025**
**2025 年 12 月 1 日，星期一**
**Good Morning!**
**早上好！**
**We're hosting a breakfast on Dec 2 and the annual Atomic Liquors DrinkUp on Dec 3 if you're in Las Vegas. If you're not, I'm deeply envious. I'm also speaking in two sessions; they're not to miss. Just search my name in the event catalog.**
如果你在拉斯维加斯，我们将在 12 月 2 日举办早餐会，并在 12 月 3 日举办年度 Atomic Liquors 聚会。如果你不在，我深表羡慕。我也将在两个会议上发言；这不容错过。只需在活动目录中搜索我的名字。
**Looking forward to seeing some of you, and dreading seeing a few more of you.**
期待见到你们中的一些人，并害怕见到另外一些人。
**From the Community**
**来自社区**
**7 Security Best Practices for MCP**
**MCP 的 7 个安全最佳实践**
**Learn what security teams are doing to protect MCP without slowing innovation.**
了解安全团队正在做什么来保护 MCP 而不减缓创新。
**As MCP (Model Context Protocol) becomes the standard for connecting LLMs to tools and data, security teams are moving fast to keep these new services safe.**
随着 MCP（模型上下文协议）成为连接 LLM 与工具和数据的标准，安全团队正在快速行动以确保这些新服务的安全。
**The MCP Security Best Practices Cheat Sheet outlines seven proven steps teams can put in place right away, including:**
MCP 安全最佳实践备忘单概述了团队可以立即实施的七个经过验证的步骤，包括：
**How to lock down MCP servers and supply chains**
如何锁定 MCP 服务器和供应链
**Enforcing least-privilege access for tokens and tools**
对令牌和工具强制执行最小特权访问
**Adding human-in-the-loop safeguards for critical actions**
为关键操作添加人在环路保障
**Get the MCP Security Cheat Sheet SPONSORED**
获取 MCP 安全备忘单（赞助内容）
**A good exploration from Yelp in working with S3 server access logs at scale. Remember, these are orders of magnitude cheaper than CloudTrail data events.**
Yelp 在大规模处理 S3 服务器访问日志方面的一个很好的探索。请记住，这些比 CloudTrail 数据事件便宜几个数量级。
**re:Inforce will not be returning next year, as it is being folded into re:Invent; this lets them quit the field without admitting defeat. The community-driven fwd:CloudSec has won.**
re:Inforce 明年将不再回归，因为它已被并入 re:Invent；这让他们可以在不承认失败的情况下退出该领域。社区驱动的 fwd:CloudSec 赢了。
**Comparing AWS Lambda Arm64 vs x86_64 Performance Across Multiple Runtimes in Late 2025 - Someone actually did the homework AWS should've updated after their 2023 blog post. Turns out ARM64 is still 20% cheaper and faster for Lambda, yet most people are still running x86 because inertia costs nothing until you see the bill. Personally I still find x86 Lambdas sneaking in because using Arm isn't the default; you've gotta specify it in the CDK. Honestly, I'd be fine with making specifying an arch a mandatory field.**
比较 2025 年末 AWS Lambda Arm64 与 x86_64 在多个运行时的性能 - 有人实际上完成了 AWS 在 2023 年博客文章之后应该更新的作业。事实证明，ARM64 对于 Lambda 来说仍然便宜 20% 且速度更快，但大多数人仍在运行 x86，因为惯性在你看账单之前是没有任何成本的。就个人而言，我仍然发现 x86 Lambda 潜入其中，因为使用 Arm 不是默认设置；你必须在 CDK 中指定它。老实说，我不介意将指定架构设为必填字段。
**AWS finally admits via a public roadmap what Lambda users have known for years: they're making it up as they go. No dates, no commitments, just a GitHub repo where your feature requests go to die while they "research" basic functionality that should've shipped in 2015. I have yet to see anything in here about "we sure do blather a lot about AI, maybe that AI could automatically update runtime versions so we don't have to email you 400 times every time we deprecate an old version?"**
AWS 终于通过公开路线图承认了 Lambda 用户多年来都知道的事情：他们正在边做边编。没有日期，没有承诺，只有一个 GitHub 存储库，你的功能请求在那里消亡，而他们“研究”那些本应在 2015 年发布的基本功能。我还在这里没有看到任何关于“我们确实在喋喋不休地谈论人工智能，也许那个人工智能可以自动更新运行时版本，这样我们就不必在每次弃用旧版本时给你发 400 封电子邮件了？”的内容。
**My friend runs Conference Parties, which is awesome. Note that our event is there for this Wednesday night! If you're throwing a party, you should absolutely be sponsoring this; it costs way less than the first round of drinks at any party you're gonna throw.**
我的朋友经营 Conference Parties，这很棒。请注意，我们的活动就在这周三晚上！如果你要举办派对，你绝对应该赞助这个；这比你要举办的任何派对的第一轮饮料便宜得多。
**The Future of AWS CodeCommit - AWS just apologized for trying to kill CodeCommit, blamed "adoption patterns," then resurrected it after realizing customers hate migrating. Git LFS arrives in 2026—because nothing says "we're serious" like a two-year roadmap for a feature GitHub launched in 2015. My take on this in The Register is that they should be praised for this reversal. More listening to customers, less blathering about AI please.**
AWS CodeCommit 的未来 - AWS 刚刚为试图扼杀 CodeCommit 而道歉，归咎于“采用模式”，然后在意识到客户讨厌迁移后复活了它。Git LFS 将于 2026 年到来——因为没有什么比为 GitHub 在 2015 年推出的功能制定两年路线图更能说明“我们是认真的”了。我在 The Register 上对此的看法是，他们应该因为这一逆转而受到赞扬。请多听听客户的意见，少喋喋不休地谈论人工智能。
**And now, a EC2 Instance Family Performance Ranking, which is likely way more diplomatic a framing than "leaderboard."**
现在，是一个 EC2 实例系列性能排名，这可能比“排行榜”更外交辞令。
**Choice Cuts**
**精选内容**
**Tired of your CI being a black box? Depot just launched GitHub Actions Analytics, giving you the visibility you need to finally cut those bloated bills. Track job performance, CPU/memory usage, and get optimization recommendations. See what's slow, what's expensive, and what's just... weird.**
厌倦了你的 CI 是一个黑匣子？Depot 刚刚推出了 GitHub Actions Analytics，为你提供所需的可见性，以最终削减那些臃肿的账单。跟踪作业性能、CPU/内存使用情况，并获得优化建议。看看什么是慢的，什么是贵的，什么是……奇怪的。
**P.S. Ready for some holiday coding fun? Join our Advent of Code 2025 event and compete for prizes while solving puzzles! SPONSORED**
P.S. 准备好享受假期的编码乐趣了吗？加入我们的 Advent of Code 2025 活动，在解决难题的同时争夺奖品！（赞助内容）
**Protect sensitive data with dynamic data masking for Amazon Aurora PostgreSQL - Dynamic data masking finally arrives for Aurora PostgreSQL, solving a problem enterprises have been MacGyvering solutions for since approximately forever. The pg_columnmask extension handles role-based masking at query runtime without duplicating data or butchering performance. Shame it took until 2024 to get column-level protection that doesn't require maintaining seventeen copies of your database as you continue to play whack-a-mole–wait, now it's eighteen.**
使用 Amazon Aurora PostgreSQL 的动态数据屏蔽保护敏感数据 - 动态数据屏蔽终于来到了 Aurora PostgreSQL，解决了一个企业大约从一开始就在拼凑解决方案的问题。pg_columnmask 扩展在查询运行时处理基于角色的屏蔽，而无需复制数据或破坏性能。遗憾的是，直到 2024 年才获得列级保护，而不需要在你继续玩打地鼠游戏时维护 17 份数据库副本——等等，现在是 18 份了。
**Amazon CloudFront announces support for mutual TLS authentication - Free security features from AWS? Someone must have lost a bet. Though I'll give credit where it's due—mTLS at the edge without extra charges is genuinely useful for B2B APIs and IoT fleets. Your compliance team will finally stop asking when you're implementing proper client auth, once they learn what the hell mTLS is.**
Amazon CloudFront 宣布支持双向 TLS 认证 - AWS 提供免费的安全功能？一定是有人打赌输了。虽然我要给予应有的赞扬——边缘的 mTLS 没有任何额外费用，对于 B2B API 和 IoT 车队来说确实很有用。一旦你的合规团队了解到 mTLS 到底是什么，他们终于会停止询问你何时实施适当的客户端身份验证。
**Amazon EC2 announces interruptible Capacity Reservations - So you're paying to reserve capacity you're not using, and AWS's brilliant solution is... letting you share your own unused capacity with yourself? I think? What the hell is this? I am more confused having read this than I was when I started. Is this just Spot Instances with extra steps and a corporate org chart requirement?**
Amazon EC2 宣布可中断的容量预留 - 所以你花钱预留了你不使用的容量，而 AWS 的绝妙解决方案是……让你与自己分享你自己未使用的容量？我想是这样？这到底是什么？读完这个我比开始时更困惑了。这只是带有额外步骤和公司组织结构要求的 Spot 实例吗？
**Introducing guidelines for network scanning - AWS just published a "please don't scan our stuff unless you're nice about it" guideline that's basically a polite letter to security researchers while they build the technical controls to actually enforce it.**
引入网络扫描指南 - AWS 刚刚发布了一份“请不要扫描我们的东西，除非你态度好”的指南，这基本上是给安全研究人员的一封礼貌信，同时他们正在建立技术控制以实际执行它。
**Practical implementation considerations to close the AI value gap - AWS notices 42% of companies are abandoning AI projects due to lack of value and thinks "this is the perfect time to sell more AI consulting." After all, if you can't be part of the solution, there's good money in prolonging the problem.**
弥合 AI 价值差距的实际实施考虑因素 - AWS 注意到 42% 的公司因缺乏价值而放弃 AI 项目，并认为“这是销售更多 AI 咨询的最佳时机”。毕竟，如果你不能成为解决方案的一部分，那么延长问题也是可以赚大钱的。
**Everything you don’t need to know about Amazon Aurora DSQL: Part 4 – DSQL components - Four blog posts deep into DSQL's architecture and we still haven't talked about pricing. That's not an accident—when AWS needs a four-part series to explain how your database works before mentioning what it costs, grab your wallet and prepare for impact. Maybe that's unfair. I couldn't tell you, because I cannot for the life of me predict what a workload on this thing is gonna cost in advance. Nobody can. It's a nondeterministic randomizer.**
关于 Amazon Aurora DSQL 你不需要知道的一切：第 4 部分 – DSQL 组件 - 深入探讨 DSQL 架构的四篇博文，我们仍然没有谈论定价。这并非偶然——当 AWS 需要分四部分来解释你的数据库如何工作，然后再提及它的成本时，请捂紧你的钱包并准备好迎接冲击。也许这不公平。我无法告诉你，因为我无论如何也无法提前预测这东西的工作负载会花费多少。没人能。它是一个非确定性的随机发生器。
**Simplify data integration using zero-ETL from self-managed databases to Amazon Redshift - AWS rebrands "we finally made DMS slightly less painful" as "zero-ETL" while you still configure endpoints, network settings, IAM policies, KMS keys, and Secrets Manager. That's not zero anything—it's just ETL with better marketing and the same architectural complexity tax.**
使用从自管数据库到 Amazon Redshift 的 zero-ETL 简化数据集成 - AWS 将“我们终于让 DMS 稍微不那么痛苦了”重塑为“zero-ETL”，而你仍然需要配置端点、网络设置、IAM 策略、KMS 密钥和 Secrets Manager。这不是零任何东西——这只是营销更好的 ETL，以及同样的架构复杂性税。
**Automatic quota management is now AWS Service Quotas adds support for automatic quota management - No, you are not having a stroke, that's the actual title this thing originally published with. AWS finally automated quota increases after years of customers filing tickets like it's 1997. Sure, it's free now, but I'm betting the "auto-scaling" comes with some interesting asterisks about which quotas qualify and how aggressively they'll actually increase before making you call support anyway.**
自动配额管理现在是 AWS Service Quotas 增加了对自动配额管理的支持 - 不，你没有中风，这是这东西最初发布时的实际标题。在客户像 1997 年一样提交工单多年后，AWS 终于自动化了配额增加。当然，它现在是免费的，但我敢打赌，“自动扩展”带有一些有趣的星号，说明哪些配额符合条件，以及在让你不得不致电支持之前，它们实际上会增加多少。
**Announcing Amazon Route 53 Accelerated Recovery for managing public DNS records - Cool, AWS finally admitted their control plane living exclusively in us-east-1 was a single point of failure. Now they've graciously built in what should've existed from day one - for free, which tells you how embarrassing this gap was. Your "stranded changes" during failover still vanish though, so maybe test that resubmission workflow before you actually need it. I'd also like if they explained how the hell this works, because "when our stuff is breaking, this thing won't" is surprisingly uncompelling in isolation.**
宣布用于管理公共 DNS 记录的 Amazon Route 53 Accelerated Recovery - 酷，AWS 终于承认他们完全位于 us-east-1 的控制平面是一个单点故障。现在他们大方地内置了本应从第一天起就存在的东西——免费的，这告诉你这个差距有多令人尴尬。不过，故障转移期间你“滞留的更改”仍然会消失，所以也许在你真正需要之前测试一下重新提交工作流。我也希望他们解释这到底是如何工作的，因为孤立地看，“当我们的东西坏了时，这个东西不会坏”令人惊讶地没有说服力。
**Announcing Unused NAT Gateway Recommendations in AWS Compute Optimizer - AWS finally notices customers paying $35/month for NAT Gateways that haven't passed a packet since 2019 and I am overcome with joy. The feature's smart enough to avoid flagging disaster recovery configs, which is progress from third party tooling's usual "delete everything and pray" cost optimization approach.**
宣布 AWS Compute Optimizer 中的未使用 NAT 网关推荐 - AWS 终于注意到客户为自 2019 年以来就没有传递过数据包的 NAT 网关每月支付 35 美元，我欣喜若狂。该功能足够聪明，可以避免标记灾难恢复配置，这是相对于第三方工具通常的“删除所有内容并祈祷”的成本优化方法的进步。
**Amazon EKS introduces Provisioned Control Plane - Reserved capacity for Kubernetes control planes sounds reasonable until you see the prices: $1.65/hr minimum, scaling to $6.90/hr for the "4XL" tier. That's an extra $60K annually just to guarantee your cluster won't choke during Black Friday. Most shops will discover their standard control plane was fine all along. I'd prefer if they had devoted this energy to the slow-as-molasses provisioning of EKS control planes from scratch.**
Amazon EKS 推出预置控制平面 - Kubernetes 控制平面的预留容量听起来很合理，直到你看到价格：最低 1.65 美元/小时，“4XL”层级扩展到 6.90 美元/小时。这每年要额外花费 6 万美元，仅仅是为了保证你的集群不会在黑色星期五期间窒息。大多数商店会发现他们的标准控制平面一直都很好。我更希望他们把这精力投入到从头开始配置 EKS 控制平面的蜗牛般速度上。
**I could not be happier that AWS Finally Lets You Find Your Idle NAT Gateways.**
我非常高兴 AWS 终于让你找到你的闲置 NAT 网关。
