CHAPTERS
Session goal: moving Claude Code prototypes into production on AWS
Antonio Rodriguez (AWS) sets the stage for a hands-on session focused on taking local Claude Code prototypes and making them production-ready on AWS. He frames the talk as a practical journey from experimenting on a laptop to deploying securely and reliably in the cloud.
Anthropic + AWS partnership and long-term investment
The speaker explains the multi-year collaboration between Anthropic and AWS and why it’s strategic for both sides. He highlights major investments and commitments that underpin Claude’s availability and scale on AWS infrastructure.
Infrastructure foundations: Project Rainier and Trainium chips
The talk shifts to the compute layer behind Claude on AWS. Antonio describes large-scale infrastructure built for training/hosting and AWS’s purpose-built silicon designed for performance and cost efficiency.
Three technical pillars of using Claude via AWS: features, security, scalability
Antonio outlines the core value propositions for running Claude through AWS: a rich platform layer around models, enterprise-grade security controls, and cloud-scale deployment flexibility. This frames the rest of the session’s product tour.
Amazon Bedrock ecosystem overview: from foundation models to agentic tooling
He gives a broad overview of Bedrock capabilities beyond model access, covering tools that support the full developer lifecycle. The emphasis is on evaluation, optimization, RAG integration, safety controls, and agent building.
Enterprise security & privacy details: sovereignty, PrivateLink, and zero operator access
Antonio drills into why regulated industries can use Claude on AWS confidently. He stresses data sovereignty, private networking, compliance alignment, and operational controls that prevent human access to customer data.
Operational advantages: centralized billing, observability, SLAs, and identity integration
The talk summarizes production operations benefits when consuming Claude via AWS. These include consolidated billing, monitoring/auditing, guaranteed availability, and deep integration with enterprise identity providers.
Three ways to use Claude on AWS (and when to choose each)
Antonio explains the three primary consumption paths for Claude in the AWS ecosystem. He contrasts Bedrock-native model invocation with a gateway approach that preserves Anthropic feature parity, plus desktop options for end users.
Workshop overview: prerequisites, tooling, and Calidraw-based exercises
The session transitions into the practical workshop. Attendees need an AWS account (provided) and Claude Code installed, and they’ll work with the Calidraw repository to learn Claude Code workflows in an applied setting.
Workshop modules: from basics to MCP automation and Git workflows
Antonio walks through module progression based on skill level. Beginner setup steps give way to more advanced workflows involving context management, automated UI actions via Playwright MCP, and Git-based collaboration patterns.
Advanced team/production workshop: standards, governance, cost control, and ROI tracking
He briefly points to an additional advanced workshop geared toward teams shipping to production. The focus is operational governance: standardization, scalable workflows, spend control, and productivity measurement.
Getting access: workshop account login flow and safe-use reminder
Antonio explains how participants join the workshop environment and what they should avoid doing with shared accounts. He describes the hosted development environment experience (terminal + VS Code UI) and acceptable usage expectations.
Alternative setups: run locally or connect Claude Desktop to Bedrock/platform on AWS
For those who prefer not to use the hosted workshop environment, Antonio outlines alternate workflows. Users can run Claude via terminal locally and configure it to point to Bedrock, or connect Claude Desktop to Bedrock/platform on AWS.
Manual configuration tips: region/model selection, token controls, telemetry, and IDE extensions
The talk closes with practical configuration parameters attendees can apply to tailor Claude Code behavior on AWS. He highlights settings for region/model defaults, rate limiting, token optimization, telemetry, and Visual Studio-related tweaks.
