Amazon Relational Database Service (RDS) Proxy now offers customers the option to use Internet Protocol version 6 (IPv6) addresses to pool and share database connections coming from an application. The existing endpoints supporting Internet Protocol version 4 (IPv4) will remain available for backwards compatibility. Additionally, customers now have the option to specify RDS Proxy target connections using either IPv4 or IPv6.
The continued growth of the Internet, particularly in the areas of mobile applications, connected devices, and IoT, has spurred an industry-wide move to IPv6. IPv6 increases the number of available addresses by several orders of magnitude so customers no longer need to manage overlapping address spaces in their VPCs.
Many applications, including those built on modern serverless architectures, may need to have a high number of open connections to the database or may frequently open and close database connections, exhausting the database memory and compute resources. Amazon RDS Proxy allows applications to pool and share database connections, improving your database efficiency and application scalability.
For information on supported database engine versions and regional availability of RDS Proxy, refer to our RDS and Aurora documentations.
Amazon Relational Database Service (RDS) Proxy now offers customers the option to use Internet Protocol version 6 (IPv6) addresses to pool and share database connections coming from an application. The existing endpoints supporting Internet Protocol version 4 (IPv4) will remain available for backwards compatibility. Additionally, customers now have the option to specify RDS Proxy target connections using either IPv4 or IPv6. The continued growth of the Internet, particularly in the areas of mobile applications, connected devices, and IoT, has spurred an industry-wide move to IPv6. IPv6 increases the number of available addresses by several orders of magnitude so customers no longer need to manage overlapping address spaces in their VPCs. Many applications, including those built on modern serverless architectures, may need to have a high number of open connections to the database or may frequently open and close database connections, exhausting the database memory and compute resources. Amazon RDS Proxy allows applications to pool and share database connections, improving your database efficiency and application scalability. For information on supported database engine versions and regional availability of RDS Proxy, refer to our RDS and Aurora documentations.
Today, AWS announced the general availability of Amazon GuardDuty custom threat detection using entity lists. This new feature enhances threat detection capabilities in GuardDuty by extending support to incorporate your own domain-based threat intelligence into the service beyond originally supported custom IP list. You can now detect threats in GuardDuty using malicious domains or IP addresses defined in your custom threat list. As part of this update, GuardDuty introduces a new finding type, Impact:EC2/MaliciousDomainRequest.Custom, which is triggered when activity related to a domain in your custom threat list is detected. Additionally, you can use entity lists to suppress alerts from trusted sources, giving you greater control over your threat detection strategy.
Entity lists offer enhanced flexibility compared to the previous IP address lists. These new lists can include IP addresses, domains, or both, allowing for more comprehensive threat intelligence integration. Unlike the legacy IP list format, entity lists provides simplified permission management and avoids impacting IAM policy size limits across multiple AWS Regions, making it easier to implement and manage custom threat detection across your AWS environment.
GuardDuty custom entity list is available in all AWS Regions where GuardDuty is offered, excluding China Regions and GovCloud (US) Regions.
Today, AWS announced the general availability of Amazon GuardDuty custom threat detection using entity lists. This new feature enhances threat detection capabilities in GuardDuty by extending support to incorporate your own domain-based threat intelligence into the service beyond originally supported custom IP list. You can now detect threats in GuardDuty using malicious domains or IP addresses defined in your custom threat list. As part of this update, GuardDuty introduces a new finding type, Impact:EC2/MaliciousDomainRequest.Custom, which is triggered when activity related to a domain in your custom threat list is detected. Additionally, you can use entity lists to suppress alerts from trusted sources, giving you greater control over your threat detection strategy. Entity lists offer enhanced flexibility compared to the previous IP address lists. These new lists can include IP addresses, domains, or both, allowing for more comprehensive threat intelligence integration. Unlike the legacy IP list format, entity lists provides simplified permission management and avoids impacting IAM policy size limits across multiple AWS Regions, making it easier to implement and manage custom threat detection across your AWS environment. GuardDuty custom entity list is available in all AWS Regions where GuardDuty is offered, excluding China Regions and GovCloud (US) Regions.
Amazon Aurora PostgreSQL Limitless Database is now available with PostgreSQL version 16.9 compatibility. This release contains product improvements and bug fixes made by the PostgreSQL community, along with Aurora Limitless-specific additions such as support for the hstore extension, the auto_explain extension, and various performance improvements. The hstore extension allows for storing sets of key/value pairs within a single PostgreSQL value, while the auto-explain extension logs execution plans of slow statements automatically.
Aurora PostgreSQL Limitless Database makes it easy for you to scale your relational database workloads by providing a serverless endpoint that automatically distributes data and queries across multiple Amazon Aurora Serverless instances while maintaining the transactional consistency of a single database. Aurora PostgreSQL Limitless Database offers capabilities such as distributed query planning and transaction management, removing the need for you to create custom solutions or manage multiple databases to scale. As your workloads increase, Aurora PostgreSQL Limitless Database adds compute resources while staying within your specified budget, so there is no need to provision for peak, and compute automatically scales down when demand is low.
Aurora PostgreSQL Limitless Database is available in the following AWS Regions: US East (N. Virginia, Ohio), US West (N. California, Oregon), Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Thailand, Tokyo), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), Middle East (Bahrain, UAE), and South America (Sao Paulo).
Amazon Aurora PostgreSQL Limitless Database is now available with PostgreSQL version 16.9 compatibility. This release contains product improvements and bug fixes made by the PostgreSQL community, along with Aurora Limitless-specific additions such as support for the hstore extension, the auto_explain extension, and various performance improvements. The hstore extension allows for storing sets of key/value pairs within a single PostgreSQL value, while the auto-explain extension logs execution plans of slow statements automatically. Aurora PostgreSQL Limitless Database makes it easy for you to scale your relational database workloads by providing a serverless endpoint that automatically distributes data and queries across multiple Amazon Aurora Serverless instances while maintaining the transactional consistency of a single database. Aurora PostgreSQL Limitless Database offers capabilities such as distributed query planning and transaction management, removing the need for you to create custom solutions or manage multiple databases to scale. As your workloads increase, Aurora PostgreSQL Limitless Database adds compute resources while staying within your specified budget, so there is no need to provision for peak, and compute automatically scales down when demand is low. Aurora PostgreSQL Limitless Database is available in the following AWS Regions: US East (N. Virginia, Ohio), US West (N. California, Oregon), Africa (Cape Town), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Osaka, Seoul, Singapore, Sydney, Thailand, Tokyo), Canada (Central), Canada West (Calgary), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Israel (Tel Aviv), Mexico (Central), Middle East (Bahrain, UAE), and South America (Sao Paulo). For pricing details, visit Amazon Aurora pricing. To learn more, read the Aurora PostgreSQL Limitless Database documentation and get started by creating an Aurora PostgreSQL Limitless Database in only a few steps in the Amazon RDS console.
AWS Backup Audit Manager now supports cross-account, cross-Region reports in Asia Pacific (Hyderabad, Jakarta, Melbourne), Europe (Spain, Zurich), and Middle East (UAE) Regions.
Now, you can use your AWS Organizations’ management or delegated administrator account to generate aggregated cross-account and cross-Region reports on your data protection policies and retrieve operational data about your backup and recovery activities. AWS Backup enables you to centralize and automate data protection policies across AWS services based on organizational best practices and regulatory standards, and AWS Backup Audit Manager is a feature within the AWS Backup service that allows you to audit and report on the compliance of your data protection policies to help you meet your business and regulatory needs.
AWS Backup Audit Manager now supports cross-account, cross-Region reports in Asia Pacific (Hyderabad, Jakarta, Melbourne), Europe (Spain, Zurich), and Middle East (UAE) Regions. Now, you can use your AWS Organizations’ management or delegated administrator account to generate aggregated cross-account and cross-Region reports on your data protection policies and retrieve operational data about your backup and recovery activities. AWS Backup enables you to centralize and automate data protection policies across AWS services based on organizational best practices and regulatory standards, and AWS Backup Audit Manager is a feature within the AWS Backup service that allows you to audit and report on the compliance of your data protection policies to help you meet your business and regulatory needs. To find a full list of AWS Regions in which AWS Backup Audit Manager is available, please refer to the AWS Backup Regional availability. To learn more about AWS Backup Audit Manager, visit the product page and documentation. To get started, visit the AWS Backup console.
Today, AWS announces the general availability of Organizational Notification Configurations for AWS User Notifications. This launch allows AWS Organizations users to centrally configure and view notifications across their organization. You can use the Management Account or Delegated Administrators (DAs) to configure and view notifications about accounts included in specific organizational units (OUs) or all accounts rolling up to an organization. Once configured, events from any of the member accounts will generate a notification in the Management Account. User Notifications supports up to 5 DAs.
You can use this capability to setup notifications for any supported Amazon EventBridge Event. For example, you can setup a notification configuration to send a push notification to the AWS Console Mobile Application anytime a user in any of the member accounts in your organization signs in to the console without MFA. Notifications will also be available in the Admin’s Console Notifications Center.
This new capability is available in all AWS Regions where AWS User Notifications is available.
To learn more about managing notifications across your organization with AWS User Notifications, please refer to the user guide.
Today, AWS announces the general availability of Organizational Notification Configurations for AWS User Notifications. This launch allows AWS Organizations users to centrally configure and view notifications across their organization. You can use the Management Account or Delegated Administrators (DAs) to configure and view notifications about accounts included in specific organizational units (OUs) or all accounts rolling up to an organization. Once configured, events from any of the member accounts will generate a notification in the Management Account. User Notifications supports up to 5 DAs. You can use this capability to setup notifications for any supported Amazon EventBridge Event. For example, you can setup a notification configuration to send a push notification to the AWS Console Mobile Application anytime a user in any of the member accounts in your organization signs in to the console without MFA. Notifications will also be available in the Admin’s Console Notifications Center. This new capability is available in all AWS Regions where AWS User Notifications is available. To learn more about managing notifications across your organization with AWS User Notifications, please refer to the user guide.
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.
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”.
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.
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.
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.
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.
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.
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.
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.
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.
