Amazon Connect now supports multi-party chat, allowing up to 4 additional agents to join an ongoing chat conversation, making it easier to collaborate and resolve customer issues quickly. For example, agents can add a supervisor or subject matter experts to join the chat, ensuring customers receive accurate and timely support.

Multi-party chat can be enabled within the AWS Console. Once enabled, agents can simply use a Quick Connect to invite additional agents to an ongoing chat. This feature is available in all commercial AWS regions where Amazon Connect is available. To learn more and get started, please refer to the help documentation or visit the Amazon Connect website.
 

​Amazon Connect now supports multi-party chat, allowing up to 4 additional agents to join an ongoing chat conversation, making it easier to collaborate and resolve customer issues quickly. For example, agents can add a supervisor or subject matter experts to join the chat, ensuring customers receive accurate and timely support. Multi-party chat can be enabled within the AWS Console. Once enabled, agents can simply use a Quick Connect to invite additional agents to an ongoing chat. This feature is available in all commercial AWS regions where Amazon Connect is available. To learn more and get started, please refer to the help documentation or visit the Amazon Connect website.    

AWS ParallelCluster 3.12 is now generally available. This release makes it possible to include Lustre and NVIDIA software components in ParallelCluster custom images. Now, you can include ParallelCluster’s recommended Nvidia drivers and CUDA libraries in custom images. This update also makes the Lustre client optional to account for scenarios where you may opt for alternative storage solutions. To enable these optional software components when creating custom images, configure the NvidiaSoftware and the LustreClient parameters in the build image configuration file when using the build-image command.

For more details on the release, review the AWS ParallelCluster 3.12.0 release notes.

AWS ParallelCluster is a fully-supported and maintained open-source cluster management tool that enables R&D customers and their IT administrators to operate high-performance computing (HPC) clusters on AWS. AWS ParallelCluster is designed to automatically and securely provision cloud resources into elastically-scaling HPC clusters capable of running scientific, engineering, and machine-learning (ML/AI) workloads at scale on AWS.

AWS ParallelCluster is available at no additional charge in the AWS Regions listed here, and you pay only for the AWS resources needed to run your applications. To learn more about launching HPC clusters on AWS, visit the AWS ParallelCluster User Guide. To start using ParallelCluster, see the installation instructions for ParallelCluster UI and CLI.

​AWS ParallelCluster 3.12 is now generally available. This release makes it possible to include Lustre and NVIDIA software components in ParallelCluster custom images. Now, you can include ParallelCluster’s recommended Nvidia drivers and CUDA libraries in custom images. This update also makes the Lustre client optional to account for scenarios where you may opt for alternative storage solutions. To enable these optional software components when creating custom images, configure the NvidiaSoftware and the LustreClient parameters in the build image configuration file when using the build-image command. For more details on the release, review the AWS ParallelCluster 3.12.0 release notes. AWS ParallelCluster is a fully-supported and maintained open-source cluster management tool that enables R&D customers and their IT administrators to operate high-performance computing (HPC) clusters on AWS. AWS ParallelCluster is designed to automatically and securely provision cloud resources into elastically-scaling HPC clusters capable of running scientific, engineering, and machine-learning (ML/AI) workloads at scale on AWS. AWS ParallelCluster is available at no additional charge in the AWS Regions listed here, and you pay only for the AWS resources needed to run your applications. To learn more about launching HPC clusters on AWS, visit the AWS ParallelCluster User Guide. To start using ParallelCluster, see the installation instructions for ParallelCluster UI and CLI.  

Amazon Managed Streaming for Apache Kafka (Amazon MSK) is now available in Asia Pacific (Malaysia) Region. Amazon MSK is a fully managed service for Apache Kafka and Kafka Connect that makes it easier for you to build and run applications that use Apache Kafka as a data store. Amazon MSK is fully compatible with Apache Kafka, which enables you to more quickly migrate your existing Apache Kafka workloads to Amazon MSK with confidence or build new ones from scratch. With Amazon MSK, you spend more time building innovative streaming applications and less time managing Kafka clusters.

Visit the AWS Regions page for all the regions where Amazon MSK is available. To get started, see the Amazon MSK Developer Guide.
 

​Amazon Managed Streaming for Apache Kafka (Amazon MSK) is now available in Asia Pacific (Malaysia) Region. Amazon MSK is a fully managed service for Apache Kafka and Kafka Connect that makes it easier for you to build and run applications that use Apache Kafka as a data store. Amazon MSK is fully compatible with Apache Kafka, which enables you to more quickly migrate your existing Apache Kafka workloads to Amazon MSK with confidence or build new ones from scratch. With Amazon MSK, you spend more time building innovative streaming applications and less time managing Kafka clusters. Visit the AWS Regions page for all the regions where Amazon MSK is available. To get started, see the Amazon MSK Developer Guide.    

Today, AWS IoT Device Management announces the general availability of a high-throughput connectivity status query API, allowing developers to query the latest connectivity state of IoT devices, for monitoring and management purposes. AWS IoT Device Management is a fully managed cloud service that helps you register, organize, monitor, and remotely manage Internet of Things (IoT) devices at scale.

Device connectivity status is crucial for monitoring device failures and executing remote commands. The new connectivity status API which will be available to AWS IoT Device Management Fleet Indexing customers, provides a high-throughput solution (350+ requests per second) for customers to ascertain device connectivity to the cloud. It also retrieves most recent connect or disconnect event timestamp along with disconnect reason, aiding troubleshooting activities. AWS IoT Device Management’s Fleet Indexing feature enables customers to search, group devices based on device metadata, state stored across thing registry, IoT device shadow and connectivity data sources. While existing search queries are optimized for fleet-level querying, this API is optimized for single-device connectivity queries and offers lower latency to reflect connectivity state changes. With connectivity status queries, developers can now easily support targeted device monitoring and management capabilities in their applications. For example, in automotive applications, developers can first query vehicle connectivity status using this API prior to issuing remote commands to the vehicle.

Connectivity status is available to AWS IoT Device Management Fleet indexing customers and in all AWS regions where AWS IoT Device Management is available. For more information please refer to the developer guide and API documentation.

​Today, AWS IoT Device Management announces the general availability of a high-throughput connectivity status query API, allowing developers to query the latest connectivity state of IoT devices, for monitoring and management purposes. AWS IoT Device Management is a fully managed cloud service that helps you register, organize, monitor, and remotely manage Internet of Things (IoT) devices at scale. Device connectivity status is crucial for monitoring device failures and executing remote commands. The new connectivity status API which will be available to AWS IoT Device Management Fleet Indexing customers, provides a high-throughput solution (350+ requests per second) for customers to ascertain device connectivity to the cloud. It also retrieves most recent connect or disconnect event timestamp along with disconnect reason, aiding troubleshooting activities. AWS IoT Device Management’s Fleet Indexing feature enables customers to search, group devices based on device metadata, state stored across thing registry, IoT device shadow and connectivity data sources. While existing search queries are optimized for fleet-level querying, this API is optimized for single-device connectivity queries and offers lower latency to reflect connectivity state changes. With connectivity status queries, developers can now easily support targeted device monitoring and management capabilities in their applications. For example, in automotive applications, developers can first query vehicle connectivity status using this API prior to issuing remote commands to the vehicle. Connectivity status is available to AWS IoT Device Management Fleet indexing customers and in all AWS regions where AWS IoT Device Management is available. For more information please refer to the developer guide and API documentation.  

Amazon RDS Proxy announces caching_sha2_password authentication plugin support for client to proxy connections on MySQL on Aurora and RDS.

Customers need to use plugins to perform authentication between databases and clients while using RDS Proxy. Starting with MySQL 8.4, community MySQL uses caching_sha2_password plugin as the default, which is more secure than the previous default plugins. To align with this, starting today, caching_sha2_password will also be the default authentication plugin for new connection creates with RDS Proxy, if a value is not specified.

RDS Proxy is a fully managed and a highly available database proxy for Amazon Aurora and RDS databases. RDS Proxy helps improve application scalability, resiliency, and security. You can setup your RDS Proxy to use caching_sha2_password authentication on all available RDS for MySQL and Aurora MySQL versions with just a few clicks on the Amazon RDS Management Console or using the AWS SDK or CLI. Support for caching_sha2_password with RDS Proxy is available in all AWS Commercial Regions. For more information, including instructions on getting started, read the Amazon RDS Proxy documentation.
 

​Amazon RDS Proxy announces caching_sha2_password authentication plugin support for client to proxy connections on MySQL on Aurora and RDS. Customers need to use plugins to perform authentication between databases and clients while using RDS Proxy. Starting with MySQL 8.4, community MySQL uses caching_sha2_password plugin as the default, which is more secure than the previous default plugins. To align with this, starting today, caching_sha2_password will also be the default authentication plugin for new connection creates with RDS Proxy, if a value is not specified. RDS Proxy is a fully managed and a highly available database proxy for Amazon Aurora and RDS databases. RDS Proxy helps improve application scalability, resiliency, and security. You can setup your RDS Proxy to use caching_sha2_password authentication on all available RDS for MySQL and Aurora MySQL versions with just a few clicks on the Amazon RDS Management Console or using the AWS SDK or CLI. Support for caching_sha2_password with RDS Proxy is available in all AWS Commercial Regions. For more information, including instructions on getting started, read the Amazon RDS Proxy documentation.    

AWS Backup introduces dual stack support for the AWS Backup API endpoint in IPv6, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. Dual stack support is also available when the AWS Backup API endpoint is privately accessed from your Amazon Virtual Private Cloud (VPC) using AWS PrivateLink. Dual stack endpoints are made available on a new AWS DNS domain name. The existing AWS Backup API endpoints are maintained for backwards compatibility reasons.

With simultaneous support for both IPv4 and IPv6 clients on AWS Backup endpoints, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. This enables you to meet IPv6 compliance requirements and removes the need for expensive networking equipment to handle the address translation between IPv4 and IPv6.

AWS Backup support for dual-stack environments is available in all regions where AWS Backup support for VPC endpoints is available. There is no additional charge when you connect to AWS Backup endpoints using Internet Protocol Version 6 (IPv6) clients. To learn more, see AWS Backup documentation.

​AWS Backup introduces dual stack support for the AWS Backup API endpoint in IPv6, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. Dual stack support is also available when the AWS Backup API endpoint is privately accessed from your Amazon Virtual Private Cloud (VPC) using AWS PrivateLink. Dual stack endpoints are made available on a new AWS DNS domain name. The existing AWS Backup API endpoints are maintained for backwards compatibility reasons. With simultaneous support for both IPv4 and IPv6 clients on AWS Backup endpoints, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. This enables you to meet IPv6 compliance requirements and removes the need for expensive networking equipment to handle the address translation between IPv4 and IPv6. AWS Backup support for dual-stack environments is available in all regions where AWS Backup support for VPC endpoints is available. There is no additional charge when you connect to AWS Backup endpoints using Internet Protocol Version 6 (IPv6) clients. To learn more, see AWS Backup documentation.  

Amazon WorkSpaces Thin Client is now available to purchase in India on Amazon Business.

Amazon WorkSpaces Thin Client is a low-cost end-user device that helps organizations reduce overall virtual desktop costs, strengthen security posture, and simplify end-user deployment. End users can set up WorkSpaces Thin Client in minutes using an on-device guided deployment experience to connect their network and peripherals and log in to their virtual desktops including Amazon WorkSpaces, Amazon WorkSpaces Secure Browser, and Amazon AppStream 2.0. WorkSpaces Thin Client helps IT organizations improve security by removing the ability to upload or download files or applications and by establishing device trust through a secure chip. With the WorkSpaces Thin Client service, IT administrators have a complete view of their inventory and can remotely reset, patch, and control access to the thin client.

The WorkSpaces Thin Client service is available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Canada (Central), Europe (Frankfurt), Europe (Ireland), and Europe (London). Devices are now available to purchase in the US, UK, France, Germany, Italy, Spain, and India on Amazon Business.

Visit the WorkSpaces Thin Client page and Amazon Business to learn more.

​Amazon WorkSpaces Thin Client is now available to purchase in India on Amazon Business. Amazon WorkSpaces Thin Client is a low-cost end-user device that helps organizations reduce overall virtual desktop costs, strengthen security posture, and simplify end-user deployment. End users can set up WorkSpaces Thin Client in minutes using an on-device guided deployment experience to connect their network and peripherals and log in to their virtual desktops including Amazon WorkSpaces, Amazon WorkSpaces Secure Browser, and Amazon AppStream 2.0. WorkSpaces Thin Client helps IT organizations improve security by removing the ability to upload or download files or applications and by establishing device trust through a secure chip. With the WorkSpaces Thin Client service, IT administrators have a complete view of their inventory and can remotely reset, patch, and control access to the thin client. The WorkSpaces Thin Client service is available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Mumbai), Canada (Central), Europe (Frankfurt), Europe (Ireland), and Europe (London). Devices are now available to purchase in the US, UK, France, Germany, Italy, Spain, and India on Amazon Business. Visit the WorkSpaces Thin Client page and Amazon Business to learn more.  

Amazon DocumentDB (with MongoDB Compatibility) introduces NVMe-backed R6gd Instances, offering up to 7x faster query performance for applications with large datasets exceeding regular instance memory. These instances can expand the data caching capacity by up to 7 times compared to a regular instance.

NVMe-backed R6gd Instances leverage the local non-volatile memory express (NVMe)-based SSD storage available on r6gd instances to store ephemeral data, reducing network-based storage access, and improving read latency and throughput. Database pages evicted from the in-memory buffer cache are cached on local NVMe storage. Additionally, temporary space is hosted on local SSD instead of network storage, reducing the latency of queries involving sorts by up to 2x and accelerating resource-intensive operations like index builds.

Customers can get started with NVMe-backed R6gd Instances through the AWS Management Console, CLI, and SDK by modifying their Amazon DocumentDB database cluster or creating a new one using R6gd instances. NVMe-backed R6gd Instances are available for Amazon DocumentDB V5.0 on both Standard and IO-Optimized cluster storage configurations. For more information visit our pricing page and documentation.

​Amazon DocumentDB (with MongoDB Compatibility) introduces NVMe-backed R6gd Instances, offering up to 7x faster query performance for applications with large datasets exceeding regular instance memory. These instances can expand the data caching capacity by up to 7 times compared to a regular instance. NVMe-backed R6gd Instances leverage the local non-volatile memory express (NVMe)-based SSD storage available on r6gd instances to store ephemeral data, reducing network-based storage access, and improving read latency and throughput. Database pages evicted from the in-memory buffer cache are cached on local NVMe storage. Additionally, temporary space is hosted on local SSD instead of network storage, reducing the latency of queries involving sorts by up to 2x and accelerating resource-intensive operations like index builds. Customers can get started with NVMe-backed R6gd Instances through the AWS Management Console, CLI, and SDK by modifying their Amazon DocumentDB database cluster or creating a new one using R6gd instances. NVMe-backed R6gd Instances are available for Amazon DocumentDB V5.0 on both Standard and IO-Optimized cluster storage configurations. For more information visit our pricing page and documentation.  

AWS Mainframe Modernization introduces dual stack support for the managed runtime environments, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients.

The urgency to transition to Internet Protocol version 6 (IPv6) is driven by the continued growth of internet, which is exhausting available Internet Protocol version 4 (IPv4) addresses. With simultaneous support for both IPv4 and IPv6 clients on AWS Mainframe Modernization runtime environments, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. You can also continue to use IPv4 connections if you do not yet utilize IPv6.

There is no additional charge when you connect to AWS Mainframe Modernization using Internet Protocol Version 6 (IPv6) clients. Support for IPv6 is available in any AWS Region where AWS Mainframe Modernization managed runtime is already deployed. To learn more, please visit AWS Mainframe Modernization product and documentation pages.

​AWS Mainframe Modernization introduces dual stack support for the managed runtime environments, enabling you to connect using Internet Protocol Version 6 (IPv6), Internet Protocol Version 4 (IPv4), or dual stack clients. The urgency to transition to Internet Protocol version 6 (IPv6) is driven by the continued growth of internet, which is exhausting available Internet Protocol version 4 (IPv4) addresses. With simultaneous support for both IPv4 and IPv6 clients on AWS Mainframe Modernization runtime environments, you are able to gradually transition from IPv4 to IPv6 based systems and applications, without needing to switch all over at once. You can also continue to use IPv4 connections if you do not yet utilize IPv6. There is no additional charge when you connect to AWS Mainframe Modernization using Internet Protocol Version 6 (IPv6) clients. Support for IPv6 is available in any AWS Region where AWS Mainframe Modernization managed runtime is already deployed. To learn more, please visit AWS Mainframe Modernization product and documentation pages.  

The post Anunciamos SPARROW: una innovadora herramienta de IA para medir y proteger la biodiversidad de la Tierra en los lugares más remotos appeared first on Source LATAM.

​The post Anunciamos SPARROW: una innovadora herramienta de IA para medir y proteger la biodiversidad de la Tierra en los lugares más remotos appeared first on Source LATAM.