Amazon CloudWatch now allows customers to automatically enable Amazon Virtual Private Cloud (VPC) flow logs to CloudWatch logs across their AWS Organization. Customers can create enablement rules in CloudWatch Telemetry Config that automatically creates flow logs for both existing and newly created VPCs matching the rule scope, ensuring consistent monitoring coverage.

With today’s launch, customers can scope rules that apply to the whole organization, specific accounts, or specific resources based on resource tags to standardize the configuration of VPC flow logs. For example, the central DevOps team can create an enablement rule to automatically turn on flow logs to CloudWatch logs for VPCs with a specific tags, e.g., env:production, and help maintain complete visibility into network traffic patterns. Enablement rules use AWS Config Service-Linked recorders to discover resources that meet the rule criteria and automatically enable them to ingest logs.

CloudWatch’s telemetry auto-enablement capability is available in the following AWS commercial regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo).

Customers incur charges for configuration items of resource types using enablement rules, according to AWS Config Pricing. Ingestion of VPC Flow Logs will be billed as vended logs as per CloudWatch Pricing. To learn more about org-wide VPC flow log enablement, visit the Amazon CloudWatch documentation.

 

​Amazon CloudWatch now allows customers to automatically enable Amazon Virtual Private Cloud (VPC) flow logs to CloudWatch logs across their AWS Organization. Customers can create enablement rules in CloudWatch Telemetry Config that automatically creates flow logs for both existing and newly created VPCs matching the rule scope, ensuring consistent monitoring coverage. With today’s launch, customers can scope rules that apply to the whole organization, specific accounts, or specific resources based on resource tags to standardize the configuration of VPC flow logs. For example, the central DevOps team can create an enablement rule to automatically turn on flow logs to CloudWatch logs for VPCs with a specific tags, e.g., env:production, and help maintain complete visibility into network traffic patterns. Enablement rules use AWS Config Service-Linked recorders to discover resources that meet the rule criteria and automatically enable them to ingest logs. CloudWatch’s telemetry auto-enablement capability is available in the following AWS commercial regions: US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Osaka), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Europe (Stockholm), and South America (São Paulo). Customers incur charges for configuration items of resource types using enablement rules, according to AWS Config Pricing. Ingestion of VPC Flow Logs will be billed as vended logs as per CloudWatch Pricing. To learn more about org-wide VPC flow log enablement, visit the Amazon CloudWatch documentation.  

Starting today, Amazon Lightsail is available in the Asia Pacific (Jakarta) Region. This expansion brings the power and simplicity of Lightsail to customers in Indonesia and surrounding regions.

With this launch, customers in Indonesia and nearby countries can now enjoy lower latency and better performance for their applications while meeting local data residency requirements. The new Region provides access to Lightsail’s features such as instances, managed databases, containers, load balancers and more, all with the same simple, predictable pricing that Lightsail customers love.

Lightsail is available in these AWS Regions: US East (Ohio, N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt, Ireland, London, Paris, Stockholm), Asia Pacific (Jakarta, Mumbai, Seoul, Singapore, Sydney, Tokyo). To learn more about Regions and Availability Zones for Lightsail, please refer to the documentation.

You can use this Region through the Lightsail Console (accessed from AWS Console), AWS Command Line Interface (CLI) and AWS SDKs.

 

​Starting today, Amazon Lightsail is available in the Asia Pacific (Jakarta) Region. This expansion brings the power and simplicity of Lightsail to customers in Indonesia and surrounding regions. With this launch, customers in Indonesia and nearby countries can now enjoy lower latency and better performance for their applications while meeting local data residency requirements. The new Region provides access to Lightsail’s features such as instances, managed databases, containers, load balancers and more, all with the same simple, predictable pricing that Lightsail customers love. Lightsail is available in these AWS Regions: US East (Ohio, N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt, Ireland, London, Paris, Stockholm), Asia Pacific (Jakarta, Mumbai, Seoul, Singapore, Sydney, Tokyo). To learn more about Regions and Availability Zones for Lightsail, please refer to the documentation. You can use this Region through the Lightsail Console (accessed from AWS Console), AWS Command Line Interface (CLI) and AWS SDKs.  

Customers in AWS Asia Pacific (Thailand) Region can now use AWS Transfer Family for file transfers over Secure File Transfer Protocol (SFTP), File Transfer Protocol (FTP), FTP over SSL (FTPS) and Applicability Statement 2 (AS2).

AWS Transfer Family provides fully managed file transfers for Amazon Simple Storage Service (Amazon S3) and Amazon Elastic File System (Amazon EFS) over SFTP, FTP, FTPS and AS2 protocols. In addition to file transfers, Transfer Family enables common file processing and event-driven automation for managed file transfer (MFT) workflows, helping customers to modernize and migrate their business-to-business file transfers to AWS.

To learn more about AWS Transfer Family, visit our product page and user-guide. See the AWS Region Table for complete regional availability information.

 

​Customers in AWS Asia Pacific (Thailand) Region can now use AWS Transfer Family for file transfers over Secure File Transfer Protocol (SFTP), File Transfer Protocol (FTP), FTP over SSL (FTPS) and Applicability Statement 2 (AS2). AWS Transfer Family provides fully managed file transfers for Amazon Simple Storage Service (Amazon S3) and Amazon Elastic File System (Amazon EFS) over SFTP, FTP, FTPS and AS2 protocols. In addition to file transfers, Transfer Family enables common file processing and event-driven automation for managed file transfer (MFT) workflows, helping customers to modernize and migrate their business-to-business file transfers to AWS. To learn more about AWS Transfer Family, visit our product page and user-guide. See the AWS Region Table for complete regional availability information.  

Mountpoint for Amazon S3 Container Storage Interface (CSI) driver now accelerates performance for repeatedly accessed data, adds support for Security-Enhanced Linux (SELinux) mount options, and simplifies logging and permissions management.

The latest version of the Mountpoint for Amazon S3 CSI driver (v2) introduces four key capabilities. First, it adds support for caching data across multiple pods. By using the new caching capabilities in Mountpoint for Amazon S3 CSI driver v2, you can finish large-scale financial simulation jobs up to 2x faster by eliminating the overhead of multiple pods individually caching the same data. Second, you can now run your Kubernetes applications on SELinux-enabled environments like Red Hat OpenShift. Third, it lets you use Amazon EKS Pod Identity to simplify how you manage access policies across Amazon EKS clusters, including cross-account access. Fourth, it simplifies how you access logs and get insights into your mounts by using kubectl, a command line tool.

To upgrade to Mountpoint for Amazon S3 CSI v2 driver, you can follow the installation guidance. You can install, configure, and update the CSI driver in the Amazon EKS console, AWS Command Line Interface (AWS CLI), EKS Application Programming Interface (API), and AWS CloudFormation. For details on supported file system operations, visit the documentation.

 

​Mountpoint for Amazon S3 Container Storage Interface (CSI) driver now accelerates performance for repeatedly accessed data, adds support for Security-Enhanced Linux (SELinux) mount options, and simplifies logging and permissions management.
The latest version of the Mountpoint for Amazon S3 CSI driver (v2) introduces four key capabilities. First, it adds support for caching data across multiple pods. By using the new caching capabilities in Mountpoint for Amazon S3 CSI driver v2, you can finish large-scale financial simulation jobs up to 2x faster by eliminating the overhead of multiple pods individually caching the same data. Second, you can now run your Kubernetes applications on SELinux-enabled environments like Red Hat OpenShift. Third, it lets you use Amazon EKS Pod Identity to simplify how you manage access policies across Amazon EKS clusters, including cross-account access. Fourth, it simplifies how you access logs and get insights into your mounts by using kubectl, a command line tool.
To upgrade to Mountpoint for Amazon S3 CSI v2 driver, you can follow the installation guidance. You can install, configure, and update the CSI driver in the Amazon EKS console, AWS Command Line Interface (AWS CLI), EKS Application Programming Interface (API), and AWS CloudFormation. For details on supported file system operations, visit the documentation.  

Amazon OpenSearch Serverless now offers automatic semantic enrichment, a breakthrough feature that simplifies semantic search implementation. You can now boost your search relevance with minimal effort, eliminating complex manual configurations through an automated setup process.

Semantic search goes beyond keyword matching by understanding the context and meaning of search queries. For example, when searching for «how to treat a headache,» semantic search intelligently returns relevant results about «migraine remedies» or «pain management techniques» even when these exact terms aren’t present in the query.

Previously, implementing semantic search required ML (Machine Learning) expertise, model hosting, and OpenSearch integration. Automatic semantic enrichment simplifies this process dramatically. With automatic semantic enrichment, you simply specify which fields need semantic search capabilities. OpenSearch Service handles all semantic enrichment automatically during data ingestion.

The feature launches with support for two language variants: English-only and Multi-lingual, covering 15 languages including Arabic, Chinese, Finnish, French, Hindi, Japanese, Korean, Spanish, and more. You pay only for actual usage during data ingestion, with no ongoing costs for storage or search queries.

This new feature is automatically enabled for all serverless collections and is now available in the following regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (Spain), Europe (Stockholm). To get started, visit our technical documentation, read our blog post, and see Amazon OpenSearch Service semantic search pricing. Check the AWS Regional Services List for availability in your region.

 

​Amazon OpenSearch Serverless now offers automatic semantic enrichment, a breakthrough feature that simplifies semantic search implementation. You can now boost your search relevance with minimal effort, eliminating complex manual configurations through an automated setup process. Semantic search goes beyond keyword matching by understanding the context and meaning of search queries. For example, when searching for «how to treat a headache,» semantic search intelligently returns relevant results about «migraine remedies» or «pain management techniques» even when these exact terms aren’t present in the query. Previously, implementing semantic search required ML (Machine Learning) expertise, model hosting, and OpenSearch integration. Automatic semantic enrichment simplifies this process dramatically. With automatic semantic enrichment, you simply specify which fields need semantic search capabilities. OpenSearch Service handles all semantic enrichment automatically during data ingestion. The feature launches with support for two language variants: English-only and Multi-lingual, covering 15 languages including Arabic, Chinese, Finnish, French, Hindi, Japanese, Korean, Spanish, and more. You pay only for actual usage during data ingestion, with no ongoing costs for storage or search queries. This new feature is automatically enabled for all serverless collections and is now available in the following regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (Spain), Europe (Stockholm). To get started, visit our technical documentation, read our blog post, and see Amazon OpenSearch Service semantic search pricing. Check the AWS Regional Services List for availability in your region.  

Today, AWS announced that AWS Parallel Computing Service (AWS PCS) supports SPANK (Slurm Plug-in Architecture for Node and job [K]control) plugins, enabling you to extend and modify how Slurm schedules and processes your high performance computing (HPC) workloads without modifying Slurm directly.

Using SPANK plugins, you can now integrate AWS PCS with container technologies, implement custom monitoring of memory and I/O patterns, and dynamically modify job launches to enhance resource management. For example, you can use Enroot and Pyxis plugins to seamlessly run containerized machine learning and HPC workloads using images from Amazon Elastic Container Registry, Docker Hub, NVIDIA NGC, or other container registries.

This feature is available in all AWS Regions where AWS PCS is available. You can implement SPANK plugins by installing and configuring them on the Amazon Machine Images (AMIs) that power your AWS PCS compute nodes. The plugins will be dynamically loaded at runtime when jobs launch, providing a low-effort approach to extend Slurm’s functionality.

To learn more about using SPANK plugins with AWS PCS, see the AWS PCS User Guide.

 

​Today, AWS announced that AWS Parallel Computing Service (AWS PCS) supports SPANK (Slurm Plug-in Architecture for Node and job [K]control) plugins, enabling you to extend and modify how Slurm schedules and processes your high performance computing (HPC) workloads without modifying Slurm directly. Using SPANK plugins, you can now integrate AWS PCS with container technologies, implement custom monitoring of memory and I/O patterns, and dynamically modify job launches to enhance resource management. For example, you can use Enroot and Pyxis plugins to seamlessly run containerized machine learning and HPC workloads using images from Amazon Elastic Container Registry, Docker Hub, NVIDIA NGC, or other container registries. This feature is available in all AWS Regions where AWS PCS is available. You can implement SPANK plugins by installing and configuring them on the Amazon Machine Images (AMIs) that power your AWS PCS compute nodes. The plugins will be dynamically loaded at runtime when jobs launch, providing a low-effort approach to extend Slurm’s functionality. To learn more about using SPANK plugins with AWS PCS, see the AWS PCS User Guide.  

Etiquetas:

• IA
• Salud
• Tecnología

The post Mejorar la detección del cáncer de mama con IA appeared first on Source LATAM.

 

​The post Mejorar la detección del cáncer de mama con IA appeared first on Source LATAM.  

Starting today, AWS Directory Service for Microsoft Active Directory customers can extend their existing Active Directory domain into AWS with the new Hybrid Edition for AWS Managed Microsoft AD. This new capability provides customers with a managed service for their AD infrastructure extended in AWS, enabling a unified Active Directory deployment between on-premises, AWS Cloud and multi-cloud environments.

Hybrid Edition automatically handles replication and maintenance between your AD environments and AWS. This provides you a simpler way to migrate AD-dependent workloads to the cloud while maintaining your existing AD data. The service preserves all your existing access controls and group policies without requiring permission reconfiguration.

With this new capability, you can easily integrate with AWS services including  Amazon EC2,  Amazon FSx for Windows File Server and Amazon Relational Database Service (RDS) across multiple AWS accounts. The managed approach significantly reduces operational overhead and allows your team to focus on business priorities while AWS handles the AD infrastructure maintenance. You can also securely share administrator credentials for Hybrid Edition using AWS Secrets Manager, ensuring no human visible credentials.

For information on regional availability of the AWS Directory Service Hybrid Edition for AWS Managed Microsoft AD, please refer to the AWS Directory Service documentation, which will be updated with the latest availability information.

To learn more about how Hybrid Edition can benefit your organization, review Extend your Active Directory domain to AWS with AWS Managed Microsoft AD (Hybrid Edition) blog post or the AWS Directory Service documentation. You can start using Hybrid Edition for AWS Managed Microsoft AD in the AWS Management Console, through the AWS CLI, or via AWS SDKs.

 

​Starting today, AWS Directory Service for Microsoft Active Directory customers can extend their existing Active Directory domain into AWS with the new Hybrid Edition for AWS Managed Microsoft AD. This new capability provides customers with a managed service for their AD infrastructure extended in AWS, enabling a unified Active Directory deployment between on-premises, AWS Cloud and multi-cloud environments.
Hybrid Edition automatically handles replication and maintenance between your AD environments and AWS. This provides you a simpler way to migrate AD-dependent workloads to the cloud while maintaining your existing AD data. The service preserves all your existing access controls and group policies without requiring permission reconfiguration.
With this new capability, you can easily integrate with AWS services including  Amazon EC2,  Amazon FSx for Windows File Server and Amazon Relational Database Service (RDS) across multiple AWS accounts. The managed approach significantly reduces operational overhead and allows your team to focus on business priorities while AWS handles the AD infrastructure maintenance. You can also securely share administrator credentials for Hybrid Edition using AWS Secrets Manager, ensuring no human visible credentials.
For information on regional availability of the AWS Directory Service Hybrid Edition for AWS Managed Microsoft AD, please refer to the AWS Directory Service documentation, which will be updated with the latest availability information.
To learn more about how Hybrid Edition can benefit your organization, review Extend your Active Directory domain to AWS with AWS Managed Microsoft AD (Hybrid Edition) blog post or the AWS Directory Service documentation. You can start using Hybrid Edition for AWS Managed Microsoft AD in the AWS Management Console, through the AWS CLI, or via AWS SDKs.  

Amazon CloudWatch launches natural language query generation powered by generative AI for OpenSearch PPL and SQL query languages in CloudWatch Logs Insights, accelerating logs analysis.

CloudWatch Logs Insights enables you to interactively search and analyze your logs with Logs Insights query language, OpenSearch Service Piped Processing Language (PPL), and OpenSearch Service Structured Query Language (SQL).

Customers using OpenSearch PPL and OpenSearch SQL can now use plain English to quickly generate queries in the context of their logs without needing extensive knowledge of the query language, reducing time to gather insights. For example, you can ask in plain English “Give me the number of errors and exceptions per hour” or “What are the top 100 source IP addresses by bytes transferred” and the queries will be automatically generated in OpenSearch PPL or SQL, depending on the language selected.

The query generator is available 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). To learn more, view documentation.

 

​Amazon CloudWatch launches natural language query generation powered by generative AI for OpenSearch PPL and SQL query languages in CloudWatch Logs Insights, accelerating logs analysis. CloudWatch Logs Insights enables you to interactively search and analyze your logs with Logs Insights query language, OpenSearch Service Piped Processing Language (PPL), and OpenSearch Service Structured Query Language (SQL). Customers using OpenSearch PPL and OpenSearch SQL can now use plain English to quickly generate queries in the context of their logs without needing extensive knowledge of the query language, reducing time to gather insights. For example, you can ask in plain English “Give me the number of errors and exceptions per hour” or “What are the top 100 source IP addresses by bytes transferred” and the queries will be automatically generated in OpenSearch PPL or SQL, depending on the language selected. The query generator is available 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). To learn more, view documentation.  

Today, Amazon Simple Email Service (SES) announces the ability to provision isolated tenants within a single SES account and apply automated reputation policies to manage email sending. With this enhancement, customers can create multiple tenants in their SES account, each with dedicated configuration sets, identities, and templates. This new feature helps customers detect and isolate deliverability issues within isolated email streams, preserving sender reputation and helping improve inbox placement with mailbox providers.

When customers specify a tenant while sending an email, SES now provides tenant-level metrics including messages sent, bounce rates, and complaint rates in real-time. If reputation issues are detected, SES can automatically pause the affected tenant to protect other email streams. Customers can control this automation with three reputation policy options: Standard (recommended) which pauses sending for high-impact findings, Strict which pauses for any reputation finding, or None for manual monitoring. SES publishes notifications to Amazon EventBridge when tenant status changes occur or new reputation findings are detected, enabling integration with existing monitoring workflows.

These new capabilities are now available in all AWS Regions where Amazon SES is offered.

To learn more about working with tenants in Amazon SES, visit the Amazon SES console or refer to the documentation for detailed instructions on creating tenants, configuring reputation policies, and monitoring tenant-level metrics.

 

​Today, Amazon Simple Email Service (SES) announces the ability to provision isolated tenants within a single SES account and apply automated reputation policies to manage email sending. With this enhancement, customers can create multiple tenants in their SES account, each with dedicated configuration sets, identities, and templates. This new feature helps customers detect and isolate deliverability issues within isolated email streams, preserving sender reputation and helping improve inbox placement with mailbox providers. When customers specify a tenant while sending an email, SES now provides tenant-level metrics including messages sent, bounce rates, and complaint rates in real-time. If reputation issues are detected, SES can automatically pause the affected tenant to protect other email streams. Customers can control this automation with three reputation policy options: Standard (recommended) which pauses sending for high-impact findings, Strict which pauses for any reputation finding, or None for manual monitoring. SES publishes notifications to Amazon EventBridge when tenant status changes occur or new reputation findings are detected, enabling integration with existing monitoring workflows. These new capabilities are now available in all AWS Regions where Amazon SES is offered. To learn more about working with tenants in Amazon SES, visit the Amazon SES console or refer to the documentation for detailed instructions on creating tenants, configuring reputation policies, and monitoring tenant-level metrics.