Amazon CloudWatch Logs now supports expanded analytics and data protection capabilities for the Infrequent Access (Logs IA) ingestion class, including support for data protection, OpenSearch’s Piped Processing Language (PPL) and OpenSearch SQL. These enhancements make it easier for customers to perform flexible analytics and protect sensitive data while cost-effectively consolidating all your logs natively on AWS, making Logs IA ideal for ad-hoc troubleshooting and forensic analysis on infrequently accessed logs.
Logs IA is a cost-effective ingestion class for consolidating logs that are queried occasionally, such as forensic investigations. Logs IA currently offers log analytics with Logs Insights Query Language, export to S3, and encryption with a lower ingestion price per GB compared to the Standard log class. With today’s launch, customers can now use OpenSearch SQL and OpenSearch PPL queries to perform advanced analytics. In addition, data protection allows customers to automatically detect and mask sensitive information in logs, helping organizations meet security and compliance requirements.
Learn more about CloudWatch Logs IA pricing and read the user guide here. For Regional availability, visit the AWS Builder Center.
Amazon CloudWatch Logs now supports expanded analytics and data protection capabilities for the Infrequent Access (Logs IA) ingestion class, including support for data protection, OpenSearch’s Piped Processing Language (PPL) and OpenSearch SQL. These enhancements make it easier for customers to perform flexible analytics and protect sensitive data while cost-effectively consolidating all your logs natively on AWS, making Logs IA ideal for ad-hoc troubleshooting and forensic analysis on infrequently accessed logs.
Logs IA is a cost-effective ingestion class for consolidating logs that are queried occasionally, such as forensic investigations. Logs IA currently offers log analytics with Logs Insights Query Language, export to S3, and encryption with a lower ingestion price per GB compared to the Standard log class. With today’s launch, customers can now use OpenSearch SQL and OpenSearch PPL queries to perform advanced analytics. In addition, data protection allows customers to automatically detect and mask sensitive information in logs, helping organizations meet security and compliance requirements.
Learn more about CloudWatch Logs IA pricing and read the user guide here. For Regional availability, visit the AWS Builder Center.
Amazon GameLift Servers now supports Amazon EC2 5th through 8th generation instances, offering enhanced price-performance, efficiency, and flexibility for game server hosting. This update allows developers to leverage the latest advancements in EC2 compute, memory, and networking across three main instance families:
General Purpose (M-series): Balanced CPU, memory, and networking for a wide range of game workloads.
Compute Optimized (C-series): High-performance compute instances with a 2:1 memory ratio, ideal for CPU-intensive game servers.
Memory Optimized (R-Series): Optimized for high-memory workloads with an 8:1 memory ratio, supporting complex simulations and large player sessions.
Each new EC2 generation brings significant improvements:
5th Gen: Proven reliability with Intel processors with balanced performance
6th Gen: Includes AWS Graviton2 ARM-based options alongside Intel and AMD variants offering enhanced price-performance efficiency.
7th Gen: The latest evolution featuring DDR5 memory, enhanced networking, and offering significant performance gains over previous generations.
8th Gen: Cutting-edge AWS Graviton4 and Intel Xeon-based instances for demanding workloads
Customers can also choose variants with local storage (d), enhanced networking (n), and different processor architectures (Intel, AMD, Graviton – i/a/g).
This update empowers developers with greater flexibility, scalability, and cost efficiency to optimize game server performance. Customers can now seamlessly transition workloads to newer EC2 generations, leveraging AWS’s continuous innovation for building, scaling, and operating multiplayer games globally.
These next-generation instances are available in Amazon GameLift Servers supported regions, except AWS China. For more information on launching fleets with next-generation EC2 instances, visit the Amazon GameLift Servers documentation and EC2 Instance Types overview.
Amazon GameLift Servers now supports Amazon EC2 5th through 8th generation instances, offering enhanced price-performance, efficiency, and flexibility for game server hosting. This update allows developers to leverage the latest advancements in EC2 compute, memory, and networking across three main instance families:
General Purpose (M-series): Balanced CPU, memory, and networking for a wide range of game workloads.
Compute Optimized (C-series): High-performance compute instances with a 2:1 memory ratio, ideal for CPU-intensive game servers.
Memory Optimized (R-Series): Optimized for high-memory workloads with an 8:1 memory ratio, supporting complex simulations and large player sessions.
Each new EC2 generation brings significant improvements:
5th Gen: Proven reliability with Intel processors with balanced performance
6th Gen: Includes AWS Graviton2 ARM-based options alongside Intel and AMD variants offering enhanced price-performance efficiency.
7th Gen: The latest evolution featuring DDR5 memory, enhanced networking, and offering significant performance gains over previous generations.
8th Gen: Cutting-edge AWS Graviton4 and Intel Xeon-based instances for demanding workloads
Customers can also choose variants with local storage (d), enhanced networking (n), and different processor architectures (Intel, AMD, Graviton – i/a/g). This update empowers developers with greater flexibility, scalability, and cost efficiency to optimize game server performance. Customers can now seamlessly transition workloads to newer EC2 generations, leveraging AWS’s continuous innovation for building, scaling, and operating multiplayer games globally. These next-generation instances are available in Amazon GameLift Servers supported regions, except AWS China. For more information on launching fleets with next-generation EC2 instances, visit the Amazon GameLift Servers documentation and EC2 Instance Types overview.
Today we’re announcing Research and Engineering Studio (RES) on AWS 2026.03, which introduces new administrator controls, expanded filesystem support, and session management improvements.
Research and Engineering Studio on AWS (RES) is an open source, easy-to-use web-based portal for administrators to create and manage secure cloud-based research and engineering environments. Using RES, scientists and engineers can visualize data and run interactive applications without the need for cloud expertise.
RES 2026.03 gives administrators more flexibility in configuring and managing their environments. Admins can now onboard multiple individual FSx for ONTAP volumes as RES filesystems. Admins can also configure DCV token expiration time, which is useful for enabling session files with longer durations, and add up to three custom links on the RES login page for resources such as account management pages, help documentation, or usage policy pages.
Version 2026.03 also improves the experience for both admins and users around virtual desktop sessions. Admins can now restart VDIs in an error state directly from the Sessions page, helping resolve launch issues with less user intervention. Users can reset a VDI session schedule back to the system default with a single button. This version also includes assorted bug fixes and performance improvements.
Today we’re announcing Research and Engineering Studio (RES) on AWS 2026.03, which introduces new administrator controls, expanded filesystem support, and session management improvements. Research and Engineering Studio on AWS (RES) is an open source, easy-to-use web-based portal for administrators to create and manage secure cloud-based research and engineering environments. Using RES, scientists and engineers can visualize data and run interactive applications without the need for cloud expertise. RES 2026.03 gives administrators more flexibility in configuring and managing their environments. Admins can now onboard multiple individual FSx for ONTAP volumes as RES filesystems. Admins can also configure DCV token expiration time, which is useful for enabling session files with longer durations, and add up to three custom links on the RES login page for resources such as account management pages, help documentation, or usage policy pages. Version 2026.03 also improves the experience for both admins and users around virtual desktop sessions. Admins can now restart VDIs in an error state directly from the Sessions page, helping resolve launch issues with less user intervention. Users can reset a VDI session schedule back to the system default with a single button. This version also includes assorted bug fixes and performance improvements. This release is available in all AWS Regions where RES is available. To learn more about RES 2026.03, including detailed release notes and deployment instructions, visit the Research and Engineering Studio documentation or check out the RES GitHub repository.
AWS Parallel Computing Service (AWS PCS) now supports additional Slurm configuration settings for slurmdbd and cgroups, enabling you to fine-tune accounting behavior and resource isolation directly through the AWS PCS console, CLI, or SDK. This feature helps you implement production-ready HPC environments with enhanced privacy controls, flexible data retention policies, and improved resource management.
Using slurmdbd settings, you can configure how Slurm accounting operates on your cluster—including privacy controls, data retention policies, and workload tracking capabilities. With cgroups support, you can prevent resource oversubscription by binding CPU cores, enforce memory limits to maintain node stability, and control device access to ensure workloads run within defined boundaries.
AWS PCS is a managed service that simplifies running and scaling HPC workloads on AWS using Slurm. You can build complete, elastic environments that integrate compute, storage, networking, and visualization tools, while the service handles cluster operations with managed updates and built-in observability features.
AWS Parallel Computing Service (AWS PCS) now supports additional Slurm configuration settings for slurmdbd and cgroups, enabling you to fine-tune accounting behavior and resource isolation directly through the AWS PCS console, CLI, or SDK. This feature helps you implement production-ready HPC environments with enhanced privacy controls, flexible data retention policies, and improved resource management.
Using slurmdbd settings, you can configure how Slurm accounting operates on your cluster—including privacy controls, data retention policies, and workload tracking capabilities. With cgroups support, you can prevent resource oversubscription by binding CPU cores, enforce memory limits to maintain node stability, and control device access to ensure workloads run within defined boundaries.
AWS PCS is a managed service that simplifies running and scaling HPC workloads on AWS using Slurm. You can build complete, elastic environments that integrate compute, storage, networking, and visualization tools, while the service handles cluster operations with managed updates and built-in observability features.
This feature is available in all AWS Regions where AWS PCS is available. You can configure these settings when creating a new cluster or by modifying an existing cluster. To learn more, see the AWS PCS User Guide.
De la revista Signal: Qué significa invertir en los bosques
Bettina von Hagen dirige un innovador fondo de inversión forestal, EFM, que ha recibido el respaldo del CIF de Microsoft. Nos cuenta cómo su organización mejora la gestión de los bosques para desbloquear sus beneficios para los inversores y para el planeta
Cuéntame sobre tu trayectoria y cómo llegaste a EFM.
Bettina von Hagen: Cofundé esta empresa hace 20 años y he sido muy persistente en la visión que establecimos entonces. Pero si retrocedo más, me apasionan los bosques y la biodiversidad desde una visita a las Islas Galápagos cuando tenía 13 años. Fue una experiencia alucinante: ver la biogeografía de la isla, la evolución, la especiación, todo eso hizo que el mundo encajara para mí, estudié biología y luego volví a las Galápagos durante un año, para trabajar en una estación de investigación como voluntaria y más tarde como guía en barcos. Después de viajar un tiempo y trabajar en Europa, obtuve un MBA en la Universidad de Chicago, me dediqué a la banca comercial durante unos seis años y me di cuenta de que me encantaban las finanzas. Me encantaba cerrar tratos, enhebrar la aguja y hacer posibles las cosas, pero solo si era en busca de objetivos medioambientales y sociales.
Así que la banca y yo nos separamos. Encontré una maravillosa organización sin ánimo de lucro llamada Ecotrust, que se centra en utilizar capital privado y financiación de subvenciones para crear empresas que impulsan objetivos medioambientales y sociales, en específico en la selva templada costera del noroeste del Pacífico. Mientras estuve allí creamos una institución bancaria, remodelamos un edificio histórico según los estándares LEED Gold [calificación de edificio verde] y al final se nos ocurrió nuestra mejor idea: crear un fondo de inversión forestal. Eso se convirtió en EFM. Hoy en día, EFM es independiente de Ecotrust, es una empresa privada de inversión en tierras forestales con 14 empleados y más de 500 millones de dólares bajo gestión y asesoramiento.
¿Cuál es el propósito de EFM?
BVH: Nuestro objetivo es adquirir bosques en nombre de inversores y llevarlos hacia una condición futura deseada. Esa situación es una en la que son sólidos a nivel financiero, almacenan más carbono, producen hábitats de mayor calidad, protegen el agua, mejoran el suelo y generan beneficios para las personas y las comunidades, con especial énfasis en las comunidades tribales.
Queremos bosques sanos y productivos, que generen un flujo de beneficios para el medio ambiente y para las personas a largo plazo. Es en realidad bastante sencillo: gestionar los bosques como si importaran, y como si las personas importaran.
Imagen: María Fernanda Guerra
¿Cuáles son los primeros pasos con las nuevas adquisiciones?
BVH: Cuando compramos una propiedad forestal evaluamos cuál es la condición futura deseada. Siempre es específico del sitio y de la comunidad, pero muchos temas son similares. En muchos bosques, se trata de prolongar la edad de los árboles antes de que sean talados. En el Oeste americano, donde trabajamos, los árboles viven muchísimo. Coníferas como el abeto de Sitka, la cicuta occidental, el abeto de Douglas y el pino ponderosa pueden vivir mil años. Son muy productivas a los 70, 80, 90, 100 años; es cuando están en su mejor momento en cuanto a calidad y cantidad de madera.
Pero las edades de rotación han disminuido de manera considerable en la última década. Los árboles se talan ahora entre los 35 y 40 años, cuando son, en esencia, adolescentes, largos y delgados y producen solo un tronco de sierra. Los bosques naturales con especies y clases de edad diversas se han convertido en algo parecido a plantaciones. Nuestra intención es mover los bosques a rotaciones más largas, trabajar en la complejidad estructural —árboles de diferentes tamaños y alturas— y centrarnos en el sotobosque [la vegetación entre el dosel y el suelo del bosque].
¿En qué consiste eso?
BVH: Una práctica común en la región es rociar herbicidas y pesticidas en helicóptero dos veces durante el ciclo de siembra. Nosotros no hacemos eso. No hay herbicidas, ni pesticidas, salvo los necesarios para especies invasoras persistentes que no responden a otros controles. Hacemos crecer árboles hasta edades mucho más avanzadas y usamos el aclareo [la eliminación selectiva de árboles para reducir la densidad]. El aclareo comercial casi ha desaparecido por las rotaciones cortas, pero si haces crecer árboles hasta 60, 70, 80 años, el aclareo vuelve a tener sentido.
Eso crea bosques más saludables. La susceptibilidad a enfermedades y fuegos proviene de plantaciones de una sola especie y de edad única. Los bosques diversificados son más resistentes. La salud forestal es un factor principal, pero la productividad también es significativa. Lo hacemos en un contexto comercial, para inversores, con el objetivo de ofrecer buenos rendimientos. Al hacer crecer los árboles más viejos, se producen productos más valiosos, con más volumen por hectárea y a menor coste.
¿Cómo se gana dinero con los bosques?
BVH: Lo fundamental es que los árboles crecen y los bosques valoran activos. De acuerdo con la productividad y la antigüedad del lugar, los árboles pueden crecer tres, seis o incluso diez por ciento al año. Eso es poco común comparado con otros activos. Los bosques no necesitan cosechas anuales como la agricultura. Puedes retrasar las cosechas durante años, y los árboles tan solo se vuelven más valiosos. Eso da flexibilidad para programar las cosechas para los mercados. Si el mercado está malo un año, puedes aguantar, siempre que tu estructura de capital no requiera grandes pagos en efectivo. Esa flexibilidad también hace que los bosques sean excelentes para estrategias de carbono. Puedes extender las rotaciones durante 10, 20, 30 años, lo que hace que los bosques sean más valiosos mientras se programan las cosechas para los mercados de madera y carbono.
En EFM, hemos firmado contratos de carbono de diez años con Microsoft y otros, al vender créditos de carbono de nuestros proyectos. Así que la monetización proviene de la venta de madera, la venta de carbono y la apreciación del capital al vender propiedades apreciadas.
Imagen: David Herasimtschuk, Freshwaters Illustrated
Pero, ¿cómo demuestras el valor que aportas en términos de eliminación de CO2?
BVH: La respuesta es adicionalidad. Todos los bosques almacenan carbono, y para las especies arbóreas del Noroeste, el contenido de carbono está bien comprendido: solo hay que medir la altura, el diámetro y la estrechatura del árbol para hacer el cálculo. El carbono que se lleva a transacción (a través de créditos de carbono) representa reducciones o almacenamiento de emisiones que van más allá de lo que ocurriría bajo las prácticas empresariales estándar y las regulaciones existentes.
Si un bosque se tala a cielo cada 40 años, lo cual es una práctica común, no almacena carbono adicional y no calificaría bajo metodologías rigurosas de carbono. La adicionalidad es clave, en especial para compradores como Microsoft que buscan créditos de alta calidad.
Una innovación reciente son las líneas de base dinámicas. Una línea de base dinámica examina lo que está por encima de las prácticas comunes no solo al inicio de un proyecto, sino de manera periódica durante él. Si cambian las prácticas empresariales o la normativa, también cambia la línea base. De este modo, se prueba la adicionalidad a lo largo del proyecto para asegurar que en verdad se añade carbono más allá de lo que existiría sin ella.
¿Cómo evalúas millones de árboles?
BVH: La silvicultura realiza inventarios de madera desde hace mucho tiempo; ahora también lo hacemos para el carbono. Es estadístico. Seleccionas parcelas basándote en un diseño de muestreo aleatorio, las mides y extrapolas al bosque en su conjunto.
Se han comenzado a desarrollar tecnologías como drones, LIDAR [un sistema que funciona con el principio del radar, pero utiliza la luz de un láser] e imágenes aéreas, pero las metodologías de carbono aún no las han aceptado. Así que ahora mismo todo se hace mediante muestreo físico. Los equipos establecen parcelas con ubicaciones conocidas, seleccionadas al azar. Verificadores independientes terceros vuelven a medir esos gráficos para asegurarse de que el volumen de carbono que se negocia en verdad existe. Es un trabajo complejo. Las parcelas pueden estar en pendientes pronunciadas, a través de ríos, en cualquier lugar. Los equipos de inventario y los verificadores tienen que alcanzarlos y medirlos.
¿Qué ocurre si hay un incendio forestal masivo? ¿Es eso como un colapso financiero?
BVH: Sí. Incendios, enfermedades, viento… todo puede ocurrir. Eso se aborda a través de la permanencia, otro criterio clave. Los proyectos de carbono aportan créditos a un fondo de amortiguamiento. Si produces, por ejemplo, 100.000 créditos al año, pones una parte en el colchón, según el riesgo de tu proyecto. El Registro lo gestiona. Si hay una inversión involuntaria —un incendio— el entorno se completa a través de retirar créditos del buffer. Los verificadores evalúan el impacto del incendio, miden el carbono perdido y retiran los créditos correspondientes.
Imagen: Brett McGinley.
Cuéntame sobre los inversores en EFM.
BVH: Todos son inversores financieros, pero sus partes interesadas están motivadas a considerar inversiones sólidas que también generen un fuerte impacto social y medioambiental. Les importa la tasa de rentabilidad y el papel de la silvicultura en su cartera basándose en consideraciones financieras habituales. Pero también les importa el impacto – por ejemplo, algunos en verdad se preocupan por el salmón, y nuestra silvicultura está muy centrada en mejorar los hábitats y la recuperación del salmón. Pueden venir por los peces, por el carbono, por la biodiversidad o porque aman los bosques. Todos comparten nuestra creencia de que los rendimientos financieros superiores se logran mejor a través de crear un impacto ambiental y social junto con el valor económico.
¿Cuál fue el último gran bosque que tomaste?
BVH: La última gran propiedad que compramos es en realidad en la que participó Microsoft. Son 68.000 acres de selva templada costera en la península Olímpica, una propiedad impresionante. La península Olímpica se encuentra al oeste de Seattle, una extensión de tres millones de acres que es el punto más occidental de los Estados Unidos continentales. Está dominado por un parque nacional de casi un millón de acres que cuenta con picos glaciares, ríos de clase mundial y bosques antiguos que descienden hasta el océano Pacífico al oeste. Hay un refugio de vida silvestre a lo largo de la costa, lleno de rocas y pilas marinas que albergan millones de aves marinas, orcas y nutrias. El terreno que compramos ha sido terreno forestal comercial durante 80 años y está muy bien situado para el tipo de gestión forestal que planeamos implementar, que es aumentar la edad de rotación de los árboles, crear más complejidad estructural y trabajar en la restauración de los ríos. La selva tropical olímpica almacena más carbono que casi cualquier otro ecosistema terrestre, porque no hay fuego.
El respaldo de Microsoft para el proyecto fue fundamental. Además del acuerdo de compra de diez años que firmaron con nosotros, su respaldo dio a los inversores mucha confianza sobre el rendimiento financiero de este bosque y fue fundamental para que incorporáramos a otros inversores.
¿Qué te motiva a nivel personal en este trabajo?
BVH: Es la mezcla de lo natural y lo financiero. Es un diagrama de Venn fascinante. Para mí, los bosques se tratan de salud, productividad, resiliencia y beneficios a largo plazo para las personas y el medio ambiente. No puedo esperar a levantarme cada día y conseguir más capital para adquirir más bosques y moverlos por ese camino. Creo que forma parte de la ecuación de cómo vamos a prosperar en este planeta.
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 aquí.
AWS Lambda now supports up to 32 GB of memory and 16 vCPUs for functions running on Lambda Managed Instances, enabling customers to run compute-intensive workloads such as large-scale data processing, media transcoding, and scientific simulations without managing any infrastructure. Customers can also configure the memory-to-vCPU ratio — 2:1, 4:1, or 8:1 — to match the resource profile of their workload. Lambda Managed Instances lets you run Lambda functions on managed Amazon EC2 instances with built-in routing, load balancing, and auto-scaling, giving you access to specialized compute configurations including the latest-generation processors and high-bandwidth networking, with no operational overhead.
Customers building compute-intensive applications such as data processing pipelines, high-throughput API backends, and batch computation workloads require substantial memory and CPU resources to process large datasets, serve low-latency responses at scale, and run complex computations efficiently. Previously, function execution environments on Lambda Managed Instances were limited to 10 GB of memory and approximately 6 vCPUs, with no option to customize the memory-to-vCPU ratio. Functions on Lambda Managed Instances can now be configured with up to 32 GB of memory, and a choice of memory-to-vCPU ratio — 2:1, 4:1, or 8:1 — allowing customers to select the right balance of memory and compute for their workload. For example, at 32 GB of memory, customers can configure 16 vCPUs (2:1), 8 vCPUs (4:1), or 4 vCPUs (8:1) depending on whether their workload is CPU-intensive or memory-intensive.
This feature is available in all AWS Regions where Lambda Managed Instances is generally available. You can configure these settings using the AWS Console, AWS CLI, AWS CloudFormation, AWS CDK, or AWS SAM. To learn more, visit the AWS Lambda Managed Instances product page and documentation.
AWS Lambda now supports up to 32 GB of memory and 16 vCPUs for functions running on Lambda Managed Instances, enabling customers to run compute-intensive workloads such as large-scale data processing, media transcoding, and scientific simulations without managing any infrastructure. Customers can also configure the memory-to-vCPU ratio — 2:1, 4:1, or 8:1 — to match the resource profile of their workload. Lambda Managed Instances lets you run Lambda functions on managed Amazon EC2 instances with built-in routing, load balancing, and auto-scaling, giving you access to specialized compute configurations including the latest-generation processors and high-bandwidth networking, with no operational overhead. Customers building compute-intensive applications such as data processing pipelines, high-throughput API backends, and batch computation workloads require substantial memory and CPU resources to process large datasets, serve low-latency responses at scale, and run complex computations efficiently. Previously, function execution environments on Lambda Managed Instances were limited to 10 GB of memory and approximately 6 vCPUs, with no option to customize the memory-to-vCPU ratio. Functions on Lambda Managed Instances can now be configured with up to 32 GB of memory, and a choice of memory-to-vCPU ratio — 2:1, 4:1, or 8:1 — allowing customers to select the right balance of memory and compute for their workload. For example, at 32 GB of memory, customers can configure 16 vCPUs (2:1), 8 vCPUs (4:1), or 4 vCPUs (8:1) depending on whether their workload is CPU-intensive or memory-intensive. This feature is available in all AWS Regions where Lambda Managed Instances is generally available. You can configure these settings using the AWS Console, AWS CLI, AWS CloudFormation, AWS CDK, or AWS SAM. To learn more, visit the AWS Lambda Managed Instances product page and documentation.
Today, AWS announces the general availability of Visible services and Visible Regions account settings in the AWS Management Console. These settings allow you to customize which services and regions appear in the Management Console for authorized users in your account, helping your users easily identify what is available to them and simplifying navigation.
You can configure these settings in the AWS Management Console under Unified Settings in the Account Settings tab. You can also configure these setting programmatically via User Experience Customization (UXC) in AWS Command Line Interface (CLI), AWS Software Development Kits (SDKs), AWS Cloud Development Kit (CDK), or AWS CloudFormation. The Visible services and Visible Regions settings are available in AWS Commercial Regions at no additional cost.
Visit the AWS User Experience Customization documentation page and API guide to learn more.
Today, AWS announces the general availability of Visible services and Visible Regions account settings in the AWS Management Console. These settings allow you to customize which services and regions appear in the Management Console for authorized users in your account, helping your users easily identify what is available to them and simplifying navigation. You can configure these settings in the AWS Management Console under Unified Settings in the Account Settings tab. You can also configure these setting programmatically via User Experience Customization (UXC) in AWS Command Line Interface (CLI), AWS Software Development Kits (SDKs), AWS Cloud Development Kit (CDK), or AWS CloudFormation. The Visible services and Visible Regions settings are available in AWS Commercial Regions at no additional cost. Visit the AWS User Experience Customization documentation page and API guide to learn more.
AWS Step Functions expands its AWS SDK integrations with 28 additional services and over 1,100 new API actions across new and existing AWS services, including Amazon Bedrock AgentCore and Amazon S3 Vectors. This expansion enables you to orchestrate a broader set of AWS services directly from your workflows without writing integration code.
AWS Step Functions is a visual workflow service capable of orchestrating over 220 AWS services to help customers build distributed applications at scale. With the Amazon Bedrock AgentCore service integration, you can invoke AI agent runtimes with built-in retries, run multiple agents in parallel using Map states, and automate agent provisioning workflows that create, update, and tear down agent infrastructure as workflow steps. This expansion also includes Amazon S3 Vectors for automating document ingestion pipelines that populate knowledge bases for AI applications. It also adds support for AWS Lambda durable execution APIs, allowing you to pass an execution name for idempotent invocations of Lambda durable functions and manage durable executions directly from your workflows.
These enhancements are now generally available in all AWS Regions where AWS Step Functions is available. Specific services and API actions are subject to the availability of the target service in the AWS Region. To learn more about AWS Step Functions SDK integrations, visit the Developer Guide, or see the full list of supported services at AWS SDK service integrations.
AWS Step Functions expands its AWS SDK integrations with 28 additional services and over 1,100 new API actions across new and existing AWS services, including Amazon Bedrock AgentCore and Amazon S3 Vectors. This expansion enables you to orchestrate a broader set of AWS services directly from your workflows without writing integration code. AWS Step Functions is a visual workflow service capable of orchestrating over 220 AWS services to help customers build distributed applications at scale. With the Amazon Bedrock AgentCore service integration, you can invoke AI agent runtimes with built-in retries, run multiple agents in parallel using Map states, and automate agent provisioning workflows that create, update, and tear down agent infrastructure as workflow steps. This expansion also includes Amazon S3 Vectors for automating document ingestion pipelines that populate knowledge bases for AI applications. It also adds support for AWS Lambda durable execution APIs, allowing you to pass an execution name for idempotent invocations of Lambda durable functions and manage durable executions directly from your workflows. These enhancements are now generally available in all AWS Regions where AWS Step Functions is available. Specific services and API actions are subject to the availability of the target service in the AWS Region. To learn more about AWS Step Functions SDK integrations, visit the Developer Guide, or see the full list of supported services at AWS SDK service integrations.
Amazon Web Services (AWS) announces the availability of Amazon EC2 I8ge instances in Europe (Stockholm), Asia Pacific (Mumbai), Asia Pacific (Malaysia), Asia Pacific (Singapore), and Asia Pacific (Sydney) AWS regions. I8ge instances are powered by AWS Graviton4 processors to deliver up to 60% better compute performance compared to previous generation Graviton2-based storage optimized Amazon EC2 instances. I8ge instances use the third generation AWS Nitro SSDs, local NVMe storage that delivers up to 55% better real-time storage performance per TB. They offer up to 60% lower storage I/O latency and up to 75% lower storage I/O latency variability compared to previous generation Im4gn instances.
I8ge instances are storage-optimized instances offering up to 120TB of locally attached NVMe storage. They are ideal for workloads that demand rapid local storage with high random read/write performance and consistently low latency for accessing large datasets. These versatile instances are offered in eleven different sizes including two metal sizes, providing flexibility to match customers’ computational needs. They deliver up to 180 Gbps of network performance bandwidth and 60 Gbps of dedicated bandwidth for Amazon Elastic Block Store (EBS), ensuring fast and efficient data transfer for the most demanding applications.
Amazon Web Services (AWS) announces the availability of Amazon EC2 I8ge instances in Europe (Stockholm), Asia Pacific (Mumbai), Asia Pacific (Malaysia), Asia Pacific (Singapore), and Asia Pacific (Sydney) AWS regions. I8ge instances are powered by AWS Graviton4 processors to deliver up to 60% better compute performance compared to previous generation Graviton2-based storage optimized Amazon EC2 instances. I8ge instances use the third generation AWS Nitro SSDs, local NVMe storage that delivers up to 55% better real-time storage performance per TB. They offer up to 60% lower storage I/O latency and up to 75% lower storage I/O latency variability compared to previous generation Im4gn instances. I8ge instances are storage-optimized instances offering up to 120TB of locally attached NVMe storage. They are ideal for workloads that demand rapid local storage with high random read/write performance and consistently low latency for accessing large datasets. These versatile instances are offered in eleven different sizes including two metal sizes, providing flexibility to match customers’ computational needs. They deliver up to 180 Gbps of network performance bandwidth and 60 Gbps of dedicated bandwidth for Amazon Elastic Block Store (EBS), ensuring fast and efficient data transfer for the most demanding applications. To begin your Graviton journey, visit the Level up your compute with AWS Graviton page. To get started, see AWS Management Console, AWS Command Line Interface (AWS CLI), and AWS SDKs. To learn more, visit the I8ge instances page.
AWS HealthImaging now supports fine-grained access control, enabling organizations to securely manage access to medical imaging data at the DICOM study and series levels. Medical imaging workflows are typically organized around DICOM studies, which are stored in AWS HealthImaging as one or more image set resources. Now customers can easily grant users access to all image sets for a set of DICOM Studies or Series with easy-to-maintain IAM policies.
Customers can now grant permissions for DICOMweb APIs using DICOM Study Instance UIDs and Series Instance UIDs directly in their IAM policies, eliminating the need to list individual image set ARNs. Customers can now create dynamic, temporary access grants using AWS Security Token Service (STS) session policies with low-latency authentication. This capability provides enhanced protection for Protected Health Information (PHI) by scoping access grants to specific Studies or Series rather than entire data stores. This launch better supports use cases such as pathologist case-level access, radiology study sharing with external partners, and controlled research data distribution. To learn more, see the AWS HealthImaging Developer Guide.
AWS HealthImaging is a HIPAA-eligible service that empowers healthcare providers, life sciences organizations, and their software partners to store, analyze, and share medical images. AWS HealthImaging is generally available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Europe (Ireland), and Europe (London).
AWS HealthImaging now supports fine-grained access control, enabling organizations to securely manage access to medical imaging data at the DICOM study and series levels. Medical imaging workflows are typically organized around DICOM studies, which are stored in AWS HealthImaging as one or more image set resources. Now customers can easily grant users access to all image sets for a set of DICOM Studies or Series with easy-to-maintain IAM policies.
Customers can now grant permissions for DICOMweb APIs using DICOM Study Instance UIDs and Series Instance UIDs directly in their IAM policies, eliminating the need to list individual image set ARNs. Customers can now create dynamic, temporary access grants using AWS Security Token Service (STS) session policies with low-latency authentication. This capability provides enhanced protection for Protected Health Information (PHI) by scoping access grants to specific Studies or Series rather than entire data stores. This launch better supports use cases such as pathologist case-level access, radiology study sharing with external partners, and controlled research data distribution. To learn more, see the AWS HealthImaging Developer Guide.
AWS HealthImaging is a HIPAA-eligible service that empowers healthcare providers, life sciences organizations, and their software partners to store, analyze, and share medical images. AWS HealthImaging is generally available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), Europe (Ireland), and Europe (London).
