Amazon Q Business, the generative AI-powered assistant for finding information, gaining insight, and taking action at work, introduced an intelligent orchestration feature that simplifies conversational experience by understanding user queries, and automatically directing the queries to the right data sources and plugins to generate relevant responses.

Earlier, users would need to manually switch between different work applications to complete their tasks and gain insights from data sources. Enabling orchestration simplifies the user conversational experience by automatically directing user queries to indexed enterprise data sources and plugins, eliminating the need for manual selection. Orchestration works with retrieval augmented generative (RAG) data for enterprise-specific knowledge, and with both built-in and custom plugins, allowing users to interact with popular business tools like Jira, Salesforce, ServiceNow, Smartsheet, and PagerDuty – all through a single conversation in Amazon Q Business.

The new orchestration feature is available in all AWS Regions where Amazon Q Business is available. To get started with the feature, customers can access the setting directly from the Amazon Q Business console. To learn more, please visit Using global controls in Amazon Q Business. To learn more about Amazon Q Business plugins and how they can enhance your organization’s productivity, visit the Amazon Q Business webpage and explore the Amazon Q Business plugin documentation.

 

​Amazon Q Business, the generative AI-powered assistant for finding information, gaining insight, and taking action at work, introduced an intelligent orchestration feature that simplifies conversational experience by understanding user queries, and automatically directing the queries to the right data sources and plugins to generate relevant responses. Earlier, users would need to manually switch between different work applications to complete their tasks and gain insights from data sources. Enabling orchestration simplifies the user conversational experience by automatically directing user queries to indexed enterprise data sources and plugins, eliminating the need for manual selection. Orchestration works with retrieval augmented generative (RAG) data for enterprise-specific knowledge, and with both built-in and custom plugins, allowing users to interact with popular business tools like Jira, Salesforce, ServiceNow, Smartsheet, and PagerDuty – all through a single conversation in Amazon Q Business. The new orchestration feature is available in all AWS Regions where Amazon Q Business is available. To get started with the feature, customers can access the setting directly from the Amazon Q Business console. To learn more, please visit Using global controls in Amazon Q Business. To learn more about Amazon Q Business plugins and how they can enhance your organization’s productivity, visit the Amazon Q Business webpage and explore the Amazon Q Business plugin documentation.  

AWS Wickr is excited to announce the launch of «Wickr Files,» a dedicated space that allows you to access and manage files in conversations. Moderators of Wickr rooms and users in self-moderated group conversations, can now upload and organize files in folders. Users can toggle between “Messages” and “Files” tabs to access relevant content and streamline collaboration.

AWS Wickr is a security-first messaging and collaboration service with features designed to help keep your internal and external communications secure, private, and compliant. AWS Wickr protects one-to-one and group messaging, voice and video calling, file sharing, screen sharing, and location sharing with end-to-end encryption. Customers have full administrative control over data, which includes addressing information governance polices, configuring ephemeral messaging options, and deleting credentials for lost or stolen devices. You can log both internal and external conversations in an AWS Wickr network to a private data store that you manage, for data retention and auditing purposes.

AWS Wickr is available in commercial AWS Regions that include US East (N. Virginia), AWS Canada (Central), AWS Asia Pacific (Malaysia, Singapore, Sydney, and Tokyo), and AWS Europe (London, Frankfurt, Stockholm, and Zurich). It is also available in AWS GovCloud (US-West) as Department of Defense Impact Level 5 (DoD IL5)-authorized AWS WickrGov.

To learn more and get started, see the following resources:

• AWS Wickr product detail page
• AWS Wickr user guide
• AWS Wickr administration guide

 

​AWS Wickr is excited to announce the launch of «Wickr Files,» a dedicated space that allows you to access and manage files in conversations. Moderators of Wickr rooms and users in self-moderated group conversations, can now upload and organize files in folders. Users can toggle between “Messages” and “Files” tabs to access relevant content and streamline collaboration. AWS Wickr is a security-first messaging and collaboration service with features designed to help keep your internal and external communications secure, private, and compliant. AWS Wickr protects one-to-one and group messaging, voice and video calling, file sharing, screen sharing, and location sharing with end-to-end encryption. Customers have full administrative control over data, which includes addressing information governance polices, configuring ephemeral messaging options, and deleting credentials for lost or stolen devices. You can log both internal and external conversations in an AWS Wickr network to a private data store that you manage, for data retention and auditing purposes. AWS Wickr is available in commercial AWS Regions that include US East (N. Virginia), AWS Canada (Central), AWS Asia Pacific (Malaysia, Singapore, Sydney, and Tokyo), and AWS Europe (London, Frankfurt, Stockholm, and Zurich). It is also available in AWS GovCloud (US-West) as Department of Defense Impact Level 5 (DoD IL5)-authorized AWS WickrGov. To learn more and get started, see the following resources:

AWS Wickr product detail page
AWS Wickr user guide
AWS Wickr administration guide  

AWS Database Migration Service Serverless (AWS DMSS) now supports files on S3 source endpoints. Using AWS DMSS, you can now migrate data in CSV or parquet format from S3 to any supported AWS DMSS target endpoint. AWS DMSS supports both full load and Change Data Capture (CDC) migration modes for CSV and Parquet files with S3 source endpoints using AWS DMS console, AWS CLI, or AWS SDKs in all regions where DMSS is available.

For information about AWS DMS S3 source endpoints see DMS S3. Visit AWS DMS to get started.

For AWS DMS regional availability, please refer to the AWS Region Table.

 

​AWS Database Migration Service Serverless (AWS DMSS) now supports files on S3 source endpoints. Using AWS DMSS, you can now migrate data in CSV or parquet format from S3 to any supported AWS DMSS target endpoint. AWS DMSS supports both full load and Change Data Capture (CDC) migration modes for CSV and Parquet files with S3 source endpoints using AWS DMS console, AWS CLI, or AWS SDKs in all regions where DMSS is available. For information about AWS DMS S3 source endpoints see DMS S3. Visit AWS DMS to get started. For AWS DMS regional availability, please refer to the AWS Region Table.  

Contact Lens now enables businesses to send automatic email notifications to agents when their contacts are evaluated, so they can review the evaluations and improve their performance. Managers can create rules to send emails based on specific evaluation criteria. For example, you can set up automatic notifications for agents who receive evaluation scores below 50%, ensuring prompt attention to performance opportunities. Managers can also personalize email content based on performance levels — whether recognizing top performers or providing constructive guidance for improvement areas.

This feature is available in all regions where Contact Lens performance evaluations are already available. To learn more, please visit our documentation and our webpage. For information about Contact Lens pricing, please visit our pricing page.

 

​Contact Lens now enables businesses to send automatic email notifications to agents when their contacts are evaluated, so they can review the evaluations and improve their performance. Managers can create rules to send emails based on specific evaluation criteria. For example, you can set up automatic notifications for agents who receive evaluation scores below 50%, ensuring prompt attention to performance opportunities. Managers can also personalize email content based on performance levels — whether recognizing top performers or providing constructive guidance for improvement areas. This feature is available in all regions where Contact Lens performance evaluations are already available. To learn more, please visit our documentation and our webpage. For information about Contact Lens pricing, please visit our pricing page.  

Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C6in instances are available in AWS Region Asia Pacific (Malaysia). These sixth-generation network optimized instances, powered by 3rd Generation Intel Xeon Scalable processors and built on the AWS Nitro System, deliver up to 200Gbps network bandwidth, for 2x more network bandwidth over comparable fifth-generation instances.

Customers can use C6in instances to scale the performance of applications such as network virtual appliances (firewalls, virtual routers, load balancers), Telco 5G User Plane Function (UPF), data analytics, high performance computing (HPC), and CPU based AI/ML workloads. C6in instances are available in 10 different sizes with up to 128 vCPUs, including bare metal size. Amazon EC2 sixth-generation x86-based network optimized EC2 instances deliver up to 100Gbps of Amazon Elastic Block Store (Amazon EBS) bandwidth, and up to 400K IOPS. C6in instances offer Elastic Fabric Adapter (EFA) networking support on 32xlarge and metal sizes.

C6in instances are available in these AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Middle East (Bahrain, UAE), Israel (Tel Aviv), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Seoul, Singapore, Sydney, Tokyo), Africa (Cape Town), South America (São Paulo), Canada (Central), and AWS GovCloud (US-West, US-East). To learn more, see the Amazon EC2 C6in instances. To get started, see the AWS Management Console, AWS Command Line Interface (AWS CLI), and AWS SDKs.

 

​Starting today, Amazon Elastic Compute Cloud (Amazon EC2) C6in instances are available in AWS Region Asia Pacific (Malaysia). These sixth-generation network optimized instances, powered by 3rd Generation Intel Xeon Scalable processors and built on the AWS Nitro System, deliver up to 200Gbps network bandwidth, for 2x more network bandwidth over comparable fifth-generation instances. Customers can use C6in instances to scale the performance of applications such as network virtual appliances (firewalls, virtual routers, load balancers), Telco 5G User Plane Function (UPF), data analytics, high performance computing (HPC), and CPU based AI/ML workloads. C6in instances are available in 10 different sizes with up to 128 vCPUs, including bare metal size. Amazon EC2 sixth-generation x86-based network optimized EC2 instances deliver up to 100Gbps of Amazon Elastic Block Store (Amazon EBS) bandwidth, and up to 400K IOPS. C6in instances offer Elastic Fabric Adapter (EFA) networking support on 32xlarge and metal sizes. C6in instances are available in these AWS Regions: US East (Ohio, N. Virginia), US West (N. California, Oregon), Europe (Frankfurt, Ireland, London, Milan, Paris, Spain, Stockholm, Zurich), Middle East (Bahrain, UAE), Israel (Tel Aviv), Asia Pacific (Hong Kong, Hyderabad, Jakarta, Malaysia, Melbourne, Mumbai, Seoul, Singapore, Sydney, Tokyo), Africa (Cape Town), South America (São Paulo), Canada (Central), and AWS GovCloud (US-West, US-East). To learn more, see the Amazon EC2 C6in instances. To get started, see the AWS Management Console, AWS Command Line Interface (AWS CLI), and AWS SDKs.  

Amazon Connect Cases now supports conditionally required fields to streamline case field population for agents and reduce data entry errors. Administrators can now configure case templates that prompt agents to enter relevant information in specific situations, such as providing a “Close Reason” when a case moves to “Closed” status, “Product Serial Number” when the “Issue Type” is “Hardware Problem”, or “Disposition Code” when handling a system-generated case. Conditionally required fields help agents follow processes for capturing necessary information, improving data quality for reporting, resolution tracking, and compliance.

For region availability, please see the availability of Amazon Connect features by Region. To learn more and get started, visit the Amazon Connect Cases webpage and documentation.
 

 

​Amazon Connect Cases now supports conditionally required fields to streamline case field population for agents and reduce data entry errors. Administrators can now configure case templates that prompt agents to enter relevant information in specific situations, such as providing a “Close Reason” when a case moves to “Closed” status, “Product Serial Number” when the “Issue Type” is “Hardware Problem”, or “Disposition Code” when handling a system-generated case. Conditionally required fields help agents follow processes for capturing necessary information, improving data quality for reporting, resolution tracking, and compliance. For region availability, please see the availability of Amazon Connect features by Region. To learn more and get started, visit the Amazon Connect Cases webpage and documentation.    

Amazon Q Developer has expanded its AWS Console error coverage from US East (N. Virginia) and US West (Oregon) to AWS Commercial regions. Users can now troubleshoot AWS Console errors using Amazon Q Developer regardless of their console region, including locations like Europe (Frankfurt).

In the Amazon Web Services (AWS) Management Console, Amazon Q Developer diagnoses common errors you encounter while working with AWS services, such as insufficient permissions, incorrect configuration, and exceeding service limits. Q Developer troubleshoots errors arising from the following services in the AWS Management Console: Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Container Service (Amazon ECS), Amazon Simple Storage Service (Amazon S3), AWS Lambda and Amazon CloudFormation (Amazon CFn). In addition, Q Developer troubleshoots IAM Permission and Athena console errors across all AWS Console pages.

To learn more about using Amazon Q Developer to troubleshoot AWS Console errors, visit the AWS documentation. Amazon Q Developer is currently available in select regions, and you can review information about where your data is processed here. For pricing details, visit the Amazon Q Developer pricing page.

 

​Amazon Q Developer has expanded its AWS Console error coverage from US East (N. Virginia) and US West (Oregon) to AWS Commercial regions. Users can now troubleshoot AWS Console errors using Amazon Q Developer regardless of their console region, including locations like Europe (Frankfurt). In the Amazon Web Services (AWS) Management Console, Amazon Q Developer diagnoses common errors you encounter while working with AWS services, such as insufficient permissions, incorrect configuration, and exceeding service limits. Q Developer troubleshoots errors arising from the following services in the AWS Management Console: Amazon Elastic Compute Cloud (Amazon EC2), Amazon Elastic Container Service (Amazon ECS), Amazon Simple Storage Service (Amazon S3), AWS Lambda and Amazon CloudFormation (Amazon CFn). In addition, Q Developer troubleshoots IAM Permission and Athena console errors across all AWS Console pages. To learn more about using Amazon Q Developer to troubleshoot AWS Console errors, visit the AWS documentation. Amazon Q Developer is currently available in select regions, and you can review information about where your data is processed here. For pricing details, visit the Amazon Q Developer pricing page.  

Amazon Connect now provides the ability to choose which states an agent can be in when adhering to their schedule, making it easier for you to customize adherence tracking to match your unique operational needs. With this launch, you can now define custom mappings between agent statuses and schedule activities. For example, schedule activity “Work” can be mapped to multiple agent statuses such as “Available” and “Back-office work.” An agent scheduled for “Work” from 8 AM to 10 AM will be considered adherent if they are either in “Available” or “Back-office work” status. Additionally, you can now view the actual name of the scheduled activity in the real-time adherence dashboard (as opposed to only Productive/Non-productive). With custom mappings and enhanced real-time dashboard, this launch provides more accurate and flexible agent adherence monitoring.

This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about Amazon Connect agent scheduling, click here.
 

 

​Amazon Connect now provides the ability to choose which states an agent can be in when adhering to their schedule, making it easier for you to customize adherence tracking to match your unique operational needs. With this launch, you can now define custom mappings between agent statuses and schedule activities. For example, schedule activity “Work” can be mapped to multiple agent statuses such as “Available” and “Back-office work.” An agent scheduled for “Work” from 8 AM to 10 AM will be considered adherent if they are either in “Available” or “Back-office work” status. Additionally, you can now view the actual name of the scheduled activity in the real-time adherence dashboard (as opposed to only Productive/Non-productive). With custom mappings and enhanced real-time dashboard, this launch provides more accurate and flexible agent adherence monitoring. This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about Amazon Connect agent scheduling, click here.    

AWS Batch on EKS now supports configurable Kubernetes namespaces, Persistent Volume Claims (PVCs), subPath to Kubernetes pod container volumes, and Kubernetes pod annotations. Using different Kubernetes namespaces for your AWS Batch jobs, you can improve workload isolation by defining job permission boundaries both within EKS cluster and for access to other AWS services. With Kubernetes PVCs and subPath you can give your AWS Batch jobs access only to the right data or particular subPath within a data volume. Finally, EKS pod annotations make it easier to integrate with external tools and other AWS services such as AWS Secrets Manager by allowing you to attach necessary metadata directly to your AWS Batch job.

You can configure Kubernetes namespaces, PVCs, subPath, and annotations while registering a new AWS Batch job definition or making a revision to an existing job definition. You can also override the namespace and annotations from your job definition when you submit the job. For more information, see Register Job Definition and Submit Job pages in the AWS Batch API reference and our AWS HPC Blog post.

AWS Batch supports developers, scientists, and engineers in running efficient batch processing for ML model training, simulations, and analysis at any scale. Configurable Kubernetes namespaces, PVCs, subPath, and annotations are available in any AWS Region where AWS Batch is available.
 

 

​AWS Batch on EKS now supports configurable Kubernetes namespaces, Persistent Volume Claims (PVCs), subPath to Kubernetes pod container volumes, and Kubernetes pod annotations. Using different Kubernetes namespaces for your AWS Batch jobs, you can improve workload isolation by defining job permission boundaries both within EKS cluster and for access to other AWS services. With Kubernetes PVCs and subPath you can give your AWS Batch jobs access only to the right data or particular subPath within a data volume. Finally, EKS pod annotations make it easier to integrate with external tools and other AWS services such as AWS Secrets Manager by allowing you to attach necessary metadata directly to your AWS Batch job. You can configure Kubernetes namespaces, PVCs, subPath, and annotations while registering a new AWS Batch job definition or making a revision to an existing job definition. You can also override the namespace and annotations from your job definition when you submit the job. For more information, see Register Job Definition and Submit Job pages in the AWS Batch API reference and our AWS HPC Blog post. AWS Batch supports developers, scientists, and engineers in running efficient batch processing for ML model training, simulations, and analysis at any scale. Configurable Kubernetes namespaces, PVCs, subPath, and annotations are available in any AWS Region where AWS Batch is available.    

Amazon EC2 now supports automated recovery of Microsoft SQL Server databases from Volume Shadow Copy Services (VSS) based EBS snapshots. Customers can use an AWS Systems Manager Automation Runbook and specify a restore point of time to automate the recovery process without needing to stop a running Microsoft SQL Server database.

Volume Shadow Copy Services (VSS) allows application data to be backed up while applications are still running. This new feature allows customers to automate the recovery from VSS-based EBS snapshots and ensure rapid recovery of large databases within minutes. This feature also offers customers the flexibility to restore to a new database or achieve point-in-time recovery.

This feature is available in all commercial AWS Regions and the AWS GovCloud (US) Regions.

To learn more, visit this technical document in the Microsoft SQL Server on Amazon EC2 User Guide.

 

​Amazon EC2 now supports automated recovery of Microsoft SQL Server databases from Volume Shadow Copy Services (VSS) based EBS snapshots. Customers can use an AWS Systems Manager Automation Runbook and specify a restore point of time to automate the recovery process without needing to stop a running Microsoft SQL Server database. Volume Shadow Copy Services (VSS) allows application data to be backed up while applications are still running. This new feature allows customers to automate the recovery from VSS-based EBS snapshots and ensure rapid recovery of large databases within minutes. This feature also offers customers the flexibility to restore to a new database or achieve point-in-time recovery. This feature is available in all commercial AWS Regions and the AWS GovCloud (US) Regions. To learn more, visit this technical document in the Microsoft SQL Server on Amazon EC2 User Guide.