Publicado el — Deja un comentario

Desde la ambición de la IA hasta el impacto empresarial

Desde la ambición de la IA hasta el impacto empresarial

7 minuto
Ilustración con cuadros de colores y con imágenes de pesronas, con las palabras: Microsoft Frontier Company al centro

Por: Rodrigo Kede Lima, presidente, Microsoft Frontier Company.

La mayoría de los líderes empresariales que conozco ya no necesitan estar convencidos de que la IA funcione. Han visto los pilotos, las demos y los copilotos. La pregunta que escucho ahora en las salas de juntas es diferente: ¿Cómo pasamos de una IA que impresiona a una IA que cambie la manera en que en verdad funciona el negocio?

Esa es la pregunta para la que Microsoft Frontier Company fue creada y, hasta la fecha, hemos participado en casi 500 proyectos con más de 200 clientes en 28 países.

Clientes como 3M, Alaska Airlines, BMW, Core42, KT, Land O’Lakes, London Stock Exchange Group, Mastercard, McKesson, Northern Trust, Novo Nordisk, Publicis Groupe, Saint-Gobain, Siemens y Unilever ven un valor real al trabajar codo con codo con nuestros equipos de Ingeniería Desplegados de manera Directa.

Más importante aún, la mayoría de los clientes a los que hemos completado proyectos iniciales han regresado para realizar más proyectos, lo que genera cientos de proyectos de seguimiento. Los clientes no vuelven por los ingenieros. Vuelven porque el primer compromiso les ha dado algo que pueden medir y pueden ver el siguiente flujo de trabajo que merece la pena rediseñar.

La tecnología está lista. Lo que ralentiza la IA es todo lo que la rodea. Eso significa identificar dónde la IA puede aportar el mayor valor, construir confianza y gobernanza, rediseñar los modelos operativos y ayudar a las personas a trabajar de nuevas maneras. La tecnología y las personas tienen que avanzar juntas.

Cómo se ve esto en la práctica

Unilever colabora con ingenieros de Microsoft para incorporar la IA a sus fábricas. En la planta de fábrica, la tecnología inteligente ayuda a los equipos a aumentar la eficiencia y a entregar productos superiores a los clientes. En la fábrica de Pondicherry — la mayor fábrica de líquidos para el cuidado doméstico de Unilever en el sur de Asia y un sitio del Faro del Foro Económico Mundial 2026 — un gemelo digital construido sobre NVIDIA Omniverse y alojado en Azure simula un entorno real de fábrica con datos en vivo integrados. Esto ayuda a anticipar los problemas antes de que ocurran, monitoriza el rendimiento en tiempo real y guía a los operadores a través de las correcciones y recomendaciones.

3M trabaja con nuestros ingenieros para ayudar a su equipo de Servicios Globales de Negocio a automatizar la gestión de pedidos de clientes. Las empresas construyen un flujo de trabajo impulsado por agentes de IA para ayudar con comprobaciones de crédito, evaluaciones de morosidad y actualizaciones del sistema, con controles humanos en el bucle y un panel de control personalizado para la visibilidad y aprobaciones en tiempo real. Se espera que la solución reduzca de manera significativa el esfuerzo manual, mejore la velocidad y la consistencia y acelere el flujo de caja, lo que libera al personal para trabajos de mayor valor y habilita operaciones escalables y auditables.

Publicis Groupe construye en conjunto con nuestros ingenieros para integrar la IA en el corazón de cómo funciona y entrega para los clientes. Los ingenieros de Microsoft trabajan codo con codo con los equipos de Publicis para diseñar y construir procesos agénticos basados en Microsoft IQ, de modo que los agentes trabajan con el contexto empresarial, los datos y el conocimiento detrás del trabajo de Publicis. Estos procesos utilizan aprendizaje por refuerzo, basándose en resultados reales y en la retroalimentación humana para continuar con las mejoras al rendimiento de los agentes a lo largo del tiempo. El enfoque combina ingeniería muy rápida con transferencia práctica de conocimiento, lo que ayuda a Publicis a desarrollar una capacidad de IA duradera. El trabajo se basa en el despliegue de Microsoft 365 Copilot por parte de Publicis a los 114.000 empleados.

Northern Trust necesitaba acelerar la incorporación a su plataforma de Soluciones de Front Office de Servicio de Activos, un proceso que duró unas dos semanas y media por cliente. Nuestros ingenieros trabajaron junto a los expertos de Northern Trust para construir un agente de incorporación impulsado por IA dentro de las herramientas de Excel y SharePoint que ya utilizan los analistas. El resultado: el tiempo de preparación de datos cayó un 83%, de dos semanas y media a tres días, con una puntuación de calidad en el primer pase del 96,5% en las pruebas. Los analistas mantienen el control mientras ganan más tiempo para un servicio al cliente de mayor valor.

KT, uno de los mayores proveedores de telecomunicaciones de Corea del Sur, quería ayudar a los operadores de red a identificar y responder a problemas más rápido. Nuestros ingenieros trabajaron desde las oficinas de KT para construir en conjunto AIO-Net, una plataforma de agentes de IA en aprendizaje continuo basada en los procedimientos operativos de KT y expertos veteranos en red. Ahora detecta problemas de red en dos o tres minutos, frente a más de diez, mientras mantiene a las personas bajo control de decisiones y acciones.

Saint-Gobain, la empresa de materiales de construcción con 360 años de historia, utiliza la IA para ayudar a reducir la huella de carbono del cemento. En su trabajo junto a sus investigadores, los ingenieros de Microsoft utilizaron Microsoft Discovery para recopilar 62.000 patentes y 44.000 resúmenes de investigación en una base de conocimiento en cuestión de horas, trabajo que Saint-Gobain estima que habría llevado a los investigadores un año. En unas seis semanas, el equipo identificó nuevas hipótesis sobre aditivos de cemento que los científicos prueban ahora en el laboratorio.

En todos estos clientes, el patrón es el mismo:

  1. Empezar por el valor, no por la tecnología.
  2. Rediseñar el proceso, no solo la tarea.
  3. Crear ciclos rápidos con los equipos del cliente.
  4. Implementar la seguridad, la gobernanza y la gestión de costes desde el primer día, para que la escalada no se estanque.

Así es como las organizaciones pasan de proyectos aislados de IA a una transformación sostenible: centrándose en resultados medibles, a través de desarrollar el trabajo y desarrollar las capacidades necesarias para mejorar con el tiempo.

Una nueva investigación de IDC subraya por qué este enfoque es importante. Mientras que el 66% de las organizaciones reporta resultados sustanciales o transformadores de la IA, solo el 48% ha comenzado a escalar o ver un valor constante en sus organizaciones. Al mismo tiempo, el 71% espera que el gasto en IA aumente al menos un 10% en el próximo año, lo que ejerce aún más presión sobre las empresas para demostrar rendimientos medibles. El reto ya no es tan solo adoptar la IA. Es reinventar cómo se realiza el trabajo y convertir esa transformación en un impacto empresarial duradero.

Nos exigimos el mismo estándar

Si pedimos a los clientes que rediseñen cómo trabajan alrededor de la IA, tenemos que hacer lo mismo. Microsoft Frontier Company fue diseñado de manera deliberada para ser plano y rápido, con una puerta principal para los clientes, y como referencia de cómo puede ser una organización nativa de IA. Aprendemos, nos ajustamos y avanzamos rápido, de la misma manera que se lo pedimos a nuestros clientes.

La verdadera medida del éxito

La brecha entre la IA que impresiona y la IA que cumple no se cerrará por sí sola. Cierra flujo de trabajo por flujo de trabajo, con personas que entienden el negocio sentadas junto a otras que pueden construir.

Nuestro éxito se medirá por algo más que lo que entregamos. La verdadera prueba es lo que nuestros clientes pueden hacer después de que hayamos trabajado juntos: gestionar, gobernar y mejorar sus propios sistemas de IA, en sus propios términos, con su inteligencia protegida. Su éxito es la medida más clara de las nuestras.

Más información en www.microsoft.com/en-us/frontier-company.

Rodrigo Kede Lima es el presidente de Microsoft Frontier Company y lidera el negocio operativo de 6.000 expertos en la industria y la ingeniería centrados en ofrecer la transformación Frontier a través de la IA para clientes de todo el mundo.

NOTA

Infografía IDC, patrocinada por Microsoft, El verdadero valor empresarial de la IA, IDC #US54985026-IG, noviembre de 2026

The post Desde la ambición de la IA hasta el impacto empresarial appeared first on Source LATAM.

 

​The post Desde la ambición de la IA hasta el impacto empresarial appeared first on Source LATAM.  

Publicado el — Deja un comentario

Amazon Connect Customer supports merging and linking related cases in the agent workspace

Amazon Connect Customer now lets agents merge and link related cases in the agent workspace, so they can resolve customer issues faster and respond consistently. When a customer contacts a business about the same issue more than once, or on different channels, the history can end up split across several cases. Agents can merge those cases into one case with a single, consolidated history. For example, an agent can merge the chat and email cases a customer opened about a delayed shipment.

Agents can also link related cases, such as cases from different customers affected by the same issue, so they can coordinate one consistent response for every affected customer.

Cases is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town). To learn more and get started, visit the Cases webpage and documentation.

 

​Amazon Connect Customer now lets agents merge and link related cases in the agent workspace, so they can resolve customer issues faster and respond consistently. When a customer contacts a business about the same issue more than once, or on different channels, the history can end up split across several cases. Agents can merge those cases into one case with a single, consolidated history. For example, an agent can merge the chat and email cases a customer opened about a delayed shipment.
Agents can also link related cases, such as cases from different customers affected by the same issue, so they can coordinate one consistent response for every affected customer.
Cases is available in the following AWS regions: US East (N. Virginia), US West (Oregon), Canada (Central), Europe (Frankfurt), Europe (London), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), and Africa (Cape Town). To learn more and get started, visit the Cases webpage and documentation.  

Publicado el — Deja un comentario

AWS Quick enhances granular governance with the ability to restrict structured data sources

Today, AWS Quick is announcing the general availability of structured data connector restrictions through custom permissions. This capability gives administrators granular control over which types of data sources users can create, update, or share, helping organizations enforce data governance requirements while enabling self-service analytics.

With this feature, administrators can configure custom permissions profiles in Enterprise edition through the Quick UI, APIs, or AWS Command Line Interface. For example, an organization can allow users to create Amazon Redshift data sources while restricting the creation of file-upload data sources. Administrators can also prevent users from sharing data sources for a particular connector. Create, update, and share restrictions can be configured independently, providing more precise controls than restrictions that apply to all data source types.

This feature is now available in all supported AWS Quick Regions listed here. To learn more, check our documentation here.

 

​Today, AWS Quick is announcing the general availability of structured data connector restrictions through custom permissions. This capability gives administrators granular control over which types of data sources users can create, update, or share, helping organizations enforce data governance requirements while enabling self-service analytics. With this feature, administrators can configure custom permissions profiles in Enterprise edition through the Quick UI, APIs, or AWS Command Line Interface. For example, an organization can allow users to create Amazon Redshift data sources while restricting the creation of file-upload data sources. Administrators can also prevent users from sharing data sources for a particular connector. Create, update, and share restrictions can be configured independently, providing more precise controls than restrictions that apply to all data source types. This feature is now available in all supported AWS Quick Regions listed here. To learn more, check our documentation here.  

Publicado el — Deja un comentario

Amazon RDS for SQL Server now supports M8id and R8id instances

Amazon Relational Database Service (Amazon RDS) for SQL Server now supports M8id and R8id instances. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, and include local NVMe SSD storage. They scale up to 384 vCPUs, 3 TiB of memory, and 22.8 TB of local NVMe SSD storage. That’s 4x the vCPUs and memory and more than 6x the local storage of M5d and R5d instances.

When you create or modify a DB instance to use M8id or R8id, RDS for SQL Server automatically places the tempdb data and log files on the local NVMe instance store. This gives tempdb lower read and write latency than Amazon EBS storage. Your database data and log files stay on Amazon EBS. Because snapshots don’t include tempdb files on the instance store, your snapshots are smaller and use less of your free backup storage. To learn more, see Instance store support for the tempdb database on Amazon RDS for SQL Server.

To use the new M8id and R8id instances, you can modify your existing RDS database instance or create a new RDS database instance from the RDS Management Console, or using the AWS SDK or CLI. M8id and R8id instances are available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), Europe (Ireland), Europe (London), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Asia Pacific (Sydney), and Asia Pacific (Malaysia). For pricing details, see Amazon RDS for SQL Server Pricing.

 

​Amazon Relational Database Service (Amazon RDS) for SQL Server now supports M8id and R8id instances. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, and include local NVMe SSD storage. They scale up to 384 vCPUs, 3 TiB of memory, and 22.8 TB of local NVMe SSD storage. That’s 4x the vCPUs and memory and more than 6x the local storage of M5d and R5d instances.
When you create or modify a DB instance to use M8id or R8id, RDS for SQL Server automatically places the tempdb data and log files on the local NVMe instance store. This gives tempdb lower read and write latency than Amazon EBS storage. Your database data and log files stay on Amazon EBS. Because snapshots don’t include tempdb files on the instance store, your snapshots are smaller and use less of your free backup storage. To learn more, see Instance store support for the tempdb database on Amazon RDS for SQL Server.
To use the new M8id and R8id instances, you can modify your existing RDS database instance or create a new RDS database instance from the RDS Management Console, or using the AWS SDK or CLI. M8id and R8id instances are available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), Europe (Ireland), Europe (London), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Asia Pacific (Sydney), and Asia Pacific (Malaysia). For pricing details, see Amazon RDS for SQL Server Pricing.  

Publicado el — Deja un comentario

Amazon MWAA now supports fine-grained access control with IAM Identity Center and multi-team environments

Amazon Managed Workflows for Apache Airflow (Amazon MWAA) now supports fine-grained access control, giving administrators precise control over who can access which workflows and resources in an Apache Airflow environment. Fine-grained access control is delivered through two new capabilities: IAM Identity Center integration and multi-team environments.

With IAM Identity Center integration, users sign in to the Apache Airflow UI with their corporate identity provider. Authorization is evaluated per request using IAM policies attached to IAM Identity Center Permission Sets, with condition keys that scope access by resource type (DAGs, connections, variables, pools, and more), action, and specific resource ID.

With multi-team environments, several teams can share a single MWAA environment. Each team gets its own DAG folder in Amazon S3, and users see only shared DAGs plus their own teams’ DAGs based on IAM Identity Center group membership. Teams reduce cost through shared infrastructure and simplify management by configuring environment settings once. Multi-team environments are based on the Apache Airflow multi-team feature, which is currently in preview.

These features are available in all AWS Regions where Amazon MWAA is available.

To learn more, visit the IAM Identity Center integration documentation and the multi-team environments documentation.

 

​Amazon Managed Workflows for Apache Airflow (Amazon MWAA) now supports fine-grained access control, giving administrators precise control over who can access which workflows and resources in an Apache Airflow environment. Fine-grained access control is delivered through two new capabilities: IAM Identity Center integration and multi-team environments.
With IAM Identity Center integration, users sign in to the Apache Airflow UI with their corporate identity provider. Authorization is evaluated per request using IAM policies attached to IAM Identity Center Permission Sets, with condition keys that scope access by resource type (DAGs, connections, variables, pools, and more), action, and specific resource ID.
With multi-team environments, several teams can share a single MWAA environment. Each team gets its own DAG folder in Amazon S3, and users see only shared DAGs plus their own teams’ DAGs based on IAM Identity Center group membership. Teams reduce cost through shared infrastructure and simplify management by configuring environment settings once. Multi-team environments are based on the Apache Airflow multi-team feature, which is currently in preview.
These features are available in all AWS Regions where Amazon MWAA is available.
To learn more, visit the IAM Identity Center integration documentation and the multi-team environments documentation.  

Publicado el — Deja un comentario

AWS Backup now supports resource modifiers for Amazon EKS restores

Today, AWS Backup announces support for resource modifiers when restoring Amazon Elastic Kubernetes Service (Amazon EKS) backups. Resource modifiers let you transform Kubernetes resources during a restore, so you can adapt a restored cluster to its target environment.

When you restore an EKS backup that has been copied across accounts or across AWS Regions, the restored cluster can carry references tied to the source environment, such as IAM roles, database endpoints, and Amazon ECR registry URIs. Previously, you had to locate and update these references manually after every restore, which was time consuming and error prone. With resource modifiers, you can define transformation rules once via a YAML file, and AWS Backup applies them automatically as part of the restore, improving the reliability of your cross-account and cross-Region disaster recovery workflows.

AWS Backup support for resource modifiers for Amazon EKS backups is available in all commercial AWS Regions and AWS GovCloud (US) Regions. To get started, see the AWS Backup Documentation and read the launch blog.

 

​Today, AWS Backup announces support for resource modifiers when restoring Amazon Elastic Kubernetes Service (Amazon EKS) backups. Resource modifiers let you transform Kubernetes resources during a restore, so you can adapt a restored cluster to its target environment.
When you restore an EKS backup that has been copied across accounts or across AWS Regions, the restored cluster can carry references tied to the source environment, such as IAM roles, database endpoints, and Amazon ECR registry URIs. Previously, you had to locate and update these references manually after every restore, which was time consuming and error prone. With resource modifiers, you can define transformation rules once via a YAML file, and AWS Backup applies them automatically as part of the restore, improving the reliability of your cross-account and cross-Region disaster recovery workflows.
AWS Backup support for resource modifiers for Amazon EKS backups is available in all commercial AWS Regions and AWS GovCloud (US) Regions. To get started, see the AWS Backup Documentation and read the launch blog.  

Publicado el — Deja un comentario

Amazon Route 53 Domains now supports self-service restore for expired and deleted domains

Amazon Route 53 Domains now lets you restore an expired or recently deleted domain yourself, using the Amazon Route 53 console, AWS CLI, or AWS SDKs. Previously, restoring a domain required a request to AWS Support. Now you can recover a domain lost to a missed renewal, an expired payment method, or an accidental deletion, and restore the website, email, and applications that depend on it.

To restore a domain, you enter the domain name, review the restoration price, accept the charge, and submit the request. Route 53 works with the top-level domain (TLD) registry to reactivate the registration and return the domain to your AWS account. Most TLD registries support restoration, and each registry sets how long after expiration or deletion a domain can still be restored. Restoring a domain typically costs more than registering or renewing one.

To learn more, see Restoring an expired or deleted domain in the Route 53 Developer Guide, or visit the Amazon Route 53 Domains page. For a complete list of supported TLDs, see the Route 53 TLD list. For pricing, visit the Route 53 pricing page.

 

​Amazon Route 53 Domains now lets you restore an expired or recently deleted domain yourself, using the Amazon Route 53 console, AWS CLI, or AWS SDKs. Previously, restoring a domain required a request to AWS Support. Now you can recover a domain lost to a missed renewal, an expired payment method, or an accidental deletion, and restore the website, email, and applications that depend on it.
To restore a domain, you enter the domain name, review the restoration price, accept the charge, and submit the request. Route 53 works with the top-level domain (TLD) registry to reactivate the registration and return the domain to your AWS account. Most TLD registries support restoration, and each registry sets how long after expiration or deletion a domain can still be restored. Restoring a domain typically costs more than registering or renewing one.
To learn more, see Restoring an expired or deleted domain in the Route 53 Developer Guide, or visit the Amazon Route 53 Domains page. For a complete list of supported TLDs, see the Route 53 TLD list. For pricing, visit the Route 53 pricing page.  

Publicado el — Deja un comentario

The next generation AgentCore runtime is now the default

Starting today, new runtimes in Amazon Bedrock AgentCore use the next generation of AgentCore runtime by default. The new runtime restores each session from a snapshot of your initialized agent, scales compute and memory with the work, and scales idle agents to zero. Every session still runs in its own hardware-isolated Firecracker microVM. Your agents can run heavy work like compiling a large codebase, driving a browser, or loading a local model inside the session. 

Sessions scale to 8 vCPU and 32 GB of memory and support container images up to 10 GB. On a 2 GB image, sessions start in under 2 seconds at P75, down from 29.7 seconds on the previous generation. Idle agents scale to zero, and memory is reclaimed within minutes of release. For multi-turn agents, that means up to 68% less billed memory per session.

Existing runtimes stay on the current version until you move them. To move an existing runtime, or to use the next generation in a Region where it isn’t the default yet, set platformVersion to V2 when you create or update a runtime. To keep a new runtime on the current version, set platformVersion to V1.

The new AgentCore Runtime is now the default runtime in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), South America (São Paulo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), Europe (Spain), Europe (Stockholm), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Thailand), and Asia Pacific (Tokyo).  To learn more, visit the AgentCore runtime documentation or the AWS Blog. For pricing details, visit AgentCore pricing.

 

​Starting today, new runtimes in Amazon Bedrock AgentCore use the next generation of AgentCore runtime by default. The new runtime restores each session from a snapshot of your initialized agent, scales compute and memory with the work, and scales idle agents to zero. Every session still runs in its own hardware-isolated Firecracker microVM. Your agents can run heavy work like compiling a large codebase, driving a browser, or loading a local model inside the session. 
Sessions scale to 8 vCPU and 32 GB of memory and support container images up to 10 GB. On a 2 GB image, sessions start in under 2 seconds at P75, down from 29.7 seconds on the previous generation. Idle agents scale to zero, and memory is reclaimed within minutes of release. For multi-turn agents, that means up to 68% less billed memory per session.
Existing runtimes stay on the current version until you move them. To move an existing runtime, or to use the next generation in a Region where it isn’t the default yet, set platformVersion to V2 when you create or update a runtime. To keep a new runtime on the current version, set platformVersion to V1.
The new AgentCore Runtime is now the default runtime in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), South America (São Paulo), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), Europe (Spain), Europe (Stockholm), Asia Pacific (Malaysia), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Thailand), and Asia Pacific (Tokyo).  To learn more, visit the AgentCore runtime documentation or the AWS Blog. For pricing details, visit AgentCore pricing.  

Publicado el — Deja un comentario

EC2 Image Builder console now integrates with the DevOps Agent for troubleshooting and resource creation

EC2 Image Builder now integrates with the AWS DevOps Agent directly in the Image Builder console, enabling you to troubleshoot failed image pipelines and create resources directly from the console chat panel. You can diagnose up to 50 failed pipelines at once and ask follow-up questions in the same conversation. You can also choose to create resources by describing what you want, and the agent populates the console with values the service has already validated.

With this integration, diagnosing a failed pipeline no longer requires manually inspecting build logs, cross-referencing error codes, or iterating through configuration fixes, saving you significant time and expertise. The agent reads build logs, workflow steps, components, and network configuration, then provides the root cause and the steps to fix it. For resource creation,  the agent verifies the configuration before populating the console for you to review and submit. If you troubleshoot or build with your own AI agents, the new EC2 Image Builder skill in the AWS Agent Toolkit provides you the same troubleshooting and creation capabilities.

This feature is available in all commercial regions. To get started, open the EC2 Image Builder console and use the DevOps Agent from the console panel. For more information, see the EC2 Image Builder documentation and for pricing refer DevOps agent Pricing page. 

 

​EC2 Image Builder now integrates with the AWS DevOps Agent directly in the Image Builder console, enabling you to troubleshoot failed image pipelines and create resources directly from the console chat panel. You can diagnose up to 50 failed pipelines at once and ask follow-up questions in the same conversation. You can also choose to create resources by describing what you want, and the agent populates the console with values the service has already validated.
With this integration, diagnosing a failed pipeline no longer requires manually inspecting build logs, cross-referencing error codes, or iterating through configuration fixes, saving you significant time and expertise. The agent reads build logs, workflow steps, components, and network configuration, then provides the root cause and the steps to fix it. For resource creation,  the agent verifies the configuration before populating the console for you to review and submit. If you troubleshoot or build with your own AI agents, the new EC2 Image Builder skill in the AWS Agent Toolkit provides you the same troubleshooting and creation capabilities.
This feature is available in all commercial regions. To get started, open the EC2 Image Builder console and use the DevOps Agent from the console panel. For more information, see the EC2 Image Builder documentation and for pricing refer DevOps agent Pricing page.   

Publicado el — Deja un comentario

AWS Network Security Manager now available in AWS European Sovereign Cloud and Additional New Regions

AWS Network Security Manager is now available in AWS European Sovereign Cloud Region and Thirty-One new Regions

Today, AWS announces the general availability of AWS Network Security Manager in the AWS European Sovereign Cloud Region and additional regions. Network Security Manager is a comprehensive network security management solution designed to simplify security policy deployment and enforcement at scale. Network Security Manager supports AWS WAF and AWS Shield in AWS European Sovereign Cloud Region. The additional regions are: US East (Ohio);  US West (N. California); US West (Oregon); Asia Pacific (Mumbai); Asia Pacific (Hong Kong); Asia Pacific (Taipei); Asia Pacific (Seoul); Asia Pacific (Osaka); Asia Pacific (Hyderabad); Asia Pacific (Singapore); Asia Pacific (Sydney); Asia Pacific (Melbourne); Asia Pacific (Malaysia); Asia Pacific (New Zealand); Asia Pacific (Thailand); Asia Pacific (Johor); Asia Pacific (Tokyo); Canada (Central);  Canada West (Calgary); Mexico (Central); Europe (Frankfurt); Europe (Zurich); Europe (Stockholm); Europe (Ireland); Europe (Milan); Europe (Spain); Europe (London); Europe (Paris); Israel (Tel Aviv); South America (São Paulo), Africa (Cape Town).

Network Security Manager features always-on security deployment automation that applies AWS WAF security protection to Internet facing assets like AWS Application Load Balancer. This automated approach helps security teams deploy and manage WAF rules and AWS Shield Advanced protections efficiently, ensuring consistent security posture across targeted accounts and resources. Teams can centrally manage security policies, automatically detect configuration drift, and apply remediation by reducing the operational overhead of manual security management while maintaining comprehensive protection.

To see which regions AWS Network Security Manager is available in, visit the AWS Region Table. For pricing information, visit the AWS Network Security Manager Pricing page. for standard regions, and the European Sovereign Cloud Pricing page.

 

​AWS Network Security Manager is now available in AWS European Sovereign Cloud Region and Thirty-One new Regions Today, AWS announces the general availability of AWS Network Security Manager in the AWS European Sovereign Cloud Region and additional regions. Network Security Manager is a comprehensive network security management solution designed to simplify security policy deployment and enforcement at scale. Network Security Manager supports AWS WAF and AWS Shield in AWS European Sovereign Cloud Region. The additional regions are: US East (Ohio);  US West (N. California); US West (Oregon); Asia Pacific (Mumbai); Asia Pacific (Hong Kong); Asia Pacific (Taipei); Asia Pacific (Seoul); Asia Pacific (Osaka); Asia Pacific (Hyderabad); Asia Pacific (Singapore); Asia Pacific (Sydney); Asia Pacific (Melbourne); Asia Pacific (Malaysia); Asia Pacific (New Zealand); Asia Pacific (Thailand); Asia Pacific (Johor); Asia Pacific (Tokyo); Canada (Central);  Canada West (Calgary); Mexico (Central); Europe (Frankfurt); Europe (Zurich); Europe (Stockholm); Europe (Ireland); Europe (Milan); Europe (Spain); Europe (London); Europe (Paris); Israel (Tel Aviv); South America (São Paulo), Africa (Cape Town). Network Security Manager features always-on security deployment automation that applies AWS WAF security protection to Internet facing assets like AWS Application Load Balancer. This automated approach helps security teams deploy and manage WAF rules and AWS Shield Advanced protections efficiently, ensuring consistent security posture across targeted accounts and resources. Teams can centrally manage security policies, automatically detect configuration drift, and apply remediation by reducing the operational overhead of manual security management while maintaining comprehensive protection. To see which regions AWS Network Security Manager is available in, visit the AWS Region Table. For pricing information, visit the AWS Network Security Manager Pricing page. for standard regions, and the European Sovereign Cloud Pricing page.