AWS launches CloudWatch cross-account observability in the AWS GovCloud (US) Regions, enabling monitoring and troubleshooting of applications across multiple AWS accounts within an AWS GovCloud (US) Region. CloudWatch Cross-account observability allows seamless searching, visualization, and analysis of metrics, logs, and traces, removing account boundaries.

Security teams, operations teams, and service owners can now easily explore cross-account telemetry and analyze them to drive powerful insights helping to efficiently monitor and troubleshoot application health issues. CloudWatch Cross-account observability enables searching log groups across multiple accounts, running cross-account Logs Insights queries, and creating Contributor Insights rules to identify top contributors generating log entries. You can now run Metrics Insights queries on your cross-account metrics for a consolidated view and create cross-account alarms. With cross-account observability, you can now use AWS X-Ray Trace Map to monitor your cross-account applications or achieve single pane of glass observability on your end-to-end distributed traces for requests spanning across multiple accounts. For example, users can obtain end-to-end distributed traces tracking AWS Lambda functions calling each other across accounts. This eliminates the need to switch between accounts during troubleshooting, saving time and providing comprehensive visibility.

CloudWatch cross-account observability is now available in all commercial AWS Regions and the AWS GovCloud (US) Regions with no extra cost for logs and metrics, and the first trace copy is free. Detailed pricing information and documentation are available on the Amazon CloudWatch pricing page and documentation pages.
 

​AWS launches CloudWatch cross-account observability in the AWS GovCloud (US) Regions, enabling monitoring and troubleshooting of applications across multiple AWS accounts within an AWS GovCloud (US) Region. CloudWatch Cross-account observability allows seamless searching, visualization, and analysis of metrics, logs, and traces, removing account boundaries. Security teams, operations teams, and service owners can now easily explore cross-account telemetry and analyze them to drive powerful insights helping to efficiently monitor and troubleshoot application health issues. CloudWatch Cross-account observability enables searching log groups across multiple accounts, running cross-account Logs Insights queries, and creating Contributor Insights rules to identify top contributors generating log entries. You can now run Metrics Insights queries on your cross-account metrics for a consolidated view and create cross-account alarms. With cross-account observability, you can now use AWS X-Ray Trace Map to monitor your cross-account applications or achieve single pane of glass observability on your end-to-end distributed traces for requests spanning across multiple accounts. For example, users can obtain end-to-end distributed traces tracking AWS Lambda functions calling each other across accounts. This eliminates the need to switch between accounts during troubleshooting, saving time and providing comprehensive visibility. CloudWatch cross-account observability is now available in all commercial AWS Regions and the AWS GovCloud (US) Regions with no extra cost for logs and metrics, and the first trace copy is free. Detailed pricing information and documentation are available on the Amazon CloudWatch pricing page and documentation pages.    

Amazon Managed Service for Prometheus now supports label-based active series limits within your workspace. This feature helps you manage active series volume across different producers such as applications, services or teams that share a workspace.

You can now allocate specific active series limits to different metric producers in your workspace, enabling you to protect your critical metrics. If a sub-set of metrics experience an unexpected surge, only the metrics sharing the same label-based active series limits are throttled. For example, you can set different limits for metrics from different applications using label sets like {app=»payment-service», environment=»prod»}. If the payment-service application produced an unexpected surge in metrics, only ingested metrics originating from the payment-service application are throttled.

This experience is enabled by the new Workspace Configuration APIs. Using these APIs, you can also manage the data retention period of your workspace. You can specify the number of days to retain metrics data within your workspace, before permanent deletion. To get started, visit AMP console’s workspace configuration tab or use AWS CLI, SDK, or APIs. Check out the Amazon Managed Service for Prometheus user guide for detailed documentation.

This feature is now available in all AWS regions where Amazon Managed Service for Prometheus is generally available.

​Amazon Managed Service for Prometheus now supports label-based active series limits within your workspace. This feature helps you manage active series volume across different producers such as applications, services or teams that share a workspace. You can now allocate specific active series limits to different metric producers in your workspace, enabling you to protect your critical metrics. If a sub-set of metrics experience an unexpected surge, only the metrics sharing the same label-based active series limits are throttled. For example, you can set different limits for metrics from different applications using label sets like {app=»payment-service», environment=»prod»}. If the payment-service application produced an unexpected surge in metrics, only ingested metrics originating from the payment-service application are throttled.
This experience is enabled by the new Workspace Configuration APIs. Using these APIs, you can also manage the data retention period of your workspace. You can specify the number of days to retain metrics data within your workspace, before permanent deletion. To get started, visit AMP console’s workspace configuration tab or use AWS CLI, SDK, or APIs. Check out the Amazon Managed Service for Prometheus user guide for detailed documentation. This feature is now available in all AWS regions where Amazon Managed Service for Prometheus is generally available.  

AWS HealthOmics now supports workflow versioning, enabling customers to manage multiple versions of their bioinformatics workflows efficiently. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows. With this release, workflow developers can create and maintain multiple versions of their workflows while retaining consistent workflow IDs and base ARNs across versions.

With workflow versioning, users can select specific workflow versions when starting a run, enabling better control and reproducibility of their analyses. This simplifies collaboration by automatically sharing new workflow versions with existing subscribers, eliminating the need for manual resharing and ensuring teams always have access to the latest workflow iterations.

Workflow versioning is supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv).

To get started with workflow versioning, see the AWS HealthOmics documentation.

​AWS HealthOmics now supports workflow versioning, enabling customers to manage multiple versions of their bioinformatics workflows efficiently. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows. With this release, workflow developers can create and maintain multiple versions of their workflows while retaining consistent workflow IDs and base ARNs across versions. With workflow versioning, users can select specific workflow versions when starting a run, enabling better control and reproducibility of their analyses. This simplifies collaboration by automatically sharing new workflow versions with existing subscribers, eliminating the need for manual resharing and ensuring teams always have access to the latest workflow iterations. Workflow versioning is supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv). To get started with workflow versioning, see the AWS HealthOmics documentation.  

Amazon CloudWatch agent support for Red Hat OpenShift Service on AWS (ROSA) enables monitoring of applications and infrastructure using familiar CloudWatch tools such as Container Insights and Application Signals. ROSA is a fully-managed cloud service that helps customers to quickly deploy, operate, and scale containerized applications on AWS with the same consistent OpenShift experience they have on-premises. This new capability allows DevOps teams and application owners to gain deep visibility into their ROSA clusters’ performance, health, and resource utilization leveraging AWS’s native observability tools.

CloudWatch agent on ROSA enables the collection and analysis of metrics, logs, and traces from containerized applications and underlying infrastructure components, helping customers to identify the impact of anomalies on end-user experience. This integration streamlines the troubleshooting process and allows teams to quickly identify issues across their ROSA clusters and other AWS services. Through unified infrastructure and application monitoring, customers can set up automated alerts, track performance trends, and correlate events across their entire application stack.

Amazon CloudWatch agent is available in all public AWS Regions and AWS GovCloud (US). Please see Amazon CloudWatch pricing for pricing details.

To get started with Amazon CloudWatch agent on Red Hat OpenShift Service on AWS, see Setting up Container Insights on RedHat OpenShift on AWS (ROSA) in the Amazon CloudWatch User Guide.

​Amazon CloudWatch agent support for Red Hat OpenShift Service on AWS (ROSA) enables monitoring of applications and infrastructure using familiar CloudWatch tools such as Container Insights and Application Signals. ROSA is a fully-managed cloud service that helps customers to quickly deploy, operate, and scale containerized applications on AWS with the same consistent OpenShift experience they have on-premises. This new capability allows DevOps teams and application owners to gain deep visibility into their ROSA clusters’ performance, health, and resource utilization leveraging AWS’s native observability tools. CloudWatch agent on ROSA enables the collection and analysis of metrics, logs, and traces from containerized applications and underlying infrastructure components, helping customers to identify the impact of anomalies on end-user experience. This integration streamlines the troubleshooting process and allows teams to quickly identify issues across their ROSA clusters and other AWS services. Through unified infrastructure and application monitoring, customers can set up automated alerts, track performance trends, and correlate events across their entire application stack. Amazon CloudWatch agent is available in all public AWS Regions and AWS GovCloud (US). Please see Amazon CloudWatch pricing for pricing details. To get started with Amazon CloudWatch agent on Red Hat OpenShift Service on AWS, see Setting up Container Insights on RedHat OpenShift on AWS (ROSA) in the Amazon CloudWatch User Guide.  

AWS Security Token Service (AWS STS) now automatically serves all requests to the global endpoint (sts.amazonaws.com) in the same AWS Region as your deployed workloads, enhancing resiliency and performance. Previously, all requests to the STS global endpoint were served from the US East (N. Virginia) Region.

With this enhancement, your applications benefit from improved latency and fault isolation as requests are processed in the same Region as your workloads. For example, if your application runs in US West (Oregon) and calls the STS global endpoint, your requests are now served locally in US West (Oregon) instead of being routed to US East (N. Virginia).

This update is available in all AWS Regions that are enabled by default. No action is required from customers to benefit from these improvements. Any requests to the STS global endpoint from Regions not enabled by default (i.e. opt-in Regions) will continue to be served in US East (N. Virginia).

We continue to recommend that you use the appropriate STS Regional endpoints whenever possible. For more information about these changes, see AWS STS global endpoint changes , and the announcement blogpost.
 

​AWS Security Token Service (AWS STS) now automatically serves all requests to the global endpoint (sts.amazonaws.com) in the same AWS Region as your deployed workloads, enhancing resiliency and performance. Previously, all requests to the STS global endpoint were served from the US East (N. Virginia) Region. With this enhancement, your applications benefit from improved latency and fault isolation as requests are processed in the same Region as your workloads. For example, if your application runs in US West (Oregon) and calls the STS global endpoint, your requests are now served locally in US West (Oregon) instead of being routed to US East (N. Virginia). This update is available in all AWS Regions that are enabled by default. No action is required from customers to benefit from these improvements. Any requests to the STS global endpoint from Regions not enabled by default (i.e. opt-in Regions) will continue to be served in US East (N. Virginia). We continue to recommend that you use the appropriate STS Regional endpoints whenever possible. For more information about these changes, see AWS STS global endpoint changes , and the announcement blogpost.    

AWS customers can now access Amazon Lightsail from within the AWS Console Mobile App to monitor and manage Lightsail instances, containers, databases, network, storage, snapshots, domains and DNS while on the go. Visit the Services tab in the AWS Console Mobile App and select Lightsail to get started.

The AWS Console Mobile App enables AWS customers monitor and manage a select set of resources and receive push notifications to stay informed and connected with their AWS resources while on-the-go. The sign-in process supports biometrics authentication, making access to AWS resources simple, secure, and quick. Lightsail offers easy-to-use virtual private server (VPS) instances, storage, databases, and more for a cost-effective monthly price. For AWS services not available natively, customers can access the AWS Management Console via an in-app browser to access service pages without additional authentication, manual navigation, or need to switch from the app to a browser.

Visit the AWS Console Mobile App product page for more information about the AWS Console Mobile App, including a full list of supported services and regions. Visit the Amazon Lightsail product page for more information about Amazon Lightsail, including supported regions.

​AWS customers can now access Amazon Lightsail from within the AWS Console Mobile App to monitor and manage Lightsail instances, containers, databases, network, storage, snapshots, domains and DNS while on the go. Visit the Services tab in the AWS Console Mobile App and select Lightsail to get started. The AWS Console Mobile App enables AWS customers monitor and manage a select set of resources and receive push notifications to stay informed and connected with their AWS resources while on-the-go. The sign-in process supports biometrics authentication, making access to AWS resources simple, secure, and quick. Lightsail offers easy-to-use virtual private server (VPS) instances, storage, databases, and more for a cost-effective monthly price. For AWS services not available natively, customers can access the AWS Management Console via an in-app browser to access service pages without additional authentication, manual navigation, or need to switch from the app to a browser. Visit the AWS Console Mobile App product page for more information about the AWS Console Mobile App, including a full list of supported services and regions. Visit the Amazon Lightsail product page for more information about Amazon Lightsail, including supported regions.  

• Categoría: Noticias de Microsoft

abril 18, 2025

Desglose de datos de IA: la sorprendente forma en que la IA facilita el trabajo duro

Nuestra nueva investigación muestra que Copilot no solo reduce el esfuerzo mental para tareas difíciles, sino que también mejora la calidad del trabajo.

Ilustración de Maria Machulska

Esta historia aparece en el boletín de WorkLab. Inscríbanse aquí.

Imaginen correr una carrera de 5 km y, en lugar de sentir esfuerzo, su ritmo cardíaco disminuye, cada zancada se vuelve más suave y fácil a medida que avanzan. No estamos hechos para eso, pero una nueva investigación sugiere que la IA podría hacer que las tareas complejas se sientan igual de fáciles.

Lo que hicimos:

Nuestros investigadores pidieron a los empleados de una empresa multinacional de servicios de TI que completaran un proyecto desafiante: resumir la información de una serie de documentos y redactar un Procedimiento Operativo Estándar (SOP, por sus siglas en inglés), junto con un conjunto de materiales de capacitación adjuntos. Veintiséis participantes del estudio tenían acceso a Copilot, mientras que un grupo de control de 22 no lo tenía.

Los participantes compartieron sus experiencias después de completar cada una de las seis tareas del proyecto y brindaron comentarios sobre el esfuerzo mental percibido que requerían. Se les pidió que calificaran cuánto esfuerzo mental requería cada paso en una escala del uno al 10.

Una vez finalizado el trabajo, los investigadores encuestaron a los participantes sobre su experiencia, incluido lo agotador que les pareció el proceso. Luego compararon las respuestas.

Lo que encontramos:

Los empleados con acceso a Copilot encontraron que la tarea era cinco veces menos agotadora que el grupo de control, y era mucho menos probable que informaran que la tarea requería mucho esfuerzo.

Pero esto es lo que resultó sorprendente: los usuarios de Copilot experimentaron una reducción notable en el esfuerzo mental con cada paso de la creación del SOP y los materiales de capacitación. En promedio, su esfuerzo percibido disminuyó un 6,3% por instancia. En contraste, el nivel de esfuerzo del grupo de control aumentó  alrededor de un 2% con cada paso subsiguiente, como el corredor que se fatiga más a medida que avanza la carrera.

De manera crucial, los usuarios de Copilot no vieron ningún impacto adverso en la calidad: de hecho, tuvieron puntuaciones mucho más altas en dimensiones como «exhaustividad» y «estructura y efectividad». También completaron los materiales a un ritmo similar o incluso más rápido que el grupo de control.

La IA reduce la carga mental con el tiempo

Los empleados con Copilot encontraron un conjunto de tareas cada vez más fácil, mientras que aquellos que no lo tenían se enfrentaron a desafíos cada vez mayores.

Lo que significa:

La IA no elimina todo el esfuerzo mental del trabajo, de hecho, aprender a usarla requiere crear un nuevo conjunto de hábitos. Pero nuestro estudio muestra que una vez que los empleados dominan Copilot, las tareas difíciles se vuelven menos agotadoras a nivel mental con el tiempo.

La energía mental es un recurso finito y precioso que toda empresa debe utilizar de la forma más inteligente y decidida posible. Ayudar a los empleados a aprovechar la IA los libera para que se concentren en lo que más importa y les da la resistencia para llegar hasta el final.

Etiquetas:

• IA
• Vida y Trabajo

The post Desglose de datos de IA: la sorprendente forma en que la IA facilita el trabajo duro appeared first on Source LATAM.

​The post Desglose de datos de IA: la sorprendente forma en que la IA facilita el trabajo duro appeared first on Source LATAM.  

AWS customers in Europe can now use Advance Pay, which allows them to pay for their AWS usage in advance and automate future invoice payments. With Advance Pay, customers can add funds to their account, which AWS will automatically use to pay invoices as they become due. This feature provides customers in Europe with more flexibility in managing their AWS expenses and simplifies the payment process for ongoing cloud services.

Advance Pay offers several benefits to AWS customers in Europe. It allows for better financial planning and budgeting by enabling upfront payments for anticipated usage. This feature can be particularly useful for organizations that prefer to pay in advance for services or need to manage their cloud spending more proactively. Additionally, the automatic payment of invoices reduces administrative overhead and ensures timely payments, helping customers maintain good standing with AWS.

With the launch, Advance Pay is now available for both AWS Europe and AWS Inc customers.

Getting started with Advance Pay is straightforward. Customers can register for the service from the Payments page in the AWS Billing and Cost Management console. To add funds, users can generate a funding document and submit an advance payment through electronic fund transfer. For more information on managing Advance Pay, including viewing funding history and setting up recurring payments, customers can refer to the “Managing your Advance Pay” section in the AWS Billing and Cost Management user guide. To learn more about Advance Pay or to get started, visit the AWS Billing and Cost Management console.
 

​AWS customers in Europe can now use Advance Pay, which allows them to pay for their AWS usage in advance and automate future invoice payments. With Advance Pay, customers can add funds to their account, which AWS will automatically use to pay invoices as they become due. This feature provides customers in Europe with more flexibility in managing their AWS expenses and simplifies the payment process for ongoing cloud services. Advance Pay offers several benefits to AWS customers in Europe. It allows for better financial planning and budgeting by enabling upfront payments for anticipated usage. This feature can be particularly useful for organizations that prefer to pay in advance for services or need to manage their cloud spending more proactively. Additionally, the automatic payment of invoices reduces administrative overhead and ensures timely payments, helping customers maintain good standing with AWS. With the launch, Advance Pay is now available for both AWS Europe and AWS Inc customers. Getting started with Advance Pay is straightforward. Customers can register for the service from the Payments page in the AWS Billing and Cost Management console. To add funds, users can generate a funding document and submit an advance payment through electronic fund transfer. For more information on managing Advance Pay, including viewing funding history and setting up recurring payments, customers can refer to the “Managing your Advance Pay” section in the AWS Billing and Cost Management user guide. To learn more about Advance Pay or to get started, visit the AWS Billing and Cost Management console.    

Amazon OpenSearch Service now supports SAML (Security Assertion Markup Language) via IAM federation for the next-generation OpenSearch UI. OpenSearch UI is a modernized operational analytics experience that enables users to gain insights cross data spanning managed domains and serverless collections from a single endpoint. OpenSearch UI already supports authentication via AWS Identity & Access Management (IAM) and IAM Identity Center (IDC). With this feature, you can now configure the SAML identity federation between your identity provider and IAM, so that your end-users can have a Single Sign-On (SSO) experience, to login from your Identity Providers and land directly in OpenSearch UI.

With SAML support, you can define a Default Relay State URL so that your end-users can click on the URL to open the login page from your Identity Provider, complete the SSO, and then land directly on the page you defined in OpenSearch UI. You can also define fine-grained access control (FGAC) by mapping Identity Provider users and roles to IAM roles with different permissions in OpenSearch, so that you can easily manage user permissions as well as to track user activities from the Identity Provider.

OpenSearch UI supports SAML in all regions that OpenSearch UI is available. To get started, create an OpenSearch UI application and follow the instructions to complete the SAML configuration. Learn more at Amazon OpenSearch Service Developer Guide.
 

​Amazon OpenSearch Service now supports SAML (Security Assertion Markup Language) via IAM federation for the next-generation OpenSearch UI. OpenSearch UI is a modernized operational analytics experience that enables users to gain insights cross data spanning managed domains and serverless collections from a single endpoint. OpenSearch UI already supports authentication via AWS Identity & Access Management (IAM) and IAM Identity Center (IDC). With this feature, you can now configure the SAML identity federation between your identity provider and IAM, so that your end-users can have a Single Sign-On (SSO) experience, to login from your Identity Providers and land directly in OpenSearch UI. With SAML support, you can define a Default Relay State URL so that your end-users can click on the URL to open the login page from your Identity Provider, complete the SSO, and then land directly on the page you defined in OpenSearch UI. You can also define fine-grained access control (FGAC) by mapping Identity Provider users and roles to IAM roles with different permissions in OpenSearch, so that you can easily manage user permissions as well as to track user activities from the Identity Provider. OpenSearch UI supports SAML in all regions that OpenSearch UI is available. To get started, create an OpenSearch UI application and follow the instructions to complete the SAML configuration. Learn more at Amazon OpenSearch Service Developer Guide.    

Amazon EventBridge announces support for Amazon Key Management Service (KMS) Customer Managed Keys (CMK) in API destinations connections. This enhancement enables you to encrypt your HTTPS endpoint authentication credentials managed by API destinations with your own keys instead of an AWS owned key (which is used by default). With CMK support, you now have more granular security control over your authentication credentials used in API destinations, helping you meet your organization’s security requirements and governance policies.

Customer managed Keys (CMK) are KMS keys that you create and manage by yourself. You can also audit and track usage of your keys via CloudTrail. EventBridge API destinations are private and public HTTPS endpoints that you can invoke as the target of an event bus rule or pipe, similar to how you invoke an AWS service or resource as a target. API destinations provides flexible authentication options for HTTPS endpoints, such as API key and OAuth, storing and managing credentials securely in AWS Secrets Manager on your behalf.

CMK support for EventBridge API destinations connections is now available across all AWS Regions where EventBridge API destinations is available. Please refer to the EventBridge user guide and KMS documentation for details.
 

​Amazon EventBridge announces support for Amazon Key Management Service (KMS) Customer Managed Keys (CMK) in API destinations connections. This enhancement enables you to encrypt your HTTPS endpoint authentication credentials managed by API destinations with your own keys instead of an AWS owned key (which is used by default). With CMK support, you now have more granular security control over your authentication credentials used in API destinations, helping you meet your organization’s security requirements and governance policies. Customer managed Keys (CMK) are KMS keys that you create and manage by yourself. You can also audit and track usage of your keys via CloudTrail. EventBridge API destinations are private and public HTTPS endpoints that you can invoke as the target of an event bus rule or pipe, similar to how you invoke an AWS service or resource as a target. API destinations provides flexible authentication options for HTTPS endpoints, such as API key and OAuth, storing and managing credentials securely in AWS Secrets Manager on your behalf. CMK support for EventBridge API destinations connections is now available across all AWS Regions where EventBridge API destinations is available. Please refer to the EventBridge user guide and KMS documentation for details.