Publicado el Deja un comentario

AWS Chatbot is now named Amazon Q Developer

AWS Chatbot is now called Amazon Q Developer. The new name recognizes the integration of Amazon Q Developer, the most capable generative AI-powered assistant for software development, in Microsoft Teams and Slack to manage and optimize AWS resources. With Amazon Q Developer, customers can monitor, operate, and troubleshoot AWS resources in chat channels faster. Customers can quickly retrieve telemetry and ask questions to understand the state of their resources. Customers can leverage the existing non-generative AI features to operationalize Dev Ops and incident response processes with customizable notifications, action buttons, and command aliases.

With this launch, the Microsoft Teams and Slack chat application names will change from AWS Chatbot to Amazon Q Developer. The notifications and responses received will display Amazon Q as the application name instead of AWS. Running tasks will now use “@Amazon Q” mention instead of “@aws”. Slack automation workflows that trigger AWS Chatbot messages within chat channels will continue to work after this renaming. For existing AWS Chatbot customers, there is no other change to how features work, setup, usage, and pricing. The service APIs, SDK, service endpoints, IAM permissions, and region availability are not affected by this change.

Customers need to allow permissions to enable generative AI features. Amazon Q Developer generative AI features are available in chat applications at no additional cost.

Amazon Q Developer is available in chat applications at no additional cost in AWS Regions where this capability is offered. Get started with using Amazon Q Developer in your chat applications with the free tier by visiting the Amazon Q Developer console. Visit the documentation & blog to learn more.

 

​AWS Chatbot is now called Amazon Q Developer. The new name recognizes the integration of Amazon Q Developer, the most capable generative AI-powered assistant for software development, in Microsoft Teams and Slack to manage and optimize AWS resources. With Amazon Q Developer, customers can monitor, operate, and troubleshoot AWS resources in chat channels faster. Customers can quickly retrieve telemetry and ask questions to understand the state of their resources. Customers can leverage the existing non-generative AI features to operationalize Dev Ops and incident response processes with customizable notifications, action buttons, and command aliases. With this launch, the Microsoft Teams and Slack chat application names will change from AWS Chatbot to Amazon Q Developer. The notifications and responses received will display Amazon Q as the application name instead of AWS. Running tasks will now use “@Amazon Q” mention instead of “@aws”. Slack automation workflows that trigger AWS Chatbot messages within chat channels will continue to work after this renaming. For existing AWS Chatbot customers, there is no other change to how features work, setup, usage, and pricing. The service APIs, SDK, service endpoints, IAM permissions, and region availability are not affected by this change. Customers need to allow permissions to enable generative AI features. Amazon Q Developer generative AI features are available in chat applications at no additional cost. Amazon Q Developer is available in chat applications at no additional cost in AWS Regions where this capability is offered. Get started with using Amazon Q Developer in your chat applications with the free tier by visiting the Amazon Q Developer console. Visit the documentation & blog to learn more.  

Publicado el Deja un comentario

Amazon Connect now supports interactive welcome messages when starting chats

Amazon Connect Chat now enables you to greet customers with interactive messages when starting chats, delivering contextual and personalized experiences that improve engagement and self-service resolution rates. For example, when a customer visits a product page and opens the chat widget, they receive a contextual greeting with options to compare similar products, check store availability, or learn about warranty details.

To customize the interactive welcome message using Amazon Lex, check the ‘Initialize bot with message’ option in the ‘Get customer input’ block in the Amazon Connect flow designer. You can either manually enter or dynamically set the initial message sent to the chat bot to personalize your customer experience.

This new feature is available in all AWS regions where Amazon Connect is available. To learn more and get started, please refer to the help documentation, pricing page, or visit the Amazon Connect website.

 

​Amazon Connect Chat now enables you to greet customers with interactive messages when starting chats, delivering contextual and personalized experiences that improve engagement and self-service resolution rates. For example, when a customer visits a product page and opens the chat widget, they receive a contextual greeting with options to compare similar products, check store availability, or learn about warranty details. To customize the interactive welcome message using Amazon Lex, check the ‘Initialize bot with message’ option in the ‘Get customer input’ block in the Amazon Connect flow designer. You can either manually enter or dynamically set the initial message sent to the chat bot to personalize your customer experience. This new feature is available in all AWS regions where Amazon Connect is available. To learn more and get started, please refer to the help documentation, pricing page, or visit the Amazon Connect website.  

Publicado el Deja un comentario

Amazon RDS for MariaDB supports minors 11.4.5, 10.11.11, 10.6.21, 10.5.28

Amazon Relational Database Service (Amazon RDS) for MariaDB now supports MariaDB minor versions 11.4.5, 10.11.11, 10.6.21, and 10.5.28. We recommend that you upgrade to the latest minor versions to fix known security vulnerabilities in prior versions of MariaDB, and to benefit from the bug fixes, performance improvements, and new functionality added by the MariaDB community.

You can leverage automatic minor version upgrades to automatically upgrade your databases to more recent minor versions during scheduled maintenance windows. You can also leverage Amazon RDS Managed Blue/Green deployments for safer, simpler, and faster updates to your MariaDB instances. Learn more about upgrading your database instances, including automatic minor version upgrades and Blue/Green Deployments, in the Amazon RDS User Guide.

Amazon RDS for MariaDB makes it straightforward to set up, operate, and scale MariaDB deployments in the cloud. Learn more about pricing details and regional availability at Amazon RDS for MariaDB. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console.
 

 

​Amazon Relational Database Service (Amazon RDS) for MariaDB now supports MariaDB minor versions 11.4.5, 10.11.11, 10.6.21, and 10.5.28. We recommend that you upgrade to the latest minor versions to fix known security vulnerabilities in prior versions of MariaDB, and to benefit from the bug fixes, performance improvements, and new functionality added by the MariaDB community. You can leverage automatic minor version upgrades to automatically upgrade your databases to more recent minor versions during scheduled maintenance windows. You can also leverage Amazon RDS Managed Blue/Green deployments for safer, simpler, and faster updates to your MariaDB instances. Learn more about upgrading your database instances, including automatic minor version upgrades and Blue/Green Deployments, in the Amazon RDS User Guide. Amazon RDS for MariaDB makes it straightforward to set up, operate, and scale MariaDB deployments in the cloud. Learn more about pricing details and regional availability at Amazon RDS for MariaDB. Create or update a fully managed Amazon RDS database in the Amazon RDS Management Console.    

Publicado el Deja un comentario

AWS CodeBuild adds support for managed runners for GitLab Self-Managed

AWS CodeBuild now supports managed runners for GitLab Self-Managed. Customers can configure their CodeBuild projects to receive GitLab Self-Managed CI/CD job events and run them on CodeBuild ephemeral hosts. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages ready for deployment.

This feature allows GitLab Self-Managed jobs to integrate natively with AWS, providing security and convenience through features such as IAM, AWS Secrets Manager, AWS CloudTrail, and Amazon VPC. Customers can access all compute platforms that CodeBuild offers, including Lambda, GPU-enhanced and Arm-based instances.

CodeBuild’s integration with GitLab Self-Managed runners is available in all regions where CodeBuild is offered. For more information about the AWS Regions where CodeBuild is available, see the AWS Regions page.

Get started by setting up webhooks in a CodeBuild project, and updating your GitLab CI YAML to use self-managed runners hosted on CodeBuild machines. To learn more about runners powered by CodeBuild for GitLab or GitHub, see CodeBuild’s documentation for self-hosted runners in AWS CodeBuild.

 

​AWS CodeBuild now supports managed runners for GitLab Self-Managed. Customers can configure their CodeBuild projects to receive GitLab Self-Managed CI/CD job events and run them on CodeBuild ephemeral hosts. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages ready for deployment. This feature allows GitLab Self-Managed jobs to integrate natively with AWS, providing security and convenience through features such as IAM, AWS Secrets Manager, AWS CloudTrail, and Amazon VPC. Customers can access all compute platforms that CodeBuild offers, including Lambda, GPU-enhanced and Arm-based instances. CodeBuild’s integration with GitLab Self-Managed runners is available in all regions where CodeBuild is offered. For more information about the AWS Regions where CodeBuild is available, see the AWS Regions page. Get started by setting up webhooks in a CodeBuild project, and updating your GitLab CI YAML to use self-managed runners hosted on CodeBuild machines. To learn more about runners powered by CodeBuild for GitLab or GitHub, see CodeBuild’s documentation for self-hosted runners in AWS CodeBuild.  

Publicado el Deja un comentario

Amazon EC2 M6a instances now available in AWS Europe (Paris)

Starting today, the general-purpose Amazon EC2 M6a instances are now available in AWS Europe (Paris) region. M6a instances are powered by third-generation AMD EPYC processors, and deliver up to 35% better price performance than comparable M5a instances. These instances offer 10% lower cost than comparable x86-based EC2 instances.

With this additional region, M6a instances are available in the following AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Asia Pacific (Hyderabad, Mumbai, Singapore, Sydney, Tokyo), Canada (Central), Europe (Frankfurt, Ireland, London, Milan, Paris), and South America (Sao Paulo). These instances can be purchased as Savings Plans, Reserved, On-Demand, and Spot instances. To get started, visit the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, visit the M6a instances pages.
 

 

​Starting today, the general-purpose Amazon EC2 M6a instances are now available in AWS Europe (Paris) region. M6a instances are powered by third-generation AMD EPYC processors, and deliver up to 35% better price performance than comparable M5a instances. These instances offer 10% lower cost than comparable x86-based EC2 instances. With this additional region, M6a instances are available in the following AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Asia Pacific (Hyderabad, Mumbai, Singapore, Sydney, Tokyo), Canada (Central), Europe (Frankfurt, Ireland, London, Milan, Paris), and South America (Sao Paulo). These instances can be purchased as Savings Plans, Reserved, On-Demand, and Spot instances. To get started, visit the AWS Management Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, visit the M6a instances pages.    

Publicado el Deja un comentario

Amazon Data Firehose is now available in AWS Asia Pacific (Thailand) and Mexico (Central) regions

Amazon Data Firehose is now available in AWS Asia Pacific (Thailand) and Mexico (Central) regions. Amazon Data Firehose is the easiest way to load streaming data into data stores and analytics tools. You can capture, transform, and deliver streaming data into Amazon S3, Apache Iceberg Tables, Amazon S3 Tables, Amazon OpenSearch Service, Amazon Redshift, and third party analytics applications such as Splunk and Datadog, enabling real-time analytics use cases.

With Amazon Data Firehose, you don’t need to write applications or manage resources. You configure your data producers to send data to Amazon Data Firehose, and it automatically delivers the data to the destination that you specified. You can also configure Amazon Data Firehose to transform your data before delivering it. To get started, you need an AWS account. Once you have an account, you can create a delivery stream in the Amazon Data Firehose Console. To learn more, explore the Amazon Data Firehose Developer Guide.

For Amazon Data Firehose availability, refer to the AWS Region Table.
 

 

​Amazon Data Firehose is now available in AWS Asia Pacific (Thailand) and Mexico (Central) regions. Amazon Data Firehose is the easiest way to load streaming data into data stores and analytics tools. You can capture, transform, and deliver streaming data into Amazon S3, Apache Iceberg Tables, Amazon S3 Tables, Amazon OpenSearch Service, Amazon Redshift, and third party analytics applications such as Splunk and Datadog, enabling real-time analytics use cases. With Amazon Data Firehose, you don’t need to write applications or manage resources. You configure your data producers to send data to Amazon Data Firehose, and it automatically delivers the data to the destination that you specified. You can also configure Amazon Data Firehose to transform your data before delivering it. To get started, you need an AWS account. Once you have an account, you can create a delivery stream in the Amazon Data Firehose Console. To learn more, explore the Amazon Data Firehose Developer Guide. For Amazon Data Firehose availability, refer to the AWS Region Table.    

Publicado el Deja un comentario

AWS CodeBuild adds support for managed webhooks in GitHub Enterprise

AWS CodeBuild’s support for managed webhooks now extends to include GitHub Enterprise. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages ready for deployment.

Customers using GitHub Enterprise as their source provider previously had to manually create webhooks for CodeBuild to receive events. CodeBuild now integrates natively to create and manage webhooks on your behalf. Additionally, you can use CloudFormation to define your webhooks in a CodeBuild project.

This feature is available in US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), GovCloud (US-East), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), Europe (Stockholm), and South America (São Paulo).

Get started using GitHub Enterprise by following our sample project. To learn more about how to get started with CodeBuild, visit the AWS CodeBuild product page.
 

 

​AWS CodeBuild’s support for managed webhooks now extends to include GitHub Enterprise. AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages ready for deployment. Customers using GitHub Enterprise as their source provider previously had to manually create webhooks for CodeBuild to receive events. CodeBuild now integrates natively to create and manage webhooks on your behalf. Additionally, you can use CloudFormation to define your webhooks in a CodeBuild project. This feature is available in US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), GovCloud (US-East), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Milan), Europe (Paris), Europe (Stockholm), and South America (São Paulo). Get started using GitHub Enterprise by following our sample project. To learn more about how to get started with CodeBuild, visit the AWS CodeBuild product page.    

Publicado el Deja un comentario

Amazon ECS adds support for additional IAM condition keys

Amazon Elastic Container Service (Amazon ECS) today launched 8 new service-specific condition keys for Identity and Access Management (IAM). These new condition keys let you create IAM policies as well as Service Control Policies (SCPs) to better enforce your organizational policies in containerized environments.

IAM condition keys allow you to author policies that enforce access control based on API request context. With today’s release, Amazon ECS has added condition keys that allow you to enforce policies related to resource configuration (ecs:task-cpu, ecs:task:memory, and ecs:compute-compatibility), container privileges (ecs:privileged), network configuration (ecs:auto-assign-public-ip and ecs:subnet), and tag propagation (ecs:propagate-tags and ecs:enable-ecs-managed-tags) for your applications deployed on Amazon ECS. For example, you can use the new ecs:auto-assign-public-ip condition key to enforce that tasks in your ECS service are not assigned public IP addresses and the ecs:privileged condition key to prevent registration of task definitions with privileges over the underlying host.

The new IAM condition context keys for Amazon ECS are available in all AWS Regions. To see the full list of IAM condition context keys supported by ECS and learn more about using condition keys with Amazon ECS, please refer to our documentation.

 

​Amazon Elastic Container Service (Amazon ECS) today launched 8 new service-specific condition keys for Identity and Access Management (IAM). These new condition keys let you create IAM policies as well as Service Control Policies (SCPs) to better enforce your organizational policies in containerized environments. IAM condition keys allow you to author policies that enforce access control based on API request context. With today’s release, Amazon ECS has added condition keys that allow you to enforce policies related to resource configuration (ecs:task-cpu, ecs:task:memory, and ecs:compute-compatibility), container privileges (ecs:privileged), network configuration (ecs:auto-assign-public-ip and ecs:subnet), and tag propagation (ecs:propagate-tags and ecs:enable-ecs-managed-tags) for your applications deployed on Amazon ECS. For example, you can use the new ecs:auto-assign-public-ip condition key to enforce that tasks in your ECS service are not assigned public IP addresses and the ecs:privileged condition key to prevent registration of task definitions with privileges over the underlying host. The new IAM condition context keys for Amazon ECS are available in all AWS Regions. To see the full list of IAM condition context keys supported by ECS and learn more about using condition keys with Amazon ECS, please refer to our documentation.  

Publicado el Deja un comentario

Amazon RDS Data API for Aurora is now available in 10 additional AWS regions

RDS Data API for Aurora Serverless v2 and Aurora provisioned PostgreSQL-Compatible and MySQL-Compatible database clusters is now available in Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Osaka), Europe (Milan), Europe (Stockholm), Middle East (Bahrain), Middle East (UAE), and South America (São Paulo) regions. RDS Data API allows you to access these Aurora clusters via a secure HTTP endpoint and run SQL statements without the use of database drivers and without managing connections.

Data API eliminates the use of drivers and improves application scalability by automatically pooling and sharing database connections (connection pooling) rather than requiring customers to manage connections. Customers can call Data API via AWS SDK and CLI. Data API also enables access to Aurora databases via AWS AppSync GraphQL APIs. API commands supported in the Data API for Aurora Serverless v2 and Aurora provisioned are backwards compatible with Data API for Aurora Serverless v1 for easy customer application migrations.

Data API supports Aurora PostgreSQL 15.3, 14.8, 13.11 and higher versions, and Aurora MySQL 3.07 and higher versions. Customers currently using Data API for ASv1 are encouraged to migrate to ASv2 to take advantage of the new Data API. To learn more, read the documentation.
 

 

​RDS Data API for Aurora Serverless v2 and Aurora provisioned PostgreSQL-Compatible and MySQL-Compatible database clusters is now available in Africa (Cape Town), Asia Pacific (Hong Kong), Asia Pacific (Jakarta), Asia Pacific (Malaysia), Asia Pacific (Osaka), Europe (Milan), Europe (Stockholm), Middle East (Bahrain), Middle East (UAE), and South America (São Paulo) regions. RDS Data API allows you to access these Aurora clusters via a secure HTTP endpoint and run SQL statements without the use of database drivers and without managing connections. Data API eliminates the use of drivers and improves application scalability by automatically pooling and sharing database connections (connection pooling) rather than requiring customers to manage connections. Customers can call Data API via AWS SDK and CLI. Data API also enables access to Aurora databases via AWS AppSync GraphQL APIs. API commands supported in the Data API for Aurora Serverless v2 and Aurora provisioned are backwards compatible with Data API for Aurora Serverless v1 for easy customer application migrations. Data API supports Aurora PostgreSQL 15.3, 14.8, 13.11 and higher versions, and Aurora MySQL 3.07 and higher versions. Customers currently using Data API for ASv1 are encouraged to migrate to ASv2 to take advantage of the new Data API. To learn more, read the documentation.    

Publicado el Deja un comentario

Anunciamos el acceso gratuito e ilimitado a Think Deeper y Voice

febrero 26, 2025

Anunciamos el acceso gratuito e ilimitado a Think Deeper y Voice

Por: Equipo de Copilot.

Lanzamos Copilot hace dos años, enfocado en ayudar a las personas a acceder al conocimiento, obtener respuestas, reflexionar, intercambiar ideas y crear. A medida que continuamos con la construcción de su compañero de IA definitivo, estamos emocionados de comenzar a implementar capacidades aún más poderosas para todos los usuarios de Copilot con acceso gratuito e ilimitado a Voice y Think Deeper (impulsado por el modelo o1 de OpenAI). Ahora pueden mantener una conversación prolongada con Copilot mediante la voz y aprovechar los modelos de razonamiento avanzados de Think Deeper para abordar preguntas o tareas más complejas, en cualquier momento. Pruébenlo hoy.

Hemos visto mucho entusiasmo por Voice y Think Deeper y sabemos que muchos de ustedes han comenzado a llegar a los límites. Esto debería ayudar. Y si aún no han probado algunas de estas experiencias, nunca ha habido un mejor momento.

Usen Voice para practicar algunas frases sencillas en un nuevo idioma que les ayuden a navegar cuando visiten un nuevo país o conozcan a gente nueva, cuéntenle a Copilot sobre un trabajo para el cual quieran aplicar y su experiencia laboral y pídanle que simule una entrevista, u obtengan algunos consejos de cocina con manos libres mientras siguen una nueva receta paso a paso.

Think Deeper es útil para abordar temas más complejos, como hacer una gran compra, evaluar el valor futuro de una renovación del hogar o planificar un cambio de carrera. Aquí hay algunas ideas para comenzar:

  • Comparar los mejores coches eléctricos. Por lo general, priorizo el diseño y la comodidad, y quiero sentir que mi compra está «preparada para el futuro». Hacer un sistema de puntuación novedoso para ayudarme con mi evaluación.
  • Tengo $15K para usar en la renovación de una casa. Mis opciones son una isla de cocina, un baño renovado o reemplazar el techo. ¿Qué aumentaría más el valor de mi casa en los próximos 3 años?
  • Vivo en un vecindario que tiene cortes de energía cada vez que hay vientos fuertes. ¿Debería comprar un generador? ¿Cuáles son los pros y los contras, las cosas que debo considerar y el impacto en mi presupuesto y conveniencia?

Trabajamos de manera ardua para ampliar el acceso ilimitado a funciones avanzadas a tantas personas como sea posible, lo más rápido posible, comenzando hoy con Voice y Think Deeper. Vale la pena señalar que pueden experimentar retrasos o interrupciones durante períodos de alta demanda o si detectamos problemas de seguridad, uso indebido u otras violaciones de los Términos del Copiloto.

Los usuarios de Copilot Pro mantendrán el acceso preferencial a nuestros últimos modelos durante el uso máximo, el acceso anticipado a las funciones experimentales de IA (más sobre eso próximamente) y el uso adicional de Copilot en aplicaciones seleccionadas de Microsoft 365 como Word, Excel y PowerPoint.

¡Gracias a todos los que usan Copilot y comparten sus comentarios! Sus comentarios sobre lo que funciona y lo que debe mejorarse nos ayuda a mejorar Copilot y a hacer más por todos. Nos encanta saber de ustedes, así que no dejen de enviarnos sus comentarios.

The post Anunciamos el acceso gratuito e ilimitado a Think Deeper y Voice appeared first on Source LATAM.

 

​The post Anunciamos el acceso gratuito e ilimitado a Think Deeper y Voice appeared first on Source LATAM.