AWS launches AWS Interconnect – last mile preview with Megaport, a fully managed connectivity offering that allows customers to connect their branch offices, data centers, and remote locations to AWS with just a few clicks, eliminating the friction and complexity of network setup. As a milestone collaboration between AWS and Megaport, AWS Interconnect – last mile combines AWS cloud innovation with Megaport operating one of the world’s largest Software Defined Networks (SDN), with 1,200+ enabled data centers across 31 countries.

Through the AWS Management Console, customers can now instantly establish private, high-speed connections to AWS by simply choosing their preferred AWS Region, bandwidth speed, Direct Connect Gateway ID and partner subscriber ID. Once initiated, AWS generates an activation key to complete connectivity provisioning with Megaport. The launch simplifies the connectivity experience by pre-provisioning capacity and automating complex network configuration including BGP peering, VLAN configuration, and ASN assignment. At GA, customers will also be able to dynamically scale bandwidth from 1 Gbps to 100 Gbps through the AWS Console. The service is designed for high availability, with zero down-time maintenance, backed by a 99.99% SLA. 

AWS Interconnect – last mile is available in the San Jose (us-west-1) and N. Virginia (us-east-1) metros through Megaport. You can create a preview Interconnect using the AWS Management Console, Command Line Interface (CLI), or API. Partners can also easily adopt via a published open API package on GitHub. For more information, see the AWS Interconnect – last mile documentation and pricing pages.

​AWS launches AWS Interconnect – last mile preview with Megaport, a fully managed connectivity offering that allows customers to connect their branch offices, data centers, and remote locations to AWS with just a few clicks, eliminating the friction and complexity of network setup. As a milestone collaboration between AWS and Megaport, AWS Interconnect – last mile combines AWS cloud innovation with Megaport operating one of the world’s largest Software Defined Networks (SDN), with 1,200+ enabled data centers across 31 countries.
Through the AWS Management Console, customers can now instantly establish private, high-speed connections to AWS by simply choosing their preferred AWS Region, bandwidth speed, Direct Connect Gateway ID and partner subscriber ID. Once initiated, AWS generates an activation key to complete connectivity provisioning with Megaport. The launch simplifies the connectivity experience by pre-provisioning capacity and automating complex network configuration including BGP peering, VLAN configuration, and ASN assignment. At GA, customers will also be able to dynamically scale bandwidth from 1 Gbps to 100 Gbps through the AWS Console. The service is designed for high availability, with zero down-time maintenance, backed by a 99.99% SLA. 
AWS Interconnect – last mile is available in the San Jose (us-west-1) and N. Virginia (us-east-1) metros through Megaport. You can create a preview Interconnect using the AWS Management Console, Command Line Interface (CLI), or API. Partners can also easily adopt via a published open API package on GitHub. For more information, see the AWS Interconnect – last mile documentation and pricing pages.  

Amazon SageMaker AI now supports serverless model customization for Muse Glimmer, Qwen3.8 27B, and Ministral 3 3B, 8B, and 14B models. In addition to deploying these models on SageMaker AI, you can now adapt them to your specific domains and workflows, using supervised fine-tuning (SFT), direct preference optimization (DPO), and reinforcement fine-tuning (RFT) techniques. You can also adapt these models with either low-rank adaptation (LoRA) or full fine-tuning techniques. This launch adds these models to a wide variety of models available for serverless customization on SageMaker AI, including models from the Nova, Gemma 4, Nemotron 3.5, Qwen, Llama, gpt-oss, and DeepSeek families.

Model customization lets you tailor foundation models with your proprietary data so a smaller, right-sized model can match frontier-model quality on your tasks, while also reducing cost and latency. You can use labeled data with SFT to improve accuracy on domain-specific tasks, preference data with DPO to align outputs with your organization’s tone, or reward signals with RFT to improve performance on new tasks. With serverless customization, SageMaker AI handles all infrastructure provisioning and training orchestration, so you can focus on your data and evaluation rather than cluster management, and only pay for what you use.

Serverless model customization on SageMaker AI is available in US East (N. Virginia), US West (Oregon), Asia Pacific (Tokyo), and Europe (Ireland). To get started, navigate to the Models page in Amazon SageMaker Studio to launch a customization job, use the SageMaker Python SDK or use our Agent skills with your choice of coding assistant. To learn more and see the full supported list of models, see the Amazon SageMaker AI model customization documentation.

​Amazon SageMaker AI now supports serverless model customization for Muse Glimmer, Qwen3.8 27B, and Ministral 3 3B, 8B, and 14B models. In addition to deploying these models on SageMaker AI, you can now adapt them to your specific domains and workflows, using supervised fine-tuning (SFT), direct preference optimization (DPO), and reinforcement fine-tuning (RFT) techniques. You can also adapt these models with either low-rank adaptation (LoRA) or full fine-tuning techniques. This launch adds these models to a wide variety of models available for serverless customization on SageMaker AI, including models from the Nova, Gemma 4, Nemotron 3.5, Qwen, Llama, gpt-oss, and DeepSeek families.
Model customization lets you tailor foundation models with your proprietary data so a smaller, right-sized model can match frontier-model quality on your tasks, while also reducing cost and latency. You can use labeled data with SFT to improve accuracy on domain-specific tasks, preference data with DPO to align outputs with your organization’s tone, or reward signals with RFT to improve performance on new tasks. With serverless customization, SageMaker AI handles all infrastructure provisioning and training orchestration, so you can focus on your data and evaluation rather than cluster management, and only pay for what you use.
Serverless model customization on SageMaker AI is available in US East (N. Virginia), US West (Oregon), Asia Pacific (Tokyo), and Europe (Ireland). To get started, navigate to the Models page in Amazon SageMaker Studio to launch a customization job, use the SageMaker Python SDK or use our Agent skills with your choice of coding assistant. To learn more and see the full supported list of models, see the Amazon SageMaker AI model customization documentation.  

Amazon Cognito multi-Region replication (MRR) now supports AWS GovCloud (US) Regions, extending the resilience benefits of MRR to more workloads. MRR lets you synchronize user and machine identity data, including credentials, user pool configurations, and federation setups, to a secondary user pool in a standby Region you designate, in near real-time. With user data in the standby Region, you can redirect traffic and keep authentication available if there is a disruption in your primary Region.

Previously, MRR was available in 16 commercial Regions. You can now also use MRR to replicate between additional AWS Regions, helping you meet resilience, data residency, and compliance requirements in the Regions that best align with your business needs.

MRR is available as an add-on for user pools in the Essentials or Plus feature tiers, and requires a multi-Region AWS KMS customer managed key (CMK). For the full list of AWS Regions where Amazon Cognito is available, see AWS Capabilities by Region. To get started, visit the developer guide for instructions and the pricing page for pricing details.

​Amazon Cognito multi-Region replication (MRR) now supports AWS GovCloud (US) Regions, extending the resilience benefits of MRR to more workloads. MRR lets you synchronize user and machine identity data, including credentials, user pool configurations, and federation setups, to a secondary user pool in a standby Region you designate, in near real-time. With user data in the standby Region, you can redirect traffic and keep authentication available if there is a disruption in your primary Region. Previously, MRR was available in 16 commercial Regions. You can now also use MRR to replicate between additional AWS Regions, helping you meet resilience, data residency, and compliance requirements in the Regions that best align with your business needs. MRR is available as an add-on for user pools in the Essentials or Plus feature tiers, and requires a multi-Region AWS KMS customer managed key (CMK). For the full list of AWS Regions where Amazon Cognito is available, see AWS Capabilities by Region. To get started, visit the developer guide for instructions and the pricing page for pricing details.  

Migration assessments in AWS Transform now evaluate on-premises storage for migration to AWS. Instead of manually analyzing thousands of volumes across protocols, capacity, and performance, you upload a storage inventory and AWS Transform does the mapping for you. It matches each workload to the best-fit service, sizes the recommendation, and projects costs to produce a total cost of ownership business case. Bring NAS shares, SAN LUNs, direct-attached disks, or backup repositories via a NetApp Digital Advisor export, RVTools file, or other inventory. AWS Transform routes workloads across Amazon S3, Amazon EBS, Amazon EFS, and Amazon FSx (NetApp ONTAP, Windows File Server, OpenZFS, Lustre). Run what-if scenarios to compare deployment options such as Single-AZ vs. Multi-AZ or cost-optimized vs. performance-optimized, then ask follow-up questions about any result in chat.

Storage migration assessments are available in all AWS Regions where AWS Transform is available. To learn more, see the AWS Transform User Guide.

​Migration assessments in AWS Transform now evaluate on-premises storage for migration to AWS. Instead of manually analyzing thousands of volumes across protocols, capacity, and performance, you upload a storage inventory and AWS Transform does the mapping for you. It matches each workload to the best-fit service, sizes the recommendation, and projects costs to produce a total cost of ownership business case. Bring NAS shares, SAN LUNs, direct-attached disks, or backup repositories via a NetApp Digital Advisor export, RVTools file, or other inventory. AWS Transform routes workloads across Amazon S3, Amazon EBS, Amazon EFS, and Amazon FSx (NetApp ONTAP, Windows File Server, OpenZFS, Lustre). Run what-if scenarios to compare deployment options such as Single-AZ vs. Multi-AZ or cost-optimized vs. performance-optimized, then ask follow-up questions about any result in chat.
Storage migration assessments are available in all AWS Regions where AWS Transform is available. To learn more, see the AWS Transform User Guide.  

Today, AWS announced the expansion of 10 Gbps and 100 Gbps dedicated connections with MACsec encryption capabilities at the existing AWS Direct Connect location in the Equinix MA3 data center near Manchester, England. You can now establish private, direct network access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones from this location. This is the third AWS Direct Connect location in England to provide 100 Gbps connections with MACsec encryption capabilities.

The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet.

For more information on the over 150 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.

​Today, AWS announced the expansion of 10 Gbps and 100 Gbps dedicated connections with MACsec encryption capabilities at the existing AWS Direct Connect location in the Equinix MA3 data center near Manchester, England. You can now establish private, direct network access to all public AWS Regions (except those in China), AWS GovCloud Regions, and AWS Local Zones from this location. This is the third AWS Direct Connect location in England to provide 100 Gbps connections with MACsec encryption capabilities.
The Direct Connect service enables you to establish a private, physical network connection between AWS and your data center, office, or colocation environment. These private connections can provide a more consistent network experience than those made over the public internet.
For more information on the over 150 Direct Connect locations worldwide, visit the locations section of the Direct Connect product detail pages. Or, visit our getting started page to learn more about how to purchase and deploy Direct Connect.  

Starting today, you can reserve compute capacity for your Amazon Aurora and Amazon RDS DB instances in one or more Availability Zones for as long as you need it. Reserving capacity helps ensure that DB instance create, restore, scale-compute, and start operations don’t fail because of insufficient capacity.

On-Demand Capacity Reservation is designed for workloads that need assurance that specific DB instance capacity will be available when they need it for business-critical events, such as migrations, product launches, seasonal peaks, high-availability deployments, or disaster recovery. You choose the DB instance class, engine, Availability Zones, and reserved capacity per Availability Zone, and RDS holds that capacity for you. Capacity can be reserved in two or more Availability Zones to support Multi-AZ deployments. To use the reserved capacity, reference the reservation when you create, restore, modify, or start a DB instance.

You can reserve capacity for immediate use with no commitment and cancel at any time, or schedule a reservation to begin 5 to 120 days in the future with a minimum commitment. Reserved capacity is billed at On-Demand rates while the reservation is active, whether or not DB instances within the reservation are running. Discounts from your existing Reserved DB Instances or Database Savings Plans apply automatically.

On-Demand Capacity Reservation is available for Amazon Aurora and Amazon RDS in all AWS commercial Regions. To learn more about On-Demand Capacity Reservation, visit the documentation for Amazon Aurora and Amazon RDS. 

​Starting today, you can reserve compute capacity for your Amazon Aurora and Amazon RDS DB instances in one or more Availability Zones for as long as you need it. Reserving capacity helps ensure that DB instance create, restore, scale-compute, and start operations don’t fail because of insufficient capacity.
On-Demand Capacity Reservation is designed for workloads that need assurance that specific DB instance capacity will be available when they need it for business-critical events, such as migrations, product launches, seasonal peaks, high-availability deployments, or disaster recovery. You choose the DB instance class, engine, Availability Zones, and reserved capacity per Availability Zone, and RDS holds that capacity for you. Capacity can be reserved in two or more Availability Zones to support Multi-AZ deployments. To use the reserved capacity, reference the reservation when you create, restore, modify, or start a DB instance.
You can reserve capacity for immediate use with no commitment and cancel at any time, or schedule a reservation to begin 5 to 120 days in the future with a minimum commitment. Reserved capacity is billed at On-Demand rates while the reservation is active, whether or not DB instances within the reservation are running. Discounts from your existing Reserved DB Instances or Database Savings Plans apply automatically.
On-Demand Capacity Reservation is available for Amazon Aurora and Amazon RDS in all AWS commercial Regions. To learn more about On-Demand Capacity Reservation, visit the documentation for Amazon Aurora and Amazon RDS.   

Amazon Connect Customer now offers two different layouts that optimize screen space on the agent workspace. Contact center agents spend hours each day in the agent workspace, which includes all of the contact controls and applications they need to resolve customer issues. Agents who handle different channels and workflows want the workspace arranged differently, so that they can quickly read, respond, and access their tools. Now, administrators can choose the best layout for each team, maximizing agent efficiency and satisfaction.

On the Modern layout, contact controls are at the top of the workspace, maximizing screen space for the applications beneath during voice calls. When agents handle chat, email, and task contacts on the Modern layout, they now have a taller, wider area to read and respond. The Classic layout offers a familiar experience for agents already using the agent workspace, now with contact controls that expand and contract by channel and a resizable agent assist application. Administrators can assign the Modern layout to a team migrating from another agent desktop with controls at the top, while teams already familiar with the agent workspace can use the Classic layout.

You can use the new layouts for the Amazon Connect Customer agent workspace in the following AWS regions: US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), and Europe (London).

To learn more and get started, see the agent workspace in the Amazon Connect Customer administrator guide.

​Amazon Connect Customer now offers two different layouts that optimize screen space on the agent workspace. Contact center agents spend hours each day in the agent workspace, which includes all of the contact controls and applications they need to resolve customer issues. Agents who handle different channels and workflows want the workspace arranged differently, so that they can quickly read, respond, and access their tools. Now, administrators can choose the best layout for each team, maximizing agent efficiency and satisfaction.
On the Modern layout, contact controls are at the top of the workspace, maximizing screen space for the applications beneath during voice calls. When agents handle chat, email, and task contacts on the Modern layout, they now have a taller, wider area to read and respond. The Classic layout offers a familiar experience for agents already using the agent workspace, now with contact controls that expand and contract by channel and a resizable agent assist application. Administrators can assign the Modern layout to a team migrating from another agent desktop with controls at the top, while teams already familiar with the agent workspace can use the Classic layout.
You can use the new layouts for the Amazon Connect Customer agent workspace in the following AWS regions: US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Canada (Central), Europe (Frankfurt), and Europe (London).
To learn more and get started, see the agent workspace in the Amazon Connect Customer administrator guide.  

octubre 21, 2026

• Categoría: Noticias de Microsoft

Microsoft empodera a más de 330.000 empleados del Grupo Volkswagen con Copilot

3 minuto

REDMOND, Washington — Microsoft Corp. anunció el miércoles que Volkswagen Group ha equipado ahora a más de 330.000 empleados en toda la empresa con Microsoft Copilot, para ayudar a su plantilla a aumentar la productividad, acelerar decisiones y mejorar los procesos basados en el conocimiento en toda la organización.

«El verdadero valor de la IA proviene de hacerla disponible a gran escala en el trabajo diario», afirmó Sophie Vassarotti, directora de Datos del Grupo y IA del Grupo Volkswagen. «Con Copilot, ofrecemos soporte de IA seguro y confiable a nuestros empleados, ayudándoles a trabajar de manera más eficiente y a tomar decisiones mejor informadas.»

El despliegue a gran escala de Copilot por parte del Grupo Volkswagen es el último paso en el enfoque deliberado y por fases del Grupo hacia la adopción de la IA. El despliegue gradual de la organización comenzó al proporcionar a los empleados un amplio acceso al chat impulsado por IA a través de Copilot Chat, para el cual Volkswagen registró más de 300.000 usuarios activos mensuales en la plataforma.

Hoy en día, los empleados utilizan Copilot con Work IQ para escenarios de productividad más avanzados, para integrar la IA aún más a profundidad en la mayoría de los procesos empresariales — desde la ingeniería hasta la producción, compras y ventas. Además, más de 26.000 agentes han estado activos en todo el Grupo solo en el último mes, lo que ha escalado las ganancias de productividad impulsadas por IA.

«Al llevar Microsoft Copilot a más de 330.000 empleados, Volkswagen Group integra la IA directo en el flujo de trabajo — lo que ayuda a las personas a aumentar la productividad, acelerar decisiones y centrarse en tareas de mayor valor», dijo Agnes Heftberger, presidenta del Consejo de Administración de Microsoft Alemania. «Volkswagen demuestra cómo las empresas pueden evolucionar la IA de una herramienta de productividad personal a una base para la innovación en IA en el futuro.»

Además, Microsoft y Volkswagen Group tienen la intención de ampliar su colaboración y ampliar aún más la Intelligent Data Foundation, el ecosistema unificado de datos del Grupo, en Microsoft Fabric, para facilitar la búsqueda, la comprensión y el uso de datos confiables en toda la empresa.

Nota para los editores

La colaboración será presentada en el Microsoft AI Tour en Colonia, Alemania, el 22 de octubre de 2026. Sophie Vassarotti (jefa de datos de Grupo e IA, Grupo Volkswagen) y Rupert Stuetzle (director general, Fabricación y Movilidad, EMEA, Microsoft) presentarán «Cómo Volkswagen Group construyen inteligencia grupal en la era de la IA» a las 9:00 a.m. CEST (Laboratorio 3 | Pabellón 1).

Microsoft (Nasdaq «MSFT» @microsoft) crea plataformas y herramientas impulsadas por IA para ofrecer soluciones innovadoras que satisfagan las necesidades cambiantes de nuestros clientes. La empresa tecnológica está comprometida a hacer que la IA esté disponible de manera amplia y a hacerlo de manera responsable, con la misión de empoderar a cada persona y organización del planeta para que consigan más.

Para más información, solo prensa:

Relaciones con los Medios de Microsoft, Nosotros. Comunicaciones para Microsoft, (425) 638-7777, rapidresponse@wecommunications.com

Nota para los editores: Para más información, noticias y perspectivas de Microsoft, por favor visiten Microsoft Source en https://news.microsoft.com/source/latam/. Los enlaces web, números de teléfono y títulos eran correctos en el momento de la publicación, pero pueden haber cambiado. Para asistencia adicional, periodistas y analistas pueden contactar con el Equipo de Respuesta Rápida de Microsoft u otros contactos apropiados listados en https://news.microsoft.com/microsoft-public-relations-contacts

Etiquetas:

• Anuncios
• Clientes
• Press Releases

The post Microsoft empodera a más de 330.000 empleados del Grupo Volkswagen con Copilot appeared first on Source LATAM.

​The post Microsoft empodera a más de 330.000 empleados del Grupo Volkswagen con Copilot appeared first on Source LATAM.  

Amazon DynamoDB global tables now support disassociating a replica without deleting its table or data. Global tables provide fully managed, multi-Region, multi-active replication. You can now stop replication to and from a replica and continue using the same table as a single-Region table.

An account can leave a shared multi-account global table and continue using its table independently. You can also stop replication to a Region while keeping its table for local workloads, validation, or audit, without creating a replacement table or copying data.

DynamoDB supports disassociating replicas in all AWS Regions for same-account and multi-account global tables that use multi-Region eventual consistency (MREC).

To get started, use the AWS Management Console, AWS CLI, DynamoDB API, or AWS CloudFormation. For more information, see Disassociating replicas in the Amazon DynamoDB Developer Guide.

​Amazon DynamoDB global tables now support disassociating a replica without deleting its table or data. Global tables provide fully managed, multi-Region, multi-active replication. You can now stop replication to and from a replica and continue using the same table as a single-Region table.
An account can leave a shared multi-account global table and continue using its table independently. You can also stop replication to a Region while keeping its table for local workloads, validation, or audit, without creating a replacement table or copying data.
DynamoDB supports disassociating replicas in all AWS Regions for same-account and multi-account global tables that use multi-Region eventual consistency (MREC).
To get started, use the AWS Management Console, AWS CLI, DynamoDB API, or AWS CloudFormation. For more information, see Disassociating replicas in the Amazon DynamoDB Developer Guide.  

AWS announces Amazon Elastic Container Service (Amazon ECS) Gateway, a new resource that simplifies ingress networking for containerized applications by dynamically provisioning and managing Application Load Balancers (ALBs) and their supporting resources directly in your account.

With ECS Gateway, platform teams define organizational networking standards once on a gateway and associate it with one or more clusters, giving organizations a centralized way to govern how traffic reaches their ECS services. Application teams simply opt in to inherit those standards without requiring networking expertise. ECS Gateway offers host-based routing, allows up to 25 services to share an ALB to optimize infrastructure costs, and gives each service a unique Domain Name System (DNS) hostname. ECS manages the full lifecycle of the underlying infrastructure, provisioning the first ALB when your first service connects, adding more ALBs when capacity is reached, and removing them when no longer needed. You can inspect these resources and the gateway route to each service to see exactly how requests reach your applications. For traffic and health monitoring, you can use standard ALB metrics in Amazon CloudWatch and target health information from Elastic Load Balancing.

To get started, create an ECS Gateway, associate it with a cluster, and opt in your ECS service by adding the gateway connector parameter using the AWS Management Console, AWS CLI, API, AWS SDKs, or AWS CloudFormation. ECS Gateway is available for ECS services using the awsvpc network mode across all launch types. It is available now in all commercial AWS Regions at no additional charge. You pay only for the underlying infrastructure provisioned in your account when your services connect to the gateway. To learn more, refer to the AWS News blog and our documentation page.

​AWS announces Amazon Elastic Container Service (Amazon ECS) Gateway, a new resource that simplifies ingress networking for containerized applications by dynamically provisioning and managing Application Load Balancers (ALBs) and their supporting resources directly in your account.
With ECS Gateway, platform teams define organizational networking standards once on a gateway and associate it with one or more clusters, giving organizations a centralized way to govern how traffic reaches their ECS services. Application teams simply opt in to inherit those standards without requiring networking expertise. ECS Gateway offers host-based routing, allows up to 25 services to share an ALB to optimize infrastructure costs, and gives each service a unique Domain Name System (DNS) hostname. ECS manages the full lifecycle of the underlying infrastructure, provisioning the first ALB when your first service connects, adding more ALBs when capacity is reached, and removing them when no longer needed. You can inspect these resources and the gateway route to each service to see exactly how requests reach your applications. For traffic and health monitoring, you can use standard ALB metrics in Amazon CloudWatch and target health information from Elastic Load Balancing.
To get started, create an ECS Gateway, associate it with a cluster, and opt in your ECS service by adding the gateway connector parameter using the AWS Management Console, AWS CLI, API, AWS SDKs, or AWS CloudFormation. ECS Gateway is available for ECS services using the awsvpc network mode across all launch types. It is available now in all commercial AWS Regions at no additional charge. You pay only for the underlying infrastructure provisioned in your account when your services connect to the gateway. To learn more, refer to the AWS News blog and our documentation page.