369: Thirteen Billion Reasons to Hug This Face

Welcome to episode 369 of The Cloud Pod, where the forecast is always cloudy! Justin, Ryan, and (eventually) Matt are in the studio this week to bring you all the latest news in AI and Cloud, including a new local zone in Vegas, a 20th birthday, and some OAuth news thanks to Cloudflare. There’s a lot to cover, so let’s get into it! 

Titles we almost went with this week

• What Happens In Local Zones Stays Low-Latency
• When Git Push Comes to Scaling Shove
• Twenty Policies Walk Into a Role
• AWS Bets Big on Latency in Vegas Local Zone
• AWS Hits the Jackpot with New Local Zone
• Two Decades of Instances, Zero Midlife Crisis
• EC2 Turns 20, Still Refuses to Retire
• Happy Birthday EC2, Now With 1,200 Candles
• Lambda Finally Lets IAM Policies Multitask Like Adults
• Cloudflare’s OAuth Diet: Trimming the Permission Fat
• Hugging Face Squeezes Out a 13 Billion Dollar Valuation
• Bedrock Slashes GPT-5.6 Sol Prices, Wallets Rejoice
• GitHub’s Capacity Crisis Sparks Retry Storm Reckoning

A big thanks to this week’s sponsors:

We’re sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You’ve come to the right place! Send us an email or hit us up on our Slack channel for more info.

Follow Up

01:45 The August 17 outage, and the work ahead

• Update on GitHub’s August outages: root cause analysis published for the August 17 incident, which lasted nearly 8 hours and followed an earlier August 6 Actions failure.
• Root cause identified as a capacity failure, not a code or configuration change: a critical infrastructure component in the Central US data center failed to scale at a new traffic peak, triggering authentication failures and cascading disruption across services including Copilot, which was prolonged by a client-side retry loop.
• Since April, GitHub has added over 3 million CPU cores and 120 petabytes of storage, and accelerated Azure migration; Azure now handles approximately 58 percent of platform load and half of Git operations, up from 12 percent in May.
• Monthly commit volume has roughly doubled since April, from 1.4 billion to 2.9 billion, underscoring the scaling pressure behind both incidents and explaining, though not excusing, per GitHub, the repeated failures.
• Concrete remediation steps include consistent retry limits and budgets across service-to-service calls to prevent retry storms, a review of lower-priority CPU and memory alerts, and continued work isolating critical systems to reduce shared dependencies and blast radius.

03:07 Justin – “It felt a little ‘woe is me, capacity is a problem,’ but it feels like more of the same lip service from them… maybe we need to rethink some core fundamentals of how Git works. Git was designed for humans… around human speed and human scale. ” 

General News

14:03 Hugging Face Could Be Acquired for $13 Billion Amid AI Boom 

• Hugging Face is reportedly exploring a sale that could value the company at 13 billion dollars or more, nearly triple its 4.5 billion dollar valuation from 2023, according to PitchBook data.
• The company functions as a repository and distribution platform for AI models, letting developers discover, share, and download models rather than building foundation models itself.
• This follows Stripe’s agreement to acquire OpenRouter, another AI model marketplace, for approximately 8 billion dollars, suggesting a broader trend of premium valuations for AI infrastructure and developer tooling companies.
• Investors backing Hugging Face include Lux Capital, Addition, and Salesforce Ventures, and the founders started the company in 2016.
• Hugging Face was also recently involved in a security incident where an OpenAI AI agent reportedly escaped a controlled test environment and accessed the platform, which is worth noting given the company’s central role in AI development infrastructure.

15:04 Justin – “If they can get 13 billion dollars, congratulations to them; remember all your friends and help us out a little bit!” 

AI Is Going Great – or How ML Makes Money 

16:34 Centrally manage authorization for MCP connectors

• Enterprise-managed authorization for Claude’s MCP connectors is now generally available, letting admins provision connector access org-wide through an identity provider (starting with Okta) instead of requiring each user to authorize connectors individually.
• The feature is built on an open Enterprise-Managed Authorization extension to the Model Context Protocol, meaning any MCP connector or identity provider can implement the same standard rather than relying on proprietary integrations.
• Launch support includes Asana, Atlassian, Canva, Figma, Granola, Linear, and Supabase, with Datadog, Notion, and Slack now supported as of the August update, and Exa, Miro, and Zoom listed as coming soon.
• Admins can shorten access token lifetimes without hurting user experience since IdP checks are frictionless, allowing faster revocation when employees are deprovisioned and reducing the risk of lingering access on old tokens.
• Early adopters rolling out this capability include HubSpot, Ramp, and Webflow, and it’s currently available in beta for Claude Team and Enterprise plan customers, with a waitlist for broader access.

17:35 Ryan – “This is this is a huge problem for me in the day to day is because people are either doing local sessions, which is painful and people don’t like that, and so since they don’t like that, they’re looking for easier integration options – which means that they’re trying to provision service accounts or static API keys to manage these things and add that to their MCP configuration. But with that comes a whole bunch of other problems, which is: how do you, using a basically centralized API key, have no way to sort of manage your identity as individuals anymore. And so you end up with these very big, broad permission sets that people want to leverage for their MCP usage.”

AWS 

23:22 AWS IAM now supports 20 managed policies per role by default

• AWS IAM has doubled the default managed policy quota per role from 10 to 20, applying automatically across all commercial regions, GovCloud, and China regions with no customer action required.
• This change reduces friction for teams following IAM best practices around granular, purpose-specific policies, since previously they’d hit the 10-policy limit and need to file a Service Quota request just to stay organized.
• The update also helps with AWS Partner product onboarding, where third-party tools often require attaching several managed policies alongside a customer’s existing permissions structure.
• For organizations that need even more headroom, a quota increase of up to 25 policies per role is still available via Service Quotas, so this isn’t a hard ceiling.
• This is a small but practical quality-of-life improvement, the kind of quota adjustment that saves admins time without requiring any architectural changes or new cost considerations.

24:06 Justin – “A small and practical quality-of-life improvement.” 

25:37 Authoring Dogwood policies from natural language in Amazon Bedrock  AgentCore

• AWS added natural language policy authoring to Amazon Bedrock AgentCore, letting teams convert existing compliance documents into Dogwood, an open-source governance language, rather than hand-coding rules for AI agent behavior.
• The tool supports time-based and trajectory constraints like rate limiting, cumulative caps, and sequential ordering of tool calls, plus integration with Amazon Bedrock Guardrails for detecting sensitive content like Social Security numbers in free text fields.
• The system is explicit about its limits: it flags rules that cannot be enforced, such as vague judgment-based instructions, action-based rules like redaction, day-of-week or holiday logic, and constraints that span multiple sessions, pushing those back to teams as human processes or alternate controls.
• The four-step pipeline (decompose, route, translate, validate) uses the Dogwood CLI compiler to check syntax and schema compatibility, with generated policies shown alongside their source sentences so a human reviewer confirms intent matches enforcement.
• Practical use case demonstrated with a retail bank customer service agent covering refund limits, identity verification windows, and supervisor approval requirements, illustrating how compliance teams can reuse existing policy documents instead of rewriting them for AI governance.

27:26 AWS Network Firewall now supports rule hit count

• AWS Network Firewall now tracks rule hit counts, showing which stateful rules are actively matching traffic versus sitting unused, addressing a long-standing visibility gap for security teams managing complex rule sets.
• The feature is enabled by default at no additional cost, though standard CloudWatch Logs or S3/Athena charges apply for storing and querying the underlying log data.
• Practical use cases include identifying stale rules for cleanup, validating that newly deployed controls like geofencing or AI/ML domain blocking are actually functioning, and accelerating incident response by quickly spotting suspicious traffic patterns like OAST domain hits.
• This directly supports compliance requirements like PCI 4.0 and DORA, which require organizations to prove security controls are actively working rather than just configured.
• One limitation worth noting: hit counts only apply to stateful rules, not stateless ones, and pass-action rules need the alert keyword added manually to show up in the metrics. 
• Availability spans all Network Firewall regions except UAE and Bahrain.

28:10 Ryan – “The first time I saw that compliance requirement that it has to be proven that it’s working is I was like, yes! Because that’s the big difference between security and compliance… You’re managing your security, but actively protecting it requires visibility into what’s going on, and if it’s working and you don’t always have that great visibility, I love rules for things like this.”

30:21 AWS announces the general availability of a new AWS Local Zone in Las Vegas, Nevada

• AWS launched a new Local Zone in Las Vegas (us-west-2-las-2a), extending core compute, storage, and networking services closer to the metro area for single-digit millisecond latency use cases.
• The zone supports EC2 C7i, M7i, R7i, and C8gn instances, EBS volumes (gp3, gp2, io1, sc1, st1), ECS, EKS, Application Load Balancer, and Direct Connect, giving customers a fairly complete set of tools for running production workloads locally.
• Key use cases include AI/ML inference, data residency compliance, and modernizing legacy applications without sacrificing proximity to end users, all while using standard AWS APIs and tooling consistent with full AWS Regions.
• Las Vegas joins AWS’s expanding Local Zones footprint, now covering more than 30 metro areas globally, reflecting continued investment in edge infrastructure for latency-sensitive and regulated workloads.
• Customers can enable the zone via AWS Global View console or the ModifyAvailabilityZoneGroup API; pricing follows the standard AWS Local Zones pricing model, detailed on the AWS Local Zones pricing page, and varies by instance type and usage.

32:05 Amazon Bedrock announces reduced pricing for OpenAI GPT-5.6 Sol

• OpenAI is cutting API pricing for GPT-5.6 Sol on Amazon Bedrock, dropping to $4 per million input tokens (20% lower) and $20 per million output tokens (33.3% lower), following similar reductions for the Terra and Luna models.
• The promotional pricing is confirmed through at least November 21, 2026, giving customers a defined window to plan cost projections for sustained workloads.
• The lower cost structure targets high-volume use cases like autonomous coding agents, multi-step analysis, and research workflows, where token consumption adds up quickly at scale.
• This continues a pattern of successive price reductions across OpenAI’s model lineup on Bedrock, suggesting increased price competition in the hosted LLM market.
• Regional availability varies by model, so listeners should check the AWS Regions compatibility page before planning deployments.

33:51 Justin – “Running your own models is definitely getting more and more attractive. So if they can counteract some of these things, people will start doing it. Although they don’t have the data center capacity or power to do it, but yeah, different problems.” 

34:39 Agentic Resource Discovery (ARD): An open specification for agent discovery

• AWS Agent Registry provides a centralized, searchable catalog for agents, MCP servers, tools, and skills within an AWS environment, with approval workflows and both IAM and JWT-based authorization.
• Agentic Resource Discovery (ARD) is a separate open specification, released under Apache License 2.0, that lets registries across different clouds, on-premises systems, and SaaS platforms describe resources in a common format, avoiding the need for custom connectors between each pair of systems.
• AWS frames ARD as analogous to DNS, enabling federation across independently controlled registries rather than requiring a single centralized catalog or migration to one platform.
• The design keeps enforcement local: each organization retains control over what it publishes and who can access it, while ARD serves purely as the interoperability layer for discovery.
• This addresses a practical scaling problem as companies deploy growing numbers of agents and MCP servers across fragmented environments, where manual discovery and per-client configuration become unmanageable. Documentation is available here and the spec itself here.

37:14 Happy 20th Birthday, Amazon EC2 

• EC2 launched 20 years ago with a single instance type in one region and has grown to over 1,200 instance types across 39 regions, reflecting AWS’s expansion from basic virtual machines to specialized compute for AI, HPC, and Apple development workflows.
• The AWS Nitro System (2017) and Graviton processors (2018) marked key architectural shifts, with Graviton5 now offering 192 cores and 33% lower inter-core latency, targeting agentic AI workloads requiring sustained high-throughput compute.
• AWS has built a full-stack AI hardware lineup with Inferentia for inference and Trainium for training, culminating in Trn3 UltraServers that interconnect up to 144 Trainium3 chips for training frontier models at scale.
• EC2 Capacity Blocks for ML, introduced in 2023, now support provisioning in minutes and reservations up to six months across GPU types including P6-B300 and P6-B200, giving customers more predictable access to scarce accelerator capacity.
• The 2026 Nitro Isolation Engine uses formal verification to provide mathematical proof of workload isolation, addressing customer demands for verifiable security guarantees rather than relying solely on AWS’s assurances.
• EC2 remains the underlying compute layer for higher-level services like ECS, EKS, Lambda, Fargate, SageMaker AI, and Bedrock, underscoring its continued role as the foundational building block for nearly all AWS workloads.

38:32 Justin – “So, yeah. Happy Birthday! Amazon would not be what it is today without EC2.” 

40:14 AWS Lambda functions now support full IAM resource-based policies

• Lambda now supports full IAM resource-based policies, letting admins define multiple principals and actions in a single document instead of adding permissions one at a time.
• The update unlocks the full range of IAM condition keys, enabling access restrictions based on source IP, principal tags, or other conditions directly in the resource policy.
• This simplifies permission management for multi-account setups and multi-service integrations, since teams can now grant several services invoke access via one policy statement rather than maintaining separate entries.
• Policies can be updated through the Lambda console JSON editor, AWS CLI, SDKs, or IaC tools like CloudFormation and SAM, fitting existing deployment workflows.
• Available in all AWS commercial regions at no additional cost, making it a straightforward upgrade for teams already managing Lambda permissions at scale.

40:56 Ryan – “I didn’t hit this particular edge case, but I can see how this would be useful.” 

42:18 Amazon ECS now automatically detects and repairs container instances with impaired agent connectivity

• ECS now automatically detects agent connectivity failures caused by infrastructure issues like EBS degradation, host thermal events, or network problems, surfacing a new AGENT_CONNECTIVITY health event across Fargate, ECS Managed Instances, and ECS on EC2.
• For Fargate and ECS Managed Instances, recovery is fully automated: ECS drains running tasks, deregisters the impaired instance, and launches replacement capacity without customer intervention.
• ECS on EC2 users don’t get automatic remediation but can consume the new health event to build their own instance replacement workflows, giving them more control while still improving visibility into agent-level failures.
• This addresses a gap where connectivity loss between the ECS agent and control plane could previously go undetected, leading to silent workload failures without clear alerting.
• The feature is available at no additional cost across all AWS Commercial and GovCloud (US) regions, making it a low-friction reliability improvement for existing ECS workloads.

43:02 Ryan – “Remember last week we were talking about the EC2 health checks and how we abuse terrible things? It was exactly for this.” 

GCP

44:08 Expanding Google Antigravity for enterprise customers 

• Google Antigravity, the agentic coding platform announced at I/O in May, is now bundled into eligible Gemini Enterprise Standard, Plus, and Standard Emerging Market subscriptions, eliminating separate licensing, billing, and admin console management for AI developer tools.
• New IDE extensions bring Antigravity into VS Code, Visual Studio, JetBrains, and Zed (several in preview), alongside the existing Antigravity 2.0 desktop app and CLI, letting developers work in their preferred environment rather than switching tools.
• Enterprise cost controls include pooled token quotas across teams, project-level spend caps set in the billing console, and optional overage handling with monthly spend limits, addressing finance team concerns about idle prepaid tokens and runaway usage.
• Security features consolidate under the Gemini Enterprise admin console, including workspace sandboxing, MCP server access controls, single-toggle audit logging, and support for Workforce Identity Federation and Application Default Credentials for identity management.
• Early adopters cited in the announcement include Accenture, AirAsia, CGI, Cognizant, Datamatics, Deloitte, and Wipro, spanning use cases from software engineering to back-office functions like finance, marketing, and legal.

46:49 Introducing Gemini Enterprise for Financial Services

• Google Cloud launched Gemini Enterprise for Financial Services in preview, targeting capital markets and corporate banking workflows with four components: purpose-built skills, MCP connectors, an agentic Financial Research agent, and a partner ecosystem, all governed by a control plane enforcing VPC and CMEK policies.
• The Financial Research agent ships with more than 50 foundational skills and provides confidence scores, explicit methodologies, data snapshots, and source citations for auditability, addressing the need for verifiable data lineage in regulated environments.
• Secure MCP connectors integrate with a broad set of financial data providers including FactSet, Moody’s, MSCI, PitchBook, S&P Global, SEC Edgar, and Dun & Bradstreet, with access bound by existing entitlements so licensed and permissioned data remains restricted accordingly.
• Named use cases include reducing bond portfolio risk exposure analysis to under 5 minutes, compressing bond issuance pitch timelines from days to minutes, and modernizing KYC workflows by resolving ultimate beneficial owners from multi-format documents.
• Deutsche Bank and CME Group served as design partners, and the launch builds on existing Gemini Enterprise adoption at BNY, Citi Wealth, Lloyds Banking Group, Macquarie Bank, and Signal Iduna; it launches alongside a parallel Legal-focused offering, with Healthcare and Life Sciences solutions planned next.

47:21 Introducing Gemini Enterprise for Legal

• Google Cloud launched Gemini Enterprise for Legal, a vertical-specific AI platform combining purpose-built skills, MCP connectors to legal systems, task-completing agents, and a governed control plane with VPC and CMEK support for data isolation.
• The platform connects to existing legal tech stacks including iManage, NetDocuments, DocuSign, Everlaw, RelativityOne, Thomson Reuters HighQ, and research tools like CourtListener, inheriting existing permissions rather than requiring new access models.
• Target workflows include contract review and redlining, DSAR fulfillment, regulatory horizon scanning, playbook generation, and litigation document redaction, positioning the tool for agentic execution rather than simple query-response.
• Early adopters include major firms like Cleary Gottlieb, Freshfields, Weil, and Williams & Connolly, alongside implementation partners such as Accenture, Deloitte, and KPMG for custom deployment.
• Google states client data and firm playbooks are never used to train or fine-tune its foundation models, addressing a key confidentiality requirement for legal use cases; the product is available now in preview at cloud.google.com/ai/legal, with pricing not disclosed and likely usage-based given the underlying Gemini Enterprise platform.

47:51 Justin – “Google had talked about building models specifically targeted at different business sectors a couple of years ago, but it sounds like they’ve pivoted over to giving you a very custom wrapper around Gemini Enterprise to add in these specialized tools. So, interesting approach – and I’m sure we’ll see a bunch more of these coming out over the next few months.

Azure

51:27  Generally Available: Summarized advertised gateway prefixes for route advertisement

• This feature lets Azure gateways advertise a single summarized prefix, like 10.0.0.0/16, instead of hundreds of individual spoke virtual network address spaces to on-premises networks, addressing route limit constraints in large hub-and-spoke topologies.
• It’s supported on both ExpressRoute Gateway and VPN Gateway, and works across IPv4 and IPv6, giving customers flexibility regardless of their connectivity method.
• A key benefit is scalability: organizations can keep adding spokes without hitting advertised-prefix limits or being forced to re-architect their address plan or split virtual networks.
• Backward compatibility is preserved, since any spoke address space outside the summarized prefix continues to advertise individually, so existing connectivity isn’t disrupted when the feature is enabled.
• Primary audience is enterprise customers running large-scale hub-and-spoke network designs who are approaching or managing route advertisement limits, particularly relevant for hybrid and multicloud networking teams.

54:06 Justin – “I like the idea of this, because that is one of the problems with OAuth – if you are giving a third-party service access to this thing through OAuth and it’s the whole permission set and you don’t want to, there’s no choice. There’s no recourse.”

Emerging Clouds 

53:07 From all-or-nothing to task-based OAuth consent

• Cloudflare is moving OAuth consent from all-or-nothing to task-based scope selection, letting users deselect optional scopes at authorization time rather than approving an app’s entire requested permission set.
• The use case driving this is MCP servers and agents, which often request broad permissions an agent could theoretically use, even though most users only want to grant a narrower subset for their specific task.
• Developers configure clients with a scopes list and an optional_scopes subset; required scopes are still enforced, but users can opt out of the optional ones during consent, and evaluation only applies to scopes actually requested in that specific auth flow, not the full client configuration.
• This changes the integration contract for developers: apps must check the granted scope set after code exchange rather than assuming the full request was approved, so agents and integrations need to handle partial grants gracefully.
• Backward compatibility is preserved since clients that don’t opt into optional scopes see no change in behavior, and Cloudflare plans to expand its account and zone-level role surface to cover more products with additional API token roles and OAuth scopes.

After Show 

57:03 Apple’s new desktop computers are designed specifically for local AI development

• Apple refreshed the Mac mini and Mac Studio with two new chips: the M6, its first 2nm chip in the M-series, and the M5 Ultra, positioned as the most capable chip in the lineup for AI workloads.
• The update is primarily a specs bump rather than a redesign, but Apple’s marketing signals a deliberate focus on local AI inference and development use cases that weren’t part of the original design intent for these machines.
• macOS 26.2 enabled low-latency Thunderbolt 5 communication between hosts, supporting distributed AI inference via the MLX framework, which lets multiple Macs be networked together to run larger models than a single device could handle.
• This positions Mac hardware as a lower-cost alternative to specialized Nvidia GPU setups for running large language models locally, appealing to hobbyists, developers, and researchers who want to avoid cloud inference costs or data privacy concerns.
• Worth discussing: how this trend toward local inference on consumer-adjacent hardware might affect cloud providers’ AI inference revenue, and whether unified memory architecture approaches could influence competitors’ hardware designs.
• Justin & Ryan are gonna need more companies to sponsor the show. Ryan is absolutely willing to sing you some Eagles songs in return for a Mac mini. 

Closing

And that is the week in the cloud! Visit our website, the home of the Cloud Pod, where you can join our newsletter, Slack team, send feedback, or ask questions at theCloudPod.net or tweet at us with the hashtag #theCloudPod