Today, AWS announces that the AWS MCP Server (preview) now publishes operational metrics to Amazon CloudWatch and introduces scalable Agent SOPs discovery using semantic similarity. Agent SOPs are pre-built, tested workflows that guide AI assistants through complex multi-step AWS tasks. These updates give you visibility into your MCP Server usage and provide a guided path for your agents to perform tasks on AWS.
Previously, customers were unable to monitor changes done through agents using AWS MCP server to track usage patterns, identify permission issues, and set up alarms on errors. With this update, the AWS MCP Server now automatically publishes metrics under the AWS-MCP namespace in CloudWatch at no additional cost. You can monitor invocation counts, success rates, client errors, server errors, and throttling for individual tools such as the AWS API caller (call_aws) and the Agent SOP retriever (retrieve_agent_sop). These metrics help you track usage patterns, identify permission issues, and set up alarms when error rates exceed your thresholds. Additionally, the documentation search tool (search_documentation) now uses semantic similarity to return relevant Agent SOPs alongside AWS documentation results, allowing AI assistants to discover the right SOP through natural language queries.
The AWS MCP Server is available in preview in the US East (N. Virginia) AWS Region at no additional cost.
To get started on AWS MCP server, please read documentation here.
Today, AWS announces that the AWS MCP Server (preview) now publishes operational metrics to Amazon CloudWatch and introduces scalable Agent SOPs discovery using semantic similarity. Agent SOPs are pre-built, tested workflows that guide AI assistants through complex multi-step AWS tasks. These updates give you visibility into your MCP Server usage and provide a guided path for your agents to perform tasks on AWS. Previously, customers were unable to monitor changes done through agents using AWS MCP server to track usage patterns, identify permission issues, and set up alarms on errors. With this update, the AWS MCP Server now automatically publishes metrics under the AWS-MCP namespace in CloudWatch at no additional cost. You can monitor invocation counts, success rates, client errors, server errors, and throttling for individual tools such as the AWS API caller (call_aws) and the Agent SOP retriever (retrieve_agent_sop). These metrics help you track usage patterns, identify permission issues, and set up alarms when error rates exceed your thresholds. Additionally, the documentation search tool (search_documentation) now uses semantic similarity to return relevant Agent SOPs alongside AWS documentation results, allowing AI assistants to discover the right SOP through natural language queries. The AWS MCP Server is available in preview in the US East (N. Virginia) AWS Region at no additional cost. To get started on AWS MCP server, please read documentation here.
Amazon Bedrock AgentCore Runtime now supports WebRTC for real-time bidirectional streaming between clients and agents, adding to the existing WebSocket protocol support. With WebRTC, developers can build voice agents for browser and mobile applications that stream audio and video bidirectionally with low latency using peer-to-peer, UDP-based transport, enabling natural, real-time conversational experiences.
WebRTC joins WebSocket as the second bidirectional streaming protocol supported by AgentCore Runtime. While WebSocket provides persistent, full-duplex connections for text and audio streaming over TCP, WebRTC is optimized for real-time media delivery where low latency is critical, such as voice agents in browser and mobile applications. WebRTC requires a TURN relay for media traffic, and AgentCore Runtime gives you flexibility in how you set that up: Amazon Kinesis Video Streams managed TURN for a fully managed experience with native AWS IAM integration, a third-party provider, or your own self-hosted TURN infrastructure. Both protocols benefit from AgentCore Runtime session isolation, observability, and scaling.
WebRTC is supported in AgentCore Runtime across fourteen AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Canada (Central), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), and Europe (Stockholm).
Amazon Bedrock AgentCore Runtime now supports WebRTC for real-time bidirectional streaming between clients and agents, adding to the existing WebSocket protocol support. With WebRTC, developers can build voice agents for browser and mobile applications that stream audio and video bidirectionally with low latency using peer-to-peer, UDP-based transport, enabling natural, real-time conversational experiences.
WebRTC joins WebSocket as the second bidirectional streaming protocol supported by AgentCore Runtime. While WebSocket provides persistent, full-duplex connections for text and audio streaming over TCP, WebRTC is optimized for real-time media delivery where low latency is critical, such as voice agents in browser and mobile applications. WebRTC requires a TURN relay for media traffic, and AgentCore Runtime gives you flexibility in how you set that up: Amazon Kinesis Video Streams managed TURN for a fully managed experience with native AWS IAM integration, a third-party provider, or your own self-hosted TURN infrastructure. Both protocols benefit from AgentCore Runtime session isolation, observability, and scaling.
WebRTC is supported in AgentCore Runtime across fourteen AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Canada (Central), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), and Europe (Stockholm).
To get started, see Bidirectional streaming in the Amazon Bedrock AgentCore documentation, which includes ready-to-deploy examples for both protocols: an Amazon Nova Sonic voice agent with KVS TURN server, Pipecat voice agents with WebSocket, WebRTC, and Daily transport, a LiveKit voice agent, and a Strands Agents SDK voice agent.
Amazon Elastic Kubernetes Service (Amazon EKS) now offers a 99.99% Service Level Agreement (SLA) for clusters running on Provisioned Control Plane, up from the 99.95% SLA offered on standard control plane. Amazon EKS is also introducing the 8XL scaling tier, the largest available Provisioned Control Plane tier.
Provisioned Control Plane gives you the ability to select your cluster’s control plane capacity from a set of well-defined scaling tiers, ensuring the control plane is pre-provisioned and ready to handle traffic spikes or unpredictable bursts. The higher 99.99% SLA is measured in 1-minute intervals, providing a more granular and stringent availability commitment for mission-critical workloads. The new 8XL tier offers double the Kubernetes API server request processing capacity of the next lower 4XL tier, enabling workloads such as ultra-scale AI/ML training, high-performance computing (HPC), and large-scale data processing.
Amazon Elastic Kubernetes Service (Amazon EKS) now offers a 99.99% Service Level Agreement (SLA) for clusters running on Provisioned Control Plane, up from the 99.95% SLA offered on standard control plane. Amazon EKS is also introducing the 8XL scaling tier, the largest available Provisioned Control Plane tier. Provisioned Control Plane gives you the ability to select your cluster’s control plane capacity from a set of well-defined scaling tiers, ensuring the control plane is pre-provisioned and ready to handle traffic spikes or unpredictable bursts. The higher 99.99% SLA is measured in 1-minute intervals, providing a more granular and stringent availability commitment for mission-critical workloads. The new 8XL tier offers double the Kubernetes API server request processing capacity of the next lower 4XL tier, enabling workloads such as ultra-scale AI/ML training, high-performance computing (HPC), and large-scale data processing. Both the 99.99% SLA and the 8XL tier are available today in all AWS regions where Amazon EKS Provisioned Control Plane is offered. To learn more about the SLA, see the Amazon EKS Service Level Agreement. For 8XL pricing and capabilities, see the EKS pricing and EKS Provisioned Control Plane documentation.
AWS Firewall Manager announces that it is now available in AWS Asia Pacific (New Zealand) Region. AWS Firewall Manager helps cloud security administrators and site reliability engineers protect applications while reducing the operational overhead of manually configuring and managing rules.
Working with AWS Firewall Manager, customers can provide defense in depth policies to address the full range of AWS security services for customers hosting their applications and workloads in AWS Taipei. Customers wishing to establish secured assets using AWS WAF can create and maintain security policies with AWS Firewall Manager.
To learn more about how AWS Firewall Manager works, see the AWS Firewall Manager documentation for more details and the AWS Region Table for the list of regions where AWS Firewall Manager is currently available. To learn more about AWS Firewall Manager, its features, and its pricing, visit the AWS Firewall Manager website.
AWS Firewall Manager announces that it is now available in AWS Asia Pacific (New Zealand) Region. AWS Firewall Manager helps cloud security administrators and site reliability engineers protect applications while reducing the operational overhead of manually configuring and managing rules. Working with AWS Firewall Manager, customers can provide defense in depth policies to address the full range of AWS security services for customers hosting their applications and workloads in AWS Taipei. Customers wishing to establish secured assets using AWS WAF can create and maintain security policies with AWS Firewall Manager. To learn more about how AWS Firewall Manager works, see the AWS Firewall Manager documentation for more details and the AWS Region Table for the list of regions where AWS Firewall Manager is currently available. To learn more about AWS Firewall Manager, its features, and its pricing, visit the AWS Firewall Manager website.
AWS DataSync now supports AWS Secrets Manager for credential management across all location types, including Hadoop Distributed File System (HDFS), Amazon FSx for Windows File Server, and Amazon FSx for NetApp ONTAP. Previously, Secrets Manager integration was limited to a subset of location types, requiring you to provide credentials directly through the DataSync API or console.
You can centralize credential management for all DataSync locations in Secrets Manager, providing a single, consistent approach across all your data transfers. You can also encrypt credentials with your own AWS KMS key instead of the default AWS-owned key, helping you meet your organization’s security requirements and governance policies. All secrets are stored in your account, allowing you to update credentials as needed, independent of the DataSync service.
DataSync supports two approaches for credential management. You can provide a secret ARN referencing credentials you manage in Secrets Manager for full control over rotation, auditing, and access policies. Alternatively, DataSync can automatically create and manage secrets on your behalf.
This capability is available is available in the majority of AWS regions where AWS DataSync is offered. For the full list of supported regions, visit the AWS Capabilities tool in Builder Center. To get started, visit the AWS DataSync console. For more information, see Managing credentials with AWS Secrets Manager in the AWS DataSync documentation.
AWS DataSync now supports AWS Secrets Manager for credential management across all location types, including Hadoop Distributed File System (HDFS), Amazon FSx for Windows File Server, and Amazon FSx for NetApp ONTAP. Previously, Secrets Manager integration was limited to a subset of location types, requiring you to provide credentials directly through the DataSync API or console.
You can centralize credential management for all DataSync locations in Secrets Manager, providing a single, consistent approach across all your data transfers. You can also encrypt credentials with your own AWS KMS key instead of the default AWS-owned key, helping you meet your organization’s security requirements and governance policies. All secrets are stored in your account, allowing you to update credentials as needed, independent of the DataSync service.
DataSync supports two approaches for credential management. You can provide a secret ARN referencing credentials you manage in Secrets Manager for full control over rotation, auditing, and access policies. Alternatively, DataSync can automatically create and manage secrets on your behalf.
This capability is available is available in the majority of AWS regions where AWS DataSync is offered. For the full list of supported regions, visit the AWS Capabilities tool in Builder Center. To get started, visit the AWS DataSync console. For more information, see Managing credentials with AWS Secrets Manager in the AWS DataSync documentation.
AWS announces the Neuron Dynamic Resource Allocation (DRA) driver for Amazon Elastic Kubernetes Service (EKS), bringing Kubernetes-native hardware-aware scheduling to AWS Trainium-based instances. The Neuron DRA driver publishes rich device attributes directly to the Kubernetes scheduler, enabling topology-aware placement decisions without custom scheduler extensions.
Deploying AI workloads on Kubernetes requires ML engineers to make infrastructure decisions that are not directly related to model development, such as determining device counts, understanding hardware and network topologies, and writing accelerator-specific manifests. This creates friction, slows iteration, and tightly couples workloads to underlying infrastructure. As use cases expand to distributed training, long-context inference, and disaggregated architectures, this complexity becomes a scaling bottleneck.
The Neuron DRA driver removes this burden by separating infrastructure concerns from ML workflows. Infrastructure teams define reusable ResourceClaimTemplates that capture device topology, allocation, and networking policies. ML engineers can simply reference these templates in their manifests, without needing to reason about hardware details. This enables consistent deployment across workload types while allowing per-workload configuration so multiple workloads can efficiently share the same nodes.
The Neuron DRA driver supports all AWS Trainium instance types and is available in all AWS Regions where AWS Trainium is available.
AWS announces the Neuron Dynamic Resource Allocation (DRA) driver for Amazon Elastic Kubernetes Service (EKS), bringing Kubernetes-native hardware-aware scheduling to AWS Trainium-based instances. The Neuron DRA driver publishes rich device attributes directly to the Kubernetes scheduler, enabling topology-aware placement decisions without custom scheduler extensions. Deploying AI workloads on Kubernetes requires ML engineers to make infrastructure decisions that are not directly related to model development, such as determining device counts, understanding hardware and network topologies, and writing accelerator-specific manifests. This creates friction, slows iteration, and tightly couples workloads to underlying infrastructure. As use cases expand to distributed training, long-context inference, and disaggregated architectures, this complexity becomes a scaling bottleneck. The Neuron DRA driver removes this burden by separating infrastructure concerns from ML workflows. Infrastructure teams define reusable ResourceClaimTemplates that capture device topology, allocation, and networking policies. ML engineers can simply reference these templates in their manifests, without needing to reason about hardware details. This enables consistent deployment across workload types while allowing per-workload configuration so multiple workloads can efficiently share the same nodes. The Neuron DRA driver supports all AWS Trainium instance types and is available in all AWS Regions where AWS Trainium is available.
For documentation, sample templates, and implementation guides, visit the Neuron DRA documentation.
Learn more:
De la revista Signal: Cómo Microsoft empuja la frontera de la innovación climática
Melanie Nakagawa se incorporó a Microsoft como directora de sostenibilidad en 2023 y, como parte de sus funciones, asumió la responsabilidad del Fondo de Innovación Climática (CIF, por sus siglas en inglés) de 1.000 millones de dólares de la compañía. En sus cargos anteriores trabajó en capital privado, gobierno y organizaciones sin ánimo de lucro, donde conectaba tecnología, finanzas e innovación. Le preguntamos sobre el fondo y cómo pueden ayudar las empresas en la lucha contra el cambio climático…
¿Por qué se creó el Fondo de Innovación Climática de Microsoft?
Melanie Nakagawa: Cuando Microsoft lanzó sus compromisos de sostenibilidad para ser carbono negativo, positivo en el agua y cero residuos para 2030, nos dimos cuenta de que había algunas tecnologías y soluciones que aún no existían a gran escala, pero que tendrían que estar disponibles de manera amplia para 2030. El Fondo de Innovación Climática se creó para construir las soluciones que el mundo necesita para el mercado del futuro.
¿Cómo deciden qué inversiones hacer?
MN: Como líder tecnológico global, Microsoft ve una increíble variedad de nuevas tecnologías a medida que surgen en el mercado. Identificamos las innovaciones sostenibles con mayor potencial de impacto climático en el límite de la adopción comercial, y alineamos el tipo adecuado de capital y colaboración para llevar esas soluciones al mercado a gran escala
¿Cuáles son algunas cosas clave que has aprendido en los primeros cinco años del fondo?
MN: Hemos aprendido cómo podemos empujar la frontera a través de validar tecnologías emergentes. Por ejemplo, Microsoft negoció un acuerdo de compra de diez años [un acuerdo para comprar productos futuros a condiciones establecidas] con una empresa de captura de carbono llamada Climeworks para extraer alrededor de 10.000 toneladas de dióxido de carbono de la atmósfera y almacenarlo de forma segura bajo tierra. El acuerdo, firmado en 2022, fue uno de los mayores contratos a largo plazo de captura directa de aire firmados hasta ese momento. Y luego, a través del CIF, Microsoft proporcionó financiación pionera para proyectos para la planta Orca de Climeworks en Islandia, la primera instalación comercial de captura aérea directa. También hemos aprendido cómo podemos actuar como un puente hacia el capital principal para que los proyectos en fase inicial puedan escalar. Un ejemplo de esto es Stegra, una empresa de acero verde bajo en carbono, a la que ayudamos a conseguir financiación de proyectos. También hemos aprendido el papel que puede desempeñar la IA para acelerar y optimizar sistemas con rapidez e innovación, y tenemos un puñado de empresas en el portafolio que apuestan por la IA primero.
Cuéntame sobre un proyecto en el que el fondo haya invertido del que estés en especial orgullosa…
MN: Algo que cada vez es más relevante para las empresas es cómo reducir sus emisiones derivadas de los viajes aéreos. A través del fondo invertimos en una empresa llamada Twelve, cuyo producto estrella es un combustible sostenible de aviación (SAF, por sus siglas en inglés) de acceso directo a potencia a líquido, elaborado con electricidad renovable, agua y dióxido de carbono. Invertimos para apoyar la ampliación de su planta de Moses Lake en Washington, y también contribuyó a una compra de SAF para Microsoft.
Creo que la forma en que se organizó la oferta es muy útil para otras empresas como modelo porque la estructuramos de una manera llamada ‘contabilidad de libros y reclamaciones’. Esto permite a Microsoft informar de emisiones más bajas por el uso sostenible de combustible de aviación, pero sin requerir una entrega física.
No poseemos aviones, así que lo que hicimos fue asociarnos con Alaska Airlines, una empresa con sede en el estado de Washington. Cuando se realiza el viaje de negocios, Microsoft ha pagado por el combustible sostenible para aviación, Alaska puede volar con ese combustible y Twelve recibe la inversión para seguir con el escalamiento y para hacer crecer su negocio. Todos salen beneficiados.
Has trabajado tanto en el gobierno como en el mundo corporativo. ¿Qué ventajas tienen las empresas para avanzar en la lucha contra el cambio climático?
MN: Una de las cosas que he aprendido de los distintos roles que he desempeñado es que, en realidad, hacen falta todos los actores para lograr el cambio: se requieren gobiernos, corporaciones, tecnología y finanzas. El papel que desempeñan las corporaciones es, ante todo, actuar con rapidez y agilidad, en lugar de estar atadas a ciclos políticos, y responder con rapidez a riesgos y oportunidades emergentes. También pueden influir en su propia cadena de valor, cómo integran la sostenibilidad en su adquisición, para influir en la reducción de emisiones entre miles de proveedores. Y, por supuesto, las corporaciones tienen la oportunidad de construir e impulsar mercados con la construcción del ecosistema para la innovación.
¿Hay algún consejo concreto que des a CEOs y CSOs que buscan multiplicar el efecto de su gasto en la sostenibilidad climática?
MN: Vemos cómo la IA puede tener un efecto transformador al acelerar soluciones en casi todos los sectores, y si se observan las inversiones en CIF en empresas impulsadas por IA, muestran cómo la automatización de datos y el análisis avanzado pueden abrir caminos emergentes para la descarbonización, la resiliencia y el crecimiento del mercado. Así que lo que a menudo decimos a otros y a muchos de nuestros clientes y socios es que el ritmo de progreso debe aumentar.
Este es un momento increíble para que líderes corporativos, inversores e innovadores integren la IA de manera reflexiva en sus estrategias y utilicen su potencial para apoyar la transición hacia soluciones de menor carbono, oportunidades de energía más limpia y soluciones más resilientes y asequibles.
¿Cuáles son algunas de las innovaciones más interesantes que llegarán en los próximos cinco años?
MN: Al mirar cinco años hacia 2030, vemos nuevas tecnologías prometedoras en la vanguardia del almacenamiento y generación de energía, la producción de hormigón y acero, el combustible de aviación, la eliminación de carbono y el reciclaje de residuos electrónicos, todo lo cual se aplica a nuestras propias operaciones globales.
Relacionado con esto, también me apasiona cómo atraer a más coinversores primerizos a estas innovaciones tecnológicas, en especial aquellas apoyadas por la CIF. Hasta ahora hemos conseguido catalizar 12.000 millones de dólares en financiación de seguimiento de los más de 800 millones que hemos asignado a través del fondo. Hasta ahora, por cada dólar asignado, se ha atraído un subsecuente de 15 dólares. Si conseguimos hacer esto con esas innovaciones tecnológicas que mencioné, podremos acelerar el ritmo y la escala de soluciones importantes.
¿Qué es lo que te mantiene en movimiento y motivada en tu trabajo?
MN: Uno de los principales motivos para mí de unirme a Microsoft hace unos años fue el CIF, la idea de que podemos desplegar y asignar recursos de Microsoft, incluidas nuestras capacidades y conocimientos de IA, a las empresas que construyen el futuro. Me entusiasman mucho las inversiones directas que realizamos para traer nuevo suministro de energía, combustibles, eliminación de carbono y materiales avanzados.
Es reconfortante saber que ideas que hace cinco o diez años solo eran un proyecto científico ahora son productos y proyectos de escala comercial y masiva, que son utilizados por millones. Y luego está la oportunidad de mostrar el verdadero significado de las alianzas estratégicas que ofrecen resultados concretos para desbloquear las tecnologías, el capital y el talento necesarios para escalar este mercado más rápido. Es un momento emocionante para el Fondo de Innovación Climática de Microsoft.
Esta es una versión digital de un artículo de muestra del número 3 de la revista Signal. Para explorar el número completo, consulten el flipbook completo en inglés aquí.
Amazon Redshift federated permissions are now supported with AWS IAM Identity Center (IdC) in multiple AWS Regions. You can extend IdC from your primary AWS Region to additional Regions for improved performance through proximity to users and reliability. In the additional regions, you now have simplified administration of Redshift fine-grained access controls at the table and column level using existing workforce identities with IdC.
When a new Region is added in IdC, you can create Redshift and Lake Formation Identity Center applications in the new Region without replicating identities from the primary Region. This enables you to use existing workforce identities to query data across warehouses in the new Region. Regardless of which warehouse is used for querying, row-level, column-level, and masking controls always apply automatically, delivering fine-grained access compliance. You can also access Amazon Redshift with single sign-on in these new Regions from Amazon QuickSight, Amazon Redshift Query Editor, or third-party SQL tools.
Amazon Redshift federated permissions are now supported with AWS IAM Identity Center (IdC) in multiple AWS Regions. You can extend IdC from your primary AWS Region to additional Regions for improved performance through proximity to users and reliability. In the additional regions, you now have simplified administration of Redshift fine-grained access controls at the table and column level using existing workforce identities with IdC. When a new Region is added in IdC, you can create Redshift and Lake Formation Identity Center applications in the new Region without replicating identities from the primary Region. This enables you to use existing workforce identities to query data across warehouses in the new Region. Regardless of which warehouse is used for querying, row-level, column-level, and masking controls always apply automatically, delivering fine-grained access compliance. You can also access Amazon Redshift with single sign-on in these new Regions from Amazon QuickSight, Amazon Redshift Query Editor, or third-party SQL tools. To get started with Redshift federated permissions using IdC, read the blog and documentation. To extend IdC support in multiple regions, read IdC documentation, Redshift documentation, Lake Formation documentation, and see the region availability.
Today, AWS announced the opening of a new AWS Direct Connect location at Equinix SY5 in Sydney, Australia. You can now establish private, direct network access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones from this location. This site is the fourth AWS Direct Connect location in Sydney and the tenth AWS Direct Connect location within Australia. This Direct Connect location offers dedicated 10 Gbps and 100 Gbps connections with MACsec encryption available.
The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet.
For more information on the over 150 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.
Today, AWS announced the opening of a new AWS Direct Connect location at Equinix SY5 in Sydney, Australia. You can now establish private, direct network access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones from this location. This site is the fourth AWS Direct Connect location in Sydney and the tenth AWS Direct Connect location within Australia. This Direct Connect location offers dedicated 10 Gbps and 100 Gbps connections with MACsec encryption available. The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet. For more information on the over 150 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.
Amazon EC2 Fleet now supports interruptible Capacity Reservations. EC2 Fleet allows you to launch instances across multiple instance types and Availability Zones. Starting today, you can specify interruptible Capacity Reservation IDs across your Launch Templates to provision instances in a single EC2 Fleet call.
When On-Demand Capacity Reservations are not in use, customers can make them temporarily available as interruptible reservations within their AWS Organization to improve utilization and save costs. When these interruptible reservations are available to your account, you can now use EC2 Fleet to easily consume them.
Amazon EC2 Fleet now supports interruptible Capacity Reservations. EC2 Fleet allows you to launch instances across multiple instance types and Availability Zones. Starting today, you can specify interruptible Capacity Reservation IDs across your Launch Templates to provision instances in a single EC2 Fleet call.
When On-Demand Capacity Reservations are not in use, customers can make them temporarily available as interruptible reservations within their AWS Organization to improve utilization and save costs. When these interruptible reservations are available to your account, you can now use EC2 Fleet to easily consume them.
This feature is available in all AWS commercial regions. To get started, refer to the EC2 Fleet documentation. To learn more about interruptible Capacity Reservations, visit the EC2 Capacity Reservations user guide.
