Publicado el Deja un comentario

Amazon SES now supports logging email sending events through AWS CloudTrail

Today, Amazon Simple Email Service (SES) launched support for logging email sending events through AWS CloudTrail. Customers can maintain a record of email send actions performed using the SES APIs, including actions taken by a user, role, or an AWS service in SES.

Previously, customers could use SES event destinations to route sending event notifications to custom data stores they created and managed themselves. This required custom solutions for data storage and data indexing, including development costs and operational oversight costs. Now, customers can configure event logging to AWS CloudTrail without any custom solution development. Customers can search for events, view the events, and download lists of events for processing in their private workflows. This gives customers a turn-key solution for event history management.

SES supports AWS CloudTrail data events for sending events in all AWS Regions where SES is available.

For more information, see the documentation on logging sending API calls with AWS CloudTrail.

 

​Today, Amazon Simple Email Service (SES) launched support for logging email sending events through AWS CloudTrail. Customers can maintain a record of email send actions performed using the SES APIs, including actions taken by a user, role, or an AWS service in SES. Previously, customers could use SES event destinations to route sending event notifications to custom data stores they created and managed themselves. This required custom solutions for data storage and data indexing, including development costs and operational oversight costs. Now, customers can configure event logging to AWS CloudTrail without any custom solution development. Customers can search for events, view the events, and download lists of events for processing in their private workflows. This gives customers a turn-key solution for event history management. SES supports AWS CloudTrail data events for sending events in all AWS Regions where SES is available. For more information, see the documentation on logging sending API calls with AWS CloudTrail.  

Publicado el Deja un comentario

La IA en el trabajo: Aceptar el punto de inflexión cognitivo de la IA

abril 11, 2025

La IA en el trabajo: Aceptar el punto de inflexión cognitivo de la IA

Las nuevas habilidades de la tecnología van a requerir una nueva división del trabajo.

Un círculo, con tres diamantes que representan la IA en el medio, y ilustraciones para cada una de las cinco tareas cognitivas mencionadas en el boletín: herramientas de redacción, lápiz y papel, gráficos y tablas, una lupa y una pila de libros.

Por Jared Spataro, CMO de IA en el Trabajo de Microsoft

En mi última columna, hablé de la nueva realidad de que la IA puede pensar y razonar a un nivel alto. Algún día miraremos hacia atrás y veremos esto como un punto de inflexión en la evolución de la tecnología, un cambio que tendrá un profundo impacto en la forma en que pensamos, organizamos y desplegamos el trabajo cognitivo.  

Cuando pienso en las habilidades actuales de la IA, considero estas cinco tareas cognitivas clave: percibir, comprender, razonar, ejecutar y crear. Observar cómo se maneja cada uno en su organización hoy en día puede ayudar a identificar oportunidades para que la IA aligere la carga.

Percepción: La percepción consiste en ver y dar sentido al mundo que loa rodea, y la IA puede percibir tanto en el mundo físico como en el digital.  

Los coches autónomos son un gran ejemplo de cómo la IA navega con habilidad por el mundo físico. Con la capacidad de identificar con precisión su entorno (carreteras, coches, bicicletas, peatones, señales, semáforos), la IA puede determinar cuándo detenerse, seguir y cambiar de dirección.

En el mundo digital, la percepción entra en juego con los agentes que usan computadoras, que pueden percibir e interactuar con las interfaces de las computadoras tal como lo hacen los humanos. Los CUA procesan datos de píxeles sin procesar para crear conciencia de lo que sucede en la pantalla y luego pueden interactuar con esa pantalla, al controlar un mouse y un teclado virtuales para hacer clic, desplazarse y escribir. Espero que las empresas los implementen en campos que van desde las ventas (ayudar en la generación de prospectos para completar formularios en automático) hasta el servicio al cliente (navegar por aplicaciones de software para encontrar y compartir información).

Comprensión: La comprensión va más allá de la percepción, se trata de ver patrones e interpretar el contexto. La capacidad de comprensión de la IA significa que puede interpretar, analizar y generar grandes cantidades de datos de texto para tareas como traducir documentos, resumir informes y evaluar los comentarios de los clientes para detectar tendencias emergentes. En el ámbito sanitario, puede ayudar a los médicos para la interpretación de las imágenes médicas y sugerir posibles diagnósticos. En finanzas, puede examinar los estados de pérdidas y ganancias y los datos de mercado para identificar señales que puedan indicar oportunidades o riesgos. 

Un ejemplo: Vodafone desplegó un agente que aprovecha las vastas bases de conocimiento internas de la empresa para mostrar con rapidez las especificaciones del producto, responder preguntas legales y más. Los equipos de ventas de la empresa de telecomunicaciones lo utilizan de manera regular para responder a las solicitudes de propuestas, lo que les da más tiempo para dedicarlo a una tarea que aprovecha las fortalezas cognitivas humanas: hablar con los clientes para comprender sus necesidades. 

Razonamiento: Lo he dicho antes: la capacidad de la IA para razonar  es uno de los mayores avances tecnológicos de nuestra vida. Los modelos de razonamiento resuelven problemas desafiantes al dividir una tarea en partes, analizar la amplitud del problema y elaborar un plan. En el camino, la IA toma muchas decisiones más pequeñas, como cambiar su estrategia y revertir el rumbo cuando sea necesario.  

Piensen en un crucigrama. Rellenan unas pocas palabras y luego descubren que algunas de sus primeras respuestas entran en conflicto con las nuevas pistas. Así que reevalúan, borran y prueban nuevas respuestas. Los modelos de razonamiento ahora pueden navegar con habilidad por este proceso iterativo de planificación y adaptación, y eso tiene grandes implicaciones para el negocio.

Imaginen usar esa capacidad para la investigación de varios pasos necesaria para crear un análisis competitivo o para producir visualizaciones de datos complejas que solo un científico de datos podría alguna vez. La IA de razonamiento puede realizar matemáticas al nivel de los humanos más hábiles y tiene un inmenso potencial para el descubrimiento científico. Cualquier parte de una empresa basada en el conocimiento se beneficiará de la IA de razonamiento.

Ejecución: El hecho de que la IA pueda ejecutar una tarea o responder a un aviso por sí sola no es nada nuevo, es el núcleo mismo de cómo funciona un modelo de aviso y respuesta. La «ejecución en el modelo» describe la capacidad de la IA para realizar tareas a través de utilizar sus capacidades internas. Este tipo de ejecución es autónoma, lo que significa que el modelo tiene todo lo que necesita, incluido el acceso a los datos necesarios, para completar una tarea.  

Pero lo que hace que la ejecución sea tan interesante, y algo que creo que será una de las mayores áreas de avance de la IA en 2025, es que vemos surgir una segunda forma de ejecución de la IA: la identificación y el uso de herramientas. Al igual que sabes que debes agarrar una regla cuando necesitas medir algo, la IA reconoce cuando necesita usar herramientas externas para completar una tarea que va más allá de sus capacidades inherentes.

Tomemos las matemáticas, por ejemplo. Por sí solos, los LLM son malos en matemáticas. Pero al mejorar sus capacidades de ejecución, pueden recurrir a herramientas externas o fuentes de conocimiento (como las capacidades de Python en Microsoft Excel) que les permiten ejecutar fórmulas matemáticas complejas. Esto desbloquea un potencial increíble para que la IA maneje de forma autónoma tareas empresariales, desde la creación de imágenes hasta la escritura de código y la visualización de datos, que requieren habilidades y capacidades más allá de su funcionalidad en el modelo.

Crear: De todas las tareas cognitivas, la creatividad es quizás la que está ligada de manera más estrecha a lo que nos hace humanos. La IA demuestra con rapidez que puede ser un poderoso socio creativo. Sobresale, por ejemplo, en la lluvia de ideas: puede generar sin cansancio cientos de nombres de productos o eslóganes (algunos mejores que otros) para que un equipo humano reaccione. En los negocios, puede producir todo, desde diseños conceptuales hasta presentaciones y videos de marketing. 

En la mayoría de los casos, lo que produce la IA es un punto de partida; los seres humanos lo elevan, al aportar su inteligencia emocional, sus matices y su experiencia vivida. Estas capacidades transforman las industrias de una manera que muchas personas, incluidos artistas y creadores, todavía están en proceso de asimilar.

No obstante, las buenas ideas son buenas ideas, sea cual sea la fuente. No buscar la opinión y la inspiración de la IA ahora es como trabajar con una mano atada a la espalda.

Lo que sigue

Hemos comenzado a entrar en un período de verdadera asociación de pensamiento entre los humanos y la IA, y todavía tratamos de entender dónde se encuentra la nueva división del trabajo. Todavía no tengo todas las respuestas, pero tengo algunos imperativos: a medida que los agentes comiencen a manejar muchas tareas cognitivas realizadas de manera tradicional por los trabajadores del conocimiento, las organizaciones necesitarán un nuevo enfoque para administrarlas. Y a medida que los agentes y los humanos colaboren, las organizaciones necesitarán nuevas formas de medir las contribuciones y el rendimiento de cada uno. 

Enfrentar este momento requerirá una nueva mentalidad que vaya más allá de pensar en la IA como un sustituto humano uno a uno. Los primeros intentos de máquinas voladoras fueron diseñados para batir sus alas, y los primeros coches eran «carruajes sin caballos». La verdadera innovación llega cuando vamos más allá de la imitación.

A pesar de los increíbles avances en IA en los últimos seis meses, muchos líderes todavía la ven como un medio de ejecución más rápida. Pero eso es solo la punta del iceberg. Ahora es el momento de avanzar en la asociación cognitiva de la IA con los humanos y aceptar todo su potencial para reinventar la forma en que trabajamos.

Para obtener más información sobre la IA y el futuro del trabajo, suscríbanse a este boletín.

The post La IA en el trabajo: Aceptar el punto de inflexión cognitivo de la IA appeared first on Source LATAM.

 

​The post La IA en el trabajo: Aceptar el punto de inflexión cognitivo de la IA appeared first on Source LATAM.  

Publicado el Deja un comentario

AWS Mainframe Modernization introduces advanced operations for runtime environments

We are excited to announce that AWS Mainframe Modernization service is now available with greater control of managed runtime environments that run modernized mainframe applications.

For both refactored and replatformed applications, you can now export data sets to an Amazon S3 bucket. Optionally, you can choose to encrypt the exported data set. This export feature makes it easier to move data set across environments, or to archive data sets.

For applications refactored with AWS Blu Age, you can now restart a batch job at a specific step. This enables advanced batch operational and recovery procedures.

For applications replatformed with Rocket Software, you can now configure your managed runtime application using a base configuration compatible with Rocket Enterprise Server deployed on non-managed environments. This base configuration provides flexibility by allowing numerous advanced configuration parameters supported by Rocket Enterprise Server, such as CICS or IMS granular parameters. It also allows transferring exported configuration parameters from a Rocket Enterprise Server deployed on Amazon EC2 to an AWS Mainframe Modernization managed runtime application.

These new features are available in any AWS Region where AWS Mainframe Modernization managed runtime is already deployed. To learn more, please visit AWS Mainframe Modernization product and documentation pages.
 

 

​We are excited to announce that AWS Mainframe Modernization service is now available with greater control of managed runtime environments that run modernized mainframe applications. For both refactored and replatformed applications, you can now export data sets to an Amazon S3 bucket. Optionally, you can choose to encrypt the exported data set. This export feature makes it easier to move data set across environments, or to archive data sets. For applications refactored with AWS Blu Age, you can now restart a batch job at a specific step. This enables advanced batch operational and recovery procedures. For applications replatformed with Rocket Software, you can now configure your managed runtime application using a base configuration compatible with Rocket Enterprise Server deployed on non-managed environments. This base configuration provides flexibility by allowing numerous advanced configuration parameters supported by Rocket Enterprise Server, such as CICS or IMS granular parameters. It also allows transferring exported configuration parameters from a Rocket Enterprise Server deployed on Amazon EC2 to an AWS Mainframe Modernization managed runtime application. These new features are available in any AWS Region where AWS Mainframe Modernization managed runtime is already deployed. To learn more, please visit AWS Mainframe Modernization product and documentation pages.    

Publicado el Deja un comentario

AWS Elemental Link UHD adds HD ingest rates as Link HD enters end of sale

AWS announces the end of sale for AWS Elemental Link HD devices effective April 15, 2024. AWS Elemental Link UHD devices will continue to be available for purchase. To support HD content contribution workflows, Link UHD has now added HD ingest pricing, providing a seamless path for new deployments. Existing Link HD devices will continue to be supported, with Link UHD now serving as the recommended solution for both HD and UHD contribution workflows.

To enable HD pricing on Link UHD devices, you can configure the device’s input resolution on the Link device configuration page when the device is not actively streaming. The configuration option provides the flexibility to optimize costs when contributing HD content through Link UHD devices.

This feature is available immediately in all AWS Regions where Link UHD is supported. The input resolution configuration option is accessible through the AWS Management Console for all Link UHD devices.

To learn more about Link UHD’s HD ingest rates and configuration options, visit the AWS Elemental Link documentation. For detailed pricing information, see AWS Elemental Link input pricing.
 

 

​AWS announces the end of sale for AWS Elemental Link HD devices effective April 15, 2024. AWS Elemental Link UHD devices will continue to be available for purchase. To support HD content contribution workflows, Link UHD has now added HD ingest pricing, providing a seamless path for new deployments. Existing Link HD devices will continue to be supported, with Link UHD now serving as the recommended solution for both HD and UHD contribution workflows. To enable HD pricing on Link UHD devices, you can configure the device’s input resolution on the Link device configuration page when the device is not actively streaming. The configuration option provides the flexibility to optimize costs when contributing HD content through Link UHD devices. This feature is available immediately in all AWS Regions where Link UHD is supported. The input resolution configuration option is accessible through the AWS Management Console for all Link UHD devices. To learn more about Link UHD’s HD ingest rates and configuration options, visit the AWS Elemental Link documentation. For detailed pricing information, see AWS Elemental Link input pricing.    

Publicado el Deja un comentario

Announcing 223 new AWS Config rules in AWS Control Tower

Today, AWS announces that AWS Control Tower supports an additional 223 managed Config rules in Control Catalog for various use cases such as security, cost, durability, and operations. With this launch, you can now search, discover, enable and manage these additional rules directly from AWS Control Tower and govern more use cases for your multi-account environment.

To get started, in AWS Control Tower go to the Control Catalog and search for controls with the implementation filter AWS Config, you will then see all the AWS Config rules present in the Catalog. If you find rules that are relevant for you, you can then directly enable them from the AWS Control Tower console. You can also use ListControls, GetControl and EnableControl APIs. With this launch we’ve updated ListControls and GetControl APIs to support three new fields: Create Time, Severity and Implementation, that you can use when searching for a control in Control Catalog. For example, you can now programmatically find high severity Config rules which were created after your previous evaluation.

You can search the new AWS Config rules in all AWS Regions where AWS Control Tower is available, including AWS GovCloud (US). When you want to deploy a rule, reference the list of supported regions for that rule to see where it can be enabled. To learn more, visit the AWS Control Tower User Guide.

 

​Today, AWS announces that AWS Control Tower supports an additional 223 managed Config rules in Control Catalog for various use cases such as security, cost, durability, and operations. With this launch, you can now search, discover, enable and manage these additional rules directly from AWS Control Tower and govern more use cases for your multi-account environment. To get started, in AWS Control Tower go to the Control Catalog and search for controls with the implementation filter AWS Config, you will then see all the AWS Config rules present in the Catalog. If you find rules that are relevant for you, you can then directly enable them from the AWS Control Tower console. You can also use ListControls, GetControl and EnableControl APIs. With this launch we’ve updated ListControls and GetControl APIs to support three new fields: Create Time, Severity and Implementation, that you can use when searching for a control in Control Catalog. For example, you can now programmatically find high severity Config rules which were created after your previous evaluation. You can search the new AWS Config rules in all AWS Regions where AWS Control Tower is available, including AWS GovCloud (US). When you want to deploy a rule, reference the list of supported regions for that rule to see where it can be enabled. To learn more, visit the AWS Control Tower User Guide.  

Publicado el Deja un comentario

Amazon Redshift Concurrency Scaling is now available in 2 additional regions

Amazon Redshift Concurrency Scaling is now available in Israel (Tel Aviv) and Canada West (Calgary) regions.

Amazon Redshift Concurrency Scaling elastically scales query processing power to provide consistently fast performance for hundreds of concurrent queries. Concurrency Scaling resources are added to your Redshift cluster transparently in seconds, as concurrency increases, to process queries without wait time. Amazon Redshift customers with an active Redshift cluster earn up to one hour of free Concurrency Scaling credits, which is sufficient for the concurrency needs of most customers. Concurrency scaling allows you to specify usage control providing customers with predictability in their month-to-month cost, even during periods of fluctuating analytical demand.

To enable Concurrency Scaling, set the Concurrency Scaling Mode to Auto in your Amazon Web Services Management Console. You can allocate Concurrency Scaling usage to specific user groups and workloads, control the number of Concurrency Scaling clusters that can be used, and monitor Cloudwatch performance and usage metrics.

To learn more about concurrency scaling including regional-availability, see our documentation and pricing page.

 

​Amazon Redshift Concurrency Scaling is now available in Israel (Tel Aviv) and Canada West (Calgary) regions. Amazon Redshift Concurrency Scaling elastically scales query processing power to provide consistently fast performance for hundreds of concurrent queries. Concurrency Scaling resources are added to your Redshift cluster transparently in seconds, as concurrency increases, to process queries without wait time. Amazon Redshift customers with an active Redshift cluster earn up to one hour of free Concurrency Scaling credits, which is sufficient for the concurrency needs of most customers. Concurrency scaling allows you to specify usage control providing customers with predictability in their month-to-month cost, even during periods of fluctuating analytical demand. To enable Concurrency Scaling, set the Concurrency Scaling Mode to Auto in your Amazon Web Services Management Console. You can allocate Concurrency Scaling usage to specific user groups and workloads, control the number of Concurrency Scaling clusters that can be used, and monitor Cloudwatch performance and usage metrics. To learn more about concurrency scaling including regional-availability, see our documentation and pricing page.  

Publicado el Deja un comentario

Amazon Corretto April 2025 Quarterly Updates

On Apr 15, 2025 Amazon announced quarterly security and critical updates for Amazon Corretto Long-Term Supported (LTS) and Feature Release (FR) versions of OpenJDK. Corretto 24.0.1, 21.0.7, 17.0.15, 11.0.27, 8u452 are now available for download. Amazon Corretto is a no-cost, multi-platform, production-ready distribution of OpenJDK.

Click on the Corretto home page to download Corretto 8, Corretto 11, Corretto 17, Corretto 21, or Corretto 24. You can also get the updates on your Linux system by configuring a Corretto Apt or Yum repo.

Feedback is welcomed!

 

​On Apr 15, 2025 Amazon announced quarterly security and critical updates for Amazon Corretto Long-Term Supported (LTS) and Feature Release (FR) versions of OpenJDK. Corretto 24.0.1, 21.0.7, 17.0.15, 11.0.27, 8u452 are now available for download. Amazon Corretto is a no-cost, multi-platform, production-ready distribution of OpenJDK. Click on the Corretto home page to download Corretto 8, Corretto 11, Corretto 17, Corretto 21, or Corretto 24. You can also get the updates on your Linux system by configuring a Corretto Apt or Yum repo. Feedback is welcomed!  

Publicado el Deja un comentario

AWS simplifies Amazon VPC Peering billing

Starting today, we are making it easier for customers to understand their inter-availability zone (AZ) VPC Peering usage within the same AWS Region by introducing a new usage type in their bill. These changes won’t affect customers’ charges and will help them easily understand their VPC Peering costs, enabling them to choose the right architecture based on cost, performance, and ease of management.

VPC Peering is an Amazon VPC feature that allows customers to establish networking connection between two VPCs, helping them route traffic between two VPCs using private IPv4 or IPv6 addresses. Previously, VPC Peering usage was reported under the intra-regional Data Transfer usage, making it difficult for customers to understand their VPC Peering usage and charges. With this launch, customers can now view their VPC Peering usage using the new usage type “Region_Name-VpcPeering-In/Out-Bytes” in Cost Explorer or Cost and Usage Report. Customers do not need to make any changes to their existing VPC Peering connections to benefit from this change, as these changes will be automatically applied.

There are no changes to the pricing for data transferred over VPC Peering connections. These changes will apply to all AWS commercial and the AWS Gov Cloud (US) Regions.
 

 

​Starting today, we are making it easier for customers to understand their inter-availability zone (AZ) VPC Peering usage within the same AWS Region by introducing a new usage type in their bill. These changes won’t affect customers’ charges and will help them easily understand their VPC Peering costs, enabling them to choose the right architecture based on cost, performance, and ease of management. VPC Peering is an Amazon VPC feature that allows customers to establish networking connection between two VPCs, helping them route traffic between two VPCs using private IPv4 or IPv6 addresses. Previously, VPC Peering usage was reported under the intra-regional Data Transfer usage, making it difficult for customers to understand their VPC Peering usage and charges. With this launch, customers can now view their VPC Peering usage using the new usage type “Region_Name-VpcPeering-In/Out-Bytes” in Cost Explorer or Cost and Usage Report. Customers do not need to make any changes to their existing VPC Peering connections to benefit from this change, as these changes will be automatically applied. There are no changes to the pricing for data transferred over VPC Peering connections. These changes will apply to all AWS commercial and the AWS Gov Cloud (US) Regions.    

Publicado el Deja un comentario

Amazon EC2 I4g instances are now available in South America (Sao Paulo) region

Starting today, Amazon Elastic Compute Cloud (EC2) I4g storage-optimized instances powered by AWS Graviton2 processors and 2nd generation AWS Nitro SSDs are now available in the South America (Sao Paulo) region.

I4g instances are optimized for workloads performing a high mix of random read/write operations and requiring very low I/O latency and high compute performance, such as transactional databases (MySQL, and PostgreSQL), real-time databases including in-memory databases, NoSQL databases, time-series databases (Clickhouse, Apache Druid, MongoDB) and real-time analytics such as Apache Spark.

Get started with I4g instances by visiting the AWS Management Console, AWS Command Line Interface (CLI), or AWS SDKs. To learn more, visit the I4g instances page.

 

 

 

​Starting today, Amazon Elastic Compute Cloud (EC2) I4g storage-optimized instances powered by AWS Graviton2 processors and 2nd generation AWS Nitro SSDs are now available in the South America (Sao Paulo) region.
I4g instances are optimized for workloads performing a high mix of random read/write operations and requiring very low I/O latency and high compute performance, such as transactional databases (MySQL, and PostgreSQL), real-time databases including in-memory databases, NoSQL databases, time-series databases (Clickhouse, Apache Druid, MongoDB) and real-time analytics such as Apache Spark. Get started with I4g instances by visiting the AWS Management Console, AWS Command Line Interface (CLI), or AWS SDKs. To learn more, visit the I4g instances page.
 
   

Publicado el Deja un comentario

Load Balancer Capacity Unit Reservation for Gateway Load Balancers

Gateway Load Balancer (GWLB) now supports Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum bandwidth capacity for your load balancer, complementing its existing ability to auto-scale based on your traffic pattern.

Gateway Load Balancer helps you deploy, scale, and manage third-party virtual appliances. With this feature, you can reserve a guaranteed capacity for anticipated traffic surge. The LCU reservation is ideal for scenarios such as onboarding and migrating new workload to your GWLB gated services without the need to wait for organic scaling, or maintaining a minimum bandwidth capacity for your firewall applications to meet specific SLA or compliance requirements. When using this feature, you pay only for the reserved LCUs and any additional usage above the reservation. You can easily configure this feature through the ELB console or API.

The feature is available for GWLB in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm) AWS Regions. This feature is not supported on Gateway Load Balancer Endpoint (GWLBe). To learn more, please refer to the GWLB documentation.

 

​Gateway Load Balancer (GWLB) now supports Load Balancer Capacity Unit (LCU) Reservation that allows you to proactively set a minimum bandwidth capacity for your load balancer, complementing its existing ability to auto-scale based on your traffic pattern. Gateway Load Balancer helps you deploy, scale, and manage third-party virtual appliances. With this feature, you can reserve a guaranteed capacity for anticipated traffic surge. The LCU reservation is ideal for scenarios such as onboarding and migrating new workload to your GWLB gated services without the need to wait for organic scaling, or maintaining a minimum bandwidth capacity for your firewall applications to meet specific SLA or compliance requirements. When using this feature, you pay only for the reserved LCUs and any additional usage above the reservation. You can easily configure this feature through the ELB console or API. The feature is available for GWLB in US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), and Europe (Stockholm) AWS Regions. This feature is not supported on Gateway Load Balancer Endpoint (GWLBe). To learn more, please refer to the GWLB documentation.