Amazon Connect now supports recurring activities in agent schedules, making it easier for you to add repeating events in a few clicks. With this launch, you can now schedule activities such as daily stand-up at 8am or team meeting every Monday at 9am as a series that automatically gets added to agent schedules. You can schedule these activities as individual so that a different recurring series is created for each selected agent, or, you can schedule these activities as shared so that all selected agents are part of the same series. This launch eliminates the need for manually creating each occurrence as a separate activity, thus reducing time spent on managing agent schedules and improving manager productivity.

This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about Amazon Connect agent scheduling, click here.

​Amazon Connect now supports recurring activities in agent schedules, making it easier for you to add repeating events in a few clicks. With this launch, you can now schedule activities such as daily stand-up at 8am or team meeting every Monday at 9am as a series that automatically gets added to agent schedules. You can schedule these activities as individual so that a different recurring series is created for each selected agent, or, you can schedule these activities as shared so that all selected agents are part of the same series. This launch eliminates the need for manually creating each occurrence as a separate activity, thus reducing time spent on managing agent schedules and improving manager productivity. This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about Amazon Connect agent scheduling, click here.  

Amazon Relational Database Service (Amazon RDS) for Oracle now supports the July 2025 Release Update (RU) for Oracle Database versions 19c and 21c. These RUs include bug and security fixes and are available for RDS for Oracle Standard Edition 2 and Enterprise Edition. Review the Oracle release notes for July RU for details.

We recommend upgrading to this RU as it includes security fixes. You can upgrade with just a few clicks in the Amazon RDS Management Console or by using the AWS SDK or CLI. You can also enable auto minor version upgrade (AmVU) to automatically upgrade your database instances. Learn more about upgrading your database instances from the Amazon RDS User Guide.

This new minor version is available in all AWS regions where Amazon RDS for Oracle is available. See Amazon RDS for Oracle Pricing for pricing details and regional availability.

​Amazon Relational Database Service (Amazon RDS) for Oracle now supports the July 2025 Release Update (RU) for Oracle Database versions 19c and 21c. These RUs include bug and security fixes and are available for RDS for Oracle Standard Edition 2 and Enterprise Edition. Review the Oracle release notes for July RU for details. We recommend upgrading to this RU as it includes security fixes. You can upgrade with just a few clicks in the Amazon RDS Management Console or by using the AWS SDK or CLI. You can also enable auto minor version upgrade (AmVU) to automatically upgrade your database instances. Learn more about upgrading your database instances from the Amazon RDS User Guide. This new minor version is available in all AWS regions where Amazon RDS for Oracle is available. See Amazon RDS for Oracle Pricing for pricing details and regional availability.  

WS CloudFormation Hooks now support managed proactive controls, allowing customers to validate resource configurations against AWS best practices without writing custom hook logic. Customers can select controls from the AWS Control Tower Controls Catalog and apply them during CloudFormation operations. This helps reduce setup time, avoid manual errors, and improve the completeness and consistency of governance coverage. With this launch, customers can also configure these controls to run in warn mode. This allows teams to test controls without blocking deployments and is currently only available through CloudFormation. It gives customers greater flexibility to evaluate control behavior before fully enforcing policies.

AWS also introduced a new Hooks Invocation Summary page in the CloudFormation console. This view provides a historical record of hook activity, showing which controls were invoked, when and where they ran, and their outcomes such as pass, warn, or fail. This helps customers troubleshoot issues faster and demonstrate control posture for audits and compliance reviews.

With this launch, customers can now use AWS managed controls as part of their provisioning workflows, without the overhead of writing and maintaining custom logic. These controls are curated by AWS and aligned with industry best practices, helping teams enforce policies consistently across environments. The new summary page offers visibility into hook execution history, enabling faster issue resolution and better reporting.

These capabilities are available in all AWS Regions where CloudFormation is supported. To learn more, visit the AWS CloudFormation Hooks documentation

​WS CloudFormation Hooks now support managed proactive controls, allowing customers to validate resource configurations against AWS best practices without writing custom hook logic. Customers can select controls from the AWS Control Tower Controls Catalog and apply them during CloudFormation operations. This helps reduce setup time, avoid manual errors, and improve the completeness and consistency of governance coverage. With this launch, customers can also configure these controls to run in warn mode. This allows teams to test controls without blocking deployments and is currently only available through CloudFormation. It gives customers greater flexibility to evaluate control behavior before fully enforcing policies. AWS also introduced a new Hooks Invocation Summary page in the CloudFormation console. This view provides a historical record of hook activity, showing which controls were invoked, when and where they ran, and their outcomes such as pass, warn, or fail. This helps customers troubleshoot issues faster and demonstrate control posture for audits and compliance reviews. With this launch, customers can now use AWS managed controls as part of their provisioning workflows, without the overhead of writing and maintaining custom logic. These controls are curated by AWS and aligned with industry best practices, helping teams enforce policies consistently across environments. The new summary page offers visibility into hook execution history, enabling faster issue resolution and better reporting. These capabilities are available in all AWS Regions where CloudFormation is supported. To learn more, visit the AWS CloudFormation Hooks documentation
   

SageMaker HyperPod now provides a new cluster creation experience that sets up all the resources needed for large-scale AI/ML workloads—including networking, storage, compute, and IAM permissions in just a few clicks. SageMaker HyperPod clusters are purpose-built for scalability and resilience, designed to accelerate large-scale distributed training and deployment of complex machine learning models like LLMs and diffusion models, as well as customization of Amazon Nova foundation models.

The new cluster creation experience for SageMaker HyperPod introduces both quick and custom setup paths that make it easier for both beginners and advanced AWS customers to get started. Previously, customers needed to manually configure networking, IAM roles, storage, and compute. With the new quick setup, model builders, who may not have AWS infrastructure expertise, can now launch a fully-operational cluster optimized for large-scale AI workloads in just a few clicks using a streamlined single-page interface that provisions all dependencies including VPCs, subnets, FSx storage, EKS/Slurm orchestrator, and essential (k8s) operators. For platform engineering teams who may want to modify the default settings, the custom setup path provides full control over every configuration—from specific subnet configurations to selective operator installations—from within the same console experience. Teams can also export an auto-generated CloudFormation template for repeatable production deployments.

You can create clusters using either the AWS Console or CloudFormation in all AWS Regions where SageMaker HyperPod is supported. To learn more, see the user guide.

​SageMaker HyperPod now provides a new cluster creation experience that sets up all the resources needed for large-scale AI/ML workloads—including networking, storage, compute, and IAM permissions in just a few clicks. SageMaker HyperPod clusters are purpose-built for scalability and resilience, designed to accelerate large-scale distributed training and deployment of complex machine learning models like LLMs and diffusion models, as well as customization of Amazon Nova foundation models. The new cluster creation experience for SageMaker HyperPod introduces both quick and custom setup paths that make it easier for both beginners and advanced AWS customers to get started. Previously, customers needed to manually configure networking, IAM roles, storage, and compute. With the new quick setup, model builders, who may not have AWS infrastructure expertise, can now launch a fully-operational cluster optimized for large-scale AI workloads in just a few clicks using a streamlined single-page interface that provisions all dependencies including VPCs, subnets, FSx storage, EKS/Slurm orchestrator, and essential (k8s) operators. For platform engineering teams who may want to modify the default settings, the custom setup path provides full control over every configuration—from specific subnet configurations to selective operator installations—from within the same console experience. Teams can also export an auto-generated CloudFormation template for repeatable production deployments. You can create clusters using either the AWS Console or CloudFormation in all AWS Regions where SageMaker HyperPod is supported. To learn more, see the user guide.  

Amazon Relational Database Service (Amazon RDS) for Oracle now supports the Spatial Patch Bundle (SPB) for the July 2025 Release Update (RU) for Oracle Database version 19c. This update delivers important fixes for Oracle Spatial and Graph functionality, helping ensure reliable and optimal performance for your spatial operations.

You can now create new DB instances or upgrade existing ones to engine version ‘19.0.0.0.ru-2025-07.spb-1.r1’. The SPB engine version will be visible in the AWS Console by selecting the «Spatial Patch Bundle Engine Versions» checkbox in the engine version selector, making it simple to identify and implement the latest spatial patches for your database environment.

To learn more about Oracle SPBs supported on Amazon RDS for each engine version, see the Amazon RDS for Oracle Release notes. For more information about the AWS Regions where Amazon RDS for Oracle is available, see the AWS Region table.

​Amazon Relational Database Service (Amazon RDS) for Oracle now supports the Spatial Patch Bundle (SPB) for the July 2025 Release Update (RU) for Oracle Database version 19c. This update delivers important fixes for Oracle Spatial and Graph functionality, helping ensure reliable and optimal performance for your spatial operations. You can now create new DB instances or upgrade existing ones to engine version ‘19.0.0.0.ru-2025-07.spb-1.r1’. The SPB engine version will be visible in the AWS Console by selecting the «Spatial Patch Bundle Engine Versions» checkbox in the engine version selector, making it simple to identify and implement the latest spatial patches for your database environment. To learn more about Oracle SPBs supported on Amazon RDS for each engine version, see the Amazon RDS for Oracle Release notes. For more information about the AWS Regions where Amazon RDS for Oracle is available, see the AWS Region table.  

Amazon Connect Outbound Campaigns now supports account-based campaigns, allowing you to reach multiple people associated with the same account. For example, when calling about a joint bank account, if the first person is unavailable, the system automatically tries to reach other authorized members of the account. You can also define a prioritized contact sequence across multiple phone numbers, for example, mobile first, then home, then work. If the first number is unreachable, Connect will automatically try the next number in the sequence.

Previously, campaigns targeted one profile and retried a single phone number. With these updates, you can target multiple profiles within the same campaign, enabling outreach to all associated contacts in an account. You can also configure fallback phone numbers within each profile, automatically moving to the next preferred phone number if the first attempt is unsuccessful. Together, these capabilities help you create more flexible and effective engagement workflows that improve right-party contact rates and simplify campaign management.

This feature is available in all AWS Regions where Amazon Connect Outbound Campaigns is supported. To get started, refer to the Amazon Connect Customer Profiles documentation to learn how to ingest customer data, and the Outbound Campaigns documentation for guidance on creating campaigns.. 

​Amazon Connect Outbound Campaigns now supports account-based campaigns, allowing you to reach multiple people associated with the same account. For example, when calling about a joint bank account, if the first person is unavailable, the system automatically tries to reach other authorized members of the account. You can also define a prioritized contact sequence across multiple phone numbers, for example, mobile first, then home, then work. If the first number is unreachable, Connect will automatically try the next number in the sequence. Previously, campaigns targeted one profile and retried a single phone number. With these updates, you can target multiple profiles within the same campaign, enabling outreach to all associated contacts in an account. You can also configure fallback phone numbers within each profile, automatically moving to the next preferred phone number if the first attempt is unsuccessful. Together, these capabilities help you create more flexible and effective engagement workflows that improve right-party contact rates and simplify campaign management. This feature is available in all AWS Regions where Amazon Connect Outbound Campaigns is supported. To get started, refer to the Amazon Connect Customer Profiles documentation to learn how to ingest customer data, and the Outbound Campaigns documentation for guidance on creating campaigns..   

Amazon Connect now provides a new API that returns real-time position in queue, enabling businesses to better estimate wait time. This new API helps contact centers manage customer expectations and offer timely alternatives like callbacks during long wait periods. Using this data, contact centers can make informed routing decisions between primary and alternative queues while optimizing resource allocation through improved queue visibility. This metric is also generated for contacts using a routing criteria and agent proficiencies. For example, customers in slow-moving queues can be proactively offered callbacks, improving their experience while reducing queue abandonment.

​Amazon Connect now provides a new API that returns real-time position in queue, enabling businesses to better estimate wait time. This new API helps contact centers manage customer expectations and offer timely alternatives like callbacks during long wait periods. Using this data, contact centers can make informed routing decisions between primary and alternative queues while optimizing resource allocation through improved queue visibility. This metric is also generated for contacts using a routing criteria and agent proficiencies. For example, customers in slow-moving queues can be proactively offered callbacks, improving their experience while reducing queue abandonment.  

Amazon FSx for NetApp ONTAP, a fully managed shared storage service built on NetApp’s popular ONTAP file system, now allows you to decrease your file system’s solid-state drive (SSD) storage capacity, enabling you to run project-based workloads with varying active working set sizes more efficiently. You can provision SSD capacity upfront to meet peak usage needs—for periodic reporting, analytics, or large-scale data ingestion and processing—and then easily decrease SSD capacity to optimize resource utilization and reduce storage costs.

An FSx for ONTAP file system offers two storage tiers: a provisioned high-performance SSD tier for your active working set, and a fully elastic capacity pool cost-optimized for infrequently accessed data. Previously, you could increase a file system’s SSD capacity to meet your workload’s growing active working set but decreasing SSD capacity required migrating to a file system with smaller SSD capacity incurring administrative overhead and tolerating application downtime. Starting today, you can decrease your file system’s provisioned SSD capacity in-place with just a few clicks in the Amazon FSx console. You can deliver optimal performance to serve peak usage for workloads with varying high-performance storage requirements, including Electronic Design Automation jobs like chip fabrication and circuit
simulation, and Media & Entertainment tasks like video editing and transcoding. Once data processing in SSD storage is complete, and results have been archived, you can decrease SSD capacity to optimize resource utilization. You can even accelerate large-scale data migrations by provisioning SSD capacity to temporarily accommodate more data in SSD, ensuring faster data ingestion, subsequently decreasing SSD capacity after data has been tiered to the capacity pool to optimize storage costs.

You can decrease SSD storage capacity on all FSx for ONTAP second-generation file systems in all AWS Regions where FSx for ONTAP second-generation file systems are available. For more information, see the FSx for ONTAP user guide.

​Amazon FSx for NetApp ONTAP, a fully managed shared storage service built on NetApp’s popular ONTAP file system, now allows you to decrease your file system’s solid-state drive (SSD) storage capacity, enabling you to run project-based workloads with varying active working set sizes more efficiently. You can provision SSD capacity upfront to meet peak usage needs—for periodic reporting, analytics, or large-scale data ingestion and processing—and then easily decrease SSD capacity to optimize resource utilization and reduce storage costs.
An FSx for ONTAP file system offers two storage tiers: a provisioned high-performance SSD tier for your active working set, and a fully elastic capacity pool cost-optimized for infrequently accessed data. Previously, you could increase a file system’s SSD capacity to meet your workload’s growing active working set but decreasing SSD capacity required migrating to a file system with smaller SSD capacity incurring administrative overhead and tolerating application downtime. Starting today, you can decrease your file system’s provisioned SSD capacity in-place with just a few clicks in the Amazon FSx console. You can deliver optimal performance to serve peak usage for workloads with varying high-performance storage requirements, including Electronic Design Automation jobs like chip fabrication and circuit simulation, and Media & Entertainment tasks like video editing and transcoding. Once data processing in SSD storage is complete, and results have been archived, you can decrease SSD capacity to optimize resource utilization. You can even accelerate large-scale data migrations by provisioning SSD capacity to temporarily accommodate more data in SSD, ensuring faster data ingestion, subsequently decreasing SSD capacity after data has been tiered to the capacity pool to optimize storage costs. You can decrease SSD storage capacity on all FSx for ONTAP second-generation file systems in all AWS Regions where FSx for ONTAP second-generation file systems are available. For more information, see the FSx for ONTAP user guide.  

The post Impulsar la red del futuro: cómo Microsoft y nuestros socios reimaginan la energía con IA appeared first on Source LATAM.

​The post Impulsar la red del futuro: cómo Microsoft y nuestros socios reimaginan la energía con IA appeared first on Source LATAM.  

AWS IoT Core now offers the DeleteConnection API, enabling programmatic disconnection of MQTT clients using their client IDs. This new capability helps enable developers to terminate MQTT connections with options to clear persistent sessions and suppress publication of Last Will and Testament messages—messages that the MQTT broker automatically publishes on a client’s behalf when it disconnects unexpectedly. Upon disconnection, the service generates lifecycle events, providing enhanced operational visibility into device connection states.

The DeleteConnection API helps developers manage device connectivity more effectively, whether redirecting devices across endpoints, troubleshooting connection issues, or handling problematic device behavior. The DeleteConnection API is now available in all AWS Regions where AWS IoT Core is supported. To learn more, visit the AWS IoT Core documentation and AWS IoT Core API reference guide.

​AWS IoT Core now offers the DeleteConnection API, enabling programmatic disconnection of MQTT clients using their client IDs. This new capability helps enable developers to terminate MQTT connections with options to clear persistent sessions and suppress publication of Last Will and Testament messages—messages that the MQTT broker automatically publishes on a client’s behalf when it disconnects unexpectedly. Upon disconnection, the service generates lifecycle events, providing enhanced operational visibility into device connection states. The DeleteConnection API helps developers manage device connectivity more effectively, whether redirecting devices across endpoints, troubleshooting connection issues, or handling problematic device behavior. The DeleteConnection API is now available in all AWS Regions where AWS IoT Core is supported. To learn more, visit the AWS IoT Core documentation and AWS IoT Core API reference guide.