Amazon CloudWatch Synthetics multi-browser support is now available in the AWS GovCloud (US-East, US-West) Regions. This expansion enables customers in these two regions to test and monitor their web applications using both Chrome and Firefox browsers.

With this launch, you can run the same canary script across Chrome and Firefox when using Playwright-based canaries or Puppeteer-based canaries. CloudWatch Synthetics automatically collects browser-specific performance metrics, success rates, and visual monitoring results while maintaining an aggregate view of overall application health. This helps development and operations teams quickly identify and resolve browser compatibility issues that could affect application reliability.

To learn more about configuring multi-browser canaries, see the canary docs in the Amazon CloudWatch Synthetics User Guide. 

 

​Amazon CloudWatch Synthetics multi-browser support is now available in the AWS GovCloud (US-East, US-West) Regions. This expansion enables customers in these two regions to test and monitor their web applications using both Chrome and Firefox browsers. With this launch, you can run the same canary script across Chrome and Firefox when using Playwright-based canaries or Puppeteer-based canaries. CloudWatch Synthetics automatically collects browser-specific performance metrics, success rates, and visual monitoring results while maintaining an aggregate view of overall application health. This helps development and operations teams quickly identify and resolve browser compatibility issues that could affect application reliability. To learn more about configuring multi-browser canaries, see the canary docs in the Amazon CloudWatch Synthetics User Guide.   

AWS Config now supports 52 additional AWS resource types across key services including Amazon EC2, Amazon Bedrock, and Amazon SageMaker. This expansion provides greater coverage over your AWS environment, enabling you to more effectively discover, assess, audit, and remediate an even broader range of resources.

With this launch, if you have enabled recording for all resource types, then AWS Config will automatically track these new additions. The newly supported resource types are also available in Config rules and Config aggregators.

You can now use AWS Config to monitor the following newly supported resource types in all AWS Regions where the supported resources are available:

Resource Types
AWS::ApiGateway::DomainName	AWS::IAM::GroupPolicy
AWS::ApiGateway::Method	AWS::IAM::RolePolicy
AWS::ApiGateway::UsagePlan	AWS::IAM::UserPolicy
AWS::AppConfig::Extension	AWS::IoTCoreDeviceAdvisor::SuiteDefinition
AWS::Bedrock::ApplicationInferenceProfile	AWS::MediaPackageV2::Channel
AWS::Bedrock::Prompt	AWS::MediaPackageV2::ChannelGroup
AWS::BedrockAgentCore::BrowserCustom	AWS::MediaTailor::LiveSource
AWS::BedrockAgentCore::CodeInterpreterCustom	AWS::MSK::ServerlessCluster
AWS::BedrockAgentCore::Runtime	AWS::PaymentCryptography::Alias
AWS::CloudFormation::LambdaHook	AWS::PaymentCryptography::Key
AWS::CloudFormation::StackSet	AWS::RolesAnywhere::CRL
AWS::Comprehend::Flywheel	AWS::RolesAnywhere::Profile
AWS::Config::AggregationAuthorization	AWS::S3::AccessGrant
AWS::DataSync::Agent	AWS::S3::AccessGrantsInstance
AWS::Deadline::Fleet	AWS::S3::AccessGrantsLocation
AWS::Deadline::QueueFleetAssociation	AWS::SageMaker::DataQualityJobDefinition
AWS::EC2::IPAMPoolCidr	AWS::SageMaker::MlflowTrackingServer
AWS::EC2::SubnetNetworkAclAssociation	AWS::SageMaker::ModelBiasJobDefinition
AWS::EC2::VPCGatewayAttachment	AWS::SageMaker::ModelExplainabilityJobDefinition
AWS::ECR::RepositoryCreationTemplate	AWS::SageMaker::ModelQualityJobDefinition
AWS::ElasticLoadBalancingV2::TargetGroup	AWS::SageMaker::MonitoringSchedule
AWS::EMR::Studio	AWS::SageMaker::StudioLifecycleConfig
AWS::EMRContainers::VirtualCluster	AWS::SecretsManager::RotationSchedule
AWS::EMRServerless::Application	AWS::SES::DedicatedIpPool
AWS::EntityResolution::MatchingWorkflow	AWS::SES::MailManagerTrafficPolicy
AWS::Glue::Registry	AWS::SSM::ResourceDataSync

To view the complete list of AWS Config supported resource types, see the supported resource types page.

 

​AWS Config now supports 52 additional AWS resource types across key services including Amazon EC2, Amazon Bedrock, and Amazon SageMaker. This expansion provides greater coverage over your AWS environment, enabling you to more effectively discover, assess, audit, and remediate an even broader range of resources. With this launch, if you have enabled recording for all resource types, then AWS Config will automatically track these new additions. The newly supported resource types are also available in Config rules and Config aggregators. You can now use AWS Config to monitor the following newly supported resource types in all AWS Regions where the supported resources are available:

Resource Types
 

AWS::ApiGateway::DomainName
AWS::IAM::GroupPolicy

AWS::ApiGateway::Method
AWS::IAM::RolePolicy

AWS::ApiGateway::UsagePlan
AWS::IAM::UserPolicy

AWS::AppConfig::Extension
AWS::IoTCoreDeviceAdvisor::SuiteDefinition

AWS::Bedrock::ApplicationInferenceProfile
AWS::MediaPackageV2::Channel

AWS::Bedrock::Prompt
AWS::MediaPackageV2::ChannelGroup

AWS::BedrockAgentCore::BrowserCustom
AWS::MediaTailor::LiveSource

AWS::BedrockAgentCore::CodeInterpreterCustom        
AWS::MSK::ServerlessCluster

AWS::BedrockAgentCore::Runtime
AWS::PaymentCryptography::Alias

AWS::CloudFormation::LambdaHook
AWS::PaymentCryptography::Key

AWS::CloudFormation::StackSet
AWS::RolesAnywhere::CRL

AWS::Comprehend::Flywheel
AWS::RolesAnywhere::Profile

AWS::Config::AggregationAuthorization
AWS::S3::AccessGrant

AWS::DataSync::Agent
AWS::S3::AccessGrantsInstance

AWS::Deadline::Fleet
AWS::S3::AccessGrantsLocation

AWS::Deadline::QueueFleetAssociation
AWS::SageMaker::DataQualityJobDefinition

AWS::EC2::IPAMPoolCidr
AWS::SageMaker::MlflowTrackingServer

AWS::EC2::SubnetNetworkAclAssociation
AWS::SageMaker::ModelBiasJobDefinition

AWS::EC2::VPCGatewayAttachment
AWS::SageMaker::ModelExplainabilityJobDefinition

AWS::ECR::RepositoryCreationTemplate
AWS::SageMaker::ModelQualityJobDefinition

AWS::ElasticLoadBalancingV2::TargetGroup
AWS::SageMaker::MonitoringSchedule

AWS::EMR::Studio
AWS::SageMaker::StudioLifecycleConfig

AWS::EMRContainers::VirtualCluster
AWS::SecretsManager::RotationSchedule

AWS::EMRServerless::Application
AWS::SES::DedicatedIpPool

AWS::EntityResolution::MatchingWorkflow
AWS::SES::MailManagerTrafficPolicy

AWS::Glue::Registry
AWS::SSM::ResourceDataSync

To view the complete list of AWS Config supported resource types, see the supported resource types page.  

We’re excited to announce a simplified pricing model for Amazon Cognito’s machine-to-machine (M2M) authentication. Starting today we are removing the M2M app client pricing dimension, making it more cost-effective for customers to build and scale their M2M applications. Cognito supports applications that access API data with machine identities. Machine identities in user pools are clients that run on application servers and connect to remote APIs. Their operation happens without user interaction such as scheduled tasks, data streams, or asset updates. This change reduces the pricing of Cognito for customers using M2M authentication by removing the app client price dimension. Customers will continue to be charged based on the number of successful M2M token requests per month.

Previously, customers were charged for each M2M app client registered, regardless of usage amount, and each successful token request made by the app client to access a resource. With this change, customers will only pay for their successful token requests, making it more cost-effective to build and scale M2M applications using Amazon Cognito.

This pricing change is automatic and requires no action from customers. It is effective in all supported Amazon Cognito regions. To learn more about Amazon Cognito pricing, visit our pricing page. 

 

​We’re excited to announce a simplified pricing model for Amazon Cognito’s machine-to-machine (M2M) authentication. Starting today we are removing the M2M app client pricing dimension, making it more cost-effective for customers to build and scale their M2M applications. Cognito supports applications that access API data with machine identities. Machine identities in user pools are clients that run on application servers and connect to remote APIs. Their operation happens without user interaction such as scheduled tasks, data streams, or asset updates. This change reduces the pricing of Cognito for customers using M2M authentication by removing the app client price dimension. Customers will continue to be charged based on the number of successful M2M token requests per month. Previously, customers were charged for each M2M app client registered, regardless of usage amount, and each successful token request made by the app client to access a resource. With this change, customers will only pay for their successful token requests, making it more cost-effective to build and scale M2M applications using Amazon Cognito. This pricing change is automatic and requires no action from customers. It is effective in all supported Amazon Cognito regions. To learn more about Amazon Cognito pricing, visit our pricing page.   

• Categoría: Noticias de Microsoft

noviembre 3, 2025

Cómo las ciudades construyen infraestructuras resilientes con IA de confianza

Por: Doug Priest, gerente sénior de estrategia empresarial, Microsoft.

A medida que los extremos climáticos se intensifican y las poblaciones urbanas crecen, las ciudades enfrentan un desafío fundamental: construir infraestructura que sea resiliente a los impactos, sostenible para operar y realista para que las agencias la mantengan a lo largo del tiempo. La IA se ha convertido en una fuerza transformadora en este esfuerzo, para permitir a los líderes de las ciudades predecir riesgos, optimizar recursos y tomar decisiones más inteligentes que protejan a las comunidades y el medio ambiente.

En Microsoft, estamos orgullosos de asociarnos con gobiernos e innovadores de todo el mundo para avanzar en la infraestructura impulsada por IA. El último Informe de Tendencias Mundiales de Ciudades Inteligentes, desarrollado en colaboración con Microsoft, destaca cómo las ciudades pasan de la planificación reactiva a la resiliencia proactiva, a través de la IA para anticiparse, adaptarse y actuar.

Lean el Informe de tendencias mundiales de ciudades inteligentes

Pasar de la predicción a la preparación en la gestión de inundaciones de Yakarta

En Yakarta, Indonesia, las inundaciones han representado durante mucho tiempo una amenaza para millones de residentes. El programa Jakarta Smart City, en asociación con SAS¹, implementó una plataforma de análisis impulsada por IA que pronostica los riesgos de inundación con hasta seis horas de anticipación. Al integrar datos de sensores de lluvia, medidores de ríos y servicios meteorológicos, el sistema permite a las autoridades cerrar compuertas, activar bombas y emitir alertas a través de la aplicación JAKI antes de que ocurra un desastre.

Este cambio de la acción reactiva a la preventiva ejemplifica cómo la IA fortalece la resiliencia. Como explica Hannah Prior, líder de resiliencia climática para el sector público mundial de Microsoft:

«Ahora hemos comenzado a entrar en una era en la que en verdad no sabemos qué va a pasar después… En el pasado, los planificadores de la ciudad habrían dicho: ‘Planifiquemos una inundación de una en 100 años’. Pero ese tipo de eventos se han vuelto mucho más comunes y, por lo tanto, más difíciles de planificar».

Mejora de las operaciones con IA: la transformación de los servicios públicos de Evergy

En los Estados Unidos, Evergy, una empresa de servicios públicos que atiende a 1,7 millones de clientes en Kansas y Missouri, ha adoptado la IA y la automatización para transformar sus operaciones. Por medio de la Plataforma de energía de Microsoft, Evergy desarrolló más de 275 soluciones de automatización que ahorran más de 120,000 horas al año. Desde el procesamiento de imágenes con drones para inspecciones de líneas eléctricas hasta la extracción inteligente de datos para la gestión de inventarios, la IA ayuda a Evergy a mejorar la eficiencia, reducir los errores y mejorar la resiliencia en toda su infraestructura energética.

Estas innovaciones no solo agilizan los procesos internos, sino que también respaldan la transición de Evergy hacia una generación de energía más limpia, con adaptabilidad de la fuerza laboral y continuidad operativa en un panorama energético en rápida evolución.

Fortalecer la resiliencia hídrica para los desafíos futuros

En el sur de Francia, la Société du Canal de Provence (SCP) aborda el estrés hídrico a través de su programa REImu, una iniciativa de red de agua inteligente impulsada por  tecnologías de Microsoft Azure. Al integrar sensores de IoT, medidores inteligentes y plataformas de big data, SCP puede monitorear el consumo, detectar fugas y pronosticar la demanda en una red de distribución de 6,000 kilómetros. El sistema también combina datos meteorológicos y agrícolas para proporcionar consejos de riego adaptables y mejorar la preparación para la sequía.

La siguiente fase utilizará IA para refinar los pronósticos de consumo y detectar ineficiencias en automático, lo que convierte las redes de agua en sistemas basados en datos y resistentes al clima.

Adoptar un enfoque de sistema de sistemas para planificar la incertidumbre

Más allá de los casos de uso individuales, las ciudades han comenzado a adoptar un enfoque de sistema de sistemas, a través de la integración de datos en los dominios del agua, la energía, el transporte y el medio ambiente para modelar interacciones complejas y planificar de manera dinámica. Plataformas como Sentient Hubs en Australia ejemplifican este cambio, lo que permite la planificación de escenarios casi en tiempo real y la toma de decisiones colaborativa.

«En realidad se trata de pasar de un plan estático de inundaciones de cinco años en un PDF en un estante a un plan dinámico y vivo que existe como una plataforma digital… Las personas pueden acceder a él en cualquier momento para comprender, casi en tiempo real, lo que sucede en sus sistemas».

—Hannah Prior, líder de resiliencia climática para el sector público mundial de Microsoft

Este enfoque transforma la planificación de la resiliencia en un proceso activo y adaptativo, que evoluciona con cada nuevo conjunto de datos y permite a las ciudades responder a la incertidumbre con confianza.

Avanzar en la sostenibilidad y la eficiencia a través de la IA

El valor de la IA se extiende más allá de la resiliencia; también ayuda a las ciudades a cumplir con los objetivos de sostenibilidad. En Múnich, Alemania, la empresa municipal Stadtwerke München utiliza Microsoft Azure IoT y Azure AI para optimizar las operaciones de los autobuses eléctricos, pronosticar la demanda de energía y reducir el desperdicio. El noventa por ciento de la electricidad de Múnich ya proviene de fuentes renovables, y la IA ayuda a la ciudad a acercarse a la neutralidad total de carbono.

En Singapur, la iniciativa Smart P.U.B. utiliza miles de sensores y análisis de IA para detectar fugas y optimizar la distribución del agua, para lograr un ahorro de agua del 5% y roturas de tuberías casi nulas.² Estos ejemplos muestran cómo la IA puede reducir las emisiones, conservar los recursos y mejorar la prestación de servicios.

Construir infraestructuras responsables e inclusivas para todos

A medida que las ciudades escalan la infraestructura impulsada por IA, la gobernanza y la equidad deben mantenerse fundamentales. El Plan de IA 2025-2026 de Seattle establece un punto de referencia para el despliegue responsable, basado en principios de innovación, responsabilidad, equidad y transparencia.³ El plan exige la supervisión humana, prohíbe las aplicaciones dañinas e introduce un marco de prueba de valor para evaluar los proyectos de IA para un impacto responsable.

Utilizada de manera responsable, la IA puede democratizar la resiliencia, al hacer que la previsión sea asequible y accesible, reducir el sesgo en la toma de decisiones y asegurar que la infraestructura sirva a todas las comunidades de manera equitativa.

Únanse a nosotros en el Smart City Expo World Congress del 4 al 6 de noviembre

El camino hacia una infraestructura resiliente y sostenible está en marcha, y la IA está en el centro de él. Desde Yakarta hasta Kansas City, desde la Provenza hasta Múnich, las ciudades muestran lo que es posible cuando la tecnología se encuentra con el propósito.

Para obtener más información sobre cómo Microsoft y nuestros socios ayudan a las ciudades a construir una infraestructura preparada para el futuro, únanse a nosotros en el Smart City Expo World Congress 2025. Descubran las últimas innovaciones, conéctense con líderes mundiales y exploren cómo la IA puede ayudar a su ciudad a prosperar en medio de la incertidumbre.

¹ https://www.sas.com/sas/partners.html

² Detección y localización de anomalías habilitadas para gemelos digitales de alta fidelidad en Singapur | El año en infraestructura | Sistemas Bentley

³ Seattle lanza un plan de implementación de IA responsable – Smart Cities World, 25 de septiembre de 2025

Etiquetas:

• IA
• Innovación
• Sostenibilidad

The post Cómo las ciudades construyen infraestructuras resilientes con IA de confianza appeared first on Source LATAM.

 

​The post Cómo las ciudades construyen infraestructuras resilientes con IA de confianza appeared first on Source LATAM.  

Amazon CloudWatch agent now supports the collection of detailed performance metrics for NVMe local volumes on Amazon EC2 instances. These metrics give you insights into behavior and performance characteristics of your NVMe local storage.

The CloudWatch agent can now be configured to collect and send detailed NVMe metrics to CloudWatch, providing deeper visibility into storage performance. The new metrics include comprehensive performance indicators such as queue depths, I/O sizes, and device utilization. These metrics are similar to the detailed performance statistics available for EBS volumes, providing a consistent monitoring experience across both storage types. You can create CloudWatch dashboards, set alarms, and analyze trends for your NVMe-based instance store volumes.

Detailed performance statistics for Amazon EC2 instance store volumes via Amazon CloudWatch agent are available for all local NVMe volumes attached to Nitro-based EC2 instances in all AWS Commercial and AWS GovCloud (US) Regions. See the Amazon CloudWatch pricing page for CloudWatch pricing details.

To get started with detailed performance statistics for Amazon EC2 instance store volumes in CloudWatch, see Collect Amazon EC2 instance store volume NVMe driver metrics in the Amazon CloudWatch User Guide. To learn more about detailed performance statistics for Amazon EC2 instance store volumes, see Amazon EC2 instance store volumes in the Amazon EC2 User Guide.

 

​Amazon CloudWatch agent now supports the collection of detailed performance metrics for NVMe local volumes on Amazon EC2 instances. These metrics give you insights into behavior and performance characteristics of your NVMe local storage. The CloudWatch agent can now be configured to collect and send detailed NVMe metrics to CloudWatch, providing deeper visibility into storage performance. The new metrics include comprehensive performance indicators such as queue depths, I/O sizes, and device utilization. These metrics are similar to the detailed performance statistics available for EBS volumes, providing a consistent monitoring experience across both storage types. You can create CloudWatch dashboards, set alarms, and analyze trends for your NVMe-based instance store volumes. Detailed performance statistics for Amazon EC2 instance store volumes via Amazon CloudWatch agent are available for all local NVMe volumes attached to Nitro-based EC2 instances in all AWS Commercial and AWS GovCloud (US) Regions. See the Amazon CloudWatch pricing page for CloudWatch pricing details. To get started with detailed performance statistics for Amazon EC2 instance store volumes in CloudWatch, see Collect Amazon EC2 instance store volume NVMe driver metrics in the Amazon CloudWatch User Guide. To learn more about detailed performance statistics for Amazon EC2 instance store volumes, see Amazon EC2 instance store volumes in the Amazon EC2 User Guide.  

You can now monitor Mountpoint operations in observability tools such as Amazon CloudWatch, Prometheus, and Grafana. With this launch, Mountpoint emits near real-time metrics such as request count or request latency using OpenTelemetry Protocol (OTLP), an open source data transmission protocol. This means you can use applications such as CloudWatch agent or the OpenTelemetry (OTel) collector to publish the metrics into observability tools and create dashboards for monitoring and troubleshooting.

Previously, Mountpoint emitted operational data into log files, and you needed to create custom tools to parse the log files for insights. Now, when you mount your Amazon S3 bucket, you can configure Mountpoint to publish the metrics to an observability tool to proactively monitor issues that might impact your applications. For example, you can check if an application is unable to access S3 due to permission issues by analyzing the S3 request error metric that provides error types at an Amazon EC2 instance granularity.

Follow the step-by-step instructions to set up the CloudWatch agent or the OTel collector and configure Mountpoint to publish metrics into an observability tool. For more information, visit the Mountpoint for Amazon S3 GitHub repository, Mountpoint product page, and Mountpoint for Amazon S3 CSI driver GitHub page.

 

​You can now monitor Mountpoint operations in observability tools such as Amazon CloudWatch, Prometheus, and Grafana. With this launch, Mountpoint emits near real-time metrics such as request count or request latency using OpenTelemetry Protocol (OTLP), an open source data transmission protocol. This means you can use applications such as CloudWatch agent or the OpenTelemetry (OTel) collector to publish the metrics into observability tools and create dashboards for monitoring and troubleshooting. Previously, Mountpoint emitted operational data into log files, and you needed to create custom tools to parse the log files for insights. Now, when you mount your Amazon S3 bucket, you can configure Mountpoint to publish the metrics to an observability tool to proactively monitor issues that might impact your applications. For example, you can check if an application is unable to access S3 due to permission issues by analyzing the S3 request error metric that provides error types at an Amazon EC2 instance granularity. Follow the step-by-step instructions to set up the CloudWatch agent or the OTel collector and configure Mountpoint to publish metrics into an observability tool. For more information, visit the Mountpoint for Amazon S3 GitHub repository, Mountpoint product page, and Mountpoint for Amazon S3 CSI driver GitHub page.  

Amazon Route 53 Resolver now supports AWS PrivateLink. Customers can now access and manage Route 53 Resolver and all the related features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) privately, without going through the public internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely over the Amazon network. When Route 53 Resolver and its features are accessed via AWS PrivateLink, all operations, such as creating, deleting, editing, and listing, can be handled via the Amazon private network. 

Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs. Route 53 Resolver also offers features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) that you can opt-into. You can use Resolver and its features with AWS PrivateLink in regions where Route 53 Resolver and all its associated features are available today, including the AWS GovCloud (US) Regions. For more information about the AWS Regions where Resolver and its features are available, see here.

To learn more about Route 53 Resolver and its features, please refer to the service documentation.

 

​Amazon Route 53 Resolver now supports AWS PrivateLink. Customers can now access and manage Route 53 Resolver and all the related features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) privately, without going through the public internet. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises applications, securely over the Amazon network. When Route 53 Resolver and its features are accessed via AWS PrivateLink, all operations, such as creating, deleting, editing, and listing, can be handled via the Amazon private network.  Amazon Route 53 Resolver responds recursively to DNS queries from AWS resources for public records, Amazon VPC-specific DNS names, and Amazon Route 53 private hosted zones, and is available by default in all VPCs. Route 53 Resolver also offers features (Resolver endpoints, Route 53 Resolver DNS Firewall, Resolver Query Logging, Resolver for AWS Outposts) that you can opt-into. You can use Resolver and its features with AWS PrivateLink in regions where Route 53 Resolver and all its associated features are available today, including the AWS GovCloud (US) Regions. For more information about the AWS Regions where Resolver and its features are available, see here. To learn more about Route 53 Resolver and its features, please refer to the service documentation.  

Amazon Lightsail now offers three larger instance bundles with up to 64 vCPUs and 256 GB memory. The new instance bundles are available with Linux operating system (OS) and application blueprints, for both IPv6-only and dual-stack networking types. You can create instances using the new bundles with pre-configured Linux OS and application blueprints including WordPress, cPanel & WHM, Plesk, Drupal, Magento, MEAN, LAMP, Node.js, Amazon Linux, Ubuntu, CentOS, Debian, AlmaLinux, and Windows.

The new larger instance bundles enable you to scale your web applications and run more compute and memory intensive workloads in Lightsail. These higher performance instance bundles are ideal for general purpose workloads that require ability to handle large spikes in load. Using this new bundle, you can run web and application servers, large databases, virtual desktops, batch processing, enterprise applications, and more.

These new bundles now available in all AWS Regions where Amazon Lightsail is available. For more information on pricing, or to get started with your free account, click here.

 

​Amazon Lightsail now offers three larger instance bundles with up to 64 vCPUs and 256 GB memory. The new instance bundles are available with Linux operating system (OS) and application blueprints, for both IPv6-only and dual-stack networking types. You can create instances using the new bundles with pre-configured Linux OS and application blueprints including WordPress, cPanel & WHM, Plesk, Drupal, Magento, MEAN, LAMP, Node.js, Amazon Linux, Ubuntu, CentOS, Debian, AlmaLinux, and Windows. The new larger instance bundles enable you to scale your web applications and run more compute and memory intensive workloads in Lightsail. These higher performance instance bundles are ideal for general purpose workloads that require ability to handle large spikes in load. Using this new bundle, you can run web and application servers, large databases, virtual desktops, batch processing, enterprise applications, and more. These new bundles now available in all AWS Regions where Amazon Lightsail is available. For more information on pricing, or to get started with your free account, click here.  

Amazon Relational Database Service (RDS) now extends the Internet Protocol Version 6 (IPv6) support to publicly accessible databases, in addition to the existing support for privately accessible databases within a VPC. This allows you to configure dual-stack (IPv4 and IPv6) connectivity for your publicly accessible RDS and Aurora databases.

IPv6 provides an expanded address space, enabling you to scale your application on AWS beyond the limitations of IPv4 addresses. With IPv6, you can assign easy to manage contiguous IP ranges to micro-services and can get virtually unlimited scale for your applications. Moreover, with support for both IPv4 and IPv6, you can gradually transition applications from IPv4 to IPv6, enabling safer migration.

This feature is available in all AWS regions where IPv6 support for privately accessible RDS databases within a VPC is already available. Get started with the AWS CLI or AWS Management Console.

To learn more about configuring your environment for IPv6, please refer to the IPv6 User Guide.

 

​Amazon Relational Database Service (RDS) now extends the Internet Protocol Version 6 (IPv6) support to publicly accessible databases, in addition to the existing support for privately accessible databases within a VPC. This allows you to configure dual-stack (IPv4 and IPv6) connectivity for your publicly accessible RDS and Aurora databases. IPv6 provides an expanded address space, enabling you to scale your application on AWS beyond the limitations of IPv4 addresses. With IPv6, you can assign easy to manage contiguous IP ranges to micro-services and can get virtually unlimited scale for your applications. Moreover, with support for both IPv4 and IPv6, you can gradually transition applications from IPv4 to IPv6, enabling safer migration. This feature is available in all AWS regions where IPv6 support for privately accessible RDS databases within a VPC is already available. Get started with the AWS CLI or AWS Management Console. To learn more about configuring your environment for IPv6, please refer to the IPv6 User Guide.  

Amazon GameLift Streams is now integrated with AWS Health and will provide automated notifications about aging stream groups. Customers are sent regular reminders via AWS Health to re-create their stream groups starting as early as the 45th day to the 335th day from the stream group creation date. Stream groups older than 180 days are restricted from adding new applications and automatically expire after the 365th day.

This feature strengthens our customer’s security posture by helping customers manage the lifecycle of stream groups and prevent the use of outdated resources that might be missing updates. While the customer focuses on their game development, the service helps maintain the health of their resources.

AWS Health will send a reminder to the linked account on the 45th day and on the 150th day from the stream group creation day, informing customers that the stream group will be restricted from adding new applications after the 180-day. A last reminder to re-create the stream group will be sent on 335th day informing customers that the stream group will expire on the 365th day.

This feature is available in all AWS Regions where Amazon GameLift Streams is offered at no additional cost.

Maintenance warnings or the expiration date of a stream group can be viewed on the Stream group details page on the service console, or by using the ExpiresAt field in the GetStreamGroup API response.

To learn more about managing your stream groups and configuring notifications, visit the Amazon GameLift documentation on Stream group lifecycle.

 

​Amazon GameLift Streams is now integrated with AWS Health and will provide automated notifications about aging stream groups. Customers are sent regular reminders via AWS Health to re-create their stream groups starting as early as the 45th day to the 335th day from the stream group creation date. Stream groups older than 180 days are restricted from adding new applications and automatically expire after the 365th day. This feature strengthens our customer’s security posture by helping customers manage the lifecycle of stream groups and prevent the use of outdated resources that might be missing updates. While the customer focuses on their game development, the service helps maintain the health of their resources. AWS Health will send a reminder to the linked account on the 45th day and on the 150th day from the stream group creation day, informing customers that the stream group will be restricted from adding new applications after the 180-day. A last reminder to re-create the stream group will be sent on 335th day informing customers that the stream group will expire on the 365th day. This feature is available in all AWS Regions where Amazon GameLift Streams is offered at no additional cost. Maintenance warnings or the expiration date of a stream group can be viewed on the Stream group details page on the service console, or by using the ExpiresAt field in the GetStreamGroup API response. To learn more about managing your stream groups and configuring notifications, visit the Amazon GameLift documentation on Stream group lifecycle.