ACUVA

Your Accurate Search for New Technology

Amazon Connect launches auto-accept for tasks, chats, and emails

By

Amazon Connect now supports the ability to configure agents with auto-accept settings for chat, tasks, emails, and callbacks. When auto-accept is enabled, incoming contacts are automatically connected to available agents instead of waiting on the agent to manually accept or reject each contact, ensuring that customers receive timely assistance. Previously, these settings were available only for inbound voice contacts. You can now enable these settings at the channel level for each agent to further optimize how agents spend their time. For example, you could choose to enable auto-accept for tasks while keeping auto-accept disabled for voice calls to ensure that the agent is connected to a voice call only once they indicate they are ready.

Amazon Aurora DSQL is now available in additional AWS Regions

By

Amazon Aurora DSQL is now available with single-Region clusters in Asia Pacific (Melbourne), Asia Pacific (Sydney), Canada (Central), and Canada West (Calgary). Aurora DSQL is the fastest serverless, distributed SQL database that enables you to build always available applications with virtually unlimited scalability, the highest availability, and zero infrastructure management. It is designed to make scaling and resilience effortless for your applications and offers the fastest distributed SQL reads and writes.

With this launch, Aurora DSQL is available in the following AWS Regions : US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), Canada West (Calgary), Asia Pacific (Melbourne), Asia Pacific (Sydney), Asia Pacific (Osaka), Asia Pacific (Tokyo), Asia Pacific (Seoul), Europe (Ireland), Europe (London), Europe (Frankfurt), and Europe (Paris).

Get started with Aurora DSQL for free with the AWS Free Tier . To learn more, visit the Aurora DSQL webpage and documentation .

AWS Payment Cryptography Achieves Cartes Bancaires Approval

By

Today, AWS Payment Cryptography has become one of the first cloud-based payment cryptography services to obtain approval from Groupement des Cartes Bancaires (CB ), France’s national card payment network. This CB approval, combined with existing compliance credentials, enables customers to run payment workloads in AWS while helping customers maintain CB compliance.

Organizations such as acquirers, payment facilitators, networks, switches, processors, and issuing banks that are moving workloads to the cloud can rely on AWS Payment Cryptography’s CB approval as part of their compliance frameworks. Organizations processing card payments typically require Hardware Security Modules (HSM) to perform cryptography in a compliant manner. AWS Payment Cryptography provides equivalent functionality in an elastic, scalable service, eliminating the operational burden of procuring and manage standalone payment HSMs. Customers can leverage the service’s shared responsibility model with PCI PIN, PCI P2PE, PCI 3DS, PCI DSS, SOC-2, CSA STAR and ISO27001 certifications as well as the additional CB approval.

AWS Payment Cryptography is available in the following AWS Regions: Canada (Montreal), US East (Ohio, N. Virginia), US West (Oregon), Europe (Ireland, Frankfurt, London, Paris), Africa (Cape Town) and Asia Pacific (Singapore, Tokyo, Osaka, Mumbai, Hyderabad, Sydney).

To start using the service, please download the latest AWS CLI/SDK and see the AWS Payment Cryptography user guide for more information including further compliance details.

Amazon Connect launches after contact work timeout configuration for tasks, chats, and emails

By

Amazon Connect now supports the ability to configure agents with after contact work timeout settings for chat, tasks, emails, and callbacks. After contact work timeouts improve agent efficiency by time-boxing the amount of time each agent can spend doing after contact work for a contact, before being automatically set back to a ready state so they can be offered another contact. You can now enable these settings at the channel level for each agent to further optimize how agents spend their time. For example, you could choose to enable a shorter ACW timeout for emails while maintaining a longer ACW timeout for voice contacts to give agents a cool-down period between phone calls to prepare for the next customer interaction.

Scroll Up