SageMaker JumpStart now offers optimized deployments, enabling customers to deploy foundation models with pre-configured settings tailored to specific use cases and performance constraints. SageMaker JumpStart optimized deployments simplify model deployment by offering task-aware configurations that optimize for cost, throughput, or latency based on your workload requirements – whether content generation, summarization, or Q&A. This launch includes support for 30+ popular models from Meta, Microsoft, Mistral AI, Qwen, Google, and TII, with visibility into key performance metrics like P50 latency, time-to-first token (TTFT), and throughput before deployment.
With SageMaker JumpStart optimized deployments, customers can select from use case-specific configurations (such as generative writing or chat-style interactions) and choose optimization targets including cost-optimized, throughput-optimized, latency-optimized, or balanced performance. Models deploy to SageMaker AI Managed Inference endpoints or SageMaker HyperPod clusters with pre-set configurations that eliminate guesswork while maintaining full visibility into deployment details. Available models include Meta Llama 3.1 and 3.2 variants, Microsoft Phi-3, Mistral AI models including the new Mistral-Small-24B-Instruct-2501, Qwen 2 and 3 series including multimodal Qwen2-VL, Google Gemma, and TII Falcon3. All deployments leverage SageMaker’s VPC deployment capabilities, ensuring data control and production-ready infrastructure with enterprise-grade security. The feature is available in all AWS regions where SageMaker JumpStart is curretly supported.
To get started with optimized deployments, navigate to Models in SageMaker Studio, select your desired foundation model in the JumpStart Models tab, choose «Deploy,» and select your use case and performance optimization target. For details, visit the SageMaker JumpStart documentation. AWS is actively expanding support to include additional models.
SageMaker JumpStart now offers optimized deployments, enabling customers to deploy foundation models with pre-configured settings tailored to specific use cases and performance constraints. SageMaker JumpStart optimized deployments simplify model deployment by offering task-aware configurations that optimize for cost, throughput, or latency based on your workload requirements – whether content generation, summarization, or Q&A. This launch includes support for 30+ popular models from Meta, Microsoft, Mistral AI, Qwen, Google, and TII, with visibility into key performance metrics like P50 latency, time-to-first token (TTFT), and throughput before deployment.
With SageMaker JumpStart optimized deployments, customers can select from use case-specific configurations (such as generative writing or chat-style interactions) and choose optimization targets including cost-optimized, throughput-optimized, latency-optimized, or balanced performance. Models deploy to SageMaker AI Managed Inference endpoints or SageMaker HyperPod clusters with pre-set configurations that eliminate guesswork while maintaining full visibility into deployment details. Available models include Meta Llama 3.1 and 3.2 variants, Microsoft Phi-3, Mistral AI models including the new Mistral-Small-24B-Instruct-2501, Qwen 2 and 3 series including multimodal Qwen2-VL, Google Gemma, and TII Falcon3. All deployments leverage SageMaker’s VPC deployment capabilities, ensuring data control and production-ready infrastructure with enterprise-grade security. The feature is available in all AWS regions where SageMaker JumpStart is curretly supported.
To get started with optimized deployments, navigate to Models in SageMaker Studio, select your desired foundation model in the JumpStart Models tab, choose «Deploy,» and select your use case and performance optimization target. For details, visit the SageMaker JumpStart documentation. AWS is actively expanding support to include additional models.
Starting today, Amazon Elastic Compute Cloud (Amazon EC2) X8aedz instances are available in Europe (Stockholm) region. These instances are powered by 5th Gen AMD EPYC processors (formerly code named Turin). These instances offer the highest maximum CPU frequency, 5GHz in the cloud.
X8aedz instances are built using the latest sixth generation AWS Nitro Cards and are ideal for electronic design automation (EDA) workloads such as physical layout and physical verification jobs, and relational databases that benefit from high single-threaded processor performance and a large memory footprint. The combination of 5 GHz processors and local NVMe storage enables faster processing of memory-intensive backend EDA workloads such as floor planning, logic placement, clock tree synthesis (CTS), routing, and power/signal integrity analysis.
X8aedz instances feature a 32:1 ratio of memory to vCPU and are available in 8 sizes ranging from 2 to 96 vCPUs with 64 to 3,072 GiB of memory, including two bare metal variants, and up to 8 TB of local NVMe SSD storage.
Customers can purchase X8aedz instances via Savings Plans, On-Demand instances, and Spot instances. To get started, sign in to the AWS Management Console. For more information visit the Amazon EC2 X8aedz instance page.
Starting today, Amazon Elastic Compute Cloud (Amazon EC2) X8aedz instances are available in Europe (Stockholm) region. These instances are powered by 5th Gen AMD EPYC processors (formerly code named Turin). These instances offer the highest maximum CPU frequency, 5GHz in the cloud. X8aedz instances are built using the latest sixth generation AWS Nitro Cards and are ideal for electronic design automation (EDA) workloads such as physical layout and physical verification jobs, and relational databases that benefit from high single-threaded processor performance and a large memory footprint. The combination of 5 GHz processors and local NVMe storage enables faster processing of memory-intensive backend EDA workloads such as floor planning, logic placement, clock tree synthesis (CTS), routing, and power/signal integrity analysis. X8aedz instances feature a 32:1 ratio of memory to vCPU and are available in 8 sizes ranging from 2 to 96 vCPUs with 64 to 3,072 GiB of memory, including two bare metal variants, and up to 8 TB of local NVMe SSD storage. Customers can purchase X8aedz instances via Savings Plans, On-Demand instances, and Spot instances. To get started, sign in to the AWS Management Console. For more information visit the Amazon EC2 X8aedz instance page.
Amazon CloudWatch RUM (Real User Monitoring) is a feature of Amazon CloudWatch that enables developers and operations teams to collect, view, and analyze client-side performance data from real end-user sessions in web and mobile applications. With its expansion to the AWS European Sovereign Cloud, customers operating under strict European data residency and sovereignty requirements can now monitor their web application performance without data leaving the sovereign boundary. This capability is designed for enterprises, public sector organizations, and regulated industries in Europe that require full control over where their data is stored and processed.
CloudWatch RUM helps teams proactively identify and resolve performance bottlenecks across both web and mobile applications by surfacing real-time metrics such as page load times, JavaScript errors, HTTP failures, and mobile-specific signals like crash rates and network latency — enabling faster root cause analysis and improved end-user experience. For example, a European public sector organization can use CloudWatch RUM within the AWS European Sovereign Cloud to monitor citizen-facing web portals and mobile apps while maintaining full data sovereignty compliance.
CloudWatch RUM in the AWS European Sovereign Cloud is available today in the EU Sovereign (eusc-de-east-1) region — to get started, visit the Amazon CloudWatch RUM documentation.
Amazon CloudWatch RUM (Real User Monitoring) is a feature of Amazon CloudWatch that enables developers and operations teams to collect, view, and analyze client-side performance data from real end-user sessions in web and mobile applications. With its expansion to the AWS European Sovereign Cloud, customers operating under strict European data residency and sovereignty requirements can now monitor their web application performance without data leaving the sovereign boundary. This capability is designed for enterprises, public sector organizations, and regulated industries in Europe that require full control over where their data is stored and processed.
CloudWatch RUM helps teams proactively identify and resolve performance bottlenecks across both web and mobile applications by surfacing real-time metrics such as page load times, JavaScript errors, HTTP failures, and mobile-specific signals like crash rates and network latency — enabling faster root cause analysis and improved end-user experience. For example, a European public sector organization can use CloudWatch RUM within the AWS European Sovereign Cloud to monitor citizen-facing web portals and mobile apps while maintaining full data sovereignty compliance.
CloudWatch RUM in the AWS European Sovereign Cloud is available today in the EU Sovereign (eusc-de-east-1) region — to get started, visit the Amazon CloudWatch RUM documentation.
Un nuevo estudio explora cómo la IA moldea lo que puedes confiar en línea
Por: Samantha Kubota, escritora de Microsoft.
Los ven en sus redes sociales: vídeos de bebés adorables que dicen cosas que suenan muy adultas, figuras públicas que hacen declaraciones poco características de ellos, fotos de naturaleza demasiado descabelladas para ser verdad. En la era de la IA, ver no siempre es creer.
Los deepfakes1 amenazan la confianza en las noticias, las elecciones, las marcas y las interacciones cotidianas, llevándonos a cuestionar qué es real. Determinar qué es auténtico o manipulado es el tema del informe de Microsoft «Media Integrity and Authentication: Status, Directions, and Futures«. El estudio evalúa los métodos de autenticación actuales para comprender mejor sus limitaciones, explorar posibles formas de fortalecerlos y ayudar a las personas a tomar decisiones informadas sobre el contenido en línea que consumen.
Los autores concluyen que ninguna solución única puede prevenir el engaño digital por sí sola. Métodos como la procedencia, la marca de agua y la huella digital pueden ofrecer información útil como quién creó el contenido, qué herramientas se usaron y si este ha sido modificado.
Jessica Young, directora de política científica y tecnológica en la Oficina del Director Científico de Microsoft.
Las personas pueden ser engañadas por los medios si carecen de información como su origen e historia, o si su información es de baja calidad o engañosa. El objetivo del informe es proporcionar una hoja de ruta para ofrecer más información de procedencia de alta garantía en la que el público pueda confiar, según Jessica Young, directora de política científica y tecnológica en la Oficina del Director Científico de Microsoft.
Ayudar a las personas a reconocer indicadores de contenido de mayor calidad es cada vez más importante a medida que los deepfakes se vuelven más disruptivos y la legislación sobre procedencia en varios países, incluido Estados Unidos, introduce aún más formas de ayudar a las personas a autenticar contenido más adelante este año.
Young, copresidenta del estudio, explica más sobre lo que todo esto significa:
¿Qué motivó el estudio?
«La motivación era doble», dice Young. «La primera es el reconocimiento del momento en el que estamos ahora mismo. Sabemos que las capacidades de IA generativa ganan cada vez más potencia. Cada vez es más difícil distinguir entre contenido auténtico —como contenido capturado por una cámara, frente a deepfakes sofisticados— y, como resultado, ahora mismo hay un gran aumento en los intereses y requisitos para utilizar esas tecnologías existentes para revelar y verificar si el contenido fue generado o manipulado por IA.
«El momento se ha gestado poco a poco, y tenemos el deseo de ayudar a asegurar que estas tecnologías generen más beneficio que daño, según cómo se usen y entiendan.»
Young añade que el documento pretende informar al ecosistema más amplio de integridad mediática y autenticación, incluidos creadores, tecnólogos, responsables políticos y otros, para entender qué es y qué no es posible en la actualidad y cómo podemos construir sobre ello en el futuro.
¿Qué logró el estudio y qué aprendiste?
El informe describe un camino para aumentar la confianza en la autenticidad de los medios. Los autores proponen una dirección que denominan «autenticación de alta confianza» para mitigar las debilidades de varios métodos de integridad mediática.
Vincular la procedencia de C2PA a una marca de agua imperceptible puede aportar una confianza más o menos alta sobre la procedencia de los medios, afirma.
También señala que el informe tiene muchas advertencias, como que la procedencia de dispositivos tradicionales sin conexión como las cámaras, que a menudo carecen de características de seguridad críticas, puede ser menos fiable porque es más fácil de modificar.
No es posible prevenir cada ataque ni evitar que ciertas plataformas eliminen señales de procedencia, por lo que el reto, dice Young, «es averiguar cómo sacar a la luz los indicadores más fiables con una seguridad sólida incorporada — y, cuando sea necesario, reforzarlos con métodos adicionales que permitan la recuperación o apoyen el trabajo manual de forense digital.»
¿En qué se diferencia este estudio de otros?
Young dice que su estudio investigó dos líneas de pensamiento «poco exploradas» para los tres métodos de verificación. Definen el primero como ataques sociotécnicos, donde la información de procedencia o los propios medios podrían manipularse para que el contenido auténtico parezca sintético o el contenido falso parezca real durante el proceso de validación.
«Imagina que ves una imagen auténtica de un evento deportivo global con el 80% del público que anima al equipo local», dice. «El equipo visitante se involucra en una discusión en línea donde alega: ‘Oye, no, todo eso es una multitud falsa.’ Alguien podría hacer una pequeña e insignificante edición a una persona en la esquina de la imagen y los métodos actuales lo considerarían generado por IA, incluso si el tamaño del público fuera real. Estos métodos que se supone que apoyan la autenticidad ahora refuerzan una narrativa falsa, en lugar de la verdadera.
«Así que, con el conocimiento de cómo funcionan los diferentes validadores, incluso con modificaciones muy sutiles, podrías manipular los resultados que el público vería para intentar engañarles sobre el contenido», dice. El segundo tema clave se basa en el trabajo del C2PA para hacer que las credenciales de contenido sean más duraderas, al tiempo que aborda la fiabilidad. Aquí es donde la investigación resulta en especial novedosa, dice Young. «Analizamos cómo se puede añadir y mantener información de procedencia en diferentes entornos — desde sistemas de alta seguridad hasta dispositivos sin conexión menos seguros — y qué significa eso para la fiabilidad.»
¿Por qué es tan difícil verificar los medios digitales?
Autenticar medios es complejo porque no existe una solución única para todos, dice Young.
«Tienes diferentes formatos que tienen distintas limitaciones o compensaciones para las señales que pueden contener», explica. «Ya sea imágenes, audio, vídeo — sin mencionar el texto, que tiene toda una gama diferente de desafíos — y lo sólidas que pueden aplicarse las soluciones allí.»
Young dice que existen diferentes requisitos y opiniones sobre qué nivel de transparencia es apropiado. En algunos casos, los usuarios pueden no querer que ninguna de sus informaciones personales se incluyan en la procedencia digital de un medio, mientras que en otros, creadores o artistas pueden querer la atribución y optar por incluir su información.
«Así que tienes diferentes requisitos o incluso consideraciones sobre lo que implica esa información de procedencia», dice. «Y luego, al igual que en el campo de la seguridad, ninguna solución es infalible. Así que todos los métodos son complementarios, pero cada uno tiene limitaciones inherentes.»
¿Y ahora qué hacemos?
Young afirma que, a medida que el contenido creado o editado por IA se vuelve más común, el uso de procedencia segura de contenido auténtico es cada vez más importante. Editores, figuras públicas, gobiernos y empresas tienen buenas razones para certificar la autenticidad del contenido que comparten. Si un medio de comunicación graba fotos de un evento, por ejemplo, vincular información de procedencia segura a esas imágenes puede ayudar a demostrar a su audiencia que el contenido es fiable.
«Los organismos gubernamentales también tienen interés en que el público sepa que sus documentos o medios formales son información fiable sobre asuntos de interés público», afirma Young.
Añade que, a medida que las modificaciones por IA en los medios se vuelven «cada vez más comunes» con fines legítimos, la procedencia segura puede proporcionar un contexto importante para evitar que un lector o espectador medio tan solo descarte ese contenido como falso o engañoso.
«Para la industria y para los reguladores, destacamos lo importante que es la investigación continua de los usuarios en esta área para impulsar una exhibición más coherente y útil de esta información al público — para asegurarnos de que en verdad sea significativa y útil en la práctica», afirma Young.
«Tenemos un conjunto limitado de tecnologías que pueden ayudarnos, y no queremos que salgan mal interpretadas o mal usadas.»
1Contenido digital (video, audio o imagen) creado con inteligencia artificial que imita de forma muy realista a una persona, haciéndola parecer que dice o hace algo que en realidad nunca ocurrió.
Amazon CloudWatch now supports auditing telemetry configuration and enabling telemetry from AWS services such as Amazon EC2, Amazon VPC, and AWS CloudTrail across multiple AWS Regions from a single region. Customers can enable the telemetry auditing feature for their account or organization across all supported regions at once and create enablement rules that automatically apply to selected regions or all available regions.
With today’s launch, customers can scope enablement rules to specific regions or all supported regions. For example, a central security team can create a single organization-wide enablement rule for VPC Flow Logs that applies across all regions, ensuring consistent telemetry collection for every VPC across every account. Rules configured for all regions automatically expand to include new regions as they become available.
CloudWatch’s cross-region telemetry configuration and enablement rule is available in all AWS commercial regions. Standard CloudWatch pricing applies for telemetry ingestion. To learn more, visit the Amazon CloudWatch documentation.
Amazon CloudWatch now supports auditing telemetry configuration and enabling telemetry from AWS services such as Amazon EC2, Amazon VPC, and AWS CloudTrail across multiple AWS Regions from a single region. Customers can enable the telemetry auditing feature for their account or organization across all supported regions at once and create enablement rules that automatically apply to selected regions or all available regions.
With today’s launch, customers can scope enablement rules to specific regions or all supported regions. For example, a central security team can create a single organization-wide enablement rule for VPC Flow Logs that applies across all regions, ensuring consistent telemetry collection for every VPC across every account. Rules configured for all regions automatically expand to include new regions as they become available.
CloudWatch’s cross-region telemetry configuration and enablement rule is available in all AWS commercial regions. Standard CloudWatch pricing applies for telemetry ingestion. To learn more, visit the Amazon CloudWatch documentation.
Amazon WorkSpaces Personal and Amazon WorkSpaces Core are now available in US East (Ohio) and Asia Pacific (Malaysia) AWS Regions. You can now provision WorkSpaces closer to your users, helping to provide in-country data residency and a more responsive experience. In US East (Ohio), organizations can also now implement disaster recovery solutions, meet local data residency compliance mandates, and support regional workforces with consistent, low-latency access to their virtual desktop environments across varying network conditions.
Amazon WorkSpaces Personal provides users with instant access to their desktops from anywhere. It allows users to stream desktops from AWS to their devices, and WorkSpaces Personal manages the AWS resources required to host and run your desktops, scales automatically, and provides access to your users on demand. Amazon WorkSpaces Core provides cloud-based, fully managed virtual desktop infrastructure (VDI) accessible to third-party VDI management solutions via API.
To get started with Amazon WorkSpaces Personal or Amazon WorkSpaces Core, sign into the WorkSpaces management console and select the AWS Region of your choice. To learn more about Amazon WorkSpaces offerings, visit the product page and technical documentation.
Amazon WorkSpaces Personal and Amazon WorkSpaces Core are now available in US East (Ohio) and Asia Pacific (Malaysia) AWS Regions. You can now provision WorkSpaces closer to your users, helping to provide in-country data residency and a more responsive experience. In US East (Ohio), organizations can also now implement disaster recovery solutions, meet local data residency compliance mandates, and support regional workforces with consistent, low-latency access to their virtual desktop environments across varying network conditions.
Amazon WorkSpaces Personal provides users with instant access to their desktops from anywhere. It allows users to stream desktops from AWS to their devices, and WorkSpaces Personal manages the AWS resources required to host and run your desktops, scales automatically, and provides access to your users on demand. Amazon WorkSpaces Core provides cloud-based, fully managed virtual desktop infrastructure (VDI) accessible to third-party VDI management solutions via API.
To get started with Amazon WorkSpaces Personal or Amazon WorkSpaces Core, sign into the WorkSpaces management console and select the AWS Region of your choice. To learn more about Amazon WorkSpaces offerings, visit the product page and technical documentation.
You can now create Amazon FSx for Lustre Persistent-2 file systems in four additional AWS Regions: Asia Pacific (Hyderabad, Jakarta), Europe (Zurich), and South America (São Paulo).
Amazon FSx for Lustre Persistent-2 file systems are built on AWS Graviton processors and provide higher throughput per terabyte (up to 1 GB/s per terabyte) and lower cost of throughput compared to previous generation FSx for Lustre file systems. Using FSx for Lustre Persistent-2 file systems, you can accelerate execution of machine learning, high-performance computing, media & entertainment, and financial simulations workloads while reducing your cost of storage.
To get started with Amazon FSx for Lustre Persistent-2 in these new regions, create a file system through the AWS Management Console. To learn more about Amazon FSx for Lustre, visit our product page, and see the AWS Region Table for complete regional availability information.
You can now create Amazon FSx for Lustre Persistent-2 file systems in four additional AWS Regions: Asia Pacific (Hyderabad, Jakarta), Europe (Zurich), and South America (São Paulo).
Amazon FSx for Lustre Persistent-2 file systems are built on AWS Graviton processors and provide higher throughput per terabyte (up to 1 GB/s per terabyte) and lower cost of throughput compared to previous generation FSx for Lustre file systems. Using FSx for Lustre Persistent-2 file systems, you can accelerate execution of machine learning, high-performance computing, media & entertainment, and financial simulations workloads while reducing your cost of storage.
To get started with Amazon FSx for Lustre Persistent-2 in these new regions, create a file system through the AWS Management Console. To learn more about Amazon FSx for Lustre, visit our product page, and see the AWS Region Table for complete regional availability information.
AWS is announcing the general availability of Amazon EC2 C8in and C8ib instances powered by custom, sixth generation Intel Xeon Scalable processors, available only on AWS. These instances feature the latest sixth generation AWS Nitro cards. C8in and C8ib instances deliver up to 43% higher performance compared to previous generation C6in instances.
C8in and C8ib instances deliver larger sizes and scale up to 384 vCPUs. C8in instances deliver 600 Gbps network bandwidth—the highest among enhanced networking EC2 instances—making them ideal for network-intensive workloads like distributed compute and large-scale data analytics. C8ib instances deliver up to 300 Gbps EBS bandwidth, the highest among non-accelerated compute instances, making them ideal for high-performance commercial databases and file systems.
C8in instances are available in US East (N. Virginia), US West (Oregon), Asia Pacific (Tokyo), and Europe (Spain) regions. C8ib instances are available in US East (N. Virginia) and US West (Oregon). Both, C8in and C8ib instances are available via Savings Plans, On-Demand, and Spot instances. For more information, visit the Amazon EC2 C8i instance page.
AWS is announcing the general availability of Amazon EC2 C8in and C8ib instances powered by custom, sixth generation Intel Xeon Scalable processors, available only on AWS. These instances feature the latest sixth generation AWS Nitro cards. C8in and C8ib instances deliver up to 43% higher performance compared to previous generation C6in instances. C8in and C8ib instances deliver larger sizes and scale up to 384 vCPUs. C8in instances deliver 600 Gbps network bandwidth—the highest among enhanced networking EC2 instances—making them ideal for network-intensive workloads like distributed compute and large-scale data analytics. C8ib instances deliver up to 300 Gbps EBS bandwidth, the highest among non-accelerated compute instances, making them ideal for high-performance commercial databases and file systems.
C8in instances are available in US East (N. Virginia), US West (Oregon), Asia Pacific (Tokyo), and Europe (Spain) regions. C8ib instances are available in US East (N. Virginia) and US West (Oregon). Both, C8in and C8ib instances are available via Savings Plans, On-Demand, and Spot instances. For more information, visit the Amazon EC2 C8i instance page.
AWS Elastic Disaster Recovery (AWS DRS) is now available in the AWS European Sovereign Cloud, enabling organizations with data sovereignty requirements to protect their mission-critical workloads with disaster recovery on AWS. AWS DRS minimizes downtime and data loss with fast, reliable recovery of on-premises and cloud-based applications using affordable storage, minimal compute, and point-in-time recovery, with Recovery Point Objectives (RPOs) measured in seconds and Recovery Time Objectives (RTOs) typically in minutes.
With AWS DRS, you can recover applications from physical infrastructure, VMware vSphere, Microsoft Hyper-V, and cloud infrastructure. AWS DRS uses a unified process for testing, recovery, and failback for a wide range of applications, including critical databases such as Oracle, MySQL, and SQL Server, and enterprise applications such as SAP.
AWS Elastic Disaster Recovery is available in the AWS European Sovereign Cloud (Germany). See the AWS Regional Services List for the latest availability information.
AWS Elastic Disaster Recovery (AWS DRS) is now available in the AWS European Sovereign Cloud, enabling organizations with data sovereignty requirements to protect their mission-critical workloads with disaster recovery on AWS. AWS DRS minimizes downtime and data loss with fast, reliable recovery of on-premises and cloud-based applications using affordable storage, minimal compute, and point-in-time recovery, with Recovery Point Objectives (RPOs) measured in seconds and Recovery Time Objectives (RTOs) typically in minutes. With AWS DRS, you can recover applications from physical infrastructure, VMware vSphere, Microsoft Hyper-V, and cloud infrastructure. AWS DRS uses a unified process for testing, recovery, and failback for a wide range of applications, including critical databases such as Oracle, MySQL, and SQL Server, and enterprise applications such as SAP. AWS Elastic Disaster Recovery is available in the AWS European Sovereign Cloud (Germany). See the AWS Regional Services List for the latest availability information. To learn more about AWS Elastic Disaster Recovery, visit our product page or documentation.
Today, AWS announces multi-session support for Amazon Quick, which enables customers to access up to five Amazon Quick accounts simultaneously within the same browser. The feature also includes the Amazon Quick account name in all URLs, enabling users to easily access the correct account when opening agents, spaces, flows, research reports, dashboards, and other assets.
Customers use multiple accounts for different environments such as development, testing, and production, and compare insights and resource configurations across multiple accounts for troubleshooting and other application-related jobs. Using multi-session capability in Amazon Quick, customers can now sign in to multiple accounts and manage their resources in a single browser. You can sign in to another account by accessing the Amazon Quick top right menu and selecting the option to sign in to another account. For users accessing global URLs without an account name, Amazon Quick presents an account input page that pre-populates the accounts they are logged into, allowing them to select the desired account. You have the option to log out of the current session in the specific browser tab or log out of all sessions.
Today, AWS announces multi-session support for Amazon Quick, which enables customers to access up to five Amazon Quick accounts simultaneously within the same browser. The feature also includes the Amazon Quick account name in all URLs, enabling users to easily access the correct account when opening agents, spaces, flows, research reports, dashboards, and other assets. Customers use multiple accounts for different environments such as development, testing, and production, and compare insights and resource configurations across multiple accounts for troubleshooting and other application-related jobs. Using multi-session capability in Amazon Quick, customers can now sign in to multiple accounts and manage their resources in a single browser. You can sign in to another account by accessing the Amazon Quick top right menu and selecting the option to sign in to another account. For users accessing global URLs without an account name, Amazon Quick presents an account input page that pre-populates the accounts they are logged into, allowing them to select the desired account. You have the option to log out of the current session in the specific browser tab or log out of all sessions. Amazon Quick multi-account sign-in is available in all supported Amazon Quick regions. To learn more about this, visit Amazon Quick Signing In
