AWS WAF now includes 500 MB of CloudWatch Logs Vended Logs Ingestion for every 1 million WAF requests processed, at no additional cost. This helps customers better manage their WAF logging costs while maintaining comprehensive security visibility.

WAF logs in CloudWatch provide valuable insights for security analysis, compliance, and troubleshooting. Customers can leverage CloudWatch’s advanced analytics capabilities, including Log Insights queries, anomaly detection, and dashboards, to monitor and analyze their web application traffic patterns and security events. The included logs allocation is automatically applied based on WAF requests usage on your AWS bill at month end, making it easy to take advantage of the new pricing.

The free WAF logs allocation is across WAF specific Vended Logs to CloudWatch, S3, and Firehose. Usage beyond the included 500 MB per 1 million WAF requests will be charged at AWS WAF specific Vended Logs pricing in CloudWatch. For pricing details, please visit the AWS WAF pricing page.

To learn more about WAF logging capabilities and how to get started, visit the AWS WAF documentation.

 

​AWS WAF now includes 500 MB of CloudWatch Logs Vended Logs Ingestion for every 1 million WAF requests processed, at no additional cost. This helps customers better manage their WAF logging costs while maintaining comprehensive security visibility. WAF logs in CloudWatch provide valuable insights for security analysis, compliance, and troubleshooting. Customers can leverage CloudWatch’s advanced analytics capabilities, including Log Insights queries, anomaly detection, and dashboards, to monitor and analyze their web application traffic patterns and security events. The included logs allocation is automatically applied based on WAF requests usage on your AWS bill at month end, making it easy to take advantage of the new pricing. The free WAF logs allocation is across WAF specific Vended Logs to CloudWatch, S3, and Firehose. Usage beyond the included 500 MB per 1 million WAF requests will be charged at AWS WAF specific Vended Logs pricing in CloudWatch. For pricing details, please visit the AWS WAF pricing page. To learn more about WAF logging capabilities and how to get started, visit the AWS WAF documentation.  

Etiquetas:

• IA
• Salud
• Tecnología

The post El grupo Ribera utiliza tecnología de IA para ayudar a pacientes y médicos appeared first on Source LATAM.

 

​The post El grupo Ribera utiliza tecnología de IA para ayudar a pacientes y médicos appeared first on Source LATAM.  

AWS Config now tracks resource tags for IAM policy resource types, enhancing the granularity of metadata you can capture to assess, audit, and evaluate configurations of your IAM policies.

With this enhancement, you can now track resource tags and their changes for IAM Policies directly in your Config recorder. This capability allows you to scope both Config-managed and custom rule evaluations based on resource tags, ensuring your IAM policies maintain desired configurations. Additionally, you can leverage Config aggregators to selectively aggregate IAM policies across multiple accounts using tags, streamlining your multi-account governance.

This feature is now available across all supported AWS Regions at no additional cost. Resource tags are automatically populated in Config when you record IAM policy resource types. For recording IAM policy resource type in your Config recorder, please refer our documentation.

 

​AWS Config now tracks resource tags for IAM policy resource types, enhancing the granularity of metadata you can capture to assess, audit, and evaluate configurations of your IAM policies. With this enhancement, you can now track resource tags and their changes for IAM Policies directly in your Config recorder. This capability allows you to scope both Config-managed and custom rule evaluations based on resource tags, ensuring your IAM policies maintain desired configurations. Additionally, you can leverage Config aggregators to selectively aggregate IAM policies across multiple accounts using tags, streamlining your multi-account governance. This feature is now available across all supported AWS Regions at no additional cost. Resource tags are automatically populated in Config when you record IAM policy resource types. For recording IAM policy resource type in your Config recorder, please refer our documentation.  

Amazon Relational Database Service (Amazon RDS) for SQL Server now supports the latest General Distribution Release (GDR) updates for Microsoft SQL Server. This release includes support for Microsoft SQL Server 2016 SP3 KB5063762 (RDS version 13.00.6465.1.v1), SQL Server 2017 CU31 KB5063759 (RDS version 14.00.3500.1.v1), SQL Server 2019 CU32 KB5063757 (RDS version 15.00.4440.1.v1) and SQL Server 2022 CU20 KB5063814 (RDS version 16.00.4210.1.v1).

The GDR updates address vulnerabilities described in CVE-2025-49758, CVE-2025-24999, CVE-2025-49759, CVE-2025-53727, and CVE-2025-47954. For additional information on the improvements and fixes included in these updates, see Microsoft documentation for KB5063762, KB5063759, KB5063757 and KB5063814. We recommend that you upgrade your Amazon RDS for SQL Server instances to apply these updates using Amazon RDS Management Console, or by using the AWS SDK or CLI. You can learn more about upgrading your database instance in the Amazon RDS SQL Server User Guide for upgrading your RDS Microsoft SQL Server DB engine.

 

​Amazon Relational Database Service (Amazon RDS) for SQL Server now supports the latest General Distribution Release (GDR) updates for Microsoft SQL Server. This release includes support for Microsoft SQL Server 2016 SP3 KB5063762 (RDS version 13.00.6465.1.v1), SQL Server 2017 CU31 KB5063759 (RDS version 14.00.3500.1.v1), SQL Server 2019 CU32 KB5063757 (RDS version 15.00.4440.1.v1) and SQL Server 2022 CU20 KB5063814 (RDS version 16.00.4210.1.v1). The GDR updates address vulnerabilities described in CVE-2025-49758, CVE-2025-24999, CVE-2025-49759, CVE-2025-53727, and CVE-2025-47954. For additional information on the improvements and fixes included in these updates, see Microsoft documentation for KB5063762, KB5063759, KB5063757 and KB5063814. We recommend that you upgrade your Amazon RDS for SQL Server instances to apply these updates using Amazon RDS Management Console, or by using the AWS SDK or CLI. You can learn more about upgrading your database instance in the Amazon RDS SQL Server User Guide for upgrading your RDS Microsoft SQL Server DB engine.  

AWS Elemental MediaConvert now integrates with Time-Addressable Media Store (TAMS), enabling customers to temporally reference and extract media asset segments. This capability allows MediaConvert customers to work more efficiently meet quick turn around deadlines. With TAMS integration, customers can extract highlights from live events for near real-time social media publishing, repurpose archived broadcast content into fresh programming or documentaries, and streamline media operations by connecting directly to existing broadcast infrastructure and content management systems.

This integration is designed for customers who operate their own TAMS servers—MediaConvert does not host or manage a TAMS instance. By leveraging your own TAMS deployment, MediaConvert can ingest time-based media segments on demand and use them as inputs in your encoding workflows. Whether you’re modernizing a legacy archive, building automation around editorial workflows, or enabling UGC teams to clip and publish with precision, the combination of MediaConvert and TAMS provides a powerful foundation for flexible, high-performance media processing at scale.

Please visit the TAMS specification and MediaConvert’s documentation for more information on this new feature.

 

​AWS Elemental MediaConvert now integrates with Time-Addressable Media Store (TAMS), enabling customers to temporally reference and extract media asset segments. This capability allows MediaConvert customers to work more efficiently meet quick turn around deadlines. With TAMS integration, customers can extract highlights from live events for near real-time social media publishing, repurpose archived broadcast content into fresh programming or documentaries, and streamline media operations by connecting directly to existing broadcast infrastructure and content management systems. This integration is designed for customers who operate their own TAMS servers—MediaConvert does not host or manage a TAMS instance. By leveraging your own TAMS deployment, MediaConvert can ingest time-based media segments on demand and use them as inputs in your encoding workflows. Whether you’re modernizing a legacy archive, building automation around editorial workflows, or enabling UGC teams to clip and publish with precision, the combination of MediaConvert and TAMS provides a powerful foundation for flexible, high-performance media processing at scale. Please visit the TAMS specification and MediaConvert’s documentation for more information on this new feature.  

Amazon Relational Database Service (Amazon RDS) Custom for SQL Server now supports the latest General Distribution Release (GDR) updates for Microsoft SQL Server. This includes support for Microsoft SQL Server 2019 CU32 KB5063757 (RDS version 15.00.4440.1.v1) and SQL Server 2022 CU20 KB5063814 (RDS version 16.00.4210.1.v1).

The GDR updates address vulnerabilities described in CVE-2025-49758, CVE-2025-24999, CVE-2025-49759, CVE-2025-53727, and CVE-2025-47954. For additional information on the improvements and fixes included in these updates, please see Microsoft documentation for KB5063757 and KB5063814. We recommend that you upgrade your Amazon RDS Custom for SQL Server instances to apply these updates using Amazon RDS Management Console, or by using the AWS SDK or CLI. You can learn more about upgrading your database instance in the Amazon RDS Custom User Guide.

 

​Amazon Relational Database Service (Amazon RDS) Custom for SQL Server now supports the latest General Distribution Release (GDR) updates for Microsoft SQL Server. This includes support for Microsoft SQL Server 2019 CU32 KB5063757 (RDS version 15.00.4440.1.v1) and SQL Server 2022 CU20 KB5063814 (RDS version 16.00.4210.1.v1). The GDR updates address vulnerabilities described in CVE-2025-49758, CVE-2025-24999, CVE-2025-49759, CVE-2025-53727, and CVE-2025-47954. For additional information on the improvements and fixes included in these updates, please see Microsoft documentation for KB5063757 and KB5063814. We recommend that you upgrade your Amazon RDS Custom for SQL Server instances to apply these updates using Amazon RDS Management Console, or by using the AWS SDK or CLI. You can learn more about upgrading your database instance in the Amazon RDS Custom User Guide.  

Amazon CloudFront announces support for hybrid post-quantum key establishment across all existing Transport Layer Security (TLS) security policies, providing enhanced protection against future quantum computing threats for client-to-edge connections. Additionally, CloudFront launched a new TLS 1.3 only security policy that enhances TLS options between viewers and edge locations. These updates allow customers to leverage quantum-resistant encryption while having more flexibility in configuring their CloudFront distributions to meet specific security and compliance requirements.

The post-quantum cryptography (PQC) capabilities are automatically enabled for client-to-edge connections, providing future-proof encryption that ensures long-term data security and regulatory compliance readiness. PQC support is available on all existing security policies by default, requiring no customer configuration. The new TLS1.3_2025 policy, which supports TLS 1.3 only, enables customers to leverage the latest TLS protocol, which provides improved security and performance compared to earlier TLS versions. This is particularly useful for organizations that enforce using the most up-to-date security standards.

These PQC capabilities and new security policy are available in all CloudFront edge locations. There are no additional charges for using PQC or the TLS1.3_2025 policy. To learn more about Post Quantum Cryptography and this new TLS policy and how to implement them in your CloudFront distributions, visit the CloudFront documentation. CloudFront documentation.

 

​Amazon CloudFront announces support for hybrid post-quantum key establishment across all existing Transport Layer Security (TLS) security policies, providing enhanced protection against future quantum computing threats for client-to-edge connections. Additionally, CloudFront launched a new TLS 1.3 only security policy that enhances TLS options between viewers and edge locations. These updates allow customers to leverage quantum-resistant encryption while having more flexibility in configuring their CloudFront distributions to meet specific security and compliance requirements. The post-quantum cryptography (PQC) capabilities are automatically enabled for client-to-edge connections, providing future-proof encryption that ensures long-term data security and regulatory compliance readiness. PQC support is available on all existing security policies by default, requiring no customer configuration. The new TLS1.3_2025 policy, which supports TLS 1.3 only, enables customers to leverage the latest TLS protocol, which provides improved security and performance compared to earlier TLS versions. This is particularly useful for organizations that enforce using the most up-to-date security standards. These PQC capabilities and new security policy are available in all CloudFront edge locations. There are no additional charges for using PQC or the TLS1.3_2025 policy. To learn more about Post Quantum Cryptography and this new TLS policy and how to implement them in your CloudFront distributions, visit the CloudFront documentation. CloudFront documentation.  

Amazon Relational Database Service (RDS) Proxy now offers customers the option to use Internet Protocol version 6 (IPv6) addresses to pool and share database connections coming from an application. The existing endpoints supporting Internet Protocol version 4 (IPv4) will remain available for backwards compatibility. Additionally, customers now have the option to specify RDS Proxy target connections using either IPv4 or IPv6.

The continued growth of the Internet, particularly in the areas of mobile applications, connected devices, and IoT, has spurred an industry-wide move to IPv6. IPv6 increases the number of available addresses by several orders of magnitude so customers no longer need to manage overlapping address spaces in their VPCs.

Many applications, including those built on modern serverless architectures, may need to have a high number of open connections to the database or may frequently open and close database connections, exhausting the database memory and compute resources. Amazon RDS Proxy allows applications to pool and share database connections, improving your database efficiency and application scalability.

For information on supported database engine versions and regional availability of RDS Proxy, refer to our RDS and Aurora documentations.

 

​Amazon Relational Database Service (RDS) Proxy now offers customers the option to use Internet Protocol version 6 (IPv6) addresses to pool and share database connections coming from an application. The existing endpoints supporting Internet Protocol version 4 (IPv4) will remain available for backwards compatibility. Additionally, customers now have the option to specify RDS Proxy target connections using either IPv4 or IPv6. The continued growth of the Internet, particularly in the areas of mobile applications, connected devices, and IoT, has spurred an industry-wide move to IPv6. IPv6 increases the number of available addresses by several orders of magnitude so customers no longer need to manage overlapping address spaces in their VPCs. Many applications, including those built on modern serverless architectures, may need to have a high number of open connections to the database or may frequently open and close database connections, exhausting the database memory and compute resources. Amazon RDS Proxy allows applications to pool and share database connections, improving your database efficiency and application scalability. For information on supported database engine versions and regional availability of RDS Proxy, refer to our RDS and Aurora documentations.  

Today, AWS announced the general availability of Amazon GuardDuty custom threat detection using entity lists. This new feature enhances threat detection capabilities in GuardDuty by extending support to incorporate your own domain-based threat intelligence into the service beyond originally supported custom IP list. You can now detect threats in GuardDuty using malicious domains or IP addresses defined in your custom threat list. As part of this update, GuardDuty introduces a new finding type, Impact:EC2/MaliciousDomainRequest.Custom, which is triggered when activity related to a domain in your custom threat list is detected. Additionally, you can use entity lists to suppress alerts from trusted sources, giving you greater control over your threat detection strategy.

Entity lists offer enhanced flexibility compared to the previous IP address lists. These new lists can include IP addresses, domains, or both, allowing for more comprehensive threat intelligence integration. Unlike the legacy IP list format, entity lists provides simplified permission management and avoids impacting IAM policy size limits across multiple AWS Regions, making it easier to implement and manage custom threat detection across your AWS environment.

GuardDuty custom entity list is available in all AWS Regions where GuardDuty is offered, excluding China Regions and GovCloud (US) Regions. 

 

​Today, AWS announced the general availability of Amazon GuardDuty custom threat detection using entity lists. This new feature enhances threat detection capabilities in GuardDuty by extending support to incorporate your own domain-based threat intelligence into the service beyond originally supported custom IP list. You can now detect threats in GuardDuty using malicious domains or IP addresses defined in your custom threat list. As part of this update, GuardDuty introduces a new finding type, Impact:EC2/MaliciousDomainRequest.Custom, which is triggered when activity related to a domain in your custom threat list is detected. Additionally, you can use entity lists to suppress alerts from trusted sources, giving you greater control over your threat detection strategy. Entity lists offer enhanced flexibility compared to the previous IP address lists. These new lists can include IP addresses, domains, or both, allowing for more comprehensive threat intelligence integration. Unlike the legacy IP list format, entity lists provides simplified permission management and avoids impacting IAM policy size limits across multiple AWS Regions, making it easier to implement and manage custom threat detection across your AWS environment. GuardDuty custom entity list is available in all AWS Regions where GuardDuty is offered, excluding China Regions and GovCloud (US) Regions.   

Amazon Aurora PostgreSQL Limitless Database is now available with PostgreSQL version 16.9 compatibility. This release contains product improvements and bug fixes made by the PostgreSQL community, along with Aurora Limitless-specific additions such as support for the hstore extension, the auto_explain extension, and various performance improvements. The hstore extension allows for storing sets of key/value pairs within a single PostgreSQL value, while the auto-explain extension logs execution plans of slow statements automatically.

Aurora PostgreSQL Limitless Database makes it easy for you to scale your relational database workloads by providing a serverless endpoint that automatically distributes data and queries across multiple Amazon Aurora Serverless instances while maintaining the transactional consistency of a single database. Aurora PostgreSQL Limitless Database offers capabilities such as distributed query planning and transaction management, removing the need for you to create custom solutions or manage multiple databases to scale. As your workloads increase, Aurora PostgreSQL Limitless Database adds compute resources while staying within your specified budget, so there is no need to provision for peak, and compute automatically scales down when demand is low.

Aurora PostgreSQL Limitless Database is available in the following AWS Regions: US East (N. Virginia, Ohio), US West (N. California, Oregon), Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Thailand, Tokyo), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), Middle East (Bahrain, UAE), and South America (Sao Paulo).

For pricing details, visit Amazon Aurora pricing. To learn more, read the Aurora PostgreSQL Limitless Database documentation and get started by creating an Aurora PostgreSQL Limitless Database in only a few steps in the Amazon RDS console.

 

​Amazon Aurora PostgreSQL Limitless Database is now available with PostgreSQL version 16.9 compatibility. This release contains product improvements and bug fixes made by the PostgreSQL community, along with Aurora Limitless-specific additions such as support for the hstore extension, the auto_explain extension, and various performance improvements. The hstore extension allows for storing sets of key/value pairs within a single PostgreSQL value, while the auto-explain extension logs execution plans of slow statements automatically. Aurora PostgreSQL Limitless Database makes it easy for you to scale your relational database workloads by providing a serverless endpoint that automatically distributes data and queries across multiple Amazon Aurora Serverless instances while maintaining the transactional consistency of a single database. Aurora PostgreSQL Limitless Database offers capabilities such as distributed query planning and transaction management, removing the need for you to create custom solutions or manage multiple databases to scale. As your workloads increase, Aurora PostgreSQL Limitless Database adds compute resources while staying within your specified budget, so there is no need to provision for peak, and compute automatically scales down when demand is low. Aurora PostgreSQL Limitless Database is available in the following AWS Regions: US East (N. Virginia, Ohio), US West (N. California, Oregon), Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Thailand, Tokyo), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), Middle East (Bahrain, UAE), and South America (Sao Paulo). For pricing details, visit Amazon Aurora pricing. To learn more, read the Aurora PostgreSQL Limitless Database documentation and get started by creating an Aurora PostgreSQL Limitless Database in only a few steps in the Amazon RDS console.