Amazon Bedrock batch inference now supports the Converse API as a model invocation type, enabling you to use a consistent, model-agnostic input format for your batch workloads.
Previously, batch inference required model-specific request formats using the InvokeModel API. Now, when creating a batch inference job, you can select Converse as the model invocation type and structure your input data using the standard Converse API request format. Output for Converse batch jobs follows the Converse API response format. With this feature, you can use the same unified request format for both real-time and batch inference, simplifying prompt management and reducing the effort needed to switch between models. You can configure the Converse model invocation type through both the Amazon Bedrock console and the API.
Amazon Bedrock batch inference now supports the Converse API as a model invocation type, enabling you to use a consistent, model-agnostic input format for your batch workloads. Previously, batch inference required model-specific request formats using the InvokeModel API. Now, when creating a batch inference job, you can select Converse as the model invocation type and structure your input data using the standard Converse API request format. Output for Converse batch jobs follows the Converse API response format. With this feature, you can use the same unified request format for both real-time and batch inference, simplifying prompt management and reducing the effort needed to switch between models. You can configure the Converse model invocation type through both the Amazon Bedrock console and the API. This capability is available in all AWS Regions that support Amazon Bedrock batch inference. To get started, see Create a batch inference job and Format and upload your batch inference data in the Amazon Bedrock User Guide.
AWS Network Firewall now integrates with Amazon EventBridge to provide real-time notifications for firewall state changes and configuration updates. This new capability enables you to monitor critical firewall operations including firewall configuration updates and endpoint status modifications across your network security infrastructure. You gain immediate visibility into changes affecting AWS Managed Rules, Partner Managed Rules, and firewall configurations.
With EventBridge integration, you gain enhanced visibility into your firewall operations in real-time. You can build automated workflows to send notifications through Amazon SNS, create tickets in your IT service management (ITSM) systems, or integrate with third-party security information and event management (SIEM) solutions. This integration helps you maintain better operational awareness of your network security infrastructure and respond quickly to configuration changes or potential issues.
AWS Network Firewall state change notifications through Amazon EventBridge are available in all AWS Regions where AWS Network Firewall and Amazon EventBridge is currently available.
AWS Network Firewall now integrates with Amazon EventBridge to provide real-time notifications for firewall state changes and configuration updates. This new capability enables you to monitor critical firewall operations including firewall configuration updates and endpoint status modifications across your network security infrastructure. You gain immediate visibility into changes affecting AWS Managed Rules, Partner Managed Rules, and firewall configurations. With EventBridge integration, you gain enhanced visibility into your firewall operations in real-time. You can build automated workflows to send notifications through Amazon SNS, create tickets in your IT service management (ITSM) systems, or integrate with third-party security information and event management (SIEM) solutions. This integration helps you maintain better operational awareness of your network security infrastructure and respond quickly to configuration changes or potential issues. AWS Network Firewall state change notifications through Amazon EventBridge are available in all AWS Regions where AWS Network Firewall and Amazon EventBridge is currently available. To learn more about AWS Network Firewall EventBridge integration, visit the AWS Network Firewall documentation. For information about Amazon EventBridge, see the Amazon EventBridge documentation.
AWS Resource Access Manager (RAM) now supports a resource share configuration that allows you to maintain resource sharing continuity when accounts move between AWS Organizations. With the new RetainSharingOnAccountLeaveOrganization parameter and corresponding ram:RetainSharingOnAccountLeaveOrganization condition key, security administrators can configure resource shares to retain access when accounts leave the organization and enforce consistent policies across their organization using Service Control Policies (SCPs).
This capability helps organizations undergoing mergers, acquisitions, or restructuring maintain access to shared resources like Route53 Resolver Rules, Transit Gateways, and IPAM pools without disruption. Security teams can use SCPs to enforce the RetainSharingOnAccountLeaveOrganization configuration organization-wide. When enabled, RAM treats organization accounts as external accounts, requiring explicit invitation acceptance and preserving resource access during account transitions between organizations.
This feature is available in all AWS commercial Regions at no additional cost. To learn more about resource share configurations, see the AWS RAM documentation or visit the AWS RAM product page.
AWS Resource Access Manager (RAM) now supports a resource share configuration that allows you to maintain resource sharing continuity when accounts move between AWS Organizations. With the new RetainSharingOnAccountLeaveOrganization parameter and corresponding ram:RetainSharingOnAccountLeaveOrganization condition key, security administrators can configure resource shares to retain access when accounts leave the organization and enforce consistent policies across their organization using Service Control Policies (SCPs). This capability helps organizations undergoing mergers, acquisitions, or restructuring maintain access to shared resources like Route53 Resolver Rules, Transit Gateways, and IPAM pools without disruption. Security teams can use SCPs to enforce the RetainSharingOnAccountLeaveOrganization configuration organization-wide. When enabled, RAM treats organization accounts as external accounts, requiring explicit invitation acceptance and preserving resource access during account transitions between organizations. This feature is available in all AWS commercial Regions at no additional cost. To learn more about resource share configurations, see the AWS RAM documentation or visit the AWS RAM product page.
Amazon CloudWatch now supports customizing destination log group names when creating CloudWatch log centralization rules. Organizations managing logs across multiple accounts can now use attributes to organize centralized logs into meaningful hierarchies — by account ID, region, organizational unit, or other AWS Organizations metadata — that match how their organization operates and what their compliance requirements demand.
You can define a destination log group name structure using attributes that CloudWatch Logs automatically replaces with actual values when logs are copied. For example, using the pattern ${source.accountId}/${source.region}/${source.logGroup} creates destination log groups like 123456789012/us-east-1/cloudtrail/managementevent, making it easy to identify which account and region logs originated from. You can use attributes, including source account ID, region, log group name, organization ID, organizational unit ID, root ID, and the full organizational path.
Customers can use centralization rules to centralize one copy of logs for free (ingestion). Additional copies are charged at $0.05/GB of logs centralized (the backup region feature is considered an additional copy). Storage charges apply. To learn more, visit the CloudWatch Logs Centralization documentation.
Amazon CloudWatch now supports customizing destination log group names when creating CloudWatch log centralization rules. Organizations managing logs across multiple accounts can now use attributes to organize centralized logs into meaningful hierarchies — by account ID, region, organizational unit, or other AWS Organizations metadata — that match how their organization operates and what their compliance requirements demand.
You can define a destination log group name structure using attributes that CloudWatch Logs automatically replaces with actual values when logs are copied. For example, using the pattern ${source.accountId}/${source.region}/${source.logGroup} creates destination log groups like 123456789012/us-east-1/cloudtrail/managementevent, making it easy to identify which account and region logs originated from. You can use attributes, including source account ID, region, log group name, organization ID, organizational unit ID, root ID, and the full organizational path.
Customizable destination log group names are available in all centralization rules supported regions.
Customers can use centralization rules to centralize one copy of logs for free (ingestion). Additional copies are charged at $0.05/GB of logs centralized (the backup region feature is considered an additional copy). Storage charges apply. To learn more, visit the CloudWatch Logs Centralization documentation.
Amazon Relational Database Service (RDS) for PostgreSQL now supports the latest minor versions 18.3, 17.9, 16.13, 15.17, and 14.22. These versions address the regression from the February 12, 2026 PostgreSQL community release. We recommend that you upgrade to the latest minor versions to fix known security vulnerabilities in prior versions of PostgreSQL, and to benefit from the bug fixes added by the PostgreSQL community.
You can upgrade your databases during scheduled maintenance windows using automatic minor version upgrades. To simplify operations at scale, enable automatic minor version upgrades and use the AWS Organizations Upgrade Rollout Policy to orchestrate thousands of upgrades in phases, first to development environments before upgrading production systems. You can also use Amazon RDS Blue/Green deployments with physical replication to minimize downtime for minor version upgrades.
Amazon RDS for PostgreSQL makes it simple to set up, operate, and scale PostgreSQL deployments in the cloud. See Amazon RDS for PostgreSQL Pricing for pricing details and regional availability. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console or by using the AWS Command Line Interface (CLI).
Amazon Relational Database Service (RDS) for PostgreSQL now supports the latest minor versions 18.3, 17.9, 16.13, 15.17, and 14.22. These versions address the regression from the February 12, 2026 PostgreSQL community release. We recommend that you upgrade to the latest minor versions to fix known security vulnerabilities in prior versions of PostgreSQL, and to benefit from the bug fixes added by the PostgreSQL community. You can upgrade your databases during scheduled maintenance windows using automatic minor version upgrades. To simplify operations at scale, enable automatic minor version upgrades and use the AWS Organizations Upgrade Rollout Policy to orchestrate thousands of upgrades in phases, first to development environments before upgrading production systems. You can also use Amazon RDS Blue/Green deployments with physical replication to minimize downtime for minor version upgrades. Amazon RDS for PostgreSQL makes it simple to set up, operate, and scale PostgreSQL deployments in the cloud. See Amazon RDS for PostgreSQL Pricing for pricing details and regional availability. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console or by using the AWS Command Line Interface (CLI).
A veces, todos necesitamos un pequeño recordatorio de lo increíbles que somos. Por suerte, la IA está aquí para ayudarlos. Pueden usar Microsoft 365 Copilot para encontrar los elogios que se esconden en su bandeja de entrada o en los chats de Teams. ¡Así que adelante, anímense! Se lo han ganado.
Entren a Microsoft 365 Copilot y dejen esto en el chat:
Usando los correos en mi carpeta de Outlook [Nombre de la carpeta], resume el reconocimiento que he recibido. Para cada correo, proporciona un breve resumen que incluya el proyecto o tema, el reconocimiento otorgado y quién lo proporcionó. Luego, compila un párrafo pulido destacando los temas clave de mis contribuciones e impacto.
Pueden cambiar un poco el prompt si quieren sacar a la luz las cosas brillantes que la gente ha dicho sobre ustedes en Teams.
El Prompt es una sección habitual de Signal que les ofrece formas específicas y súper rápidas de usar la IA para resolver problemas, potenciar su creatividad y hacer más en el trabajo.
Celebramos 250 millones: Empoderar a las comunidades para que habiliten la economía global de la IA
Por: Melanie Nakagawa, directora de sostenibilidad, Microsoft.
Antes del Mobile World Congress, donde líderes mundiales, gobiernos e industria se reúnen en el mayor evento de conectividad del mundo, Microsoft ha marcado un hito importante en nuestros esfuerzos por expandir el acceso digital a nivel mundial. En 2022, asumimos un compromiso valiente para ampliar el acceso a internet a 250 millones de personas antes de finales de 2025. Hoy, nos enorgullece compartir que hemos alcanzado y superado ese objetivo, para extender la cobertura de conectividad a más de 299 millones de personas en todo el mundo, incluidas más de 124 millones en África.
Este hito representa más que un número. Refleja más de una década de colaboración sostenida con gobiernos, organizaciones sin ánimo de lucro, proveedores de conectividad local y socios de desarrollo en todo el mundo. Juntos, hemos trabajado para llegar a comunidades donde el acceso ha sido limitado a nivel histórico, lo que ha permitido abrir caminos hacia la educación, la sanidad, la oportunidad económica y la participación digital.
Alcanzar este hito es también un momento de reflexión y renovación. A partir de años de progreso, Microsoft evoluciona su enfoque hacia el acceso digital para centrarse no solo en la cobertura, sino también en la adopción, la habilitación y la participación a largo plazo en la economía de la IA.
Como parte de este nuevo capítulo, anunciamos una nueva colaboración con Starlink. Esta colaboración amplía el conjunto de herramientas disponibles para ayudar a ofrecer acceso digital en comunidades rurales, agrícolas y de difícil acceso. Combinado con socios locales de entrega e instituciones comunitarias, fortalece las bases para comunidades preparadas para la IA en todo el mundo.
Por qué importa el acceso digital en la era de la IA
A pesar del progreso continuo, 2.200 millones de personas en todo el mundo siguen desconectadas, y muchas más se enfrentan a barreras relacionadas con la asequibilidad, la fiabilidad o el acceso a servicios digitales relevantes. Estas brechas ya limitan las oportunidades y se amplían el riesgo a medida que la IA se vuelve más central en el crecimiento de las economías y el funcionamiento de las sociedades.
En el Mobile World Congress 2024, Brad Smith, vicepresidente y presidente de Microsoft, compartió nuestros Principios de Acceso a la IA, donde subraya que la electricidad y la conectividad son bases esenciales para una economía inclusiva de la IA. Desde entonces, el ritmo del cambio solo se ha acelerado. De hecho, el Informe de Difusión de la IA de Microsoft 2025 muestra que la IA se adopta más rápido que cualquier tecnología de propósito general en la historia, pero la adopción sigue desigual. Como ilustran los datos, la adopción en el Norte Global se acelera más rápido que en el Sur Global. Las diferencias en infraestructuras, acceso a herramientas y preparación digital contribuyen a una creciente brecha entre economías de ingresos altos y de ingresos bajos.
Este gráfico del Informe de Difusión de la IA 2025 refuerza una idea clara: el acceso a la IA por sí solo no es suficiente. Para que las comunidades participen de manera significativa en la era digital y de la IA, la conectividad debe combinarse con energía fiable, dispositivos asequibles, habilidades digitales y tecnologías diseñadas para uso real. Donde existen estas condiciones, se produce la adopción. En Zambia, por ejemplo, la adopción de IA generativa a nivel nacional es del 12 por ciento, pero entre quienes tienen acceso a internet sube al 34 por ciento.
Profundizar el enfoque de Microsoft hacia el acceso digital
Basándonos en lo que hemos aprendido, Microsoft impulsa un modelo de acceso digital más holístico que reconoce la conectividad como solo una parte de un sistema más amplio. En la práctica, esto significa colaboración para ofrecer no solo acceso a internet, sino también infraestructuras energéticas más fiables, acceso al agua cuando sea relevante, dispositivos, habilidades digitales y herramientas en la nube e IA, todo diseñado y desplegado para las comunidades a las que sirve. Al trabajar entre organizaciones y gobiernos para abordar estas necesidades fundamentales en paralelo, este enfoque ayuda a garantizar que el acceso digital sea utilizable, duradero y capaz de respaldar resultados reales.
Un foco central de este trabajo son los modelos de acceso comunitarios que sean sostenibles a nivel financiero, escalables y alineados con las prioridades nacionales de desarrollo. Estos modelos reúnen instituciones locales como escuelas, centros de salud, cooperativas y centros comunitarios, y se implementan en colaboración con gobiernos, empresas, organizaciones sin ánimo de lucro y organizaciones financieras para el desarrollo. Al integrar infraestructuras, habilitación y financiación desde el principio, estos programas holísticos pueden ayudar a desbloquear inversiones a largo plazo, apoyar el crecimiento responsable y permitir que las comunidades participen a plenitud en la economía digital y de la IA.
El progreso a esta escala solo es posible gracias a alianzas sólidas basadas en la entrega local, la confianza comunitaria y la sostenibilidad a largo plazo. El trabajo de Microsoft para extender la conectividad a más de 299 millones de personas se ha construido junto a socios que comprenden las realidades del despliegue en la última milla y la adopción digital.
En África, Microsoft colabora con socios como Cassava Technologies para ampliar la infraestructura digital regional y fomentar un acceso a internet de alta calidad en Sudáfrica, Malawi, Kenia y Zambia. Las colaboraciones con proveedores locales como Tizeti ofrecen conectividad asequible y fiable a través de redes Wi-Fi alimentadas por energía solar en Nigeria y Ghana.
En América Latina, la colaboración de Microsoft con Anditel se centra en ampliar el acceso a internet y energía para comunidades rurales y agrarias en Colombia mediante modelos liderados a nivel local, alineados con las prioridades nacionales. En India, Microsoft trabaja con AirJaldi para combinar la conectividad asequible con formación en habilidades digitales y vías prácticas de uso, lo que permite ayudar a las comunidades a ir más allá del acceso básico hacia una adopción significativa.
Estas colaboraciones hicieron posible alcanzar el hito de los 250 millones. También reflejan un principio que guía nuestro trabajo. El acceso digital duradero se construye con comunidades, no para ellas.
Ampliación del portafolio: colaboración con Starlink
Sobre esta base, Microsoft continúa con la expansión y diversificación de su cartera para llegar a comunidades donde la infraestructura tradicional por sí sola no puede satisfacer la demanda.
A través de nuestra colaboración con Starlink, Microsoft combina conectividad satelital en órbita terrestre baja con modelos de despliegue comunitarios y alianzas con ecosistemas locales. Esto pretende ampliar el conjunto de herramientas disponibles para ofrecer acceso digital, manteniéndose integrado con firmeza en un enfoque holístico y basado en asociaciones.
Kenia ofrece un ejemplo temprano de este modelo en la práctica. En su colaboración con Starlink y el proveedor local de servicios de internet Mawingu Networks, Microsoft apoya la conectividad de 450 centros comunitarios en regiones rurales y desatendidas, incluidas cooperativas de agricultores, centros de agregación y centros digitales. Estos despliegues combinan conectividad satelital con habilidades digitales, herramientas y coordinación de ecosistemas para apoyar la productividad agrícola, el acceso a mercados y la adopción de servicios digitales y habilitados por IA.
Más allá de los 250 millones: Construir comunidades preparadas para la IA
Superar la marca de los 250 millones de conectividad es un momento para celebrar. También es un punto de partida para lo que viene después.
El próximo capítulo del trabajo de acceso digital de Microsoft está previsto centrarse en garantizar que el acceso se traduzca en adopción, uso y oportunidades a largo plazo. Al continuar la colaboración con gobiernos, instituciones financieras para el desarrollo, organizaciones sin ánimo de lucro y socios del sector privado, y la ampliación del acceso a la energía, mecanismos de financiación y soluciones de IA centradas en la comunidad, Microsoft trabaja para garantizar que todos, en cualquier lugar, puedan participar en la economía digital y de la IA.
Starting today, AWS customers based in the United Kingdom can use Bacs Direct Debit to pay for their AWS services. This new feature provides a convenient and automated way to manage your cloud spend directly from your GBP-based bank account.
Customers can securely connect any personal or business bank account that supports the Bacs standard. Previously, AWS only accepted credit or debit cards and EUR-based bank accounts in the UK.
During sign-up, customers can choose «Bacs Direct Debit» from the AWS sign-up page, select their bank, and authenticate using their bank’s mobile app or online banking credentials. This securely verifies ownership and links the bank account to the AWS account. By default, this account will be used for future AWS invoices.
Existing customers can add Bacs Direct Debit by navigating to the Payment Preferences page in the AWS Billing console. They choose «Add payment method,» select «Bacs Direct Debit,» and follow the same bank selection and authentication flow. Once verified, the bank account is available as a payment method for future invoices.
Starting today, AWS customers based in the United Kingdom can use Bacs Direct Debit to pay for their AWS services. This new feature provides a convenient and automated way to manage your cloud spend directly from your GBP-based bank account.
Customers can securely connect any personal or business bank account that supports the Bacs standard. Previously, AWS only accepted credit or debit cards and EUR-based bank accounts in the UK.
During sign-up, customers can choose «Bacs Direct Debit» from the AWS sign-up page, select their bank, and authenticate using their bank’s mobile app or online banking credentials. This securely verifies ownership and links the bank account to the AWS account. By default, this account will be used for future AWS invoices.
Existing customers can add Bacs Direct Debit by navigating to the Payment Preferences page in the AWS Billing console. They choose «Add payment method,» select «Bacs Direct Debit,» and follow the same bank selection and authentication flow. Once verified, the bank account is available as a payment method for future invoices.
Bacs Direct Debit is available to customers in UK regions at not additional cost. To learn more, see Managing your Bacs direct debit payment method.
Amazon Bedrock now supports OpenAI-compatible Projects API in the Mantle inference engine in Amazon Bedrock. Amazon Bedrock is a fully managed service that offers a broad selection of best-in-class foundation models from leading AI companies like Anthropic, Meta, and OpenAI, along with a broad set of specialized developer tools that make it easy to build and scale compelling generative AI applications. Mantle is Amazon Bedrock’s distributed inference engine for large-scale model serving that supports OpenAI-compatible APIs.
With Projects API, customers who have more than one application, environment, or team can now create individual projects to achieve better isolation across all of them. You can assign different IAM-based access control to each project and add tags to each project for better cost visibility.
Projects are available for all customers using the OpenAI-compatible APIs, the Responses API and Chat Completions API, through the Mantle inference engine in Amazon Bedrock. There is no additional charge for using the Projects API. You pay only for the underlying model inference you consume. To get started with the Projects API in Amazon Bedrock, visit the Amazon Bedrock documentation.
Amazon Bedrock now supports OpenAI-compatible Projects API in the Mantle inference engine in Amazon Bedrock. Amazon Bedrock is a fully managed service that offers a broad selection of best-in-class foundation models from leading AI companies like Anthropic, Meta, and OpenAI, along with a broad set of specialized developer tools that make it easy to build and scale compelling generative AI applications. Mantle is Amazon Bedrock’s distributed inference engine for large-scale model serving that supports OpenAI-compatible APIs. With Projects API, customers who have more than one application, environment, or team can now create individual projects to achieve better isolation across all of them. You can assign different IAM-based access control to each project and add tags to each project for better cost visibility. Projects are available for all customers using the OpenAI-compatible APIs, the Responses API and Chat Completions API, through the Mantle inference engine in Amazon Bedrock. There is no additional charge for using the Projects API. You pay only for the underlying model inference you consume. To get started with the Projects API in Amazon Bedrock, visit the Amazon Bedrock documentation.
Amazon OpenSearch Service has enhanced Cluster Insights with two new insights — Cluster Overload and Suboptimal Sharding Strategy. Suboptimal Sharding Strategy provides instant visibility into shard imbalances that cause uneven workload distribution, while Cluster Overload surfaces elevated cluster resource utilization that can lead to request throttling or rejections. Both insights come with details of affected resources along with actionable mitigation recommendations.
Previously, identifying resource constraints and shard imbalances required manually correlating multiple metrics and logs, making it difficult to detect issues early. With these new insights, you can proactively monitor cluster health and take timely action.
Suboptimal Sharding Strategy detects shard imbalances caused by indices with too few shards relative to the number of data nodes, or by shards carrying disproportionately large amounts of data compared to others. It identifies the root cause of uneven workload distribution and provides recommendations to help you achieve optimal shard distribution for improved query performance and resource utilization. Similarly, Cluster Overload helps you identify elevated resource utilization, including CPU, memory, disk I/O, disk throughput, and disk utilization that can potentially lead to request throttling or rejections. It also provides scale-up recommendations so you can take timely action to protect your critical workloads.
These new insights are available at no additional cost for OpenSearch version 2.17 or later in all Regions where the OpenSearch UI is available. See the complete list of supported Regions here. To learn more, visit the Cluster Insights documentation or view the complete catalog of available insights.
Amazon OpenSearch Service has enhanced Cluster Insights with two new insights — Cluster Overload and Suboptimal Sharding Strategy. Suboptimal Sharding Strategy provides instant visibility into shard imbalances that cause uneven workload distribution, while Cluster Overload surfaces elevated cluster resource utilization that can lead to request throttling or rejections. Both insights come with details of affected resources along with actionable mitigation recommendations. Previously, identifying resource constraints and shard imbalances required manually correlating multiple metrics and logs, making it difficult to detect issues early. With these new insights, you can proactively monitor cluster health and take timely action. Suboptimal Sharding Strategy detects shard imbalances caused by indices with too few shards relative to the number of data nodes, or by shards carrying disproportionately large amounts of data compared to others. It identifies the root cause of uneven workload distribution and provides recommendations to help you achieve optimal shard distribution for improved query performance and resource utilization. Similarly, Cluster Overload helps you identify elevated resource utilization, including CPU, memory, disk I/O, disk throughput, and disk utilization that can potentially lead to request throttling or rejections. It also provides scale-up recommendations so you can take timely action to protect your critical workloads. These new insights are available at no additional cost for OpenSearch version 2.17 or later in all Regions where the OpenSearch UI is available. See the complete list of supported Regions here. To learn more, visit the Cluster Insights documentation or view the complete catalog of available insights.
