Salesforce Contact Center with Amazon Connect, now generally available, is a groundbreaking offering that integrates native digital and voice capabilities into Salesforce Service Cloud, delivering a unified and streamlined experience for agents. Salesforce users can now unify and route voice, chat, email, and case management across Amazon Connect and Service Cloud capabilities, streamlining operational efficiency and enhancing customer service interactions.

With Salesforce Contact Center with Amazon Connect, companies can now seamlessly integrate their Salesforce CRM data and agent experience with Amazon Connect’s leading voice, digital channels, and routing capabilities. Salesforce users can innovate with personalized and responsive service across every touchpoint. Customers receive personalized, AI-powered self-service experiences across Amazon Connect voice and chat, quickly solving issues. For more complex inquiries, the seamless transition from self-service to agent-assistance connects customers to the right agent, who has a unified view of the customer’s data, issue, and interaction history in Salesforce Service Cloud. Integrated data and APIs empower agents with Amazon Connect Contact Lens real-time voice transcripts and supervisors with call monitoring in Salesforce Service Cloud. Salesforce admins can quickly deploy and configure an integrated contact center solution in minutes with Amazon Connect voice, digital channels and routing of Salesforce cases.

This feature is available in all AWS Regions where Amazon Connect is available. To learn more and get started, see the Salesforce Contact Center with Amazon Connect documentation. To learn more about Amazon Connect, see Amazon Connect.

 

​Salesforce Contact Center with Amazon Connect, now generally available, is a groundbreaking offering that integrates native digital and voice capabilities into Salesforce Service Cloud, delivering a unified and streamlined experience for agents. Salesforce users can now unify and route voice, chat, email, and case management across Amazon Connect and Service Cloud capabilities, streamlining operational efficiency and enhancing customer service interactions. With Salesforce Contact Center with Amazon Connect, companies can now seamlessly integrate their Salesforce CRM data and agent experience with Amazon Connect’s leading voice, digital channels, and routing capabilities. Salesforce users can innovate with personalized and responsive service across every touchpoint. Customers receive personalized, AI-powered self-service experiences across Amazon Connect voice and chat, quickly solving issues. For more complex inquiries, the seamless transition from self-service to agent-assistance connects customers to the right agent, who has a unified view of the customer’s data, issue, and interaction history in Salesforce Service Cloud. Integrated data and APIs empower agents with Amazon Connect Contact Lens real-time voice transcripts and supervisors with call monitoring in Salesforce Service Cloud. Salesforce admins can quickly deploy and configure an integrated contact center solution in minutes with Amazon Connect voice, digital channels and routing of Salesforce cases. This feature is available in all AWS Regions where Amazon Connect is available. To learn more and get started, see the Salesforce Contact Center with Amazon Connect documentation. To learn more about Amazon Connect, see Amazon Connect.  

Amazon Redshift Serverless is now available on two different release cycles – Current Track and Trailing Track. With the Current Track you will get the most up-to-date certified release version with the latest features, security updates, and performance enhancements. With the Trailing Track you will be on the previous certified release. With the Trailing Track feature, you now have the option to run a subset of Amazon Redshift Serverless workgroups in the Amazon Redshift Serverless Trailing Track to allow for a few weeks of integration validation in your environment before adopting the release across all your workgroups.

Each Amazon Redshift Serverless release undergoes thorough testing by our QA and security teams. By default, all Amazon Redshift Serverless workgroups are created in the Current Track to take advantage of the most up-to-date certified release. Amazon Redshift Serverless Trailing track provides you additional diligence and time needed for testing and development environments to evaluate the Current Track, before adopting the Current Track for your mission-critical workloads in production. The Trailing track ensures maximum stability, making it ideal for mission-critical workloads in production environments. With a few clicks in the Amazon Redshift console, you can choose the Current Track or Trailing Track.

Amazon Redshift Serverless Current and Trailing Tracks support is available in all commercial AWS regions and the AWS GovCloud (US) Regions where Amazon Redshift Serverless is available.

Refer to this documentation to learn more about the Current and Trailing Tracks in Amazon Redshift Serverless.

 

​Amazon Redshift Serverless is now available on two different release cycles – Current Track and Trailing Track. With the Current Track you will get the most up-to-date certified release version with the latest features, security updates, and performance enhancements. With the Trailing Track you will be on the previous certified release. With the Trailing Track feature, you now have the option to run a subset of Amazon Redshift Serverless workgroups in the Amazon Redshift Serverless Trailing Track to allow for a few weeks of integration validation in your environment before adopting the release across all your workgroups. Each Amazon Redshift Serverless release undergoes thorough testing by our QA and security teams. By default, all Amazon Redshift Serverless workgroups are created in the Current Track to take advantage of the most up-to-date certified release. Amazon Redshift Serverless Trailing track provides you additional diligence and time needed for testing and development environments to evaluate the Current Track, before adopting the Current Track for your mission-critical workloads in production. The Trailing track ensures maximum stability, making it ideal for mission-critical workloads in production environments. With a few clicks in the Amazon Redshift console, you can choose the Current Track or Trailing Track. Amazon Redshift Serverless Current and Trailing Tracks support is available in all commercial AWS regions and the AWS GovCloud (US) Regions where Amazon Redshift Serverless is available.
Refer to this documentation to learn more about the Current and Trailing Tracks in Amazon Redshift Serverless.  

Today, AWS announced several upgrades to the Amazon Q Business browser extension to enhance its utility and improve user efficiency when performing browser-based tasks. The upgrades include company knowledge access, in-line PDF support, the ability to delete previous attachments from conversation context, image file attachment support, and an expanded prompt context window.

With the new upgrades, browser extension users are now able to access questions from a wide range of data sources that include not only their open web pages and attached documents, but also their company’s indexed data, PDFs they open in their browser, and multimodal file attachments such as charts and images. Users now also gain finer control over their prompt context with the ability to remove previous web pages or attachments that are no longer relevant from their conversation context.

With the expanded context window, users can incorporate larger web pages and files alongside more detailed prompts to enhance the helpfulness of responses they receive from Amazon Q. Furthermore, the extension provides a convenient link to continue their work in the Amazon Q Business web experience, where users can access powerful features like Actions and Q Apps.

These new features are available on the Amazon Q Business browser extension in all regions where Amazon Q Business is available.

To learn more, visit the Amazon Q Business product page or review the documentation for detailed setup instructions and feature descriptions.

 

​Today, AWS announced several upgrades to the Amazon Q Business browser extension to enhance its utility and improve user efficiency when performing browser-based tasks. The upgrades include company knowledge access, in-line PDF support, the ability to delete previous attachments from conversation context, image file attachment support, and an expanded prompt context window. With the new upgrades, browser extension users are now able to access questions from a wide range of data sources that include not only their open web pages and attached documents, but also their company’s indexed data, PDFs they open in their browser, and multimodal file attachments such as charts and images. Users now also gain finer control over their prompt context with the ability to remove previous web pages or attachments that are no longer relevant from their conversation context. With the expanded context window, users can incorporate larger web pages and files alongside more detailed prompts to enhance the helpfulness of responses they receive from Amazon Q. Furthermore, the extension provides a convenient link to continue their work in the Amazon Q Business web experience, where users can access powerful features like Actions and Q Apps. These new features are available on the Amazon Q Business browser extension in all regions where Amazon Q Business is available. To learn more, visit the Amazon Q Business product page or review the documentation for detailed setup instructions and feature descriptions.  

Amazon Connect Tasks can now be configured to expire up to 90 days from creation, with a default of 7 days. For example, tasks like auto repairs can take weeks to complete or that have longer follow-up times can stay active for up to 90 days before being escalated to a supervisor, while more time-critical tasks like rescheduling a hotel reservation can be distributed and tracked to completion within minutes. Amazon Connect Tasks empowers you to prioritize, assign, and track all contact center agent tasks to completion, improving agent productivity and ensuring customer issues are quickly resolved.

This feature is supported in all AWS regions where Amazon Connect Tasks is offered. To learn more, see our documentation. To learn more about Amazon Connect, the easy-to-use cloud contact center, visit the Amazon Connect website.

 

​Amazon Connect Tasks can now be configured to expire up to 90 days from creation, with a default of 7 days. For example, tasks like auto repairs can take weeks to complete or that have longer follow-up times can stay active for up to 90 days before being escalated to a supervisor, while more time-critical tasks like rescheduling a hotel reservation can be distributed and tracked to completion within minutes. Amazon Connect Tasks empowers you to prioritize, assign, and track all contact center agent tasks to completion, improving agent productivity and ensuring customer issues are quickly resolved. This feature is supported in all AWS regions where Amazon Connect Tasks is offered. To learn more, see our documentation. To learn more about Amazon Connect, the easy-to-use cloud contact center, visit the Amazon Connect website.  

AWS announces Amazon Redshift Query Editor V2 now supports increased maximum result set and export size to 100MB of your query result sets with no row limit in AWS GovCloud (US) Regions. Prior to this limit of your query result sets was* 5MB or 100,000 rows. This enhancement provides greater flexibility for you and your team to work with large datasets, enabling you to generate, analyze, and export more comprehensive data without previous constraints.

If you work with large datasets, such as security logs, gaming data, and other big data workloads, that require in-depth analysis, the previous 5MB or 100,000-row limit on result sets and exports often fell short of your needs, forcing you to piece together insights from multiple queries and downloads. With the new 100MB result set size and export capabilities in Amazon Redshift Query Editor, you can now generate a single, more complete view of your data, export it directly as a CSV or JSON file, and conduct richer analysis to drive better-informed business decisions.

The increased 100MB result set and export size capabilities for Amazon Redshift Query Editor V2 are available in AWS GovCloud (US) Regions. For more information about the AWS Regions where Redshift is available, please refer to the AWS Regions table.

To learn more, see the Amazon Redshift documentation.
 

 

​AWS announces Amazon Redshift Query Editor V2 now supports increased maximum result set and export size to 100MB of your query result sets with no row limit in AWS GovCloud (US) Regions. Prior to this limit of your query result sets was* 5MB or 100,000 rows. This enhancement provides greater flexibility for you and your team to work with large datasets, enabling you to generate, analyze, and export more comprehensive data without previous constraints. If you work with large datasets, such as security logs, gaming data, and other big data workloads, that require in-depth analysis, the previous 5MB or 100,000-row limit on result sets and exports often fell short of your needs, forcing you to piece together insights from multiple queries and downloads. With the new 100MB result set size and export capabilities in Amazon Redshift Query Editor, you can now generate a single, more complete view of your data, export it directly as a CSV or JSON file, and conduct richer analysis to drive better-informed business decisions. The increased 100MB result set and export size capabilities for Amazon Redshift Query Editor V2 are available in AWS GovCloud (US) Regions. For more information about the AWS Regions where Redshift is available, please refer to the AWS Regions table. To learn more, see the Amazon Redshift documentation.    

Amazon OpenSearch Service now offers support for managed VPC endpoints (powered by AWS PrivateLink) in two additional regions – AWS GovCloud (US-East), and AWS GovCloud (US-West). Managed VPC endpoints allow to connect to your Amazon OpenSearch Service VPC-enabled domain in a Virtual Private Cloud (VPC). With an Amazon OpenSearch Service managed endpoint, you can now privately access your OpenSearch Service domain within your VPC from your client applications in other VPCs, within the same or across AWS accounts, without using public IPs or requiring traffic to traverse the Internet.

With this release, OpenSearch Service allows you to create an endpoint to an OpenSearch Service domain from another VPC in the same account or in another AWS account. You can either use the OpenSearch Service console or OpenSearch Service APIs to create an OpenSearch Service managed VPC endpoint.

Amazon OpenSearch Service managed VPC endpoints are powered by AWS PrivateLink. If you use OpenSearch Service managed VPC endpoints to access your OpenSearch Service domain from your client applications in another VPC, you will incur standard AWS data transfer charges and the associated cost for the AWS PrivateLink interface endpoint.

Please refer to the AWS Region Table for more information about OpenSearch Service availability. For more information, including instructions on getting started with setting up cross-VPC connectivity, please refer the OpenSearch Service documentation.

 

​Amazon OpenSearch Service now offers support for managed VPC endpoints (powered by AWS PrivateLink) in two additional regions – AWS GovCloud (US-East), and AWS GovCloud (US-West). Managed VPC endpoints allow to connect to your Amazon OpenSearch Service VPC-enabled domain in a Virtual Private Cloud (VPC). With an Amazon OpenSearch Service managed endpoint, you can now privately access your OpenSearch Service domain within your VPC from your client applications in other VPCs, within the same or across AWS accounts, without using public IPs or requiring traffic to traverse the Internet. With this release, OpenSearch Service allows you to create an endpoint to an OpenSearch Service domain from another VPC in the same account or in another AWS account. You can either use the OpenSearch Service console or OpenSearch Service APIs to create an OpenSearch Service managed VPC endpoint. Amazon OpenSearch Service managed VPC endpoints are powered by AWS PrivateLink. If you use OpenSearch Service managed VPC endpoints to access your OpenSearch Service domain from your client applications in another VPC, you will incur standard AWS data transfer charges and the associated cost for the AWS PrivateLink interface endpoint. Please refer to the AWS Region Table for more information about OpenSearch Service availability. For more information, including instructions on getting started with setting up cross-VPC connectivity, please refer the OpenSearch Service documentation.  

AWS Verified Access is a FedRAMP High authorized service in the AWS GovCloud Regions and a FedRAMP Moderate authorized service in the AWS US East and US West commercial regions. Federal agencies, public sector organizations, and other enterprises with FedRAMP compliance requirements can now leverage AWS Verified Access to enable secure VPN-less access to corporate HTTP, non-HTTP applications, and infrastructure resources. Built based on AWS Zero Trust principles, you can use Verified Access to implement a work-from-anywhere model with added security and scalability.

AWS Verified Access allows admins to define fine-grained access policies based upon a user’s identity and device posture. It evaluates access for each and every connection request and continuously monitors active connections, terminating connections when security requirements specified in the access policies aren’t met. For example, you can centrally define access policies granting Finance applications access only to authenticated users of the Finance group using compliant and managed devices. Further, you can also use Verified Access to enable access to non-HTTP(S) applications and resources such as databases, and SAP and git-repositories running on EC2 instances. Verified Access simplifies your security operations by allowing you to centrally create, group, and manage access policies for all applications and resources with similar security requirements from a single interface.

To learn more about AWS Verified Access, visit the product page.

 

​AWS Verified Access is a FedRAMP High authorized service in the AWS GovCloud Regions and a FedRAMP Moderate authorized service in the AWS US East and US West commercial regions. Federal agencies, public sector organizations, and other enterprises with FedRAMP compliance requirements can now leverage AWS Verified Access to enable secure VPN-less access to corporate HTTP, non-HTTP applications, and infrastructure resources. Built based on AWS Zero Trust principles, you can use Verified Access to implement a work-from-anywhere model with added security and scalability. AWS Verified Access allows admins to define fine-grained access policies based upon a user’s identity and device posture. It evaluates access for each and every connection request and continuously monitors active connections, terminating connections when security requirements specified in the access policies aren’t met. For example, you can centrally define access policies granting Finance applications access only to authenticated users of the Finance group using compliant and managed devices. Further, you can also use Verified Access to enable access to non-HTTP(S) applications and resources such as databases, and SAP and git-repositories running on EC2 instances. Verified Access simplifies your security operations by allowing you to centrally create, group, and manage access policies for all applications and resources with similar security requirements from a single interface. To learn more about AWS Verified Access, visit the product page.  

AWS Verified Access is a FedRAMP High authorized service in the AWS GovCloud Regions and a FedRAMP Moderate authorized service in the AWS US East and US West commercial regions. Federal agencies, public sector organizations, and other enterprises with FedRAMP compliance requirements can now leverage AWS Verified Access to enable secure VPN-less access to corporate HTTP, non-HTTP applications, and infrastructure resources. Built based on AWS Zero Trust principles, you can use Verified Access to implement a work-from-anywhere model with added security and scalability.

AWS Verified Access allows admins to define fine-grained access policies based upon a user’s identity and device posture. It evaluates access for each and every connection request and continuously monitors active connections, terminating connections when security requirements specified in the access policies aren’t met. For example, you can centrally define access policies granting Finance applications access only to authenticated users of the Finance group using compliant and managed devices. Further, you can also use Verified Access to enable access to non-HTTP(S) applications and resources such as databases, and SAP and git-repositories running on EC2 instances. Verified Access simplifies your security operations by allowing you to centrally create, group, and manage access policies for all applications and resources with similar security requirements from a single interface.

To learn more about AWS Verified Access, visit the product page.

 

​AWS Verified Access is a FedRAMP High authorized service in the AWS GovCloud Regions and a FedRAMP Moderate authorized service in the AWS US East and US West commercial regions. Federal agencies, public sector organizations, and other enterprises with FedRAMP compliance requirements can now leverage AWS Verified Access to enable secure VPN-less access to corporate HTTP, non-HTTP applications, and infrastructure resources. Built based on AWS Zero Trust principles, you can use Verified Access to implement a work-from-anywhere model with added security and scalability. AWS Verified Access allows admins to define fine-grained access policies based upon a user’s identity and device posture. It evaluates access for each and every connection request and continuously monitors active connections, terminating connections when security requirements specified in the access policies aren’t met. For example, you can centrally define access policies granting Finance applications access only to authenticated users of the Finance group using compliant and managed devices. Further, you can also use Verified Access to enable access to non-HTTP(S) applications and resources such as databases, and SAP and git-repositories running on EC2 instances. Verified Access simplifies your security operations by allowing you to centrally create, group, and manage access policies for all applications and resources with similar security requirements from a single interface. To learn more about AWS Verified Access, visit the product page.  

Today, we announce support for AWS Glue Data Catalog views with AWS Glue 5.0 for Apache Spark jobs. AWS Glue Data Catalog views with AWS Glue 5.0 allows customers to create views from Glue 5.0 Spark jobs that can be queried from multiple engines without requiring access to referenced tables.

AWS Glue is a serverless, scalable data integration service that makes it simple to discover, prepare, move, and integrate data from multiple sources. AWS Glue Data Catalog views are virtual tables in which the contents are defined by a SQL query that references one or more tables. These views support multiple SQL query engines, so you can access the same view across different AWS services. Administrators can control underlying data access using the rich SQL dialect provided by AWS Glue 5.0 Spark jobs. Access is managed with AWS Lake Formation permissions, including named resource grants, data filters, and lake formation tags. All requests are logged in AWS CloudTrail.

AWS Glue Data Catalog views is generally available on AWS Glue 5.0, in all AWS Glue 5.0 regions.

To learn more, visit the AWS Glue product page and our documentation.

 

​Today, we announce support for AWS Glue Data Catalog views with AWS Glue 5.0 for Apache Spark jobs. AWS Glue Data Catalog views with AWS Glue 5.0 allows customers to create views from Glue 5.0 Spark jobs that can be queried from multiple engines without requiring access to referenced tables. AWS Glue is a serverless, scalable data integration service that makes it simple to discover, prepare, move, and integrate data from multiple sources. AWS Glue Data Catalog views are virtual tables in which the contents are defined by a SQL query that references one or more tables. These views support multiple SQL query engines, so you can access the same view across different AWS services. Administrators can control underlying data access using the rich SQL dialect provided by AWS Glue 5.0 Spark jobs. Access is managed with AWS Lake Formation permissions, including named resource grants, data filters, and lake formation tags. All requests are logged in AWS CloudTrail. AWS Glue Data Catalog views is generally available on AWS Glue 5.0, in all AWS Glue 5.0 regions. To learn more, visit the AWS Glue product page and our documentation.  

AWS CodePipeline V2 type pipeline introduces CodeBuild rule and Commands rule that customers can use in their stage level condition to gate a pipeline execution. You can use CodeBuild rule to start a CodeBuild build or Commands rule to run simple shell commands before exiting a stage, when all actions in the stage have completed successfully, or when any action in the stage has failed.

These new rules will provide more flexibility to your deployment process and enable more release safety controls. With these two rules, you can run integration tests as a stage level condition when your deployment completes and automatically roll back or fail your deployment when the integration tests fail. You can also run custom cleanup scripts using these new rules when the stage execution fails.

To learn more about using these rules in stage level conditions in your pipeline, visit our documentation. For more information about AWS CodePipeline, visit our product page. This feature is available in all regions where AWS CodePipeline is supported.
 

 

​AWS CodePipeline V2 type pipeline introduces CodeBuild rule and Commands rule that customers can use in their stage level condition to gate a pipeline execution. You can use CodeBuild rule to start a CodeBuild build or Commands rule to run simple shell commands before exiting a stage, when all actions in the stage have completed successfully, or when any action in the stage has failed. These new rules will provide more flexibility to your deployment process and enable more release safety controls. With these two rules, you can run integration tests as a stage level condition when your deployment completes and automatically roll back or fail your deployment when the integration tests fail. You can also run custom cleanup scripts using these new rules when the stage execution fails. To learn more about using these rules in stage level conditions in your pipeline, visit our documentation. For more information about AWS CodePipeline, visit our product page. This feature is available in all regions where AWS CodePipeline is supported.