Starting November 1, 2026, the Amazon Cognito Service Level Agreement (SLA) commits to a Monthly Uptime Percentage of 99.99% for user pools on the Plus feature plan, up from 99.9%. User pools already on Plus are automatically covered by the new Service Commitment. User pools on Essentials and Lite stay at the 99.9% Service Commitment with no change to their terms.
To qualify for the 99.99% Service Commitment, you can switch a user pool to the Plus feature plan using the AWS Management Console, AWS Command Line Interface (CLI), or AWS Software Development Kits (SDKs). The Plus feature plan also includes threat protection features such as adaptive authentication, compromised credentials detection, and threat and user activity logging and export.
Starting November 1, 2026, the Amazon Cognito Service Level Agreement (SLA) commits to a Monthly Uptime Percentage of 99.99% for user pools on the Plus feature plan, up from 99.9%. User pools already on Plus are automatically covered by the new Service Commitment. User pools on Essentials and Lite stay at the 99.9% Service Commitment with no change to their terms.
To qualify for the 99.99% Service Commitment, you can switch a user pool to the Plus feature plan using the AWS Management Console, AWS Command Line Interface (CLI), or AWS Software Development Kits (SDKs). The Plus feature plan also includes threat protection features such as adaptive authentication, compromised credentials detection, and threat and user activity logging and export.
For full terms and exclusions, see the Amazon Cognito SLA. To learn more about feature plans, see user pool feature plans.
AWS Identity and Access Management (IAM) Roles Anywhere now supports automatic revocation checking using certificate revocation list (CRL) distribution points (CDPs). This helps keep revocation checks in sync with your certificate authority (CA) and can help improve your security posture. When you enable this capability on a trust anchor, IAM Roles Anywhere reads the CDP URLs embedded in authenticating certificates, downloads the corresponding CRLs, and denies credential requests that use revoked certificates.
Previously, to check revocation status, you had to import CRLs into IAM Roles Anywhere and re-import them each time your CA published an update, which added operational overhead. With this launch, IAM Roles Anywhere downloads CRLs from your CDPs and refreshes them periodically, so you no longer need to re-import them. You can use this capability with AWS Private Certificate Authority or your own public key infrastructure (PKI), provided your certificates include publicly accessible CDP URLs that meet the distribution point requirements. To enable it on a trust anchor, use the IAM Roles Anywhere console, AWS SDKs, or AWS CLI.
AWS Identity and Access Management (IAM) Roles Anywhere now supports automatic revocation checking using certificate revocation list (CRL) distribution points (CDPs). This helps keep revocation checks in sync with your certificate authority (CA) and can help improve your security posture. When you enable this capability on a trust anchor, IAM Roles Anywhere reads the CDP URLs embedded in authenticating certificates, downloads the corresponding CRLs, and denies credential requests that use revoked certificates.
Previously, to check revocation status, you had to import CRLs into IAM Roles Anywhere and re-import them each time your CA published an update, which added operational overhead. With this launch, IAM Roles Anywhere downloads CRLs from your CDPs and refreshes them periodically, so you no longer need to re-import them. You can use this capability with AWS Private Certificate Authority or your own public key infrastructure (PKI), provided your certificates include publicly accessible CDP URLs that meet the distribution point requirements. To enable it on a trust anchor, use the IAM Roles Anywhere console, AWS SDKs, or AWS CLI.
This feature is available at no additional cost in all commercial AWS Regions. To learn more, see Automatic revocation checking with CRL distribution points in the IAM Roles Anywhere User Guide.
Amazon SageMaker AI now supports IAM Identity Center (IdC) multi-region replication, enabling you to deploy SageMaker AI Studio domains in different regions from your IdC instance’s primary region. Previously, the primary IdC instance had to reside in the same region as the SageMaker AI Studio domain; now customers can replicate their primary IdC instance into the region where they wish to use SageMaker AI Studio domains. This capability helps customers maintain compliance while utilizing centralized workforce identity management.
As an Amazon SageMaker AI Studio administrator, you can deploy SageMaker AI domains that align with your workforce’s location and data residency requirements, independent of where your primary IdC instance is set up. Organizations can retain their primary IdC instance in one region while operating SageMaker AI Studio workloads in compliance-mandated regions, support global operations through centralized identity management, and satisfy data sovereignty requirements without compromising single sign-on (SSO) capabilities.
Multi-region IdC replication is available in all standard AWS Regions where Amazon SageMaker AI Studio is supported, including: Asia Pacific (Tokyo), Europe (Ireland), US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), South America (São Paulo), Asia Pacific (Seoul), Europe (London), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Asia Pacific (Mumbai), Europe (Paris), Europe (Stockholm).
Amazon SageMaker AI now supports IAM Identity Center (IdC) multi-region replication, enabling you to deploy SageMaker AI Studio domains in different regions from your IdC instance’s primary region. Previously, the primary IdC instance had to reside in the same region as the SageMaker AI Studio domain; now customers can replicate their primary IdC instance into the region where they wish to use SageMaker AI Studio domains. This capability helps customers maintain compliance while utilizing centralized workforce identity management.
As an Amazon SageMaker AI Studio administrator, you can deploy SageMaker AI domains that align with your workforce’s location and data residency requirements, independent of where your primary IdC instance is set up. Organizations can retain their primary IdC instance in one region while operating SageMaker AI Studio workloads in compliance-mandated regions, support global operations through centralized identity management, and satisfy data sovereignty requirements without compromising single sign-on (SSO) capabilities.
To get started see the SageMaker AI documentation and to learn about setting up IAM Identity Center multi-region support see the IAM Identity Center User Guide.
Multi-region IdC replication is available in all standard AWS Regions where Amazon SageMaker AI Studio is supported, including: Asia Pacific (Tokyo), Europe (Ireland), US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Frankfurt), South America (São Paulo), Asia Pacific (Seoul), Europe (London), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Asia Pacific (Mumbai), Europe (Paris), Europe (Stockholm).
Infraestructura para la era Frontier: Escalar la inteligencia mediante la colaboración abierta entre la industria
11 minuto
Por: Reynold D’Sa y Rani Borkar.
En Microsoft, nuestra visión es construir una Frontier Firm (Empresa Frontier): una donde las personas y la tecnología trabajen juntas, a través de combinar la experiencia humana, el contexto y el juicio con tecnología que pueda extender la inteligencia a lo largo del trabajo cotidiano. El potencial es significativo: ayudar a las personas a crear, resolver problemas complejos y avanzar en algunos de los desafíos más importantes de la sociedad.
Pero para darse cuenta de ese potencial se requiere una infraestructura Frontier. La siguiente fase de Super Inteligencia necesita un motor de infraestructura unificado que ofrezca más inteligencia con mayor eficiencia, para hacer que la IA sea más accesible, fiable y sostenible en ciencia, sanidad, educación y economía. Este es el trabajo de todo un ecosistema, y es justo la visión que hemos impulsado durante años a través de nuestra colaboración industrial dentro de la Open Compute Project Foundation.
Diseñar silicio en el bucle con cargas de trabajo reales
Al entrar en la siguiente fase de Super Intelligence, la inferencia se ha comenzado a convertir en la carga de trabajo dominante y ahí es donde la eficiencia, la latencia y el coste en verdad importan. Azure Maia 300, nuestro acelerador de IA de próxima generación de nuestra familia Maia, avanza en la frontera de la eficiencia de inferencia. Maia 300 es un sistema completo diseñado para los nuevos tipos de cargas de trabajo de IA que surgen hoy en día: razonamiento de contexto largo, experiencias conversacionales sensibles a la latencia y tareas agentes sostenidas y de varios pasos. Al mejorar la eficiencia en todo el sistema, esperamos que Maia 300 entregue un 40% más de tokens por vatio en comparación con los principales sistemas basados en GPU. Y en una configuración completa de 96 aceleradores, ofrece hasta siete veces el rendimiento de tokens a escala de rack que Maia 200.
Maia refleja nuestro enfoque de diseño conjunto de sistemas. Está diseñado junto con la infraestructura de Microsoft y cargas de producción, para reunir modelos, marcos de aplicaciones, núcleos, bibliotecas de comunicación, software de sistemas y silicio personalizado en un único bucle de optimización. Maia 200 se despliega en Estados Unidos, Europa y Australia, y ofrece hasta 1,7 veces más tokens por vatio para capacidades de IA integradas en Microsoft Teams, Copilot y Cowork en comparación con la infraestructura líder de GPU.
Sistemas Azure Maia 200 en un centro de datos
La IA no se trata solo de aceleradores. Las cargas de trabajo agénticas generan demandas nuevas para las CPUs. Cada interacción con agentes genera orquestación, recuperación de datos, gestión de memoria y llamadas de servicio que deben ocurrir de manera rápida y eficiente. Por eso diseñamos Cobalt 200 como una CPU nativa de agentes. Cobalt 200 ofrece una mejora de rendimiento de más del 50% respecto a Cobalt 100 y reduce la latencia de llamadas a agentes en un 33%, además de proporcionar un 23% más de rendimiento en cargas de trabajo agentes.
Sistemas Azure Cobalt 200 en un centro de datos
Maia y Cobalt están diseñados en el bucle con nuestras mayores cargas de trabajo empresariales. Esto da a Microsoft una ventaja única para ajustar el rendimiento, la fiabilidad y el coste justo a lo que los clientes necesitan en producción.
Aplicamos el mismo principio al almacenamiento y la seguridad. La Unidad de Procesamiento de Datos Azure Boost traslada las funciones de compresión, transacciones de red y seguridad fuera de la CPU hacia un silicio diseñado de manera específica, permitiéndonos ofrecer cuatro veces más rendimiento al consumir mucha menos energía.
Y Azure Integrated HSM integra la seguridad como parte de la base del hardware, con nuestro chip de seguridad interno en todos los nuevos servidores de centros de datos. Acerca las operaciones criptográficas a la carga de trabajo mientras mantiene las claves protegidas dentro del límite de seguridad del hardware, sin estar expuestas en la memoria de la aplicación.
Construir una estructura de IA abierta y resiliente
En nuestro trabajo con socios industriales, Microsoft desarrolló Multipath Reliable Connection (MRC), para replantear Ethernet para la IA. Su arquitectura multiplano escala más allá de las 100.000 GPUs con dos niveles de red, lo que reduce la energía, complejidad, puntos de fallo y costes. Al distribuir el tráfico de manera inteligente a través de múltiples rutas y mediante pulverización de paquetes, MRC limita la congestión y mantiene un rendimiento fiable para entrenamiento a escala de frontera.
También promovemos la conectividad abierta de escalabilidad a través del Acuerdo Multifuente de Interconexión de Computación Óptica (OCI MSA, por sus siglas en inglés). OCI, la primera especificación óptica para sistemas de escalado multi-rack, permite infraestructuras de alto ancho de banda, eficiente a nivel energético y multi-proveedor. De cara al futuro, seguiremos con nuestro trabajo con la industria para ampliar la participación en OCI MSA.
De manera paralela, el flujo de trabajo Ethernet para Redes Escalables (ESUN, por sus siglas en inglés) reúne a más de 175 organizaciones para definir los requisitos para la ampliación de redes basadas en Ethernet. El grupo ha publicado la versión 1.0 de la especificación y está en proceso de desarrollo de la versión 1.1 para finales de este año. Lean más sobre nuestras innovaciones en redes con la comunidad abierta.
Replantear la energía de la red a la silicio
La infraestructura de IA también obliga a un rediseño fundamental de la entrega de energía. A través de OCP y la iniciativa Open Systems for AI, Microsoft ayuda a avanzar en la transición de la industria hacia una infraestructura de corriente continua (VDC, por sus siglas en inglés) de 800 voltios.
Mt. Diablo, la arquitectura sidecar desagregada de centro de datos de alta tensión (DC) de Microsoft, separa la conversión de energía del rack de cálculo para que cada uno pueda escalar de manera independiente. Incluye un diseño modular que soporta cerca de 100 kilovatios (kW) hasta más de un megavatio (MW), con alimentaciones redundantes, telemetría y almacenamiento opcional de energía. Microsoft, junto con socios de OCP, contribuyó con las especificaciones de Mt. Diablo v0.7 y v1.0 a OCP.
Microsoft y sus socios avanzan en arquitecturas basadas en transformadores de estado sólido para hacer que la conversión de energía sea más eficiente, sensible y escalable para los centros de datos de próxima generación de 800 VDC. A través de la iniciativa Clean Backup Power de OCP, estamos en proceso de desarrollo de requisitos abiertos para sistemas de respaldo fiables que reduzcan la dependencia del diésel. De manera paralela, Microsoft colaboró con socios para lanzar una especificación común de interfaz de red que alinee a las compañías eléctricas, operadores y proveedores de equipos a medida que evolucionan las arquitecturas de energía hiperescalada. Lean más sobre el enfoque de Microsoft para la transición a 800VDC y la escalada sostenible de la infraestructura eléctrica.
La refrigeración como consideración de diseño de primera clase
Microsoft aborda la refrigeración como un reto a nivel de centro de datos, para impulsar la innovación desde el diseño de instalaciones en corriente continua hasta tecnologías de refrigeración líquida a nivel de rack.
Nuestra unidad de intercambiador de calor Azure de tercera generación, Mt. Atlas, casi duplica su capacidad de refrigeración respecto a la generación anterior, para mantener la misma huella operativa. También contribuimos con arquitectura de referencia pública a través de OCP para ayudar a acelerar la adopción en la industria.
A nivel de centro de datos, Microsoft impulsa una estrategia de refrigeración zonal en sus centros de datos de IA de próxima generación para manejar la creciente mezcla de aceleradores refrigerados por líquido y sistemas tradicionales refrigerados por aire. Al adaptar la refrigeración a las necesidades específicas de cada carga de trabajo e introducir múltiples bucles de agua independientes, donde cada uno suministra refrigerante a diferentes temperaturas, pretendemos aumentar la eficiencia y el rendimiento a través de apoyar los objetivos de reducción de energía, carbono y agua de Microsoft.
Innovación en seguridad por hardware abierto
Microsoft cree que una sólida seguridad en la nube se construye a través de la apertura, la transparencia y la colaboración con la industria. Este principio se refleja en nuestro papel fundador en el Confidential Computing Consortium, en nuestro trabajo para establecer Caliptra como una raíz de confianza de silicio de código abierto, y en nuestras contribuciones al marco de conformidad de seguridad OCP S.A.F.E. A medida que la IA transforma el panorama de la ciberseguridad y los avances en computación cuántica introducen nuevos riesgos criptográficos, proteger las claves y credenciales que son la base de la confianza digital nunca ha sido tan importante.
Para abordar estos desafíos, y basándose en nuestro compromiso con la transparencia en seguridad y la colaboración con la industria, Microsoft, Marvell y Oracle presentan Tessera Integrated HSM, una iniciativa de código abierto para módulos integrados de seguridad de hardware. Tessera Integrated HSM mantiene la arquitectura de carga de trabajo conectada de manera directa e introducida por Azure Integrated HSM, para abrir su arquitectura, especificaciones, protocolos, controladores, software, firmware y silicio a la comunidad en general. Descubran más sobre Tessera Integrated HSM.
Resiliencia de la flota a gran escala
A medida que la infraestructura de IA crece, la fiabilidad de la flota es esencial para proteger las cargas de trabajo de los clientes, la capacidad y la calidad del servicio. A través de OCP, Microsoft ha publicado especificaciones comunes de RAS, depuración, telemetría y diagnóstico, además de contribuir con trabajos en gestión de fallos de hardware, CPU y GPU, y gestión de fallos en memoria de flotas. Utilizamos años de datos de flotas y IA para validar, predecir e impulsar acciones de flota destinadas a prevenir fallos, identificar problemas y recuperarse de forma más autónoma. Descubran más sobre cómo Microsoft promueve la fiabilidad de flotas a través de la colaboración con la industria.
Avanzar en la sostenibilidad en toda la infraestructura
Escalar la IA de manera responsable implica considerar todo el ciclo de vida del centro de datos para ayudar a alcanzar nuestros compromisos para 2030 de ser carbono negativos, positivos en el agua y cero residuos. Como empresa, estamos comprometidos a incorporar la sostenibilidad en la manera en que diseñamos, construimos y operamos nuestros centros de datos que se extienden a las comunidades donde los construimos. A través de OCP, Microsoft colabora con socios en acero y hormigón de bajo contenido de carbono incorporado, con vías para reducir las emisiones de hormigón en más del 50% por yarda cúbica.
Promovemos la reutilización del calor residual y ayudamos a desarrollar Reglas de Categoría de Producto de Servicios en la Nube para informes coherentes y auditables sobre carbono durante el ciclo de vida. Dentro de nuestros centros de datos, la refrigeración líquida en circuito cerrado, la gestión inteligente de energía y los acuerdos de energía renovable ayudan a reducir el consumo de recursos, mientras que los Centros Circulares reutilizan o reciclan más del 90% de los servidores y componentes. Más allá del centro de datos, invertimos en habilidades locales, alianzas e infraestructuras para que las comunidades que acogen este crecimiento puedan crecer con nosotros. Lean el informe de Sostenibilidad Ambiental 2026 de Microsoft.
Construir Frontier juntos
Nuestra visión es ayudar a cada organización a convertirse en una Empresa Frontier, a través de unir la experiencia humana con la IA en un bucle de aprendizaje continuo que convierte el conocimiento y la creatividad en inteligencia escalable. Comprender que la visión requiere co-diseño full-stack: silicio, computación, memoria, redes, energía, refrigeración, modelos y aplicaciones que funcionen como una plataforma única, segura, fiable, eficiente y sostenible, para ofrecer a los clientes la opción sin trasladarles complejidad.
Un futuro así no puede ser llevado a cabo por una sola organización. A través de OCP, impulsamos interfaces abiertas, compartimos lecciones de la infraestructura operativa a escala global y colaboramos en toda la industria para que la innovación avance más rápido y el ecosistema deje de resolver los mismos problemas de manera repetida. Juntos, podemos transformar la innovación de vanguardia en una infraestructura que haga la inteligencia accesible y asequible para todas las organizaciones, en todos los sectores y en todas las regiones del mundo.
En OCP Global Summit 2026, invitamos a la comunidad a construir ese futuro con nosotros.
The post Infraestructura para la era Frontier: Escalar la inteligencia mediante la colaboración abierta entre la industria appeared first on Source LATAM.
Amazon Elastic Container Service (Amazon ECS) introduces json-file log driver support for Amazon ECS Managed Instances and log driver volumes for Amazon ECS Managed Daemons. Together, these features let you collect application logs with the observability agent of your choice and forward them to any destination you choose.
With this launch, your application containers on ECS Managed Instances can write their logs as local files in standard Docker json-file format, which most observability agents read natively. Your managed daemons can directly read these files through a volume mount, without specifying host bind mount paths or requiring root privileges. As a result, one managed daemon on each instance can collect logs from every application container that uses the json-file log driver. Amazon ECS keeps each container’s logs in a dedicated directory named with the container ID and retains them until the container is removed, so your managed daemon can use native file-based log collection and trace every log back to the container that produced it.
To get started, set the log driver to json-file in the logConfiguration of your application task definition. Next, register a daemon task definition that specifies a volume with logDriverVolumeConfiguration, and mount the volume into your daemon container using mountPoints. You can configure this using the AWS Management Console, AWS CLI, API, AWS SDKs or AWS CloudFormation. This feature is available in all commercial AWS Regions where Amazon ECS Managed Instances and Managed Daemons are available, at no additional cost. To learn more, refer to our documentation page and visit Amazon ECS Managed Instances.
Amazon Elastic Container Service (Amazon ECS) introduces json-file log driver support for Amazon ECS Managed Instances and log driver volumes for Amazon ECS Managed Daemons. Together, these features let you collect application logs with the observability agent of your choice and forward them to any destination you choose. With this launch, your application containers on ECS Managed Instances can write their logs as local files in standard Docker json-file format, which most observability agents read natively. Your managed daemons can directly read these files through a volume mount, without specifying host bind mount paths or requiring root privileges. As a result, one managed daemon on each instance can collect logs from every application container that uses the json-file log driver. Amazon ECS keeps each container’s logs in a dedicated directory named with the container ID and retains them until the container is removed, so your managed daemon can use native file-based log collection and trace every log back to the container that produced it. To get started, set the log driver to json-file in the logConfiguration of your application task definition. Next, register a daemon task definition that specifies a volume with logDriverVolumeConfiguration, and mount the volume into your daemon container using mountPoints. You can configure this using the AWS Management Console, AWS CLI, API, AWS SDKs or AWS CloudFormation. This feature is available in all commercial AWS Regions where Amazon ECS Managed Instances and Managed Daemons are available, at no additional cost. To learn more, refer to our documentation page and visit Amazon ECS Managed Instances.
Amazon Connect Customer now includes case IDs and reference numbers in contact records, helping supervisors and analysts understand which customer issues drive contact volume. Cases track issues, such as refund requests or billing disputes, across interactions and teams. Supervisors can now identify the cases associated with an interaction directly on the Contact Details page without searching individual cases. Analysts can access the same information through the DescribeContact API and contact event streams to measure the number of interactions per case.
Cases is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town). To learn more and get started, visit the Cases webpage and documentation.
Amazon Connect Customer now includes case IDs and reference numbers in contact records, helping supervisors and analysts understand which customer issues drive contact volume. Cases track issues, such as refund requests or billing disputes, across interactions and teams. Supervisors can now identify the cases associated with an interaction directly on the Contact Details page without searching individual cases. Analysts can access the same information through the DescribeContact API and contact event streams to measure the number of interactions per case.
Cases is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town). To learn more and get started, visit the Cases webpage and documentation.
Amazon DocumentDB (with MongoDB compatibility) is now available in the Asia Pacific (Taipei) and Asia Pacific (New Zealand) Regions, adding to the list of available Regions where you can use Amazon DocumentDB.
Amazon DocumentDB is a fully managed, native JSON database that makes it simple and cost-effective to operate critical document workloads at virtually any scale without managing infrastructure. Amazon DocumentDB is designed to give you the scalability and durability you need when operating mission-critical MongoDB workloads. Storage scales automatically up to 128 TiB without any impact to your application. In addition, Amazon DocumentDB natively integrates with Amazon CloudWatch, AWS CloudTrail, AWS Lambda, AWS Backup, and more. Amazon DocumentDB supports millions of requests per second and can be scaled out to 15 low-latency read replicas in minutes with no application downtime.
Amazon DocumentDB (with MongoDB compatibility) is now available in the Asia Pacific (Taipei) and Asia Pacific (New Zealand) Regions, adding to the list of available Regions where you can use Amazon DocumentDB.
Amazon DocumentDB is a fully managed, native JSON database that makes it simple and cost-effective to operate critical document workloads at virtually any scale without managing infrastructure. Amazon DocumentDB is designed to give you the scalability and durability you need when operating mission-critical MongoDB workloads. Storage scales automatically up to 128 TiB without any impact to your application. In addition, Amazon DocumentDB natively integrates with Amazon CloudWatch, AWS CloudTrail, AWS Lambda, AWS Backup, and more. Amazon DocumentDB supports millions of requests per second and can be scaled out to 15 low-latency read replicas in minutes with no application downtime.
To learn more about Amazon DocumentDB, please visit the Amazon DocumentDB product page and pricing page. You can create an Amazon DocumentDB cluster from the AWS Management Console, AWS Command Line Interface (CLI), or AWS SDKs.
AWS announces new Linux bundles for Amazon WorkSpaces Personal, including Rocky Linux 10, Red Hat Enterprise Linux 10, and Ubuntu 26.04 LTS. With these bundles, you can launch WorkSpaces on the latest enterprise Linux operating systems and use newer software packages that are only available in these releases. These new bundles feature modern Wayland display technology, giving you access to the latest Linux desktop capabilities. The new OS options also bring stronger security and longer support lifecycles from each distribution.
While Rocky Linux 8 and 9, Red Hat Enterprise Linux 8 and 9, and Ubuntu 22.04 LTS and 24.04 LTS powered WorkSpaces bundles remain available, the new bundles let you adopt the latest releases on your own timeline. Your existing WorkSpaces keep running with no changes. You can move users to the new operating systems once your applications and workflows are ready.
To get started, select a managed Rocky Linux 10, Red Hat Enterprise Linux 10, or Ubuntu 26.04 LTS bundle when you create a new Linux WorkSpace. These bundles are available in Standard, Performance, Power, and PowerPro sizes in all AWS Regions where Amazon WorkSpaces is available. For a full list of supported operating systems, see Bundles and images for WorkSpaces Personal. For pricing information, visit the Amazon WorkSpaces pricing page.
AWS announces new Linux bundles for Amazon WorkSpaces Personal, including Rocky Linux 10, Red Hat Enterprise Linux 10, and Ubuntu 26.04 LTS. With these bundles, you can launch WorkSpaces on the latest enterprise Linux operating systems and use newer software packages that are only available in these releases. These new bundles feature modern Wayland display technology, giving you access to the latest Linux desktop capabilities. The new OS options also bring stronger security and longer support lifecycles from each distribution.
While Rocky Linux 8 and 9, Red Hat Enterprise Linux 8 and 9, and Ubuntu 22.04 LTS and 24.04 LTS powered WorkSpaces bundles remain available, the new bundles let you adopt the latest releases on your own timeline. Your existing WorkSpaces keep running with no changes. You can move users to the new operating systems once your applications and workflows are ready.
To get started, select a managed Rocky Linux 10, Red Hat Enterprise Linux 10, or Ubuntu 26.04 LTS bundle when you create a new Linux WorkSpace. These bundles are available in Standard, Performance, Power, and PowerPro sizes in all AWS Regions where Amazon WorkSpaces is available. For a full list of supported operating systems, see Bundles and images for WorkSpaces Personal. For pricing information, visit the Amazon WorkSpaces pricing page.
Amazon RDS for Oracle now lets you copy the option group associated with a DB snapshot when you copy that snapshot to another AWS Region.
Amazon RDS for Oracle uses option groups to enable and configure features that make it simple to manage your databases. Option groups are specific to the AWS Region where you create them. Previously, customers wanting to replicate RDS backups that had option groups to a different AWS Region had to copy the snapshot without the option group and then recreate the option group in the target Region before restoring the snapshot. Now, you no longer need to separate the steps and can instead initiate the snapshot copy and specify the option group copy in the same request as the snapshot copy.
The existing boolean parameter CopyOptionGroup on the CopyDBSnapshot API and CLI commands now also support cross-Region copy, along with cross-account copy. You can now copy options groups to the destination snapshot in the target AWS Region from the source snapshot by setting this parameter to true.
This capability is available on Amazon RDS for Oracle in all commercial AWS Regions and the AWS GovCloud (US) Regions. To learn more, review the Amazon RDS API Documentation.
Amazon RDS for Oracle now lets you copy the option group associated with a DB snapshot when you copy that snapshot to another AWS Region.
Amazon RDS for Oracle uses option groups to enable and configure features that make it simple to manage your databases. Option groups are specific to the AWS Region where you create them. Previously, customers wanting to replicate RDS backups that had option groups to a different AWS Region had to copy the snapshot without the option group and then recreate the option group in the target Region before restoring the snapshot. Now, you no longer need to separate the steps and can instead initiate the snapshot copy and specify the option group copy in the same request as the snapshot copy.
The existing boolean parameter CopyOptionGroup on the CopyDBSnapshot API and CLI commands now also support cross-Region copy, along with cross-account copy. You can now copy options groups to the destination snapshot in the target AWS Region from the source snapshot by setting this parameter to true.
This capability is available on Amazon RDS for Oracle in all commercial AWS Regions and the AWS GovCloud (US) Regions. To learn more, review the Amazon RDS API Documentation.
AWS Interconnect – last mile is now available in preview with Equinix. You can connect your infrastructure across Equinix’s global network of 282 data centers worldwide to AWS in a few clicks.
Interconnect – last mile gives you managed, private, and resilient connections to AWS, so you don’t have to order cross-connects or configure routers. To set up in the AWS Management Console, choose an AWS Region, a bandwidth speed, a Direct Connect gateway, and your Equinix Fabric One project ID. AWS generates an activation key, which you enter in the Equinix Fabric One portal to complete the setup. You can also initiate the connection from the Equinix Fabric One portal. AWS and Equinix set up quad-redundant capacity in advance, across two locations and four separate links, with BGP peering, VLANs and ASNs configured for you. Every connection is built for maximum resilience and comes with a 99.99% availability SLA. Traffic between AWS and Equinix edge devices is encrypted with MACsec by default.
During the preview, you can order 1 Gbps Interconnect – last mile connections at no charge to the US West (N. California) Region through the San Jose metro and to the US East (N. Virginia) Region through the Northern Virginia metro. When Interconnect – last mile with Equinix becomes generally available, you’ll be able to scale bandwidth from 1 Gbps to 100 Gbps in the console. You can create connections using the console, the AWS CLI, or the API. Partners can integrate using the open API package on GitHub. To learn more, see the AWS Interconnect – last mile documentation.
AWS Interconnect – last mile is now available in preview with Equinix. You can connect your infrastructure across Equinix’s global network of 282 data centers worldwide to AWS in a few clicks.
Interconnect – last mile gives you managed, private, and resilient connections to AWS, so you don’t have to order cross-connects or configure routers. To set up in the AWS Management Console, choose an AWS Region, a bandwidth speed, a Direct Connect gateway, and your Equinix Fabric One project ID. AWS generates an activation key, which you enter in the Equinix Fabric One portal to complete the setup. You can also initiate the connection from the Equinix Fabric One portal. AWS and Equinix set up quad-redundant capacity in advance, across two locations and four separate links, with BGP peering, VLANs and ASNs configured for you. Every connection is built for maximum resilience and comes with a 99.99% availability SLA. Traffic between AWS and Equinix edge devices is encrypted with MACsec by default.
During the preview, you can order 1 Gbps Interconnect – last mile connections at no charge to the US West (N. California) Region through the San Jose metro and to the US East (N. Virginia) Region through the Northern Virginia metro. When Interconnect – last mile with Equinix becomes generally available, you’ll be able to scale bandwidth from 1 Gbps to 100 Gbps in the console. You can create connections using the console, the AWS CLI, or the API. Partners can integrate using the open API package on GitHub. To learn more, see the AWS Interconnect – last mile documentation.
