EVERY SPOKEN WORD
20 min read · 3,635 words- SPSpeaker
[upbeat music] Good afternoon, everybody. Let's continue with the agenda. Thank you for joining this session. My name is Antonio Rodriguez. I work, uh, in Amazon Web Services, and I'm also a developer, as many of you, and also a Claude whisperer. As I like to say, we are really just whispering models these days, not really writing code. And, uh, in this session, we are going to be talking about how to take the applications that you are building in Claude Code from prototypes that you might have in your computer to fully production-ready applications that you can have in the cloud, in this case, with Amazon Web Services. And, uh, I think the story that, uh, we are telling today is a story about teamwork, a story about better together. Because, uh, I remember I joined the team and started working, uh, with Anthropic more than three years ago. I remember we were still launching Claude 2 as the big, uh, uh, amazing model that was, uh, you know, changing and shifting the ground, uh, below us. And, um, on-- fr- since then, we have, uh, tried to combine the best frontier models that Anthropic has been developing with the best cloud provider, uh, that we had, uh, in Amazon Web Services. And, uh, this session, by the way, is a hands-on session, so what we are going to do is that I'm going to give you a brief introduction into how do we work together, Anthropic and AWS, and how you can use Claude in AWS in many different ways that we have, uh, available today. And then we are going to give you some accounts in AWS, so that you can, free of charge and with no limitations, test Claude in, in, in Bedrock in this case, and also in, uh, in general in AWS, so that you can see, uh, how to use it. You have, uh, guided instructions and a workshop, and again, we are going to give you an environment so that you can play around with it. So, um, again, this collaboration, uh, started and, uh, has been continued as a very long-term relationship. And, um, we have, uh, proven this year by year. Amazon has invested, uh, it has done a multi-billion investment in Anthropic, uh, because we really believe that we are building the future of AI together. And at the same time, uh, we are the primary cloud provider for Anthropic, and, uh, Anthropic has, uh, committed, uh, more than one hundred, uh, billion on usage in AWS as well in the infrastructure that we are offering for powering the models that you are using every day with Claude. And, um, an example of the-- this investment is Project Rainier. Project Rainier is actually, uh, one of the largest, uh, uh, AI compute, uh, um, infrastructure that was built for training and hosting the Claude models that you are using today with Anthropic. We are also using, uh, custom and purpose-built, uh, chipsets that are specifically made for, uh, the Claude models in the chipsets that we call Trainium. So we have, uh, our third generation of Trainium chipsets already built, uh, by Amazon, so that you can actually get the best speed and also, uh, use it in the most cost-effective way, uh, when you are expending, uh, tokens with, uh, with Claude. And, uh, I think that if we start diving into the technical part of, uh, this collaboration, there are three angles that we basically offer you when you use Claude through AWS. I think the first one is that you have a very comprehensive list of features that you can use, uh, for, let's say, accompanying the model, uh, that you are using. So in Bedrock, you have a full platform, uh, so that you can combine and fine-tune the models as well. Uh, we are the only provider that allows you to fine-tune Haiku, in example, in the cloud. And, uh, we have full integrations with the rest of the features that we have available in Bedrock and the AWS ecosystem in general. The second and very important point is the security. So we can make sure that you keep control of your data at all times. We avoid this hopping of data going to the public internet. You can keep everything private in your AWS boundary. So we make sure that you, uh, always align with the compliance and security, uh, best practices that you might have in your companies or, or the regulations. If you are working in banking or healthcare, uh, these kind of industries is, uh, highly regulated industries, it's very important, uh, that you actually have these options, uh, for controlling everything that you're doing with Claude. And, uh, obviously, the data privacy part, uh, we work, uh, nowadays in the latest generation inference engine that we have in Bedrock. Uh, we have zero operator access, uh, in the platform, which means that no one from Amazon or from Anthropic can actually get access to those instances, so your data remains fully private. We are not sharing that data with anyone. No one is using that data for training models or anything like that. So you keep a full restriction. And again, this is because we need, uh, to align with a lot of compliance regulations that, uh, our customers need. There are hundreds of thousands of customers who are using these models every day, and therefore it's very important for us to align on those. Last but not least, the scalability. The, uh, using those models, Claude models through Bedrock gives you, um, uh, practically infinite in-- scalability in the sense that you can, uh, really decide how do you want to do the deployments. You have full flexibility for choosing regions as well. In example, you could decide that you want to deploy Claude only in London region in AWS or only in the European region, in example, if you have to align with GDPR and, uh, and these kind of regulations. Now, if we see the whole ecosystem... Who, who is familiar with Amazon Bedrock, by the way, in this room?Okay, so I was expecting less hands, uh, to be honest because, uh, this is really, uh, a Claude, uh, uh, event. But, uh, it's great to hear that, uh, you are using Bedrock or you know about Bedrock at least. And Bedrock has been growing, uh, a lot since, uh, the, the beginning, since the last, uh, three or four years when we released the service. And, uh, today, apart from the core, which is obviously the foundation models that you have access to, and obviously, uh, Anthropic cloud models are a very important point-- part of that. You also have other features that help you in the full journey as a developer. So you have a feature that help you doing evaluation, that help you doing prompt optimization, uh, that help you fine-tuning the models as we mentioned before or, uh, doing model distillation as well if you need it. We also give you some features that help you connecting. If you have rack use cases, you can have knowledge bases that are fully managed so that you can attach to it as well. We have, uh, guardrails, which is a way in which you can apply content filters. You can deny topics. Uh, you can, uh, protect, uh, PII data or sensitive data by doing automatic masking, and so on. And, uh, you can also control hallucinations from the models by doing, uh, proper grounding, automated reasoning checks. And, uh, m- even more important in the last, uh, two years, I would say, tools for building with agentic AI. And, uh, this, uh... I-if you are using Claude agents, then awesome. But if you are using the Claude Agent SDK, and you are looking for an infrastructure for hosting your agents in a secure way in the cloud, then you can also use Amazon Bedrock Agent Core, which is, uh, again, fully compatible with any open framework that you might be using for agentic AI today, like LangChain, like Groq AI, and obviously Claude Agent S-SDK as well. Now, if I have to summarize in a single slide everything that I'm saying so far on the why the better together story, why is it better to, uh, use Claude in AWS, I would say this is probably the slide, right? So first of all, as I mentioned, the data sovereignty that you can get when you are using Claude in AWS. You have, uh, full control of the environment that you are setting up and where you are using it. You also have centralized billing from AWS, so you can actually have a single bill. If your companies are already using AWS or you are using AWS for other things, you can have a, a consolidated, a single bill that is ha- actually having the usage of Claude included with everything else that you might be u- doing today. You have full observability through our services like CloudWatch or CloudTrail as well, in which, uh, you can actually see details of metrics, logs. Uh, you can see the traces o-of everything that has happened. And, uh, we also offer SLAs. So, uh, we make sure that you have a guarantee availability on the services, so you have an uptime that is, uh, secure for your applications, and you can go, uh, safe to production and make sure that you can scale at the, at the cloud scale, uh, safely. Um, another very important point is that we have built-in auth integration. So if you are using single sign-on, or if you are doing au- uh, Open Authorization OAuth, or if you are using IAM roles in AWS, an example, um, you can directly integrate that with your identity provider. You could be using Microsoft Entra ID. You could be using Okta. You could be using any of those, uh, identity providers today, and that is a built-in integration that you can do also for using Claude in Bedrock. And, uh, last point, you can use PrivateLink, which means that all the communication can remain fully private, so, uh, you make sure that no data is being sent to the public internet at any point, uh, when you are using Claude in Bedrock in there. As I mentioned, I mentioned about compliance before. These are some of the, uh, compliance regulations that we, uh, support, and we are, uh, good for you to use as well, like an example, FedRAMP, HIPAA, and so on and so forth. There is a full list online if you want to check it out and, uh, and more information about all of these topics. Now, the good news is that today you have three ways of using Claude in, uh, AWS. And actually, this is, uh, the, the most options that you are going to find in the whole industry right now with-- First one is you can use Claude models directly through Amazon Bedrock, as I mentioned before. So basically, everything that I was saying so far in which you have the same, uh, high cost on it, Opus experience that you might be getting, uh, directly, but in this case, uh, fully through the Amazon Bedrock, uh, APIs that are offered to you. We have, uh, recently added Opus four dot seven and included the Messages API as well, so that you can directly invoke with the Messages API if that's a method that you prefer. Now, we have also recently launched Claude platform in A- on AWS. Claude platform on AWS is actually generally available since a few days ago, and this allows you to have the same exact experience that you might be using today directly with Anthropic. But in this case, with a consolidated billing through AWS and having the access control fully done on AWS as well. We act as a gateway in this case, and we send all the inference requests to Anthropic so that they can process the request for you. So it's giving you the best of both worlds. So you get, again, the security, the billing, the consolidated access control that we are giving in AWS. And at the same time, you have all the feature parity with Anthropic, including everything that we have been hearing in this event and the latest features that, uh, you might be using today, including web search, files, agents, and, uh, so on and so forth. Now, the third, uh, way in which, uh, you can use it is also if you are not using programmatically Claude, but you are rather using Claude Desktop. So you might be using CoWork, you might be using, uh, Claude Code through the Claude Desktop application.You can also use it directly from AWS, and again, you can pay in a consolidated bill in AWS. Uh, and, uh, you have two ways of, of, uh, doing that as well. One is through the Claude Enterprise in, uh, in the AWS Marketplace, in which you, uh, pretty much subscribe to the number of developers that you, uh, have using this application as well. But you now also have the option of using it, uh, on, um, let's say point directly, uh, the cohort three P, which is, uh, one of the latest additions also that the Anthropic team did for ex- uh, connecting Claude Desktop to third parties. In this case, you can connect Claude Desktop to Bedrock, or you can connect even Claude Desktop to the cloud platform on AWS if you prefer to do so. So again, you have all sort of combinations to make your life easier and, uh, pretty much meet you where you are on your needs on this. Perfect. Let's dive into the actual workshop that we are going to be building together. Um, I just want to, uh, make a recap that, first of all, you need two prerequisites for running this workshop. One is you need an AWS account, so that's-- we got you covered. We are going to give you, again, a workshop account that has, uh, an environment that you can play around with and, uh, you can pretty much, uh, be, uh, free of charge, uh, free of any concern of using that environment. And then the other thing is that you obviously need to have Claude Code installed, uh, as an application. And, uh, we have a few options for you. So if, uh, the folks on the back help me switch into my laptop, I can show you what is exactly what we are doing. Um, you are going to find that in the accounts that we are setting up for you, we are having the workshop that is called Introduction to Claude Code on AWS. And, uh, this workshop has some instructions to how to set up everything that we are doing. We are pretty much, uh, playing around with this Calidraw, uh, tool, with the repository of Calidraw, so you can see how Claude Code can help you playing around with Calidraw and drawing architecture diagrams for you, an example. Um, this is a basic workshop is if you are already an advanced user. So who, who is, uh, getting started with Claude Code in this room? All right. Who would say that is a ninja in Claude Code? So you are-- You have all the skills on Claude Code. Who is in the middle? All right. [laughs] Who's not answering? So, um, yeah, I guess most of the room is probably in the middle. So you will find that probably module one is basic for you, so it's, uh, just using Claude Code on AWS and learning how to set it up and, uh, point to Calidraw and so on. Uh, module two and module three are probably more interesting for you. We are going to start, uh, playing with the context. We are going to start using Playwright MCP so we can actually, uh, take screenshots of the diagram that we are drawing and, uh, making, uh, modific- automated modifications through Claude Code on it. We are also playing around with, uh, uh, Gi- the Git workflows on, on Claude Code, and so on. And in the module three, we are going to play with sub-agents and plugins, and we are also creating custom skills, hooks, and some advanced, uh, parameters for configuration. I just want to mention that we have an even more advanced, uh, workshop that is also available for you if you look for this URL. And, um, basically there you have all the things that are very interesting for teams who wants to move to production in a safe way. So here you can learn how to set up, uh, team standards, how to implement and, and distribute, uh, advanced workflows as well, how to do a scalability, cost control, and so on. So an example, you could see, um, how to set up dashboards like this one for making sure that you can control all the use that you are doing of, uh, Claude Code tokens, uh, in your accounts and so on and so forth. Developer productivity measurements, uh, measuring return of investment of your applications, and so on. And last, you have also options for using, uh, the Claude Agent SDK on the Amazon, uh, Bedrock Agent Corp, so you can learn how to build the agents connected to the Claude infrastructure, uh, that we have, uh, here in, in AWS as well. But coming back to our workshop, again, uh, you have, uh, different ways of, uh, doing it. You will see that at the very beginning, you will, uh, see a screen that looks like this with some terms and conditions. I just want to remind everybody that those are workshop accounts. It's, uh, individual for you, but make sure that you don't upload confidential information, personal information, or anything like that. You will have to agree to the terms and conditions and click on the Join Event. And from that point on, uh, you are going to see pretty much this experience that you have in the instructions here, where you're actually going to have, uh, an environment fully deployed for you. And, uh, you will see a URL here that will take you to a terminal and, uh, uh, pretty much a Visual Studio Code UI where you can actually work on all the instructions that we are doing in the workshop. Let's say that you don't want to follow this path and you want to do it in your own machine. Then you can do it. You can use, uh, Claude directly in a terminal. If you prefer, you can configure it for pointing to Bedrock, uh, with instructions that we are giving you in the workshop. Let's say that you want to use Cowork, uh, or, or the Claude Desktop app. Uh, you can do it as well. Again, here I'm pointing to my Bedrock account. So I have, uh, Claude Desktop pointing to Bedrock and, uh, here I'm doing this Calidraw, uh, application and the, and the workshop that we have for you, uh, over there as well. And, uh, there is more information. At the end, we are going to be sharing with you, uh, more on, uh, a guidance and example for how to use Claude Code and Cowork on Amazon Bedrock. There is a full blog from my colleagues, uh, who is, uh, covering all of this in detail, and so on and so forth. All right, let's go back to the slides, uh, please on the back. Thank you. Perfect. So, um, the instructions for accessing the accounts are very easy. All you have to do is go to join.workshop.aws, and you have to input that access code that you see on the screen. I think my colleagues, uh, have been around. Uh, over there you have the two, uh, solutions architects from AWS who can help you with questions. If you have any questions, just raise your hand and we can get, uh, close and we can help you out. We also have been handing over some, uh, pieces of paper that has this information so that you can get it, uh, easier for copy and paste it in, in your, uh, laptops. Um, one last comment, uh, with regards to advanced configurations. If you want to use, uh, things like an example, uh, s- configuring the settings that you are using in Claude Code manually, um, this is the kind of, uh, parameters that you will need to set up. You might take a picture now, uh, if you want. So the- here is how to set up, uh, the region, point it to Bedrock, choose the default model, and so on and so forth. And then on the right-hand side, you also have, uh, some parameters for reducing the token usage or doing rate limiting and, uh, how to enable auto-reporting for telemetry and, uh, things like that. You also have some information here about, uh, uh, how to configure extensions in the case that you're using Visual Studio. Uh, but again, it is all about asking Claude to configure itself, or you can do it manually if you prefer through the extensions that we have there. It helps you with some things like an example, disable the login prompt that is, uh, a bit annoying e-every time that you start, or things like, uh, uh, hiding the onboarding, uh, message that you're always getting in Claude Code and, and so on and so forth. [upbeat music]
Episode duration: 19:41
Install uListen for AI-powered chat & search across the full episode — Get Full Transcript
Transcript of episode 5YHIrTYxM3w
