Publicado el — Deja un comentario

Microsoft en Andicom: Agentes de IA y Empresas Frontera, la nueva competitividad



septiembre 4, 2025

Microsoft en Andicom: Agentes de IA y Empresas Frontera, la nueva competitividad

La inteligencia artificial marcó la agenda de Andicom 2025. Con la irrupción de los agentes y el nacimiento de las Empresas Frontera, 2025 marca un punto de quiebre que obliga a las organizaciones a adaptarse con rapidez.

Cartagena, Colombia – En su edición número 40, ANDICOM reafirmó el papel de Colombia como epicentro regional para debatir sobre el futuro de la tecnología. En este escenario, Microsoft puso sobre la mesa los temas que definirán un nuevo capítulo en la evolución de la inteligencia artificial: la irrupción de los agentes, el surgimiento de las Empresas Frontera y la transformación del trabajo en Sudamérica.

Un hombre en el escenario durante una conferencia
Jeeva Akr, Líder Global de Azure, en Andicom 2025

A lo largo del congreso, Microsoft destacó cómo la IA está pasando de la experimentación a convertirse en un eje fundamental de la estrategia, la productividad y la competitividad. La compañía tuvo presencia de marca dentro de la exposición junto a socios como AlfaPeople, Pi Data Strategy, Tanium y Visión Software, permitiendo a los asistentes conocer de primera mano soluciones enfocadas en IA y Copilot, aplicadas a casos reales de negocio.

Como parte de la agenda académica, Jeeva Akr, Global Leader de Azure Analytics, compartió su visión sobre el futuro de la IA en el keynote: “Trazando el rumbo organizacional de la Analítica, la IA y la Gobernanza a gran escala”, y señaló que: “El futuro está en manos de quienes sepan combinar visión, datos y confianza para escalar la innovación”.

Grupo de personas sentadas en un escenario frente a una pantalla en una conferencia
Pablo Junco, Data & AI Director Latin America, en panel de Andicom

Por su parte, Pablo Junco, Senior Director de Data & AI para Latinoamérica, participó en el panel “Tendencias y desafíos tecnológicos para 2030: IA, ciberseguridad, computación cuántica y ecosistemas digitales sostenibles”.

En este contexto, Junco afirmó: “2025 marca un punto de quiebre: la inteligencia artificial ha dejado de ser un experimento y ya es parte esencial de la estrategia y las operaciones empresariales”. Mostrando así que, en esta nueva fase, la IA ya no se limita a áreas de innovación, sino que en las compañías más competitivas está integrada en operaciones críticas, flujos de trabajo y procesos de decisión.

Uno de los temas centrales de Microsoft a lo largo de Andicom fue el papel de los agentes de IA, considerados la siguiente gran evolución tecnológica: sistemas capaces de observar, razonar y actuar de manera autónoma, aprendiendo del contexto y transformando la forma en que operan las organizaciones. Estos agentes pueden colaborar con las personas o ejecutar tareas en su nombre, y al ser personalizables y contextuales, ya están revolucionando procesos en múltiples industrias.

La compañía destacó en los diferentes espacios en los que participó que, en 2025, los agentes no son simplemente una herramienta más, sino la base de una nueva infraestructura laboral.En este marco surgen conceptos como las Empresas Frontera, organizaciones que reinventan sus modelos operativos alrededor de la IA, y los jefes de agentes, responsables de diseñar, entrenar y gestionar estos sistemas.

“Formar jefes de agentes y consolidar una cultura de innovación es tan importante como la propia tecnología. Debemos capacitar a los equipos con las herramientas necesarias para adaptarse a esta nueva era y asegurar que la transformación impulse su trabajo y el crecimiento sostenible y justo de las organizaciones”, agregó Junco.

Un hombre en el escenario durante una conferencia
Jeeva Akr, Líder Global de Azure, Andicom 2025

El Work Trend Index 2025 confirma esta tendencia: el 76% de los líderes empresariales en Colombia planea contratar nuevos roles especializados en IA, mientras que el 90% prevé incorporar agentes digitales en los próximos 12 a 18 meses. Este cambio exige no solo nuevas estructuras organizacionales, sino también la formación de habilidades digitales avanzadas y pensamiento crítico.

En ese sentido, Junco recomendó avanzar con un enfoque ordenado: diagnosticar procesos, definir pilotos con métricas claras y mantener la supervisión humana como principio fundamental. Para Microsoft, 2025 será el año en que nazcan las Empresas Frontera, aquellas que dejan de experimentar para reinventar sus modelos a partir de la inteligencia artificial. Según sus datos, en este tipo de compañías el 71% de los empleados a nivel global afirma que su organización está prosperando, frente al 37% en el resto.

La magnitud de la transformación es clara: en 2025 hay 3.800 millones de personas económicamente activas en el mundo y, para 2028, se estima que existirán más de 13.000 millones de agentes de IA. El reto será aprender a liderarlos y aprovechar su potencial para impulsar innovación y crecimiento.

“El futuro del trabajo no depende solo de la tecnología, sino de cómo institucionalizamos la gobernanza de la inteligencia artificial. Transparencia, ética, seguridad y métricas claras deben acompañar la innovación, mientras desarrollamos el talento necesario para que esta transformación sea sostenible e inclusiva. Ese es el verdadero reto, pero también la gran oportunidad para América Latina”, concluyó Junco.

En este contexto, ANDICOM 2025 se consolida como un epicentro de sinergias y acuerdos, un espacio donde gobierno, empresas y medios se reúnen para construir una hoja de ruta común hacia la competitividad y la adopción responsable de la inteligencia artificial en la región.

Acerca de Microsoft

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

The post Microsoft en Andicom: Agentes de IA y Empresas Frontera, la nueva competitividad appeared first on Source LATAM.

 

​The post Microsoft en Andicom: Agentes de IA y Empresas Frontera, la nueva competitividad appeared first on Source LATAM.  

Publicado el — Deja un comentario

Validate best practice compliance for SAP with AWS Systems Manager

AWS Systems Manager Configuration Manager now supports SAP HANA, allowing you to automatically test your SAP HANA databases running on AWS against best practices defined in the AWS Well-Architected Framework SAP Lens.

Keeping SAP optimally configured requires SAP administrators to stay current with best practices from multiple sources including AWS, SAP, and operating system vendors and manually check their configurations to validate adherence. AWS Systems Manager Configuration Manager automatically assesses SAP applications running on AWS against these standards, proactively identifying misconfigurations and recommending specific remediation steps, allowing you to make the necessary changes before potential impacts to business operations. Configuration checks can be scheduled or run on-demand.

SSM for SAP Configuration Manager is available in all commercial AWS Regions.

To learn more, visit the AWS Systems Manager for SAP documentation.

 

​AWS Systems Manager Configuration Manager now supports SAP HANA, allowing you to automatically test your SAP HANA databases running on AWS against best practices defined in the AWS Well-Architected Framework SAP Lens. Keeping SAP optimally configured requires SAP administrators to stay current with best practices from multiple sources including AWS, SAP, and operating system vendors and manually check their configurations to validate adherence. AWS Systems Manager Configuration Manager automatically assesses SAP applications running on AWS against these standards, proactively identifying misconfigurations and recommending specific remediation steps, allowing you to make the necessary changes before potential impacts to business operations. Configuration checks can be scheduled or run on-demand. SSM for SAP Configuration Manager is available in all commercial AWS Regions. To learn more, visit the AWS Systems Manager for SAP documentation.  

Publicado el — Deja un comentario

Amazon Managed Service for Prometheus adds quota visibility through AWS Service Quotas and CloudWatch

Amazon Managed Service for Prometheus, a fully managed Prometheus-compatible monitoring service now allows you to view applied quota values and their utilization for your Amazon Managed Service for Prometheus workspaces using AWS Service Quotas and Amazon CloudWatch. This update gives you a comprehensive view of quota utilization across your workspaces.

AWS Service Quotas allows you to quickly understand your applied service quota values and request increases in a few clicks. With Amazon CloudWatch usage metrics, you can create alarms to be notified when your Amazon Managed Service for Prometheus workspaces approach applied limits and visualize usage in CloudWatch dashboards.

Usage metrics for Amazon Managed Service for Prometheus service limits are available at no additional cost and are always enabled. You can access Service Quotas and usage metrics in CloudWatch through the AWS console, AWS APIs, and CLI. These features are available in all AWS regions where Amazon Managed Service for Prometheus is generally available.

For detailed information, check out the Amazon Managed Service for Prometheus user guide. To learn more about the service, visit the product page and pricing page.

 

​Amazon Managed Service for Prometheus, a fully managed Prometheus-compatible monitoring service now allows you to view applied quota values and their utilization for your Amazon Managed Service for Prometheus workspaces using AWS Service Quotas and Amazon CloudWatch. This update gives you a comprehensive view of quota utilization across your workspaces. AWS Service Quotas allows you to quickly understand your applied service quota values and request increases in a few clicks. With Amazon CloudWatch usage metrics, you can create alarms to be notified when your Amazon Managed Service for Prometheus workspaces approach applied limits and visualize usage in CloudWatch dashboards. Usage metrics for Amazon Managed Service for Prometheus service limits are available at no additional cost and are always enabled. You can access Service Quotas and usage metrics in CloudWatch through the AWS console, AWS APIs, and CLI. These features are available in all AWS regions where Amazon Managed Service for Prometheus is generally available. For detailed information, check out the Amazon Managed Service for Prometheus user guide. To learn more about the service, visit the product page and pricing page.  

Publicado el — Deja un comentario

AWS adds support for three new condition keys to govern API keys for Amazon Bedrock

AWS today launched three new condition keys that help administrators govern API keys for Amazon Bedrock. The new condition keys help you control the generation, expiration, and the type of API keys allowed. Amazon Bedrock supports two types of API keys: short-term API keys valid for up to 12 hours or long-term API keys which are IAM service-specific credentials for use with Bedrock only.

The new iam:ServiceSpecificCredentialServiceName condition key lets you control what target AWS services are allowed when creating IAM service-specific credentials. For example, you could allow the creation of Bedrock long-term API keys but not credentials for AWS CodeCommit or Amazon Keyspaces. The new iam:ServiceSpecificCredentialAgeDays condition key lets you control the maximum duration of Bedrock long-term API keys at creation. The new bedrock:BearerTokenType condition key let’s you allow or deny Bedrock requests based on whether the API key is short-term or long-term.

These new condition keys are available in all AWS Regions. To learn more about using the new condition keys, visit the IAM User Guide or Amazon Bedrock User Guide.

 

​AWS today launched three new condition keys that help administrators govern API keys for Amazon Bedrock. The new condition keys help you control the generation, expiration, and the type of API keys allowed. Amazon Bedrock supports two types of API keys: short-term API keys valid for up to 12 hours or long-term API keys which are IAM service-specific credentials for use with Bedrock only. The new iam:ServiceSpecificCredentialServiceName condition key lets you control what target AWS services are allowed when creating IAM service-specific credentials. For example, you could allow the creation of Bedrock long-term API keys but not credentials for AWS CodeCommit or Amazon Keyspaces. The new iam:ServiceSpecificCredentialAgeDays condition key lets you control the maximum duration of Bedrock long-term API keys at creation. The new bedrock:BearerTokenType condition key let’s you allow or deny Bedrock requests based on whether the API key is short-term or long-term. These new condition keys are available in all AWS Regions. To learn more about using the new condition keys, visit the IAM User Guide or Amazon Bedrock User Guide.  

Publicado el — Deja un comentario

AWS Clean Rooms supports configurable compute size for PySpark jobs

AWS Clean Rooms now supports configurable compute size for PySpark, offering customers the flexibility to customize and allocate resources to run PySpark jobs based on their performance, scale, and cost requirements. With this launch, customers can specify the instance type and cluster size at job runtime for each analysis that uses PySpark, the Python API for Apache Spark. For example, customers can use large instance configurations to achieve the performance needed for their complex data sets and analyses, or smaller instances to optimize costs.

AWS Clean Rooms helps companies and their partners easily analyze and collaborate on their collective datasets without revealing or copying one another’s underlying data. For more information about the AWS Regions where AWS Clean Rooms is available, see the AWS Regions table. To learn more about collaborating with AWS Clean Rooms, visit AWS Clean Rooms.

 

​AWS Clean Rooms now supports configurable compute size for PySpark, offering customers the flexibility to customize and allocate resources to run PySpark jobs based on their performance, scale, and cost requirements. With this launch, customers can specify the instance type and cluster size at job runtime for each analysis that uses PySpark, the Python API for Apache Spark. For example, customers can use large instance configurations to achieve the performance needed for their complex data sets and analyses, or smaller instances to optimize costs. AWS Clean Rooms helps companies and their partners easily analyze and collaborate on their collective datasets without revealing or copying one another’s underlying data. For more information about the AWS Regions where AWS Clean Rooms is available, see the AWS Regions table. To learn more about collaborating with AWS Clean Rooms, visit AWS Clean Rooms.  

Publicado el — Deja un comentario

Amazon EC2 announces AMI Usage to better monitor the use of AMIs

Amazon EC2 introduces AMI Usage, providing new capabilities that allow you to track AMI consumption across AWS accounts and identify resources in your account that are dependent on particular AMIs. This enhanced visibility helps you monitor AMI utilization patterns across your AWS infrastructure and safely manage AMI deregistrations.

Up until today, you had to write custom scripts to track the use of AMIs across accounts and resources, leading to operational overhead. Now, with AMI Usage, you can generate a report that lists the accounts that are using your AMIs in EC2 instances and launch templates. You can also check utilization of any AMI within your account across multiple resources, including instances, launch templates, Image Builder recipes, and SSM parameters. These new capabilities empower you to maintain clear oversight of AMI usage across your AWS ecosystem, better manage the lifecycle of your AMIs, and optimize costs.

AMI Usage is available to all customers at no additional cost in all AWS regions including AWS China (Beijing) Region, operated by Sinnet, and AWS China (Ningxia) Region, operated by NWCD, and AWS GovCloud (US). To learn more, please visit our documentation.

 

​Amazon EC2 introduces AMI Usage, providing new capabilities that allow you to track AMI consumption across AWS accounts and identify resources in your account that are dependent on particular AMIs. This enhanced visibility helps you monitor AMI utilization patterns across your AWS infrastructure and safely manage AMI deregistrations. Up until today, you had to write custom scripts to track the use of AMIs across accounts and resources, leading to operational overhead. Now, with AMI Usage, you can generate a report that lists the accounts that are using your AMIs in EC2 instances and launch templates. You can also check utilization of any AMI within your account across multiple resources, including instances, launch templates, Image Builder recipes, and SSM parameters. These new capabilities empower you to maintain clear oversight of AMI usage across your AWS ecosystem, better manage the lifecycle of your AMIs, and optimize costs. AMI Usage is available to all customers at no additional cost in all AWS regions including AWS China (Beijing) Region, operated by Sinnet, and AWS China (Ningxia) Region, operated by NWCD, and AWS GovCloud (US). To learn more, please visit our documentation.  

Publicado el — Deja un comentario

Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions

Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions. Repository creation templates allow you to configure the settings for the new repositories that Amazon ECR creates on your behalf during pull through cache and replication operations. These settings include encryption, lifecycle policies, access permissions, and tag immutability. Each template uses a prefix to match and apply configurations to new repositories automatically, enabling you to maintain consistent settings across your container registries.

To learn more about ECR repository creation template, see our documentation.

 

​Amazon Elastic Container Registry (ECR) now supports repository creation templates in the AWS GovCloud (US) Regions. Repository creation templates allow you to configure the settings for the new repositories that Amazon ECR creates on your behalf during pull through cache and replication operations. These settings include encryption, lifecycle policies, access permissions, and tag immutability. Each template uses a prefix to match and apply configurations to new repositories automatically, enabling you to maintain consistent settings across your container registries. To learn more about ECR repository creation template, see our documentation.  

Publicado el — Deja un comentario

CloudFormation Hooks adds Managed Controls and Hook Activity Summary

AWS CloudFormation Hooks now supports managed proactive controls, enabling customers to validate resource configurations against AWS best practices without writing custom Hooks logic. Customers can select controls from the AWS Control Tower Controls Catalog and apply them during CloudFormation operations. When using CloudFormation, customers can configure these controls to run in warn mode, allowing teams to test controls without blocking deployments and giving them the flexibility to evaluate control behavior before enforcing policies in production. This significantly reduces setup time, eliminates manual errors, and ensures comprehensive governance coverage across your infrastructure.

AWS also introduced a new Hooks Invocation Summary page in the CloudFormation console. This centralized view provides a complete historical record of Hooks activity, showing which controls were invoked, their execution details, and outcomes such as pass, warn, or fail. This simplifies compliance reporting issues faster.

With this launch, customers can now leverage AWS-managed controls as part of their provisioning workflows, eliminating the overhead of writing and maintaining custom logic. These controls are curated by AWS and aligned with industry best practices, helping teams enforce consistent policies across all environments. The new summary page delivers essential visibility into Hook invocation history, enabling faster issue resolution and streamlined compliance reporting.

The Hook invocation summary page is available in all commercial and GovCloud (US) regions, and control selection is available in all in all commercials regions. To learn more, visit the AWS CloudFormation Proactive Control Hooks and AWS CloudFormation Hooks View Invocations documentations.

 

​AWS CloudFormation Hooks now supports managed proactive controls, enabling customers to validate resource configurations against AWS best practices without writing custom Hooks logic. Customers can select controls from the AWS Control Tower Controls Catalog and apply them during CloudFormation operations. When using CloudFormation, customers can configure these controls to run in warn mode, allowing teams to test controls without blocking deployments and giving them the flexibility to evaluate control behavior before enforcing policies in production. This significantly reduces setup time, eliminates manual errors, and ensures comprehensive governance coverage across your infrastructure.
AWS also introduced a new Hooks Invocation Summary page in the CloudFormation console. This centralized view provides a complete historical record of Hooks activity, showing which controls were invoked, their execution details, and outcomes such as pass, warn, or fail. This simplifies compliance reporting issues faster.
With this launch, customers can now leverage AWS-managed controls as part of their provisioning workflows, eliminating the overhead of writing and maintaining custom logic. These controls are curated by AWS and aligned with industry best practices, helping teams enforce consistent policies across all environments. The new summary page delivers essential visibility into Hook invocation history, enabling faster issue resolution and streamlined compliance reporting.
The Hook invocation summary page is available in all commercial and GovCloud (US) regions, and control selection is available in all in all commercials regions. To learn more, visit the AWS CloudFormation Proactive Control Hooks and AWS CloudFormation Hooks View Invocations documentations.  

Publicado el — Deja un comentario

AWS HealthOmics is now available in Asia Pacific (Seoul) Region

Today, AWS announces that AWS HealthOmics private workflows are now available in the Asia Pacific (Seoul) Region, expanding access to fully managed bioinformatics workflows for healthcare and life sciences customers in Korea. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed bioinformatics workflows. HealthOmics enables customers to focus on scientific discovery rather than infrastructure management, reducing time to value for research, drug discovery, and agriculture science initiatives.

With private workflows, customers can build and scale genomics data analysis pipelines using familiar domain-specific languages including Nextflow, WDL, and CWL. The service provides built-in features such as call caching to resume runs, dynamic run storage that automatically scales with run storage needs, Git integrations for version-controlled workflow development, and third-party container registry support through Amazon ECR pull-through cache. These capabilities make it easier to migrate existing pipelines and accelerate development of new genomics workflows while maintaining full data provenance and compliance requirements.

Private workflows are now available in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), Asia Pacific (Singapore), and Asia Pacific (Seoul).

To get started, see the AWS HealthOmics documentation.

 

​Today, AWS announces that AWS HealthOmics private workflows are now available in the Asia Pacific (Seoul) Region, expanding access to fully managed bioinformatics workflows for healthcare and life sciences customers in Korea. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed bioinformatics workflows. HealthOmics enables customers to focus on scientific discovery rather than infrastructure management, reducing time to value for research, drug discovery, and agriculture science initiatives. With private workflows, customers can build and scale genomics data analysis pipelines using familiar domain-specific languages including Nextflow, WDL, and CWL. The service provides built-in features such as call caching to resume runs, dynamic run storage that automatically scales with run storage needs, Git integrations for version-controlled workflow development, and third-party container registry support through Amazon ECR pull-through cache. These capabilities make it easier to migrate existing pipelines and accelerate development of new genomics workflows while maintaining full data provenance and compliance requirements. Private workflows are now available in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Israel (Tel Aviv), Asia Pacific (Singapore), and Asia Pacific (Seoul). To get started, see the AWS HealthOmics documentation.  

Publicado el — Deja un comentario

ECS Exec is now available in the AWS Management Console

The Amazon ECS console now supports ECS Exec, enabling you to open secure, interactive shell access directly from the AWS Management Console to any running container.

ECS customers often need to access running containers to debug applications and examine running processes. ECS Exec provides easy and secure access to running containers without requiring inbound ports or SSH key management. Previously, ECS Exec was only accessible through the AWS API, CLI, or SDKs, requiring customers to switch interfaces when troubleshooting in the console. With this new feature, customers can now connect to running containers directly from the AWS Management Console, streamlining troubleshooting workflows.

To get started, you can turn on ECS Exec directly in the console when creating or updating services and standalone tasks. Additional settings like encryption and logging can also be configured at the cluster level through the console. Once enabled, simply navigate to a task details page, select a container, and click «Connect» to open an interactive session through CloudShell. The console also displays the underlying AWS CLI command, which you can customize or copy to use in your local terminal.

ECS Exec console support is now available in all AWS commercial regions. To learn more, visit the ECS developer guide.

 

​The Amazon ECS console now supports ECS Exec, enabling you to open secure, interactive shell access directly from the AWS Management Console to any running container.
ECS customers often need to access running containers to debug applications and examine running processes. ECS Exec provides easy and secure access to running containers without requiring inbound ports or SSH key management. Previously, ECS Exec was only accessible through the AWS API, CLI, or SDKs, requiring customers to switch interfaces when troubleshooting in the console. With this new feature, customers can now connect to running containers directly from the AWS Management Console, streamlining troubleshooting workflows.
To get started, you can turn on ECS Exec directly in the console when creating or updating services and standalone tasks. Additional settings like encryption and logging can also be configured at the cluster level through the console. Once enabled, simply navigate to a task details page, select a container, and click «Connect» to open an interactive session through CloudShell. The console also displays the underlying AWS CLI command, which you can customize or copy to use in your local terminal.
ECS Exec console support is now available in all AWS commercial regions. To learn more, visit the ECS developer guide.