We are pleased to announce general availability of Amazon EC2 P6-B200 instances in AWS US East (N. Virginia) on SageMaker Studio notebooks.

Amazon EC2 P6-B200 instances are powered by 8 NVIDIA Blackwell GPUs with 1440 GB of high-bandwidth GPU memory and 5th Generation Intel Xeon processors (Emerald Rapids). These instances deliver up to 2x better performance compared to P5en instances for AI training. Customers can use P6-B200 instances to interactively develop and fine-tune large foundation models, including LLMs, mixture of experts models, and multi-modal reasoning models. These instances enable efficient experimentation with larger models directly in JupyterLab or CodeEditor environments for generative AI applications such as enterprise copilots and content generation across text, images, and video.

Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.

​We are pleased to announce general availability of Amazon EC2 P6-B200 instances in AWS US East (N. Virginia) on SageMaker Studio notebooks.
Amazon EC2 P6-B200 instances are powered by 8 NVIDIA Blackwell GPUs with 1440 GB of high-bandwidth GPU memory and 5th Generation Intel Xeon processors (Emerald Rapids). These instances deliver up to 2x better performance compared to P5en instances for AI training. Customers can use P6-B200 instances to interactively develop and fine-tune large foundation models, including LLMs, mixture of experts models, and multi-modal reasoning models. These instances enable efficient experimentation with larger models directly in JupyterLab or CodeEditor environments for generative AI applications such as enterprise copilots and content generation across text, images, and video.
Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.  

Elastic Network Adapter (ENA) Express now supports traffic between Amazon EC2 instances in different Availability Zones within a Region, delivering up to 25 Gbps single-flow bandwidth. ENA Express is a networking feature that uses the AWS Scalable Reliable Datagram (SRD) protocol to improve network performance. SRD is a reliable network protocol that delivers performance improvements through advanced congestion control and multi-pathing. Amazon Elastic Block Store (EBS) io2 Block Express and Elastic Fabric Adapter (EFA) for high performance computing and machine learning workloads also leverage SRD.

Workloads such as distributed storage, databases, and file systems require deployments spanning multiple Availability Zones for resilience, yet single flows between zones support up to 5 Gbps with ENA. ENA Express delivers up to 25 Gbps single-flow bandwidth for traffic between Availability Zones. To achieve this, ENA Express detects compatibility between your EC2 instances and establishes an SRD connection when both communicating instances have ENA Express enabled. Once established, SRD uses multi-pathing to route your traffic across the network and avoids head-of-line blocking as it does not need packets to arrive in order. Using these capabilities, ENA Express delivers the performance benefits transparently to your application with TCP and UDP protocols.

ENA Express for connections between Availability Zones within a Region is available for all supported instance types and sizes in Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, New Zealand, Osaka, Seoul, Singapore, Sydney, Taipei, Thailand, Tokyo), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), US East (N. Virginia, Ohio), US West (N. California, Oregon), and AWS GovCloud (US) Regions. ENA Express comes at no additional cost. For a list of supported instances and configuration guidance, please review the latest EC2 documentation.

​Elastic Network Adapter (ENA) Express now supports traffic between Amazon EC2 instances in different Availability Zones within a Region, delivering up to 25 Gbps single-flow bandwidth. ENA Express is a networking feature that uses the AWS Scalable Reliable Datagram (SRD) protocol to improve network performance. SRD is a reliable network protocol that delivers performance improvements through advanced congestion control and multi-pathing. Amazon Elastic Block Store (EBS) io2 Block Express and Elastic Fabric Adapter (EFA) for high performance computing and machine learning workloads also leverage SRD.
Workloads such as distributed storage, databases, and file systems require deployments spanning multiple Availability Zones for resilience, yet single flows between zones support up to 5 Gbps with ENA. ENA Express delivers up to 25 Gbps single-flow bandwidth for traffic between Availability Zones. To achieve this, ENA Express detects compatibility between your EC2 instances and establishes an SRD connection when both communicating instances have ENA Express enabled. Once established, SRD uses multi-pathing to route your traffic across the network and avoids head-of-line blocking as it does not need packets to arrive in order. Using these capabilities, ENA Express delivers the performance benefits transparently to your application with TCP and UDP protocols.
ENA Express for connections between Availability Zones within a Region is available for all supported instance types and sizes in Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, New Zealand, Osaka, Seoul, Singapore, Sydney, Taipei, Thailand, Tokyo), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), US East (N. Virginia, Ohio), US West (N. California, Oregon), and AWS GovCloud (US) Regions. ENA Express comes at no additional cost. For a list of supported instances and configuration guidance, please review the latest EC2 documentation.  

We are pleased to announce general availability of Amazon EC2 G6e instances in the Middle East (Dubai), Asia Pacific (Tokyo, Seoul) and Europe (Frankfurt, Stockholm, Spain) on SageMaker Studio notebooks.

Amazon EC2 G6e instances are powered by up to 8 NVIDIA L40s Tensor Core GPUs with 48 GB of memory per GPU and third generation AMD EPYC processors. G6e instances deliver up to 2.5x better performance compared to EC2 G5 instances. Customers can use G6e instances to interactively test model deployment and for interactive model training use cases such as generative AI fine-tuning. You can use G6e instances to deploy large language models (LLMs) with up to 13B parameters and diffusion models for generating images, video, and audio.

Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.

​We are pleased to announce general availability of Amazon EC2 G6e instances in the Middle East (Dubai), Asia Pacific (Tokyo, Seoul) and Europe (Frankfurt, Stockholm, Spain) on SageMaker Studio notebooks.
Amazon EC2 G6e instances are powered by up to 8 NVIDIA L40s Tensor Core GPUs with 48 GB of memory per GPU and third generation AMD EPYC processors. G6e instances deliver up to 2.5x better performance compared to EC2 G5 instances. Customers can use G6e instances to interactively test model deployment and for interactive model training use cases such as generative AI fine-tuning. You can use G6e instances to deploy large language models (LLMs) with up to 13B parameters and diffusion models for generating images, video, and audio.
Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.  

We are pleased to announce general availability of Amazon EC2 P4de instances in Asia Pacific (Tokyo, Singapore) and Europe (Frankfurt) on SageMaker Studio notebooks.

Amazon EC2 P4de instances are powered by 8 NVIDIA A100 GPUs with 80GB high-performance HBM2e GPU memory, 2X higher than the GPUs in our current P4d instances. The new P4de instances provide a total of 640GB of GPU memory, which provide up to 60% better ML training performance along with 20% lower cost to train when compared to P4d instances. The improved performance will allow customers to reduce model training times and accelerate time to market. Increased GPU memory on P4de will also benefit workloads that need to train on large datasets of high-resolution data.

Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.

​We are pleased to announce general availability of Amazon EC2 P4de instances in Asia Pacific (Tokyo, Singapore) and Europe (Frankfurt) on SageMaker Studio notebooks. Amazon EC2 P4de instances are powered by 8 NVIDIA A100 GPUs with 80GB high-performance HBM2e GPU memory, 2X higher than the GPUs in our current P4d instances. The new P4de instances provide a total of 640GB of GPU memory, which provide up to 60% better ML training performance along with 20% lower cost to train when compared to P4d instances. The improved performance will allow customers to reduce model training times and accelerate time to market. Increased GPU memory on P4de will also benefit workloads that need to train on large datasets of high-resolution data. Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.  

We are pleased to announce general availability of Amazon EC2 G6 instances in the Middle East (Dubai) and Asia Pacific (Malaysia) on SageMaker Studio notebooks.

Amazon EC2 G6 instances are powered by up to 8 NVIDIA L4 Tensor Core GPUs with 24 GB of memory per GPU and third generation AMD EPYC processors. G6 instances offer 2x better performance for deep learning inference compared to EC2 G4dn instances. Customers can use G6 instances to interactively test model deployment and for interactive model training for use cases such as generative AI fine-tuning and inference workloads, natural language processing, language translation, computer vision, and recommender engines.

Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.

​We are pleased to announce general availability of Amazon EC2 G6 instances in the Middle East (Dubai) and Asia Pacific (Malaysia) on SageMaker Studio notebooks.
Amazon EC2 G6 instances are powered by up to 8 NVIDIA L4 Tensor Core GPUs with 24 GB of memory per GPU and third generation AMD EPYC processors. G6 instances offer 2x better performance for deep learning inference compared to EC2 G4dn instances. Customers can use G6 instances to interactively test model deployment and for interactive model training for use cases such as generative AI fine-tuning and inference workloads, natural language processing, language translation, computer vision, and recommender engines.
Visit developer guides for instructions on setting up and using JupyterLab and CodeEditor applications on SageMaker Studio. For pricing information on these instances, please visit our pricing page.  

Amazon Aurora DSQL single-Region clusters are now available in Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Singapore), Europe (Stockholm), and South America (Sao Paulo). Aurora DSQL is the fastest serverless, distributed SQL database that enables you to build always available applications with virtually unlimited scalability, the highest availability, and zero infrastructure management. It is designed to make scaling and resilience effortless for your applications and offers the fastest distributed SQL reads and writes.

With this launch, Aurora DSQL is available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), Canada West (Calgary), Asia Pacific (Hong Kong), Asia Pacific (Melbourne), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Singapore), Asia Pacific (Sydney), , Asia Pacific (Tokyo), Asia Pacific (Seoul), Europe (Ireland), Europe (London), Europe (Frankfurt), Europe (Paris), Europe (Stockholm), and South America (Sao Paulo).

Get started with Aurora DSQL for free with the AWS Free Tier. To learn more, visit the Aurora DSQL webpage and documentation.

​Amazon Aurora DSQL single-Region clusters are now available in Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Singapore), Europe (Stockholm), and South America (Sao Paulo). Aurora DSQL is the fastest serverless, distributed SQL database that enables you to build always available applications with virtually unlimited scalability, the highest availability, and zero infrastructure management. It is designed to make scaling and resilience effortless for your applications and offers the fastest distributed SQL reads and writes. With this launch, Aurora DSQL is available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), Canada West (Calgary), Asia Pacific (Hong Kong), Asia Pacific (Melbourne), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Singapore), Asia Pacific (Sydney), , Asia Pacific (Tokyo), Asia Pacific (Seoul), Europe (Ireland), Europe (London), Europe (Frankfurt), Europe (Paris), Europe (Stockholm), and South America (Sao Paulo). Get started with Aurora DSQL for free with the AWS Free Tier. To learn more, visit the Aurora DSQL webpage and documentation.  

AWS HealthOmics now supports caching completed task outputs of cancelled runs, enabling customers to reuse outputs and avoid recomputing previously completed tasks. When caching is enabled and a run is cancelled, HealthOmics automatically stores completed task outputs in the customer’s S3 bucket, allowing customers to restart runs from the point of cancellation. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs at scale with fully managed bioinformatics workflows.

Caching of cancelled runs helps researchers, bioinformaticians, and workflow developers debug and iteratively develop workflows efficiently by storing intermediate files and completed task outputs for inspection. This saves customers the cost of recomputing completed tasks that may have taken hours and accelerates subsequent runs by executing only the remaining incomplete tasks.

Caching cancelled runs is now available for Nextflow, WDL, and CWL runs in all AWS HealthOmics regions: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), and Asia Pacific (Singapore, Seoul). To learn more, visit the workflow cache documentation. 

​AWS HealthOmics now supports caching completed task outputs of cancelled runs, enabling customers to reuse outputs and avoid recomputing previously completed tasks. When caching is enabled and a run is cancelled, HealthOmics automatically stores completed task outputs in the customer’s S3 bucket, allowing customers to restart runs from the point of cancellation. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs at scale with fully managed bioinformatics workflows.
Caching of cancelled runs helps researchers, bioinformaticians, and workflow developers debug and iteratively develop workflows efficiently by storing intermediate files and completed task outputs for inspection. This saves customers the cost of recomputing completed tasks that may have taken hours and accelerates subsequent runs by executing only the remaining incomplete tasks.
Caching cancelled runs is now available for Nextflow, WDL, and CWL runs in all AWS HealthOmics regions: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), and Asia Pacific (Singapore, Seoul). To learn more, visit the workflow cache documentation.   

• Categoría: Noticias de Microsoft

mayo 11, 2026

Día Mundial de la Clave de Acceso: Avanzar la autenticación sin contraseña

Por: Vasu Jakkal y Nadim Abdo.

El Día Mundial de la Clave de Acceso (World Passkey Day) es una oportunidad para reflexionar sobre los avances hacia un objetivo común: reducir nuestra dependencia de las contraseñas y otros métodos de autenticación de phishing a través de acelerar la adopción de las claves de acceso. A medida que los ciberataques se vuelven más automatizados e impulsados por IA, cada cuenta solo es tan segura como su credencial más débil. El progreso real requiere más que añadir opciones de inicio de sesión más sólidas: requiere eliminar credenciales que puedan ser objetivo de phishing y fortalecer rutas de ataque comunes como los flujos de recuperación. En colaboración con la FIDO Alliance, Microsoft está comprometida a promover la adopción de claves de acceso mediante un trabajo continuo de estándares, una participación activa en grupos de trabajo y otras contribuciones a un futuro sin contraseña.

Exploren las soluciones de identidad y acceso de Microsoft Entra

Las contraseñas siguen como una fuente importante de riesgo; son difíciles de gestionar y fáciles de robar. Junto con formas más débiles de autenticación multifactor, también son muy vulnerables al phishing: las campañas impulsadas por IA pueden aumentar la tasa de clics de hasta el 54%.¹ En respuesta, Microsoft amplía la adopción de claves de acceso en todo nuestro ecosistema. Reducimos la dependencia de la autenticación heredada y reforzamos la recuperación de cuentas para que no se convierta en una puerta trasera para los ciberatacantes.

«En lugar de secretos vulnerables o información personal que, en potencia, puede ser identificable, una clave de acceso utiliza una clave privada almacenada de manera segura en el dispositivo del usuario. Solo funciona en la web o aplicación para la que el usuario lo creó, y solo si ese mismo usuario lo desbloquea con sus biométricos o PIN. Esto significa que los usuarios con clave de acceso no pueden ser engañados para iniciar sesión en un sitio web malicioso que se asemeje al original, y una clave de acceso es inutilizable a menos que el usuario esté presente y consiente. Estas son algunas de las cualidades que hacen que las claves de acceso sean una forma de autenticación ‘resistente al phishing’.»

Del informe de defensa digital de Microsoft.

La adopción de claves de acceso continúa su crecimiento en toda la industria

La adopción de claves de acceso se acelera: la Alianza FIDO estima que ya hay 5.000 millones de claves de acceso en uso en todo el mundo.² En los servicios de consumo de Microsoft, incluidos OneDrive, Xbox y Copilot, cientos de millones de usuarios inician sesión con llaves de acceso cada día.

Hay muchas razones para elegir las claves de acceso como método estándar de autenticación en lugar de las contraseñas. Las tasas de éxito en iniciar sesión son mayores que con contraseñas, y la exposición a ataques basados en credenciales es menor.³ Tanto las organizaciones como los usuarios particulares prefieren la experiencia de inicio de sesión más sencilla y segura que ofrecen las claves de acceso.⁴

Dentro de Microsoft, hemos eliminado métodos de autenticación más débiles y hemos implementado la autenticación resistente al phishing, para cubrir al 99,6% de los usuarios y dispositivos de nuestro entorno.⁵ Ha hecho que iniciar sesión sea mucho más sencillo: sin códigos para introducir, sin indicaciones extra que gestionar, solo una experiencia sencilla para todos.

Actualizaciones del producto durante el inicio de sesión y la recuperación

En Microsoft, hemos integrado poco a poco y de manera constante, el soporte de claves de acceso en cada capa de la experiencia de identidad, desde cuentas de consumo hasta acceso empresarial con Microsoft Entra, y desde la autenticación basada en dispositivos como Windows Hello hasta el gestor de contraseñas de Microsoft. Este trabajo garantiza que las personas puedan crear y usar claves de acceso donde inicien sesión, con una experiencia coherente y resistente al phishing en dispositivos, aplicaciones y entornos.

Para hacer que las claves de acceso sean más accesibles, ampliamos dónde y cómo pueden usarlas las personas:

• Las claves de acceso sincronizadas y los perfiles de clave de acceso en Microsoft Entra ID facilitan escalar el inicio de sesión sin contraseña en entornos diversos. Ampliamos la flexibilidad en la gestión de claves de acceso en la nube, incluido el soporte para políticas más grandes y complejas, y la transición de los inquilinos a un modelo unificado de perfil de claves de acceso.
• Las claves de acceso Entra en Windows facilitan que los usuarios creen y utilicen claves vinculadas a dispositivos directo en dispositivos Windows personales o no gestionados por medio de Windows Hello, y estarán disponibles en general a finales de mayo de 2026.
• Las claves de acceso para Microsoft Entra External ID estarán disponibles a nivel general a finales de mayo de 2026, para que sus aplicaciones orientadas al cliente puedan ofrecer una experiencia de inicio de sesión más fluida y de nivel consumidor.
• La autenticación por clave de acceso preferida en Microsoft Entra ID (vista previa) detecta los métodos registrados y solicita primero el más fuerte. Si se registra una clave, eso es lo que el usuario ve—de inmediato. 
• En el lado del consumidor, con Microsoft Password Manager, los usuarios pueden ahora guardar y sincronizar las claves de acceso entre dispositivos conectados con su cuenta de Microsoft, y pronto se desplegará soporte para iOS y Android a través de Microsoft Edge.

La recuperación de cuentas también desempeña un papel fundamental en el mantenimiento de la integridad de los sistemas de identidad. A nivel histórico, han sido vulnerables a ciberatacantes que intentan secuestrar el proceso de recuperación, por ejemplo, haciéndose pasar por usuarios legítimos y solicitar nuevas credenciales.

La recuperación de cuentas Microsoft Entra ID, disponible a nivel general hoy en día, refuerza la seguridad de los flujos de recuperación al permitir a los usuarios recuperar el acceso a sus cuentas mediante un proceso robusto de verificación de identidad. Los usuarios pueden recuperar el acceso tras perder todos los métodos de autenticación por medio de comprobaciones de identificación y biometrías emitidas por el gobierno. En disponibilidad general, ampliamos nuestro ecosistema de verificación de identidad con dos nuevos socios—1Kosmos y CLEAR1—uniéndose a nuestros socios actuales Au10tix, IDEMIA y TrueCredential.

Eliminación de credenciales phishing de las cuentas de usuario

Fortalecer la autenticación es importante, pero reducir el riesgo significa eliminar por completo las credenciales de phishing. Microsoft sigue con la eliminación de los métodos heredados y orienta a los usuarios hacia una autenticación resistente al phishing. A partir de enero de 2027, las preguntas de seguridad se eliminarán como opción de restablecimiento de contraseña en el ID de Microsoft Entra debido a su susceptibilidad a la conjetura y la ingeniería social.

La lógica es sencilla: mejorar los métodos fuertes mientras elimina los débiles reduce la superficie de ataque. Esto es cada vez más urgente a medida que los agentes de IA actúan en nombre de los usuarios. Si una identidad se ve comprometida, los ciberatacantes pueden aprovechar esos agentes para acceder a sistemas, ejecutar flujos de trabajo y operar dentro de los permisos existentes. Las organizaciones deben abordar este riesgo con rapidez.

Un futuro más seguro y utilizable

El año pasado, Microsoft se unió a decenas de organizaciones en la toma del Compromiso Passkey (Passkey Pledge), un compromiso para acelerar la adopción de la autenticación resistente al phishing y para ir más allá de las contraseñas. Desde entonces, hemos visto avances significativos, desde cientos de millones de cuentas de consumo mejor protegidas hasta despliegues a gran escala en organizaciones como la nuestra.

Lo que antes parecía un cambio a largo plazo por fin ha comenzado a ganar impulso real: la autenticación se vuelve más sencilla, segura y sin contraseña.

Para una perspectiva más profunda sobre cómo los ciberatacantes intentan eludir la autenticación mediante métodos de respaldo y procesos de recuperación—y cómo abordar esas lagunas—lean nuestra publicación complementaria.

Primeros pasos

Las organizaciones que deseen fortalecer su postura de seguridad de identidad pueden habilitar claves de acceso para sus usuarios y ampliar las protecciones de políticas tanto en escenarios de inicio de sesión como de recuperación.

Comiencen con un despliegue de autenticación sin contraseña resistente al phishing en Microsoft Entra ID.

Las personas pueden crear y usar llaves de acceso para sus cuentas personales para mayor seguridad y comodidad.

Descubran más sobre Microsoft Entra

Para saber más sobre las soluciones de seguridad de Microsoft, visiten nuestra página web. Guarden el blog de Security en sus Favoritos para estar al día con nuestra cobertura experta sobre temas de seguridad. Además, síganos en LinkedIn (Microsoft Security) y X (@MSFTSecurity) para las últimas noticias y actualizaciones sobre ciberseguridad.

¹Informe de Defensa Digital de Microsoft 2025.

²FIDO Alliance informa sobre el uso global generalizado en el Día Mundial de la Clave de Acceso. FIDO Alliance, 2026.

³Claves de acceso sincronizadas y recuperación de cuentas de alta garantía, blog de Microsoft Entra. 16 de diciembre de 2025.

⁴Defensores de la Alianza FIDO en la adopción generalizada de claves de acceso y un futuro sin contraseña en el Día Mundial de las Claves Electrónicas 2025, FIDO News Center. 1 de mayo de 2025.

⁵Informe de progreso de la Iniciativa de Seguridad y Futuro de Microsoft (SFI)—noviembre de 2025.

Etiquetas:

• Seguridad

The post Día Mundial de la Clave de Acceso: Avanzar la autenticación sin contraseña appeared first on Source LATAM.

​The post Día Mundial de la Clave de Acceso: Avanzar la autenticación sin contraseña appeared first on Source LATAM.  

Today, AWS announced the general availability of Claude Platform on AWS, a new service that gives customers direct access to Anthropic’s native Claude Platform experience through their existing AWS account. AWS is the first cloud provider to offer access to the native Claude Platform experience. Developers and organizations now have the choice to access Anthropic’s native Claude Platform experience, including APIs, console, and early-access beta features, directly through their existing AWS account, without managing separate accounts, billing, or tracking.

Claude Platform on AWS is operated by Anthropic, and customer data is processed outside the AWS security boundary. Claude Platform on AWS is designed for development teams and enterprises that want access to Anthropic’s native Claude Platform development experience and do not have specific regional data residency requirements. Customers still use existing IAM credentials and access controls, consolidated AWS billing, and CloudTrail audit logging for full security visibility. Features available through Claude Platform on AWS include Claude Managed Agents (beta), advisor strategy (beta), web search, web fetch, code execution, files API (beta), Skills (beta), MCP connector (beta), prompt caching, citations, batch processing, and the Claude Console for prompt development and evaluation. 

Claude Platform on AWS is available in US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), South America (São Paulo), Europe (Dublin), Europe (London), Europe (Frankfurt), Europe (Milan), Europe (Zurich), Europe (Paris), Europe (Stockholm), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Parcific (Melborune), Asia, Pacific (Jakarta), Asia Pacific (Sydney), and Asia Pacific (Melbourne). To learn more, visit the Claude Platform on AWS product page. To get started, see the Claude Platform on AWS documentation.

​Today, AWS announced the general availability of Claude Platform on AWS, a new service that gives customers direct access to Anthropic’s native Claude Platform experience through their existing AWS account. AWS is the first cloud provider to offer access to the native Claude Platform experience. Developers and organizations now have the choice to access Anthropic’s native Claude Platform experience, including APIs, console, and early-access beta features, directly through their existing AWS account, without managing separate accounts, billing, or tracking.
Claude Platform on AWS is operated by Anthropic, and customer data is processed outside the AWS security boundary. Claude Platform on AWS is designed for development teams and enterprises that want access to Anthropic’s native Claude Platform development experience and do not have specific regional data residency requirements. Customers still use existing IAM credentials and access controls, consolidated AWS billing, and CloudTrail audit logging for full security visibility. Features available through Claude Platform on AWS include Claude Managed Agents (beta), advisor strategy (beta), web search, web fetch, code execution, files API (beta), Skills (beta), MCP connector (beta), prompt caching, citations, batch processing, and the Claude Console for prompt development and evaluation. 
Claude Platform on AWS is available in US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), South America (São Paulo), Europe (Dublin), Europe (London), Europe (Frankfurt), Europe (Milan), Europe (Zurich), Europe (Paris), Europe (Stockholm), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Parcific (Melborune), Asia, Pacific (Jakarta), Asia Pacific (Sydney), and Asia Pacific (Melbourne). To learn more, visit the Claude Platform on AWS product page. To get started, see the Claude Platform on AWS documentation.  

AWS Transform now supports replatforming applications to containers during migration to AWS. This release extends AWS Transform’s agentic AI capabilities to automate the containerization of your source code, enabling you to migrate and modernize in parallel, reducing the time and complexity of moving from on-premises to cloud-native architectures. Migration teams can containerize source code from GitHub, Bitbucket, GitLab, or .zip files, generate Docker images, publish to Amazon Elastic Container Registry (Amazon ECR), and deploy to Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). This brings containerization into the same workflow your team uses to plan and execute rehost migrations.

AWS Transform analyzes your source code repositories, generates Dockerfiles, and builds container images with integrated security scanning for common vulnerabilities and exposures (CVEs). It produces deployment-ready Terraform infrastructure-as-code and Helm charts for your target environment. The service supports monolithic repositories (monorepos) and multi-repo structures, private dependency resolution through AWS CodeArtifact, and containerization of thousands of applications at scale. During migration wave planning, you can assign applications to either a rehost or replatform-to-containers path, so you can move and realize the benefits of AWS faster.

This new capability is available in all AWS Regions where AWS Transform is offered.

To learn more, please visit the AWS Transform User Guide.

​AWS Transform now supports replatforming applications to containers during migration to AWS. This release extends AWS Transform’s agentic AI capabilities to automate the containerization of your source code, enabling you to migrate and modernize in parallel, reducing the time and complexity of moving from on-premises to cloud-native architectures. Migration teams can containerize source code from GitHub, Bitbucket, GitLab, or .zip files, generate Docker images, publish to Amazon Elastic Container Registry (Amazon ECR), and deploy to Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). This brings containerization into the same workflow your team uses to plan and execute rehost migrations. AWS Transform analyzes your source code repositories, generates Dockerfiles, and builds container images with integrated security scanning for common vulnerabilities and exposures (CVEs). It produces deployment-ready Terraform infrastructure-as-code and Helm charts for your target environment. The service supports monolithic repositories (monorepos) and multi-repo structures, private dependency resolution through AWS CodeArtifact, and containerization of thousands of applications at scale. During migration wave planning, you can assign applications to either a rehost or replatform-to-containers path, so you can move and realize the benefits of AWS faster. This new capability is available in all AWS Regions where AWS Transform is offered.
To learn more, please visit the AWS Transform User Guide.