---
title: "Oct 31–Nov 6: Amazon's Washington data center fight, and more"
show: "AWS Drama"
canonical: "https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week/"
date: "2026-11-06T03:35:25+00:00"
duration: "28:51"
duration_seconds: 1731
audio: "https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week/2026-11-06-week-aws.mp3"
chapters: "https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week/chapters.json"
transcript: "https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week.txt"
feed: "https://podcasts.robotpaper.ai/aws/feed.xml"
language: "en"
author: "Roy Osherove"
ai_generated_voices: true
---

# Oct 31–Nov 6: Amazon's Washington data center fight, and more

AWS Drama · Nov 6, 2026 · 29 min

- Listen: [MP3, 28 MB](https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week/2026-11-06-week-aws.mp3)
- Subscribe via RSS: https://podcasts.robotpaper.ai/aws/feed.xml (paste into any podcast app)
- Web page: https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week/
- Chapters (JSON): https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week/chapters.json
- Transcript (text): https://podcasts.robotpaper.ai/aws/ep/2026-11-06-week.txt
- Show: [AWS Drama](https://podcasts.robotpaper.ai/aws/) (RSS: https://podcasts.robotpaper.ai/aws/feed.xml)

## Chapters

- `00:00:00` Intro
- `00:00:17` A Microsoft departure
- `00:01:26` Gateway gets dropped
- `00:03:13` The hostname fight
- `00:05:06` Dropbox buys a rival
- `00:06:55` Bots managing bots
- `00:08:47` The engineer rewrite
- `00:10:38` Spend cap backlash
- `00:12:27` Accounts locked out
- `00:14:19` The trillion ambition
- `00:16:06` Washington pushes back
- `00:18:00` The news
- `00:18:11` Image security checks
- `00:19:16` Software inventory
- `00:20:19` Certificate revocation
- `00:21:32` Automatic bot signals
- `00:22:43` Web Answer for agents
- `00:23:46` Agent cloud desktops
- `00:24:56` GovCloud model routing
- `00:26:07` Shared GPU inference
- `00:27:18` Kimi stays in India
- `00:28:28` Outro

## Show notes

New format: this show was RobotPaper's weekly AWS news podcast. From this episode it is AWS Drama, with one host, Rachel: the week's ten messiest AWS stories, then the news. Same feed; earlier episodes stay available.

### The drama: the ten messiest AWS stories of the week (10)

- Tech Moves: Microsoft loses a CVP to AWS and gains one from Alteryx; Lila Bio and BECU name execs
- cloudonaut Monthly - October 2026: Goodbye API Gateway!
- The hostname fight
- Dropbox ditched AWS S3 for its own in-house system. Now it’s buying Tigris to sell S3-compatible storage to AI developers.
- AWS Kiro aims to solve identity crisis by adding another identity: bot orchestrator
- Amazon rewrites its software engineering playbook for an era when AI writes the code
- We are the team behind spend limits in the new AWS experience. AMA!
- Accounts locked out
- AWS installs an AI accelerator every 14 seconds and eyes $1 trillion annual revenue
- Amazon plans its first large-scale data centers in Washington state as residents raise concerns

### The news (9)

- EC2 Amazon Machine Images can now be scanned for vulnerabilities through Amazon Inspector
- AWS Security Hub now provides an SBOM inventory for your compute resources
- IAM Roles Anywhere now supports automatic certificate revocation checking
- AWS WAF announces automatic SDK integration for Amazon CloudFront distributions
- Announcing Web Answer on Amazon Bedrock AgentCore
- Amazon WorkSpaces for AI agents now supports Linux and Windows 11 cloud desktops
- Amazon Bedrock expands API support and introduces Cross-Region Inferencing for OpenAI models in AWS GovCloud (US)
- Amazon SageMaker AI inference now supports GPU partitioning for real-time endpoints
- Introducing India-based inference for Kimi K3 on Amazon Bedrock

The voices you're hearing are AI-generated; the stories come from public sources linked in the show notes.\
Music: Eleven Music.\
An independent project; not affiliated with or endorsed by Amazon Web Services, Y Combinator, Hacker News or any vendor or news outlet mentioned. Opinions are the hosts' own.\
Produced by Roy Osherove.

## Transcript

\[Rachel\] Hi, I'm Rachel, and this is AWS Drama, generated by RobotPaper dot A-I. We start with some drama, then we'll jump into the news. Let's count down the ten messiest AWS stories of the week.

\[Rachel\] Number ten: after more than thirty-three years at Microsoft, a senior executive's next chapter comes in an Amazon box. GeekWire reports that Mazhar Mohammed has left Microsoft to become vice president of AWS Streaming and Messaging. He joined Microsoft straight out of a master's degree program, working as a software design engineer on Windows N-T. His career there went on to cover messaging, mobile services, and partner experience for cloud services. Most recently, he was corporate vice president for the commerce and fraud protection platform. So the move brings someone with both messaging and cloud-partner experience into Amazon's streaming and messaging leadership. The public announcement was much shorter than that career history. GeekWire says Mohammed posted that he was happy to share the news, alongside a photo of an Amazon box and a request for Alexa to play New Beginnings. After more than three decades at one company, the change of employer came with its own soundtrack.

\[Rachel\] Number nine: a software company is breaking up with its gateway, and another database got rejected along the way. In its November second update, cloudonaut describes replacing Amazon API Gateway in the architecture for its virus and malware scanning service. The business now serves more than two hundred customers. Its complaint is concrete: the gateway adds latency and cost, and its request-size and timeout limits get in the way of scanning larger files. The replacement puts an Application Load Balancer in front of Amazon EC2 instances, which handle requests and send asynchronous jobs to a queue. But dropping the gateway also means replacing the usage plans and throttling it previously supplied. The team rebuilt those controls around Amazon ElastiCache for Valkey, with one atomic operation checking authentication, request rates, and monthly quotas. Then came the database reversal. Cloudonaut had praised Amazon Aurora DSQL the previous month and considered making it its default serverless database. For this project, regional availability stopped that plan. The team chose Amazon DynamoDB for subscriptions and A-P-I keys to avoid running into missing Regions during future expansion. The authors report lower request latency from the new design and say support for larger synchronous scans is coming. The production rollout is still planned for the coming weeks. This is a customer's architecture change, with the rollout still ahead, and the gateway already out of the design.

\[Rachel\] Number eight: the new front door arrived with an address people did not want. Amazon ECS Gateway lets platform teams configure networking once, then lets application teams attach their container services. AWS provisions the supporting resources inside the customer's account, and the gateway itself adds no charge beyond those resources. InfoQ reports that the first fight was over the hostname. Each service gets a generated address, while the announcement and documentation do not describe custom-domain support. In the AWS subreddit discussion quoted by InfoQ, one commenter asked how an existing application was supposed to use that address. Another explained why simply adding a domain alias would not solve host-based routing. Then the argument moved from convenience to the bill. InfoQ says the documented design puts twenty-five services on each load balancer. The gateway adds more as they fill, but does not move services between balancers or consolidate partly empty ones. Those remaining balancers still cost money. Some commenters dismissed the feature as a wrapper around existing networking services. Another defended the separation of responsibilities: the platform team defines the network, and application teams deploy against it. That commenter said the test would be whether it removed complexity without taking away too much control. The documentation also warns that changing managed resources outside the gateway can break traffic and later operations. The launch promised less networking work; the discussion immediately became about which networking choices disappeared with it.

\[Rachel\] Number seven: Dropbox left Amazon's storage, and now it wants to sell an alternative. The New Stack reports that Dropbox plans to acquire Tigris for three hundred and fifty million dollars. The deal supports an upcoming service called D-B-X Agent Cloud, starting with object storage for developers building AI applications. The history makes this an awkward reunion with a familiar market. Starting in twenty fifteen, Dropbox moved more than ninety percent of its user data off Amazon S3 and onto its own Magic Pocket infrastructure to improve performance and reduce costs. Now it is buying a company whose product speaks the S3 interface while keeping data accessible across different clouds and computing providers. Tigris automatically places data near where it is needed and charges no fees for transferring data out of its storage service. That pitch goes straight at one of the costs developers encounter when storage sits in one cloud and model computing happens somewhere else. Dropbox tells The New Stack that operating its own infrastructure and selling a developer storage product require different capabilities. Tigris brings a commercial product, an experienced team, customers, and developer relationships. The acquisition still needs the usual approvals. Dropbox has not announced a launch date for Agent Cloud or detailed the technical integration. Existing Tigris customers are being told they will not need to migrate or change their service when the deal closes. The former S3 customer is preparing to compete for S3 customers.

\[Rachel\] Number six: Kiro has another job title, and this time it manages the other agents. AWS launched Kiro Crew bots on Thursday. Each bot can have its own responsibility, instructions, tools, permissions, and memory, while coordinating multiple worker sessions and recurring jobs. The Register framed the launch as another turn in Kiro's identity crisis: an editor, an agentic environment, a workspace, and now a bot orchestrator. Its sharper question was about the bill. If multiple bots keep separate memories and process overlapping context, how much repeated work gets charged? AWS told The Register that all the bots bill through the developer's existing Kiro plan. Their learned memories stay separate intentionally, but they share the workspace, the agent framework, the codebase, and tools, so each bot does not have to rediscover the project structure. InfoWorld found a related concern among analysts. Dave McCarthy of IDC called the extra retries and tool calls a coordination tax that can compound token consumption and computing costs. Stephanie Walter of HyperFrame Research said more background activity does not, by itself, establish higher productivity. She recommended comparing completed work, review time, and operating cost, and checking whether ordinary automation could handle a recurring task more simply. Those are concerns about the design and its use, rather than a reported failure of the new bots. The product promises to take coordination off developers' hands; the analysts are asking what that coordination will cost.

\[Rachel\] Number five: Amazon is rewriting the engineer's job, and token spending is getting an awkward performance review. GeekWire reports that revised internal guidelines emphasize customer outcomes over inputs such as lines of code or AI usage. AWS vice president Marc Brooker says that, for the vast majority of Amazon developers, agents now generate almost all the implementation code they previously wrote by hand. Amazon declined to provide GeekWire the underlying role guidelines. A published accompanying letter acknowledges that usage metrics can correlate with useful results, but says they need careful judgment. That qualification lands against a history of pressure. GeekWire recounts Financial Times reporting that Amazon shut down its KiroRank leaderboard in May after employees used the tool excessively to climb the rankings. Asked whether that episode helped prompt the revised guidelines, Brooker said he did not recall the leaderboard or its details. He also said AI use does not directly determine reviews or promotions through a usage metric, though better performance can matter. The letter calls work that does not benefit from current AI tools a finding rather than a failing, provided the engineer can explain it. GeekWire also revealed Velocity Labs, a roughly thirty-five-person AWS team formed in April to experiment quickly. Brooker says it took a model from concept to public release in less than a week last month. The change in expectations is substantial, but the stated measure is still what the work achieves, rather than how busy the agents look.

\[Rachel\] Number four: AWS finally brought a hard spending cap to the discussion, and longtime customers asked why they were outside the door. The team behind spend limits held an ask-me-anything session on the AWS subreddit on Thursday. Their explanation: a project in the new AWS experience pauses when it reaches its monthly limit, instead of continuing to accrue charges. The replies immediately pressed on what pause actually means. The team said the whole project becomes unavailable, including S3 buckets and database tables. Applications go offline, data transfers stop, and data is retained for ninety days. Raising the limit during that period restores access. This is different from a budget alert that simply sends a warning. Then came the eligibility fight. Existing accounts cannot use these limits yet. The team said support for existing accounts is on the roadmap, without giving a date. One longtime customer said they created a new account specifically for the caps, then faced days of checks while trying to register a domain and deploy a distribution, and ultimately used Cloudflare for delivery. Another commenter called the spending cap a godsend after years of waiting. There are tradeoffs beyond account age. The team said these projects do not support commitments such as Savings Plans or Reserved Instances, and paid third-party software subscriptions are not supported yet. Per-service and per-resource limits are also unavailable. The hard ceiling has arrived, but the thread spent much of its time on who can stand underneath it.

\[Rachel\] Number three: the account was closed, the website was down, and the escalation route became Reddit. A nonprofit administrator posted on the AWS subreddit that its ten-year-old account had been suspended and closed after an organizational change triggered what the author described as a false fraud alert. They said production had been down for five days and years of data had no backup outside the account. There is an important ending: the author updated the post to say AWS reopened the account within twelve hours of the Reddit appeal. They thanked support, then asked why going public appeared necessary. Two other reports fed the same argument. A second nonprofit said suspicious-activity messages had gone to an unmonitored email address, the review window was missed, and attempts to reach chat or phone support failed. An AWS support representative asked for the case number in the thread. Separately, another customer said twenty-seven instances across twelve Regions became unavailable after a declined payment and renewed identity checks, with a deletion warning for November sixth. These are customers' accounts of suspensions and recovery attempts. In the replies, some people demanded paid support for production workloads. Others asked why Basic Support lacked an urgent route for billing and verification problems. One reply described upgrading after partial account access returned and still waiting two more days for recovery. Another pointed to the missing independent backups. The resolved nonprofit case supplies the clearest outcome: the account returned, but the argument over how to reach a human did not end there.

\[Rachel\] Number two: Amazon's trillion-dollar cloud ambition comes with a very large construction bill. Reporting on the earnings call, The Register says Andy Jassy expects AWS to become a trillion-dollar annual business in five to ten years. That is his projection. The current quarterly revenue was just under forty-six billion dollars, up thirty-nine point three percent from a year earlier. Jassy said the company installs an AI accelerator about every fourteen seconds, with customers using capacity almost as quickly as it arrives. He also described Amazon Bedrock as the fastest-growing multibillion-dollar service in AWS history. His argument is that AI demand pulls the rest of the cloud along: customers want inference near their data and applications, while training and agent tools also consume ordinary computing and storage. But expansion is already taking cash. The Register reports an expected two hundred and twenty billion dollars of Amazon capital spending this year, with seventy-five point nine billion spent in the last quarter alone, mostly on AWS. GeekWire's weekly discussion paired the fast cloud growth with Amazon profits that missed expectations as the AI buildout and growing debt weighed on earnings. Jassy's response on the call was that the company can fund the plan and that the opportunity will not conveniently spread itself over twenty-five years. The ambition is measured in a trillion dollars of future revenue. The infrastructure spending is happening now.

\[Rachel\] And number one: Amazon's big data-center expansion has reached its home state, and the neighbors are asking for a pause. GeekWire reports proposed campuses in Walla Walla County and West Richland, with Amazon confirming the West Richland project this week. These would be its first large-scale Washington campuses; the company already operates smaller facilities in the state. Both proposals start with three buildings. West Richland could eventually reach twenty-one on a thousand-acre property near about two hundred homes. Residents asked the council for a temporary moratorium. On Tuesday, the council removed a data-center noise exemption, barred the facilities from light industrial zones, and prohibited cryptocurrency mining, but the moratorium did not pass. Over at Wallula Gap, the scrutiny is also substantial. GeekWire cites a Union-Bulletin analysis finding just twenty-three supportive submissions among seven hundred and six public comments. Most submissions came from outside the county, and many used template language requesting a fuller environmental assessment. Those numbers describe the submissions, rather than a poll of local residents. Amazon says a full West Richland buildout could create more than a thousand permanent jobs. It promises to pay all its property taxes and work with utilities to avoid raising neighbors' electricity bills. GeekWire also notes that annual renewable-energy matching does not mean every facility runs on renewables around the clock, and Amazon's water-use comparisons exclude water used to generate electricity. The next public encounter is an open house on November nineteenth. The expansion has a plan; the neighbors still want answers.

\[Rachel\] And that's the drama. While those campuses face their next public meeting, the services already running inside AWS have news of their own.

\[Rachel\] First up: Amazon Inspector can now scan EC2 machine images for software vulnerabilities before those images launch any instances. There is no need to start a machine or install additional scanning software. The feature supports continuous checks across an image catalog, plus one-time scans of individual images from the EC2 console. Scanning can be enabled for an account or across an organization. Findings also flow into AWS Security Hub, where organization-wide image scanning is available as an add-on. The enforcement side connects those findings to the Allowed A-M-Is setting: administrators can set security criteria and apply them across an organization with Declarative Policies. EC2 Image Builder pipelines can also scan images and restrict distribution when they fail the required standards. AWS says the capability is available in every commercial Region where Inspector is offered.

\[Rachel\] Security Hub also has a new software inventory. It brings together the software bills of materials that Inspector generates for EC2 instances, Amazon Elastic Container Registry images, and AWS Lambda functions. The result is a continuously updated view of installed packages across an organization. Each package entry includes its version, type, and the number of resources that contain it. The list can be filtered and grouped by package attributes, account, and Region. A separate Installed software tab on each resource shows its packages during investigation of a finding. The inventory can also be queried through the Security Hub API. There is no new enablement step: it populates automatically wherever Inspector is enabled. AWS includes it with Security Hub Essentials at no additional cost, in all Regions where Security Hub is available.

\[Rachel\] On identity, AWS Identity and Access Management Roles Anywhere can now check certificate revocation automatically. When the feature is enabled on a trust anchor, the service follows distribution-point addresses embedded in an authenticating certificate, downloads the corresponding revocation lists, and rejects credential requests that use revoked certificates. Previously, administrators had to import those lists and repeat the import whenever the certificate authority published an update. Roles Anywhere now retrieves and refreshes the lists periodically. The feature works with AWS Private Certificate Authority or an organization's existing public key infrastructure. There is a condition: the certificates must include publicly accessible distribution-point addresses that meet the service's requirements. Administrators can enable the setting through the console, software development kits, or command line. AWS says automatic revocation checking is available in all commercial Regions at no additional cost.

\[Rachel\] AWS Web Application Firewall can now add its JavaScript integration automatically through Amazon CloudFront. CloudFront inserts the required script tag into the HTML it serves, without an application-code or deployment change. That client-side code supplies signals for targeted Bot Control, account takeover prevention, and account creation fraud prevention. Previously, teams had to maintain the tag across individual pages and application releases. The setting is available on web access control lists attached to CloudFront that contain at least one of those managed rule groups. The defaults deserve attention: it is enabled for new qualifying lists created in the console, but disabled when those lists are created programmatically. Existing lists remain unchanged. Configuration is supported through the console, command line, development kits, Cloud Development Kit, and CloudFormation. AWS charges no extra fee for the automatic integration.

\[Rachel\] On agents, Amazon Bedrock AgentCore has launched Web Answer in general availability. It is a managed tool that takes a natural-language question and returns a synthesized answer with citations to current web sources in one call. The tool builds on AgentCore Web Search, which launched in June. Web Answer plans searches, runs several in parallel, and decides when it has enough evidence to produce an answer. Builders can constrain that work with domain inclusion and exclusion lists, plus publication-date filters. The tool attaches to an AgentCore Gateway as a target and is called through the Model Context Protocol, with AWS Identity and Access Management authentication. AWS describes the integration as having zero data egress. Web Answer is available in the U S East Region in Northern Virginia, with pricing charged per tool call.

\[Rachel\] Amazon WorkSpaces for AI agents now supports Linux and Windows eleven cloud desktops alongside its existing Windows Server option. The operating-system choice can match the applications and workflows assigned to an agent. Linux desktops give agents full root access for developer work, including builds, tests, and scripts. Windows eleven desktops give them an environment for the enterprise applications that employees already use. AWS says both additions retain the security and governance controls offered with Windows Server desktops. Those include network isolation, access controlled through Identity and Access Management, and the organization's existing compliance boundaries. The announcement frames this as a way to run agents in established working environments without moving the applications to a different platform. It also directs customers to the WorkSpaces agent-access documentation for the setup process and details of operating agents on the service.

\[Rachel\] Also on Bedrock, OpenAI's G-P-T five point six Terra and Luna models now support the Bedrock Runtime endpoint in AWS GovCloud. That includes the Responses, Converse, and Chat Completions A-P-Is. Cross-Region Inference is being added within GovCloud, routing requests across its two U S Regions for greater throughput and redundancy while keeping processing within that geography. The endpoint change also brings these native OpenAI interfaces under the account-level controls used for other Bedrock models. Invocation logs can go to S3 or Amazon CloudWatch Logs. CloudWatch metrics cover invocation and token counts, latency, throttling, and errors. Costs appear by model in AWS Cost Explorer and the Cost and Usage Report. AWS says Cross-Region Inference for OpenAI models is available across the Regions where those models are offered on Bedrock, with model cards listing the applicable details.

\[Rachel\] For model hosting, Amazon SageMaker AI inference now supports graphics-processor partitioning on real-time endpoints. It uses NVIDIA Multi-Instance GPU technology to divide one accelerator into as many as seven isolated partitions, each with its own memory and compute. That allows smaller models, including embedding models, rerankers, classifiers, and fine-tuned models, to share an accelerator. AWS says the hardware isolation prevents a busy model from taking memory or throughput from its neighbors. The partition layout is configured when creating an endpoint that hosts inference components. Models are still invoked by name, so that application interface stays the same. The feature supports P four d, P five, G seven, and G seven e instances. Availability covers seven Regions: Northern Virginia, Ohio, Oregon, and four locations across Asia and Europe. The deployment documentation contains the configuration details.

\[Rachel\] And Bedrock now offers inference within India for Moonshot AI's Kimi K three, a multimodal, open-weight model. The India geographic inference profile limits processing destinations to Mumbai and Hyderabad. It joins the model's existing global and U S options. The profile determines the eligible destination Regions, while Bedrock manages routing between them. AWS says the traffic is encrypted in transit and remains on the AWS network. Its accompanying walkthrough demonstrates extracting information from scanned Hindi documents, then answering questions in mixed Hindi and English. The model can examine the document images directly, without a separate optical character recognition or translation service in that example. Bedrock supports Chat Completions, Responses, Converse, and InvokeModel interfaces for Kimi K three. The blog recommends short-lived credentials where possible and points to the model card for current source-Region and destination-Region availability.

\[Rachel\] Amazon's Washington expansion met local resistance, while the service news brought more security checks and more tools for agents and model hosting. This episode was generated by RobotPaper dot A-I. I'm Rachel. Stay messy, cloud people.

---

The voices you're hearing are AI-generated; the stories come from public sources linked in the show notes. An independent project; not affiliated with or endorsed by Amazon Web Services, Y Combinator, Hacker News or any vendor or news outlet mentioned. Opinions are the hosts' own. Produced by Roy Osherove. Privacy: We count visits to these pages with Cloudflare Web Analytics (cookieless). Google Analytics (which sets cookies): visitors in the EU/EEA, the UK and Switzerland are asked first and it runs only if they accept (we go by the country Cloudflare reports for the connection; if it is unknown, we ask). Elsewhere it loads by default. Anyone can turn it off with the Privacy settings button at the bottom of every page; the choice is kept for a year in this browser (local storage "analytics-consent"). We count feed fetches and downloads in aggregate; IP addresses are hashed and never stored. If you send feedback, we keep what you write (and your email if you give it) to read and reply. © 2026 Roy Osherove.
