Dashboard Q&A by Amazon Q in QuickSight enables QuickSight Authors to add Data Q&A to their dashboards in one-click. With dashboard Q&A, QuickSight users can ask and answer questions about their data using natural language.

Dashboard Q&A capabilities of Q in QuickSight automatically extract semantic information presented in dashboards and use it to enable Q&A over specific data and improves existing Topic based Q&A experiences by automatically using semantics from dashboards to improve Q&A answers. With Dashboard Q&A Authors can quickly deliver self-service access to customized data insights for the entire organization.

Dashboard Q&A is launching to all regions in which QuickSight’s generative data Q&A is available today, as documented here.

To learn more, visit our documentation.

 

​Dashboard Q&A by Amazon Q in QuickSight enables QuickSight Authors to add Data Q&A to their dashboards in one-click. With dashboard Q&A, QuickSight users can ask and answer questions about their data using natural language. Dashboard Q&A capabilities of Q in QuickSight automatically extract semantic information presented in dashboards and use it to enable Q&A over specific data and improves existing Topic based Q&A experiences by automatically using semantics from dashboards to improve Q&A answers. With Dashboard Q&A Authors can quickly deliver self-service access to customized data insights for the entire organization. Dashboard Q&A is launching to all regions in which QuickSight’s generative data Q&A is available today, as documented here. To learn more, visit our documentation.  

Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, adds support for cross-account ingestion. Starting today, you can agentlessly scrape metrics from Amazon Elastic Kubernetes Service clusters in different accounts than your Amazon Managed Service for Prometheus workspace.

While it was previously possible to apply AWS multi-account best practices for centralized observability with Amazon Managed Service for Prometheus workspaces, you had to use self-managed collection. This meant that you had to run, scale, and patch telemetry agents yourself to scrape metrics from Amazon Elastic Kubernetes Service clusters in various accounts in order to ingest them into a central Amazon Managed Service for Prometheus workspaces in a different account. With this launch, you can now use the Amazon Managed Service for Prometheus collector to get rid of this heavy lifting and ingest metrics in a cross-account setup without having to self-run a collector. In addition, you can now also use the Amazon Managed Service for Prometheus collector to scrape metrics from for Amazon Elastic Kubernetes Service clusters to ingest them into Amazon Managed Service for Prometheus workspaces created with customer managed keys.

Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is available. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.
 

 

​Amazon Managed Service for Prometheus collector, a fully-managed agentless collector for Prometheus metrics, adds support for cross-account ingestion. Starting today, you can agentlessly scrape metrics from Amazon Elastic Kubernetes Service clusters in different accounts than your Amazon Managed Service for Prometheus workspace. While it was previously possible to apply AWS multi-account best practices for centralized observability with Amazon Managed Service for Prometheus workspaces, you had to use self-managed collection. This meant that you had to run, scale, and patch telemetry agents yourself to scrape metrics from Amazon Elastic Kubernetes Service clusters in various accounts in order to ingest them into a central Amazon Managed Service for Prometheus workspaces in a different account. With this launch, you can now use the Amazon Managed Service for Prometheus collector to get rid of this heavy lifting and ingest metrics in a cross-account setup without having to self-run a collector. In addition, you can now also use the Amazon Managed Service for Prometheus collector to scrape metrics from for Amazon Elastic Kubernetes Service clusters to ingest them into Amazon Managed Service for Prometheus workspaces created with customer managed keys. Amazon Managed Service for Prometheus collector is available in all regions where Amazon Managed Service for Prometheus is available. To learn more about Amazon Managed Service for Prometheus collector, visit the user guide or product page.    

Amazon Connect Cases now allows agents and supervisors to filter cases in the agent workspace by custom field values, making it easier to narrow down search results and find relevant cases. Users can also customize the case list view and search results layout by adding custom columns, hiding or rearranging existing columns, and adjusting the number of cases per page. These enhancements enable users to tailor the case list view to meet their needs and manage their case workloads more effectively.

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 allows agents and supervisors to filter cases in the agent workspace by custom field values, making it easier to narrow down search results and find relevant cases. Users can also customize the case list view and search results layout by adding custom columns, hiding or rearranging existing columns, and adjusting the number of cases per page. These enhancements enable users to tailor the case list view to meet their needs and manage their case workloads more effectively. 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 Elastic Block Store (Amazon EBS) now supports additional resource-level permissions for creating EBS volumes from snapshots. With this launch, you now have more granular controls to set resource-level permissions for the creation of a volume and selection of the source snapshot when calling the CreateVolume action in your IAM policy. This allows you to control the IAM identities that can create EBS volumes from source snapshots, and the conditions that they can use these snapshots to create EBS volumes.

To meet your specific permission needs on the source snapshots, you can also specify any of 5 EC2-specific condition keys in your IAM policy: ec2:Encrypted, ec2:VolumeSize, ec2:Owner, ec2:ParentVolume, and ec2:SnapshotTime. Additionally, you can use global condition keys for the source snapshot.

This new resource-level permission model is available in all AWS Regions where EBS volumes are available. To learn more about using resource-level permissions to create EBS volume, or transitioning to the new resource-level permission model from previous permission model, please visit the launch blog. For more information about Amazon EBS, please visit the product page.

 

​Amazon Elastic Block Store (Amazon EBS) now supports additional resource-level permissions for creating EBS volumes from snapshots. With this launch, you now have more granular controls to set resource-level permissions for the creation of a volume and selection of the source snapshot when calling the CreateVolume action in your IAM policy. This allows you to control the IAM identities that can create EBS volumes from source snapshots, and the conditions that they can use these snapshots to create EBS volumes. To meet your specific permission needs on the source snapshots, you can also specify any of 5 EC2-specific condition keys in your IAM policy: ec2:Encrypted, ec2:VolumeSize, ec2:Owner, ec2:ParentVolume, and ec2:SnapshotTime. Additionally, you can use global condition keys for the source snapshot. This new resource-level permission model is available in all AWS Regions where EBS volumes are available. To learn more about using resource-level permissions to create EBS volume, or transitioning to the new resource-level permission model from previous permission model, please visit the launch blog. For more information about Amazon EBS, please visit the product page.  

Today, Amazon Q Developer announces an improved software development agent capable of running build and test scripts on generated code to validate the code before the developers review. This new capability detects errors, ensures generated code is in sync with the project’s current state, and accelerates the development process by producing higher quality code on the first iteration.

With the developer’s natural language input request and project-specific context, the Amazon Q Developer agent is designed to assist in implementing complex multi-file features and bug fixes. The agent will analyze the existing codebase, make necessary code changes, and run the selected build and test commands to ensure the code is working as expected. Where errors are found, the agent will iterate on the code prior to requesting the developer’s review. Throughout the process, the agent maintains a real-time connection with the developer, providing updates as changes are made. With control over what commands Amazon Q runs through a Devfile, you can customize the development process for better accuracy.

The Amazon Q Developer agent for software development is available for JetBrains and Visual Studio Code IDEs in all AWS regions where Q Developer is available.

To learn more about Amazon Q Developer, visit the service overview page. For more details about this announcement and how to get started using the Amazon Q Developer agent for software development, read the AWS DevOps & Developer Productivity blog.

 

​Today, Amazon Q Developer announces an improved software development agent capable of running build and test scripts on generated code to validate the code before the developers review. This new capability detects errors, ensures generated code is in sync with the project’s current state, and accelerates the development process by producing higher quality code on the first iteration. With the developer’s natural language input request and project-specific context, the Amazon Q Developer agent is designed to assist in implementing complex multi-file features and bug fixes. The agent will analyze the existing codebase, make necessary code changes, and run the selected build and test commands to ensure the code is working as expected. Where errors are found, the agent will iterate on the code prior to requesting the developer’s review. Throughout the process, the agent maintains a real-time connection with the developer, providing updates as changes are made. With control over what commands Amazon Q runs through a Devfile, you can customize the development process for better accuracy. The Amazon Q Developer agent for software development is available for JetBrains and Visual Studio Code IDEs in all AWS regions where Q Developer is available. To learn more about Amazon Q Developer, visit the service overview page. For more details about this announcement and how to get started using the Amazon Q Developer agent for software development, read the AWS DevOps & Developer Productivity blog.  

The Amazon EventBridge console now displays the source and detail type of all available AWS service events when you create a rule in the EventBridge console. This makes it easier for customers to discover and utilize the full range of AWS service events when building event-driven architectures. Additionally, the EventBridge documentation now includes an automatically updated list of all AWS service events, facilitating access to the most current information.

Amazon EventBridge Event Bus is a serverless event router that enables you to create highly scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services. With this update, developers can quickly search and filter through all available AWS service events, including event types, within the EventBridge console, when configuring event patterns in the sandbox and rules, and in the documentation, enabling customers to more efficiently create event-driven integrations and reduce misconfiguration.

This feature in the EventBridge console is available in all commercial AWS Regions. To learn more about discovering and using AWS service events in Amazon EventBridge, see the updated list of AWS service events in the documentation here.
 

 

​The Amazon EventBridge console now displays the source and detail type of all available AWS service events when you create a rule in the EventBridge console. This makes it easier for customers to discover and utilize the full range of AWS service events when building event-driven architectures. Additionally, the EventBridge documentation now includes an automatically updated list of all AWS service events, facilitating access to the most current information. Amazon EventBridge Event Bus is a serverless event router that enables you to create highly scalable event-driven applications by routing events between your own applications, third-party SaaS applications, and other AWS services. With this update, developers can quickly search and filter through all available AWS service events, including event types, within the EventBridge console, when configuring event patterns in the sandbox and rules, and in the documentation, enabling customers to more efficiently create event-driven integrations and reduce misconfiguration. This feature in the EventBridge console is available in all commercial AWS Regions. To learn more about discovering and using AWS service events in Amazon EventBridge, see the updated list of AWS service events in the documentation here.    

Amazon Connect now includes the ability for agents to schedule time off up to 24 months in the future, making it easier for managers and agents to plan ahead of time. With this launch, agents can now book time off in Connect up to 24 months ahead of time (an increase from 13 months). Additionally, you can now upload pre-approved time off windows for a scheduling group (group allowance) for up to 27 months at a time (an increase from 13 months). These increased limits provide agents more flexibility to plan their personal time and also provide managers better visibility into future staffing needs, thus enabling more efficient resource allocation.

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 includes the ability for agents to schedule time off up to 24 months in the future, making it easier for managers and agents to plan ahead of time. With this launch, agents can now book time off in Connect up to 24 months ahead of time (an increase from 13 months). Additionally, you can now upload pre-approved time off windows for a scheduling group (group allowance) for up to 27 months at a time (an increase from 13 months). These increased limits provide agents more flexibility to plan their personal time and also provide managers better visibility into future staffing needs, thus enabling more efficient resource allocation. 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 Deadline Cloud now includes the ability to specify a limit for a specific resource, like a floating license, and also constrain the maximum number of workers that work on a job. AWS Deadline Cloud is a fully managed service that simplifies render management for teams creating computer-generated graphics and visual effects, for films, television and broadcasting, web content, and design.

By adding a limit to your Deadline Cloud farm, you can specify a maximum amount of concurrent usage of resources by workers in your farm. Capping resource usage ensures tasks don’t start until the resources needed to run are available. For example, if you have 50 floating licenses for a particular plugin required by your rendering workflow, a Deadline Cloud limit allows you to ensure no more than 50 tasks requiring that limit are started, preventing tasks from failing due to the license being unavailable. Additionally, setting a maximum number of workers on a job enables you to prevent any single job from consuming all the available workers so that you can efficiently run multiple jobs concurrently when there are a limited number of workers available.

Limits are available in all AWS Regions where Deadline Cloud is available.

To learn more, visit the AWS Deadline Cloud documentation.
 

 

​AWS Deadline Cloud now includes the ability to specify a limit for a specific resource, like a floating license, and also constrain the maximum number of workers that work on a job. AWS Deadline Cloud is a fully managed service that simplifies render management for teams creating computer-generated graphics and visual effects, for films, television and broadcasting, web content, and design. By adding a limit to your Deadline Cloud farm, you can specify a maximum amount of concurrent usage of resources by workers in your farm. Capping resource usage ensures tasks don’t start until the resources needed to run are available. For example, if you have 50 floating licenses for a particular plugin required by your rendering workflow, a Deadline Cloud limit allows you to ensure no more than 50 tasks requiring that limit are started, preventing tasks from failing due to the license being unavailable. Additionally, setting a maximum number of workers on a job enables you to prevent any single job from consuming all the available workers so that you can efficiently run multiple jobs concurrently when there are a limited number of workers available. Limits are available in all AWS Regions where Deadline Cloud is available. To learn more, visit the AWS Deadline Cloud documentation.    

Amazon RDS Custom for SQL Server now offers enhanced storage and performance capabilities, supporting up to 64TiB of storage and 256,000 I/O operations per second (IOPS) with io2 Block Express volumes. This represents an improvement from the previous limit of 16 TiB and 64,000 IOPS with io2 Block Express. These enhancements enable transactional databases and data warehouses to handle larger workloads on a single Amazon RDS Custom for SQL Server database instance.

The support for 64TiB and 256,000 IOPS with io2 Block Express for Amazon RDS Custom for SQL Server is now generally available in all AWS regions where both Amazon RDS io2 Block Express volumes and Amazon RDS Custom for SQL Server are currently supported.

Amazon RDS Custom for SQL Server is a managed database service that allows customization of the underlying operating system and includes the ability to bring your own licensed SQL Server media or use SQL Server Developer Edition while providing the time-savings, durability, and scalability benefits of a managed database service. To get started, visit the Amazon RDS Custom for SQL Server User Guide. See Amazon RDS Custom Pricing for up-to-date pricing of instances, storage, data transfer and regional availability.
 

 

​Amazon RDS Custom for SQL Server now offers enhanced storage and performance capabilities, supporting up to 64TiB of storage and 256,000 I/O operations per second (IOPS) with io2 Block Express volumes. This represents an improvement from the previous limit of 16 TiB and 64,000 IOPS with io2 Block Express. These enhancements enable transactional databases and data warehouses to handle larger workloads on a single Amazon RDS Custom for SQL Server database instance. The support for 64TiB and 256,000 IOPS with io2 Block Express for Amazon RDS Custom for SQL Server is now generally available in all AWS regions where both Amazon RDS io2 Block Express volumes and Amazon RDS Custom for SQL Server are currently supported. Amazon RDS Custom for SQL Server is a managed database service that allows customization of the underlying operating system and includes the ability to bring your own licensed SQL Server media or use SQL Server Developer Edition while providing the time-savings, durability, and scalability benefits of a managed database service. To get started, visit the Amazon RDS Custom for SQL Server User Guide. See Amazon RDS Custom Pricing for up-to-date pricing of instances, storage, data transfer and regional availability.    

Amazon AppStream 2.0 now allows administrator to control whether admin consent is required when users link their OneDrive for Business accounts as a persistent storage option.

The new capability simplifies the management of AppStream 2.0 persistent storage and the admin consent process. After enabling OneDrive for Business for an AppStream 2.0 stack and specifying the OneDrive domains, administrators can now configure whether admin consent is needed for each OneDrive domain. If admin consent is required, administrators must approve users’ OneDrive connections within their Azure Active Directory environment when users attempt to link their account to AppStream 2.0.

This feature is available at no additional cost in all AWS Regions where AppStream 2.0 is offered. It is supported only on AppStream stacks using single-session Windows fleets.

To get started, open the AppStream 2.0 console and create a stack. In the Enable storage step, enable OneDrive for business and configure the admin consent settings. For more details, refer to Administer OneDrive for business. You can also programmatically manage the setting using AppStream 2.0 APIs. For API details, see the CreateStack API documentation.

 

​Amazon AppStream 2.0 now allows administrator to control whether admin consent is required when users link their OneDrive for Business accounts as a persistent storage option. The new capability simplifies the management of AppStream 2.0 persistent storage and the admin consent process. After enabling OneDrive for Business for an AppStream 2.0 stack and specifying the OneDrive domains, administrators can now configure whether admin consent is needed for each OneDrive domain. If admin consent is required, administrators must approve users’ OneDrive connections within their Azure Active Directory environment when users attempt to link their account to AppStream 2.0. This feature is available at no additional cost in all AWS Regions where AppStream 2.0 is offered. It is supported only on AppStream stacks using single-session Windows fleets. To get started, open the AppStream 2.0 console and create a stack. In the Enable storage step, enable OneDrive for business and configure the admin consent settings. For more details, refer to Administer OneDrive for business. You can also programmatically manage the setting using AppStream 2.0 APIs. For API details, see the CreateStack API documentation.