IAM Identity Center helps you configure the single sign-on experience of your workforce to AWS accounts and applications. You can now replicate IAM Identity Center from the primary AWS Region where you first enabled it to additional Regions of your choice. This feature enhances resilience of user access to AWS accounts and helps you deploy AWS applications in the AWS Regions that best align with your business needs such as application data residency and proximity to users.

When you enable this feature, IAM Identity Center automatically replicates your identities, entitlements, and other information from the primary Region to additional Regions. If IAM Identity Center is affected by a disruption in the primary Region, IAM Identity Center users continue to have access to their AWS accounts using the already provisioned entitlements in the additional Regions. 

AWS application administrators can use the standard application deployment workflow to deploy their application in an additional Region. They can assign users to the application in that Region, while you continue to administer IAM Identity Center in the primary Region.

IAM Identity Center multi-Region support is currently available in the 17 enabled-by-default commercial AWS Regions for organization instances of IAM Identity Center connected to an external identity provider, such as Okta. The IAM Identity Center organization instance must be configured with a multi-Region customer managed KMS key (CMK). To find out which AWS applications support deployment in additional Regions, visit AWS applications that you can use with IAM Identity Center. Standard AWS KMS charges apply for storing and using CMKs. IAM Identity Center is provided at no additional cost. To learn more about IAM Identity Center, visit the product detail page. To get started, see the IAM Identity Center User Guide. 

​IAM Identity Center helps you configure the single sign-on experience of your workforce to AWS accounts and applications. You can now replicate IAM Identity Center from the primary AWS Region where you first enabled it to additional Regions of your choice. This feature enhances resilience of user access to AWS accounts and helps you deploy AWS applications in the AWS Regions that best align with your business needs such as application data residency and proximity to users.
When you enable this feature, IAM Identity Center automatically replicates your identities, entitlements, and other information from the primary Region to additional Regions. If IAM Identity Center is affected by a disruption in the primary Region, IAM Identity Center users continue to have access to their AWS accounts using the already provisioned entitlements in the additional Regions. 
AWS application administrators can use the standard application deployment workflow to deploy their application in an additional Region. They can assign users to the application in that Region, while you continue to administer IAM Identity Center in the primary Region. IAM Identity Center multi-Region support is currently available in the 17 enabled-by-default commercial AWS Regions for organization instances of IAM Identity Center connected to an external identity provider, such as Okta. The IAM Identity Center organization instance must be configured with a multi-Region customer managed KMS key (CMK). To find out which AWS applications support deployment in additional Regions, visit AWS applications that you can use with IAM Identity Center. Standard AWS KMS charges apply for storing and using CMKs. IAM Identity Center is provided at no additional cost. To learn more about IAM Identity Center, visit the product detail page. To get started, see the IAM Identity Center User Guide.   

• Categoría: Noticias de Microsoft

febrero 3, 2026

Windows 365 for Agents: El próximo capítulo del PC en la nube

Por: Phil Gerity, Somesh Goel, Gaurav Dhawan, Matt Shadbolt, Joydeep Mukherjee.

Un nuevo capítulo para Windows 365

En 2021, Microsoft introdujo Windows 365, para reinventar el PC como un servicio en la nube que transmite un PC en la nube: una experiencia Windows completa, segura y personalizada para cualquier dispositivo, en cualquier lugar. Esta innovación ofreció a las organizaciones la flexibilidad para escalar recursos informáticos al instante, reducir la complejidad informática y reforzar la seguridad, todo ello mientras empoderaba a los empleados para trabajar casi desde cualquier lugar. En solo cuatro años, Windows 365 se ha convertido en la solución emblemática de software como servicio (SaaS, por sus siglas en inglés) de Microsoft para ofrecer computación segura, gestionada y de nivel empresarial a nivel global, para ayudar a las empresas a reducir costes, simplificar la gestión y acelerar la productividad.

Y ahora, Windows 365 habilita otro hito en la informática: el recién anunciado Windows 365 for Agents (Windows para Agentes) permite ejecutar agentes autónomos de IA de forma segura en PCs en la nube. Esto significa que las organizaciones pueden automatizar flujos de trabajo complejos, escalar operaciones sin añadir personal y desbloquear nuevas ganancias de productividad, todo ello mientras se mantiene la seguridad y el cumplimiento de nivel empresarial. Al extender el mismo entorno de confianza desde los usuarios humanos hasta las cargas de trabajo de los agentes, las empresas pueden acelerar la innovación y mejorar la productividad de los empleados.

Las interfaces agénticas pasan a formar parte de la interfaz de PC. Y la gente usará software (agentes) para controlar el software. Esta abstracción moderna permite que las personas sean más productivas al dedicar más tiempo a tareas que aportan valor y delegar tareas que no aportan valor a los agentes.

La arquitectura que distingue a Windows 365

Windows 365 está construido sobre un conjunto de capacidades probadas de nivel empresarial que forman el núcleo del servicio. Su arquitectura «alojada en nombre de» (HOBO, por sus siglas en inglés) utiliza máquinas virtuales Azure de instancia única que se ejecutan en la suscripción de Microsoft, se gestionan a través de Microsoft Intune, se aseguran con el ID Microsoft Entra y se conectan mediante transporte de conexión inversa.

Estos componentes reúnen las tecnologías más confiables de Microsoft para proporcionar una base segura, fiable y escalable para ejecutar cargas de trabajo en la nube de PC en las siguientes áreas clave:

• Identidad y seguridad: Microsoft Entra ID gestiona una autenticación fuerte, incluida MFA sin contraseña y resistente a PHH, con políticas de Acceso Condicional que aplican restricciones basadas en la ubicación, gestión de riesgos de inicio de sesión y cumplimiento de dispositivos. Los PC en la nube soportan tanto la unión Entra (nativa en la nube) como la unión híbrida a los Servicios de Dominio Active Directory locales (AD DS, por sus siglas en inglés).
• Gestión unificada: Todos los PC en la nube pueden inscribirse en Microsoft Intune, donde los administradores definen políticas de aprovisionamiento, despliegan aplicaciones, configuran ajustes y hacen cumplir las líneas de seguridad —a través de la misma consola y flujos de trabajo que los dispositivos físicos.
• Provisión de PC en la nube: Nuestro tejido de servicio provisiona, escala y gestiona en automático los PC en la nube a escala global, con el simple disparador de la asignación de licencias y la definición de políticas de aprovisionamiento, para eliminar así cualquier gestión de infraestructura en la nube necesaria para nuestros clientes.
• Conectividad global: Las conexiones de los usuarios nunca llegan directo a los PCs en la nube a través de internet. Tanto el dispositivo cliente como el PC en la nube establecen conexiones salientes a la nube de Microsoft, lo que elimina por completo los puertos entrantes. Nuestros algoritmos de enrutamiento inteligentes dirigen el tráfico a la pasarela de menor latencia. También utilizamos técnicas estándar de la industria como STUN y TURN para mantener una conectividad rápida y fiable incluso en entornos de red restrictivos.

Ampliación de Windows 365 a agentes

Con la aparición de agentes que usan ordenadores (CUAs, por sus siglas en inglés) como una clase de capacidades de IA, reconocimos un requisito clave: los agentes de IA deben operar en sus propios entornos informáticos seguros para ejecutar tareas, interactuar con sistemas empresariales y aplicaciones de línea de negocio, y operar dentro de los límites de seguridad, sin cargar a los usuarios humanos por el compartir entornos.

Un agente de IA que interactúa con una interfaz gráfica requiere los mismos recursos fundamentales que cualquier usuario: computación, red, identidad y controles de políticas. En lugar de construir una pila de virtualización separada, Windows 365 para Agentes funciona sobre una infraestructura idéntica de Azure VM con los mismos sistemas de gestión Intune e identidad Entra.

Más allá de crear una plataforma Cloud PC para cargas de trabajo de agentes de IA, Windows 365 para Agentes introduce un conjunto de capacidades diseñadas para hacer que las cargas de trabajo de agentes sean seguras, escalables y rentables. Estas mejoras van más allá de tan solo ejecutar agentes de IA en PCs en la nube: optimizan cómo se provisionan, gestionan y controlan los agentes, lo que mantiene la seguridad y el cumplimiento de nivel empresarial. Desde reservas de recursos elásticas hasta salvaguardas con personas en el proceso, estas innovaciones ayudan a las organizaciones a automatizar tareas complejas, reducir costes inactivos y garantizar la confianza en las operaciones autónomas.

• Pools de PC en la nube: En lugar de asignaciones persistentes de usuario uno a uno, los agentes extraen pools compartidos organizados por equipo o carga de trabajo. Desde PCs en la nube preprovisionados para un checkout rápido hasta provisiones programadas para reducir costes inactivos, la escalada elástica permite a las organizaciones ajustar de manera dinámica los recursos disponibles para los agentes para adaptarse a las necesidades del negocio.
• Modelo de check-in/check-out: Los agentes prestan un PC en la nube para realizar una tarea y luego la vuelven a registrar para su reutilización. Este enfoque efímero y con alcance de tarea maximiza la utilización y permite la facturación de consumo basada en el uso real en lugar de tarifas mensuales fijas.
• Interfaces programáticas para el control de agentes: Windows 365 para Agentes estarán disponibles interfaces para crear, prestar y observar ordenadores en la nube para constructores de agentes de terceros en los servidores de herramientas Agent 365.
• Agentes que usan ordenadores (CUAs): A diferencia de la automatización robótica tradicional de procesos (RPA, por sus siglas en inglés), que se basa en selectores de elementos frágiles (reglas que se rompen cuando cambia una interfaz), las CUAs interpretan de manera visual el contenido de la pantalla por medio de visión de IA y razonan sobre qué acciones tomar. Se adaptan cuando cambian las interfaces sin romper los flujos de trabajo: procesar capturas de pantalla, generar planes de acción y ejecutar comandos paso a paso.  La ejecución de código, así como los servidores MCP locales, dentro de este mismo entorno, ofrecen una combinación poderosa de capacidades en un PC en la nube aislado.
• Humano en el bucle: Al reconocer la necesidad de confianza en los sistemas autónomos, la plataforma permite al usuario tomar el control en cualquier momento durante la ejecución del agente, intervenir para gestionar decisiones complejas o proporcionar credenciales, y luego devolver el control al agente cuando termina.
• Identidad del agente: Cada agente opera con un ID único de Microsoft Entra autenticado mediante credenciales criptográficas—sin contraseñas para robar o hacer phishing. TI puede distinguir las acciones de los agentes de las humanas en los registros de auditoría, lo que brinda una observabilidad granular de las operaciones de la IA.

Windows como plataforma para el trabajo inteligente

Extender los PCs en la nube a agentes digitales refleja la misión de Microsoft: empoderar a cada persona y organización para lograr más. Así como Windows democratizó la informática personal y Windows 365 llevó ese poder a la nube, Windows 365 para Agentes ofrece una plataforma segura y escalable para que los agentes digitales operen en cualquier momento y lugar.

Estamos al borde de una nueva era, donde los agentes, construidos de forma responsable y desplegados de forma segura, se convierten en colaboradores de confianza en el trabajo y la creatividad. La plataforma Windows siempre ha permitido a otros construir, crear e innovar. Windows 365 para Agentes amplía esa promesa al ofrecer a los creadores de agentes:

• Seguridad y cumplimiento de nivel empresarial para agentes de IA
• Herramientas programáticas para simplificar la construcción de flujos de trabajo sofisticados
• Capacidades de gestión que dan confianza y control a los equipos de TI
• Experiencias de usuario naturales y fiables para una integración más fluida

Los principios que dieron forma a Windows 365—seguridad, fiabilidad, gestión y escala—siguen guiándonos. La misma infraestructura que sirve a millones de usuarios humanos se convierte ahora en la base para la próxima generación de trabajo inteligente.

¿Listos para saber más?

• Consulten nuestros anuncios de Ignite: Windows 365 para Agentes desbloquea automatización de IA segura y escalable – Windows IT Pro Blog
• Para una experiencia de creación de agentes sin código impulsada por Windows 365 para Agentes, consideren Microsoft Copilot Studio: Automatizar aplicaciones web y de escritorio con uso en el ordenador (vista previa) – Microsoft Copilot Studio | Microsoft Learn
• Si son creadores de agentes y quieren crear agentes listos para empresas, empiecen a integrarse con Agent 365: Microsoft Agent 365: El plano de control para agentes de IA | Microsoft 365 Blog que incluye el uso en el ordenador como herramienta en el Agent SDK: Agentes de prueba que usan el Microsoft Agent 365 SDK | Microsoft Learn

Nota del editor – 22 de enero de 2026 – Se realizaron cambios en el texto para mayor claridad tras la publicación inicial.

Etiquetas:

• IA
• Tecnología

The post Windows 365 for Agents: El próximo capítulo del PC en la nube appeared first on Source LATAM.

​The post Windows 365 for Agents: El próximo capítulo del PC en la nube appeared first on Source LATAM.  

AWS Multi-Party Approval now requires approvers to verify their voting actions with a one-time password (OTP) sent to their registered AWS Identity Center email address. This additional security layer prevents AWS IAM Identity Center administrators from bypassing multi-party approval controls by impersonating approvers through credential resets or authentication endpoint modifications. When approvers access the Approval Portal and attempt to cast their vote on protected operations, the system generates a six-digit verification code and sends it to their email. Approvers enter this code within 10 minutes to complete their vote, with up to three attempts allowed.

The OTP verification process activates only when approvers submit their vote decision, they can review all approval request details before verification is required. If approvers don’t receive the email or the code expires, they can request a new code through the interface.

AWS Multi-party approval with OTP verification for voting is available in all AWS Regions where Mulit-party approval is offered at no additional charge. To learn more, visit the AWS Multi-party approval documentation

​AWS Multi-Party Approval now requires approvers to verify their voting actions with a one-time password (OTP) sent to their registered AWS Identity Center email address. This additional security layer prevents AWS IAM Identity Center administrators from bypassing multi-party approval controls by impersonating approvers through credential resets or authentication endpoint modifications. When approvers access the Approval Portal and attempt to cast their vote on protected operations, the system generates a six-digit verification code and sends it to their email. Approvers enter this code within 10 minutes to complete their vote, with up to three attempts allowed. The OTP verification process activates only when approvers submit their vote decision, they can review all approval request details before verification is required. If approvers don’t receive the email or the code expires, they can request a new code through the interface. AWS Multi-party approval with OTP verification for voting is available in all AWS Regions where Mulit-party approval is offered at no additional charge. To learn more, visit the AWS Multi-party approval documentation  

Amazon Lightsail now offers memory-optimized instance bundles with up to 512 GB memory. The new instance bundles are available in 7 sizes, with Linux and Windows 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 OS and application blueprints including WordPress, cPanel & WHM, Plesk, Drupal, Magento, MEAN, LAMP, Node.js, Ruby on Rails, Amazon Linux, Ubuntu, CentOS, Debian, AlmaLinux, and Windows.

The new memory-optimized instance bundles enable you to run memory-intensive workloads that require high RAM-to-vCPU ratios in Lightsail. These high-memory instance bundles are ideal for workloads such as in-memory databases, real-time big data analytics, in-memory caching systems, high-performance computing (HPC) applications, and large-scale enterprise applications that process extensive datasets in memory.

These new bundles are now available in all AWS Regions where Amazon Lightsail is available. For more information on pricing, click here.

​Amazon Lightsail now offers memory-optimized instance bundles with up to 512 GB memory. The new instance bundles are available in 7 sizes, with Linux and Windows 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 OS and application blueprints including WordPress, cPanel & WHM, Plesk, Drupal, Magento, MEAN, LAMP, Node.js, Ruby on Rails, Amazon Linux, Ubuntu, CentOS, Debian, AlmaLinux, and Windows. The new memory-optimized instance bundles enable you to run memory-intensive workloads that require high RAM-to-vCPU ratios in Lightsail. These high-memory instance bundles are ideal for workloads such as in-memory databases, real-time big data analytics, in-memory caching systems, high-performance computing (HPC) applications, and large-scale enterprise applications that process extensive datasets in memory. These new bundles are now available in all AWS Regions where Amazon Lightsail is available. For more information on pricing, click here.  

Today, AWS announced the availability of DeepSeek OCR, MiniMax M2.1, and Qwen3-VL-8B-Instruct in Amazon SageMaker JumpStart, expanding the portfolio of foundation models available to AWS customers. These three models bring specialized capabilities spanning document intelligence, multilingual coding, advanced multimodal reasoning, and vision-language understanding, enabling customers to build sophisticated AI applications across diverse use cases on AWS infrastructure.

These models address different enterprise AI challenges with specialized capabilities:
DeepSeek OCR explores visual-text compression for document processing. It can extract structured information from forms, invoices, diagrams, and complex documents with dense text layouts.
MiniMax M2.1 is optimized for coding, tool use, instruction following, and long-horizon planning. It automates multilingual software development and executes complex, multi-step office workflows, empowering developers to build autonomous applications.
Qwen3-VL-8B-Instruct delivers ssuperior text understanding and generation, deeper visual perception and reasoning, extended context length, enhanced spatial and video dynamics comprehension, and stronger agent interaction capabilities.
With SageMaker JumpStart, customers can deploy any of these models with just a few clicks to address their specific AI use cases.

To get started with these models, navigate to the SageMaker JumpStart model catalog in the SageMaker console or use the SageMaker Python SDK to deploy the models to your AWS account. For more information about deploying and using foundation models in SageMaker JumpStart, see the Amazon SageMaker JumpStart documentation. 

​Today, AWS announced the availability of DeepSeek OCR, MiniMax M2.1, and Qwen3-VL-8B-Instruct in Amazon SageMaker JumpStart, expanding the portfolio of foundation models available to AWS customers. These three models bring specialized capabilities spanning document intelligence, multilingual coding, advanced multimodal reasoning, and vision-language understanding, enabling customers to build sophisticated AI applications across diverse use cases on AWS infrastructure. These models address different enterprise AI challenges with specialized capabilities: DeepSeek OCR explores visual-text compression for document processing. It can extract structured information from forms, invoices, diagrams, and complex documents with dense text layouts. MiniMax M2.1 is optimized for coding, tool use, instruction following, and long-horizon planning. It automates multilingual software development and executes complex, multi-step office workflows, empowering developers to build autonomous applications. Qwen3-VL-8B-Instruct delivers ssuperior text understanding and generation, deeper visual perception and reasoning, extended context length, enhanced spatial and video dynamics comprehension, and stronger agent interaction capabilities. With SageMaker JumpStart, customers can deploy any of these models with just a few clicks to address their specific AI use cases. To get started with these models, navigate to the SageMaker JumpStart model catalog in the SageMaker console or use the SageMaker Python SDK to deploy the models to your AWS account. For more information about deploying and using foundation models in SageMaker JumpStart, see the Amazon SageMaker JumpStart documentation.   

AWS Security Token Service (STS) now supports validation of select identity provider specific claims from Google, GitHub, CircleCI and Oracle Cloud Infrastructure in IAM role trust policies and resource control policies for OpenID Connect (OIDC) federation into AWS via the AssumeRoleWithWebIdentity API.

With this new capability, you can reference these custom claims as condition keys in IAM role trust policies and resource control policies, expanding your ability to implement fine-grained access control for federated identities and help you establish your data perimeters. This enhancement builds upon IAM’s existing OIDC federation capabilities, which allow you to grant temporary AWS credentials to users authenticated through external OIDC-compatible identity providers.

​AWS Security Token Service (STS) now supports validation of select identity provider specific claims from Google, GitHub, CircleCI and Oracle Cloud Infrastructure in IAM role trust policies and resource control policies for OpenID Connect (OIDC) federation into AWS via the AssumeRoleWithWebIdentity API. With this new capability, you can reference these custom claims as condition keys in IAM role trust policies and resource control policies, expanding your ability to implement fine-grained access control for federated identities and help you establish your data perimeters. This enhancement builds upon IAM’s existing OIDC federation capabilities, which allow you to grant temporary AWS credentials to users authenticated through external OIDC-compatible identity providers.  

Amazon CloudFront announces support for mutual TLS authentication (mTLS) for origins, a security protocol that enables customers to verify that requests to their origin servers come only from their authorized CloudFront distributions using TLS certificates. This certificate-based authentication provides cryptographic verification of CloudFront’s identity, eliminating the need for customers to manage custom security controls.

Previously, verifying that requests came from CloudFront distributions required customers to build and maintain custom authentication solutions like shared secret headers or IP allow-lists, particularly for public or externally hosted origins. These approaches required ongoing operational overhead to rotate secrets, update allow-lists, and maintain custom code. Now with origin mTLS support, customers can implement a standardized, certificate-based authentication approach that eliminates this operational burden. This enables organizations to enforce strict authentication for their proprietary content, ensuring that only verified CloudFront distributions can establish connections to backend infrastructure ranging from AWS origins and on-premises servers to third-party cloud providers and external CDNs. Customers can leverage client certificates issued by AWS Private Certificate Authority or third-party private Certificate Authorities, which they import through AWS Certificate Manager.

Customers can configure origin mTLS using the AWS Management Console, CLI, SDK, CDK, or CloudFormation. Origin mTLS is supported for all origins that support mutual TLS on AWS such as Application Load Balancer and API Gateway, as well as on-premises and custom origins. There is no additional charge for origin mTLS. Origin mTLS is also available in the Business and Premium flat-rate pricing plans. For detailed implementation guidance and best practices, visit the CloudFront origin mutual TLS documentation.

​Amazon CloudFront announces support for mutual TLS authentication (mTLS) for origins, a security protocol that enables customers to verify that requests to their origin servers come only from their authorized CloudFront distributions using TLS certificates. This certificate-based authentication provides cryptographic verification of CloudFront’s identity, eliminating the need for customers to manage custom security controls. Previously, verifying that requests came from CloudFront distributions required customers to build and maintain custom authentication solutions like shared secret headers or IP allow-lists, particularly for public or externally hosted origins. These approaches required ongoing operational overhead to rotate secrets, update allow-lists, and maintain custom code. Now with origin mTLS support, customers can implement a standardized, certificate-based authentication approach that eliminates this operational burden. This enables organizations to enforce strict authentication for their proprietary content, ensuring that only verified CloudFront distributions can establish connections to backend infrastructure ranging from AWS origins and on-premises servers to third-party cloud providers and external CDNs. Customers can leverage client certificates issued by AWS Private Certificate Authority or third-party private Certificate Authorities, which they import through AWS Certificate Manager. Customers can configure origin mTLS using the AWS Management Console, CLI, SDK, CDK, or CloudFormation. Origin mTLS is supported for all origins that support mutual TLS on AWS such as Application Load Balancer and API Gateway, as well as on-premises and custom origins. There is no additional charge for origin mTLS. Origin mTLS is also available in the Business and Premium flat-rate pricing plans. For detailed implementation guidance and best practices, visit the CloudFront origin mutual TLS documentation.  

AWS Network Firewall now supports flexible cost allocation through AWS Transit Gateway native attachments in AWS GovCloud (US) Regions, enabling you to automatically distribute data processing costs across different AWS accounts. Customers can create metering policies to apply data processing charges based on their organization’s chargeback requirements instead of consolidating all expenses in the firewall owner account.

This capability helps security and network teams better manage centralized firewall costs by distributing charges to application teams based on actual usage. Organizations can now maintain centralized security controls while automatically allocating inspection costs to the appropriate business units or application owners, eliminating the need for custom cost management solutions.

Flexible cost allocation is available in AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. You can enable these features using the AWS Management Console, AWS Command Line Interface (CLI) and the AWS Software Development Kit (SDK).

There are no additional charges for using this attachment or flexible cost allocation beyond standard pricing of AWS Network Firewall and AWS Transit Gateway. To get started, visit the Flexible Cost Allocation on AWS Transit Gateway service documentation.

​AWS Network Firewall now supports flexible cost allocation through AWS Transit Gateway native attachments in AWS GovCloud (US) Regions, enabling you to automatically distribute data processing costs across different AWS accounts. Customers can create metering policies to apply data processing charges based on their organization’s chargeback requirements instead of consolidating all expenses in the firewall owner account. This capability helps security and network teams better manage centralized firewall costs by distributing charges to application teams based on actual usage. Organizations can now maintain centralized security controls while automatically allocating inspection costs to the appropriate business units or application owners, eliminating the need for custom cost management solutions. Flexible cost allocation is available in AWS GovCloud (US-East) and AWS GovCloud (US-West) Regions. You can enable these features using the AWS Management Console, AWS Command Line Interface (CLI) and the AWS Software Development Kit (SDK). There are no additional charges for using this attachment or flexible cost allocation beyond standard pricing of AWS Network Firewall and AWS Transit Gateway. To get started, visit the Flexible Cost Allocation on AWS Transit Gateway service documentation.  

Amazon Connect now offers APIs to configure and run tests that simulate contact center experiences, making it easy to validate workflows, self-service voice interactions, and their outcomes. With these APIs, you can programmatically configure test parameters, including the caller’s phone number or customer profile, the reason for the call (such as «I need to check my order status»), the expected responses (such as «Your request has been processed»), and business conditions like after-hours scenarios or full call queues. With this launch, you can also integrate testing directly into CI/CD pipelines, run multiple tests simultaneously to validate workflows at scale, and enable automated regression testing as part of your deployment cycles. These capabilities allow you to rapidly validate changes to your workflows and confidently deploy new customer experiences to production.

To learn more about these features, see the Amazon Connect API Reference and Amazon Connect Administrator Guide. These features are available in Asia Pacific (Mumbai), Africa (Cape Town), Europe (Frankfurt), US East (N. Virginia), Asia Pacific (Seoul), Europe (London), Asia Pacific (Tokyo), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), and Canada (Central) regions. To learn more about Amazon Connect, AWS’s AI-native customer experience solution, please visit the Amazon Connect website.

​Amazon Connect now offers APIs to configure and run tests that simulate contact center experiences, making it easy to validate workflows, self-service voice interactions, and their outcomes. With these APIs, you can programmatically configure test parameters, including the caller’s phone number or customer profile, the reason for the call (such as «I need to check my order status»), the expected responses (such as «Your request has been processed»), and business conditions like after-hours scenarios or full call queues. With this launch, you can also integrate testing directly into CI/CD pipelines, run multiple tests simultaneously to validate workflows at scale, and enable automated regression testing as part of your deployment cycles. These capabilities allow you to rapidly validate changes to your workflows and confidently deploy new customer experiences to production.
To learn more about these features, see the Amazon Connect API Reference and Amazon Connect Administrator Guide. These features are available in Asia Pacific (Mumbai), Africa (Cape Town), Europe (Frankfurt), US East (N. Virginia), Asia Pacific (Seoul), Europe (London), Asia Pacific (Tokyo), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), and Canada (Central) regions. To learn more about Amazon Connect, AWS’s AI-native customer experience solution, please visit the Amazon Connect website.  

Amazon Connect now delivers improved estimated wait time metrics for queues and enqueued contacts, empowering organizations. This allows contact centers to set accurate customer expectations, provide convenient options such as callbacks when hold times are extended, and balance workloads effectively across multiple queues. By leveraging the improved estimated wait time metrics, contact centers can make more strategic routing choices across queues while gaining enhanced visibility for better resource planning. For example, a customer calling about billing during peak hours with a 15-minute wait is seamlessly transferred to a cross-trained team with 2-minute availability, getting help faster without repeating their issue. The metric works seamlessly with routing criteria and agent proficiency configurations. 

​Amazon Connect now delivers improved estimated wait time metrics for queues and enqueued contacts, empowering organizations. This allows contact centers to set accurate customer expectations, provide convenient options such as callbacks when hold times are extended, and balance workloads effectively across multiple queues. By leveraging the improved estimated wait time metrics, contact centers can make more strategic routing choices across queues while gaining enhanced visibility for better resource planning. For example, a customer calling about billing during peak hours with a 15-minute wait is seamlessly transferred to a cross-trained team with 2-minute availability, getting help faster without repeating their issue. The metric works seamlessly with routing criteria and agent proficiency configurations.