AWS HealthImaging announces two enhancements that make it easier to manage diverse medical imaging data in the cloud.

First, HealthImaging now supports video data, encoded per the DICOM standard. With this launch, video data can be stored in a HealthImaging data store, alongside still image data. The service supports the DICOM video formats: MPEG2, MPEG-4 AVC/H.264, HEVC/H.265, corresponding to DICOM transfer syntax UIDs 1.2.840.10008.1.2.4.100 through 1.2.840.10008.1.2.4.108. This data can be retrieved as DICOM instances (.dcm files) and directly as video objects. For more information, see the documentation.

Second, HealthImaging has added support for retrieving lossless images in the JPEG 2000 lossless format (transfer syntax UID 1.2.840.10008.1.2.4.90). The service supports retrieving both DICOM instances (.dcm files) and image frames in the JPEG 2000 lossless format. HealthImaging’s transcoding to JPEG 2000 makes it easier to interoperate with external applications that consume data in this widely adopted format.

AWS HealthImaging is a HIPAA-eligible service that empowers healthcare providers and their software partners to store, analyze, and share medical images at petabyte scale. With AWS HealthImaging, you can run your medical imaging applications at scale from a single, authoritative copy of each medical image in the cloud, while reducing total cost of ownership. To learn more, see the AWS HealthImaging Developer Guide.

AWS HealthImaging is generally available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Ireland).

 

​AWS HealthImaging announces two enhancements that make it easier to manage diverse medical imaging data in the cloud. First, HealthImaging now supports video data, encoded per the DICOM standard. With this launch, video data can be stored in a HealthImaging data store, alongside still image data. The service supports the DICOM video formats: MPEG2, MPEG-4 AVC/H.264, HEVC/H.265, corresponding to DICOM transfer syntax UIDs 1.2.840.10008.1.2.4.100 through 1.2.840.10008.1.2.4.108. This data can be retrieved as DICOM instances (.dcm files) and directly as video objects. For more information, see the documentation. Second, HealthImaging has added support for retrieving lossless images in the JPEG 2000 lossless format (transfer syntax UID 1.2.840.10008.1.2.4.90). The service supports retrieving both DICOM instances (.dcm files) and image frames in the JPEG 2000 lossless format. HealthImaging’s transcoding to JPEG 2000 makes it easier to interoperate with external applications that consume data in this widely adopted format. AWS HealthImaging is a HIPAA-eligible service that empowers healthcare providers and their software partners to store, analyze, and share medical images at petabyte scale. With AWS HealthImaging, you can run your medical imaging applications at scale from a single, authoritative copy of each medical image in the cloud, while reducing total cost of ownership. To learn more, see the AWS HealthImaging Developer Guide. AWS HealthImaging is generally available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Ireland).  

Amazon Aurora now supports PostgreSQL major version 17 (17.4). This release contains product improvements and bug fixes from the PostgreSQL community along with Aurora- specific feature improvements such as enhanced memory management, faster storage metadata initialization during failovers, and optimized write-heavy workloads on new Graviton 4 high-end instances. This release also includes new features for Babelfish, Aurora-specific security fixes, and updates to key extensions including pgvector 0.8.0 and postgis 3.5.1. Please refer to the PostgreSQL community announcement and Amazon Aurora PostgreSQL updates for more details about the release.

To use the new version, create a new Aurora PostgreSQL-compatible database with just a few clicks in the Amazon RDS Management Console. Please review the Aurora documentation to learn more about upgrading and refer the Aurora version policy to help decide how often to upgrade and plan your upgrade process. PostgreSQL 17.4 is available in all commercial AWS Regions and AWS GovCloud (US) Regions.

Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.
 

 

​Amazon Aurora now supports PostgreSQL major version 17 (17.4). This release contains product improvements and bug fixes from the PostgreSQL community along with Aurora- specific feature improvements such as enhanced memory management, faster storage metadata initialization during failovers, and optimized write-heavy workloads on new Graviton 4 high-end instances. This release also includes new features for Babelfish, Aurora-specific security fixes, and updates to key extensions including pgvector 0.8.0 and postgis 3.5.1. Please refer to the PostgreSQL community announcement and Amazon Aurora PostgreSQL updates for more details about the release. To use the new version, create a new Aurora PostgreSQL-compatible database with just a few clicks in the Amazon RDS Management Console. Please review the Aurora documentation to learn more about upgrading and refer the Aurora version policy to help decide how often to upgrade and plan your upgrade process. PostgreSQL 17.4 is available in all commercial AWS Regions and AWS GovCloud (US) Regions. Amazon Aurora is designed for unparalleled high performance and availability at global scale with full MySQL and PostgreSQL compatibility. It provides built-in security, continuous backups, serverless compute, up to 15 read replicas, automated multi-Region replication, and integrations with other AWS services. To get started with Amazon Aurora, take a look at our getting started page.    

Amazon Neptune Database now supports Graviton3-based R7g and Graviton4-based R8g database instances for Amazon Neptune engine versions 1.4.5 or above, and priced -16% vs R6g.

Graviton3-based R7g are the first AWS database instances to feature the latest DDR5 memory, which provides 50% more memory bandwidth compared to DDR4, enabling high-speed access to data in memory. R7g database instances offer up to 30Gbps enhanced networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS). Graviton4-based R8g instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory.

R7g instances for Neptune are now available US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Europe (Ireland), Europe (London), Asia Pacific (Hong Kong), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Hyderabad), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Malaysia), Canada (Central), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), and South America (São Paulo). R8g instances for Neptune are now available in: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Asia Pacific (Sydney), Europe (Frankfurt), Europe (Stockholm), and Europe (Spain). You can launch R7g and R8g instances for Neptune using the AWS Management Console or using the AWS CLI. Upgrading a Neptune cluster to R7g or R8g instances requires a simple instance type modification for Neptune engine versions 1.4.5 or higher. For more information on pricing and regional availability, refer to the Amazon Neptune pricing page.
 

 

​Amazon Neptune Database now supports Graviton3-based R7g and Graviton4-based R8g database instances for Amazon Neptune engine versions 1.4.5 or above, and priced -16% vs R6g. Graviton3-based R7g are the first AWS database instances to feature the latest DDR5 memory, which provides 50% more memory bandwidth compared to DDR4, enabling high-speed access to data in memory. R7g database instances offer up to 30Gbps enhanced networking bandwidth and up to 20 Gbps of bandwidth to the Amazon Elastic Block Store (Amazon EBS). Graviton4-based R8g instances offer larger instance sizes, up to 48xlarge and features an 8:1 ratio of memory to vCPU, and the latest DDR5 memory. R7g instances for Neptune are now available US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Europe (Ireland), Europe (London), Asia Pacific (Hong Kong), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Mumbai), Asia Pacific (Hyderabad), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Malaysia), Canada (Central), Europe (Frankfurt), Europe (Stockholm), Europe (Spain), and South America (São Paulo). R8g instances for Neptune are now available in: US East (N. Virginia), US East (Ohio), US West (Oregon), Europe (Ireland), Asia Pacific (Tokyo), Asia Pacific (Mumbai), Asia Pacific (Sydney), Europe (Frankfurt), Europe (Stockholm), and Europe (Spain). You can launch R7g and R8g instances for Neptune using the AWS Management Console or using the AWS CLI. Upgrading a Neptune cluster to R7g or R8g instances requires a simple instance type modification for Neptune engine versions 1.4.5 or higher. For more information on pricing and regional availability, refer to the Amazon Neptune pricing page.    

Starting today, you can use Amazon Route 53 Resolver DNS Firewall and DNS Firewall Advanced in the Asia Pacific (Thailand) and Mexico (Central) Regions, to govern and filter outbound DNS traffic for your Amazon Virtual Private Cloud (VPC).

Route 53 Resolver DNS Firewall is a managed service that enables you to block DNS queries made for domains identified as low-reputation or suspected to be malicious, and to allow queries for trusted domains. In addition, Route 53 Resolver DNS Firewall Advanced is a capability of DNS Firewall that allows you to detect and block DNS traffic associated with Domain Generation Algorithms (DGA) and DNS Tunneling threats. DNS Firewall can be enabled only for Route 53 Resolver, which is a recursive DNS server that is available by default in all Amazon Virtual Private Clouds (VPCs). The Route 53 Resolver responds to DNS queries from AWS resources within a VPC for public DNS records, VPC-specific domain names, and Route 53 private hosted zones.

See here for the list of AWS Regions where Route 53 Resolver DNS Firewall is available. Visit our product page and documentation to learn more about Amazon Route 53 Resolver DNS Firewall and its pricing.

 

​Starting today, you can use Amazon Route 53 Resolver DNS Firewall and DNS Firewall Advanced in the Asia Pacific (Thailand) and Mexico (Central) Regions, to govern and filter outbound DNS traffic for your Amazon Virtual Private Cloud (VPC). Route 53 Resolver DNS Firewall is a managed service that enables you to block DNS queries made for domains identified as low-reputation or suspected to be malicious, and to allow queries for trusted domains. In addition, Route 53 Resolver DNS Firewall Advanced is a capability of DNS Firewall that allows you to detect and block DNS traffic associated with Domain Generation Algorithms (DGA) and DNS Tunneling threats. DNS Firewall can be enabled only for Route 53 Resolver, which is a recursive DNS server that is available by default in all Amazon Virtual Private Clouds (VPCs). The Route 53 Resolver responds to DNS queries from AWS resources within a VPC for public DNS records, VPC-specific domain names, and Route 53 private hosted zones. See here for the list of AWS Regions where Route 53 Resolver DNS Firewall is available. Visit our product page and documentation to learn more about Amazon Route 53 Resolver DNS Firewall and its pricing.  

Amazon Connect outbound campaigns now offers reporting on recipients and campaign executions along with additional metrics for tracking progress and troubleshooting issues. These capabilities are available in the Contact Lens dashboards and allow you to easily monitor campaign engagement by tracking total outreach against the total number of recipients targeted. You can drill down into your campaign and examine performance data for each campaign execution – for example, if you run a campaign every week for a month, you can drill down to view campaign performance for each week. You can also identify and resolve any delivery issues against each campaign – for example, out of the 20 delivery issues, you now know 12 had ineligible timezones, and 8 reached communication limit thresholds. The real-time campaigns dashboard shows the journey of your campaign, from how many recipients you targeted to how many you reached. All new metrics are also available through the GetMetricDataV2 API and Zero-ETL data lake for custom reporting or integrations with other data sources.

These enhanced outbound campaign analytics are available in all AWS regions where Amazon Connect outbound campaigns is available. For more information about outbound campaign analytics, consult the Amazon Connect Administrator Guide and Amazon Connect API Reference. To learn more about Amazon Connect Outbound Campaigns, please visit the outbound campaigns webpage.

 

​Amazon Connect outbound campaigns now offers reporting on recipients and campaign executions along with additional metrics for tracking progress and troubleshooting issues. These capabilities are available in the Contact Lens dashboards and allow you to easily monitor campaign engagement by tracking total outreach against the total number of recipients targeted. You can drill down into your campaign and examine performance data for each campaign execution – for example, if you run a campaign every week for a month, you can drill down to view campaign performance for each week. You can also identify and resolve any delivery issues against each campaign – for example, out of the 20 delivery issues, you now know 12 had ineligible timezones, and 8 reached communication limit thresholds. The real-time campaigns dashboard shows the journey of your campaign, from how many recipients you targeted to how many you reached. All new metrics are also available through the GetMetricDataV2 API and Zero-ETL data lake for custom reporting or integrations with other data sources. These enhanced outbound campaign analytics are available in all AWS regions where Amazon Connect outbound campaigns is available. For more information about outbound campaign analytics, consult the Amazon Connect Administrator Guide and Amazon Connect API Reference. To learn more about Amazon Connect Outbound Campaigns, please visit the outbound campaigns webpage.  

Model Distillation is the process of transferring knowledge from a more capable model (teacher) to a less capable one (student) with the goal to make the faster and cost-efficient student model as performant as the teacher for a specific use-case. With general availability, we now add support for the following new models: Amazon Nova Premier (teacher) and Nova Pro (student), Claude 3.5 Sonnet v2 (teacher), Llama 3.3 70B (teacher) and Llama 3.2 1B/3B (student). Amazon Bedrock Model Distillation now enables smaller models to accurately predict function calling for Agents use cases while helping to deliver substantially faster response times and lower operational costs. Distilled models in Amazon Bedrock are up to 500% faster and 75% less expensive than original models, with less than 2% accuracy loss for use cases like RAG. In addition to RAG use cases, Model Distillation also adds support for data augmentation for Agents use cases for function calling prediction.

Amazon Bedrock Model Distillation offers a single workflow that automates the process needed to generate teacher responses, adds data synthesis to improve teacher responses, and then trains the student model. Amazon Bedrock Model Distillation may choose to apply different data synthesis methods that are best suited for your use-case to create a distilled model that approximately matches the advanced model for the specific use-case. 

Learn more in our documentation, website, and blog.

 

​Model Distillation is the process of transferring knowledge from a more capable model (teacher) to a less capable one (student) with the goal to make the faster and cost-efficient student model as performant as the teacher for a specific use-case. With general availability, we now add support for the following new models: Amazon Nova Premier (teacher) and Nova Pro (student), Claude 3.5 Sonnet v2 (teacher), Llama 3.3 70B (teacher) and Llama 3.2 1B/3B (student). Amazon Bedrock Model Distillation now enables smaller models to accurately predict function calling for Agents use cases while helping to deliver substantially faster response times and lower operational costs. Distilled models in Amazon Bedrock are up to 500% faster and 75% less expensive than original models, with less than 2% accuracy loss for use cases like RAG. In addition to RAG use cases, Model Distillation also adds support for data augmentation for Agents use cases for function calling prediction. Amazon Bedrock Model Distillation offers a single workflow that automates the process needed to generate teacher responses, adds data synthesis to improve teacher responses, and then trains the student model. Amazon Bedrock Model Distillation may choose to apply different data synthesis methods that are best suited for your use-case to create a distilled model that approximately matches the advanced model for the specific use-case.  Learn more in our documentation, website, and blog.  

AWS B2B Data Interchange now offers customers the option to use Internet Protocol version 6 (IPv6) while accessing the AWS B2B Data Interchange Service APIs.

More and more customers are adopting IPv6 to mitigate IPv4 address exhaustion in their private networks or to satisfy government mandates such as the US Office of Management and Budget (OMB) M-21-07 memorandum. With this launch, customers can standardize their applications and workflows for managing their AWS B2B Data Interchange resources on the new version of Internet Protocol by using the new dual-stack AWS B2B Data Interchange Service endpoints.

IPv6 support for AWS B2B Data Interchange Service APIs is available in all commercial regions where AWS B2B Data Interchange is available. To learn more, visit the AWS B2B Data Interchange user guide.

 

​AWS B2B Data Interchange now offers customers the option to use Internet Protocol version 6 (IPv6) while accessing the AWS B2B Data Interchange Service APIs. More and more customers are adopting IPv6 to mitigate IPv4 address exhaustion in their private networks or to satisfy government mandates such as the US Office of Management and Budget (OMB) M-21-07 memorandum. With this launch, customers can standardize their applications and workflows for managing their AWS B2B Data Interchange resources on the new version of Internet Protocol by using the new dual-stack AWS B2B Data Interchange Service endpoints. IPv6 support for AWS B2B Data Interchange Service APIs is available in all commercial regions where AWS B2B Data Interchange is available. To learn more, visit the AWS B2B Data Interchange user guide.  

Amazon Connect Contact Lens now include a pre-configured agent adherence widget which supports filtering and sorting on agent adherence metrics, making day-to-day adherence management more efficient for supervisors. With this launch, supervisors can apply filters on adherence status, duration, and percentage; sort by duration or percentage; and apply conditional formatting within the agent adherence widget on the queue and agent performance dashboard. For example, a supervisor can highlight agents who have been falling behind schedule for more than 5 minutes, quickly identify breaches, and notify the agents accordingly. With this widget, supervisors can simplify the process of monitoring adherence, improving productivity, and enabling faster response times to adherence issues.

This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about this feature, see the Queue and agent performance dashboard in Amazon Connect.

 

​Amazon Connect Contact Lens now include a pre-configured agent adherence widget which supports filtering and sorting on agent adherence metrics, making day-to-day adherence management more efficient for supervisors. With this launch, supervisors can apply filters on adherence status, duration, and percentage; sort by duration or percentage; and apply conditional formatting within the agent adherence widget on the queue and agent performance dashboard. For example, a supervisor can highlight agents who have been falling behind schedule for more than 5 minutes, quickly identify breaches, and notify the agents accordingly. With this widget, supervisors can simplify the process of monitoring adherence, improving productivity, and enabling faster response times to adherence issues. This feature is available in all AWS Regions where Amazon Connect agent scheduling is available. To learn more about this feature, see the Queue and agent performance dashboard in Amazon Connect.  

Today, AWS announced managed support for Energy Data Insights (EDI) on AWS – delivered through AWS Managed Service (AMS), which enables energy customers to easily deploy, manage, and operate their subsurface data management platform on AWS, in compliance with the (OSDU®) standard. Now, you can automatically deploy EDI on AWS and accelerate your data ingestion from weeks to hours, and intelligently process and organize your subsurface data with minimal manual effort. AWS extends your team with operational capabilities, allowing you to focus on innovation and accelerating time to value with your subsurface data.

With AWS-provided managed support, EDI on AWS removes the undifferentiated heavy-lifting and the complexities of deploying, operating, and maintaining an OSDU Data Platform on AWS, optimizing your EDI operations and security while ensuring round-the-clock availability and protection of the service. AWS handles critical operations on your behalf such as incident management, and backup and restore, significantly improving the resilience of your OSDU Data Platform on AWS. You also receive timely support for application upgrades and patches, allowing you to stay current with the latest features and improvements.

EDI on AWS is available with pay-as-you-go pricing in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Ireland), Europe (Paris), and South America (São Paulo).

To learn more about EDI, visit the Product Detail page.

 

​Today, AWS announced managed support for Energy Data Insights (EDI) on AWS – delivered through AWS Managed Service (AMS), which enables energy customers to easily deploy, manage, and operate their subsurface data management platform on AWS, in compliance with the (OSDU®) standard. Now, you can automatically deploy EDI on AWS and accelerate your data ingestion from weeks to hours, and intelligently process and organize your subsurface data with minimal manual effort. AWS extends your team with operational capabilities, allowing you to focus on innovation and accelerating time to value with your subsurface data.
With AWS-provided managed support, EDI on AWS removes the undifferentiated heavy-lifting and the complexities of deploying, operating, and maintaining an OSDU Data Platform on AWS, optimizing your EDI operations and security while ensuring round-the-clock availability and protection of the service. AWS handles critical operations on your behalf such as incident management, and backup and restore, significantly improving the resilience of your OSDU Data Platform on AWS. You also receive timely support for application upgrades and patches, allowing you to stay current with the latest features and improvements.
EDI on AWS is available with pay-as-you-go pricing in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Ireland), Europe (Paris), and South America (São Paulo).
To learn more about EDI, visit the Product Detail page.  

Amazon Q Developer in chat applications now supports AWS Systems Manager just-in-time node access approvals from Microsoft Teams and Slack. AWS customers can now monitor node access requests and approvals from chat channels to enhance security posture and meet compliance requirements.

The Just-in-time node access provides customers policy-based time-bound access to nodes and helps them comply with zero-standing privileges operations model. This launch provides a seamless integration for managing Just-in-time access request approvals in chat applications.

When configuring Just-in-time approval policies, customers can designate Amazon SNS topics associated with Amazon Q Developer in chat applications configurations for managing node access approval requests. As operators make new node access requests, approvers are notified about the requests in the chat channels. They can then approve or reject access requests directly from the chat channel.

Systems Manager node access approval management in chat applications is available at no additional cost in AWS Regions where Amazon Q Developer and System Manager Just-in-time node access are offered. Visit the user guide and Systems Manager pricing to get started.

 

​Amazon Q Developer in chat applications now supports AWS Systems Manager just-in-time node access approvals from Microsoft Teams and Slack. AWS customers can now monitor node access requests and approvals from chat channels to enhance security posture and meet compliance requirements. The Just-in-time node access provides customers policy-based time-bound access to nodes and helps them comply with zero-standing privileges operations model. This launch provides a seamless integration for managing Just-in-time access request approvals in chat applications. When configuring Just-in-time approval policies, customers can designate Amazon SNS topics associated with Amazon Q Developer in chat applications configurations for managing node access approval requests. As operators make new node access requests, approvers are notified about the requests in the chat channels. They can then approve or reject access requests directly from the chat channel. Systems Manager node access approval management in chat applications is available at no additional cost in AWS Regions where Amazon Q Developer and System Manager Just-in-time node access are offered. Visit the user guide and Systems Manager pricing to get started.