AWS Identity and Access Management (IAM) now offers three new global condition keys that will make it easier for you to establish a network perimeter. The new condition keys – aws:VpceAccount, aws:VpceOrgPaths, and aws:VpceOrgID – help you ensure that requests to your AWS resources or by your identities are made through your VPC endpoints.

The condition keys provide you with varied levels of granularity, enabling you to implement your network perimeter controls at an account, organization path, and entire organization level. The controls automatically scale with your VPC usage, eliminating the need to enumerate VPC endpoints or update policies as you add or remove them. You can use these condition keys with both new and existing service control policies (SCPs), resource control policies (RCPs), resource-based policies, and identity-based policies.

The condition keys are supported for a select set of AWS services and are available in all commercial AWS Regions where those services support AWS PrivateLink.

To learn more about these new condition keys and supported services, please visit the AWS IAM documentation and AWS blog.

 

​AWS Identity and Access Management (IAM) now offers three new global condition keys that will make it easier for you to establish a network perimeter. The new condition keys – aws:VpceAccount, aws:VpceOrgPaths, and aws:VpceOrgID – help you ensure that requests to your AWS resources or by your identities are made through your VPC endpoints. The condition keys provide you with varied levels of granularity, enabling you to implement your network perimeter controls at an account, organization path, and entire organization level. The controls automatically scale with your VPC usage, eliminating the need to enumerate VPC endpoints or update policies as you add or remove them. You can use these condition keys with both new and existing service control policies (SCPs), resource control policies (RCPs), resource-based policies, and identity-based policies. The condition keys are supported for a select set of AWS services and are available in all commercial AWS Regions where those services support AWS PrivateLink. To learn more about these new condition keys and supported services, please visit the AWS IAM documentation and AWS blog.  

AWS HealthOmics introduces support for third-party container registries, enabled through Amazon Elastic Container Registry (ECR) pull-through cache, along with URI remapping rules for automatic translation of third-party container URIs to ECR URIs. This enhancement enables AWS HealthOmics customers to more easily access containerized tools from popular third-party registries without needing to manually migrate them to private ECR repositories, or make changes to the workflow definition. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows.

The ECR pull-through cache capability allows bioinformatics teams to automatically retrieve and cache containers from popular registries including Amazon ECR Public, Docker Hub, Quay, GitHub Container Registry, GitLab Container Registry, Kubernetes container image registry, and Microsoft Azure Container Registry. This helps customers accelerate workflow development and execution by eliminating manual container synchronization tasks. Additionally, the new container URI remapping feature automatically translates third-party registry references in workflow definitions to corresponding private ECR URIs using customer-defined mapping rules, eliminating the need to manually update workflow definitions when migrating workflows.

ECR pull-through cache and container URI remapping features are now supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv).

To learn more about these new features and how to implement them in your workflows, see the AWS HealthOmics documentation.

 

​AWS HealthOmics introduces support for third-party container registries, enabled through Amazon Elastic Container Registry (ECR) pull-through cache, along with URI remapping rules for automatic translation of third-party container URIs to ECR URIs. This enhancement enables AWS HealthOmics customers to more easily access containerized tools from popular third-party registries without needing to manually migrate them to private ECR repositories, or make changes to the workflow definition. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows. The ECR pull-through cache capability allows bioinformatics teams to automatically retrieve and cache containers from popular registries including Amazon ECR Public, Docker Hub, Quay, GitHub Container Registry, GitLab Container Registry, Kubernetes container image registry, and Microsoft Azure Container Registry. This helps customers accelerate workflow development and execution by eliminating manual container synchronization tasks. Additionally, the new container URI remapping feature automatically translates third-party registry references in workflow definitions to corresponding private ECR URIs using customer-defined mapping rules, eliminating the need to manually update workflow definitions when migrating workflows. ECR pull-through cache and container URI remapping features are now supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv). To learn more about these new features and how to implement them in your workflows, see the AWS HealthOmics documentation.  

Starting today, Amazon EC2 High Memory U7i instances with 12TB of memory (u7i-12tb.224xlarge) are now available in the US Asia Pacific (Seoul) region. U7i-12tb instances are part of AWS 7th generation and are powered by custom fourth generation Intel Xeon Scalable Processors (Sapphire Rapids). U7i-12tb instances offer 12TiB of DDR5 memory enabling customers to scale transaction processing throughput in a fast-growing data environment.

U7i-12tb instances offer 896 vCPUs, support up to 100Gbps Elastic Block Storage (EBS) for faster data loading and backups, deliver up to 100Gbps of network bandwidth, and support ENA Express. U7i instances are ideal for customers using mission-critical in-memory databases like SAP HANA, Oracle, and SQL Server.

To learn more about U7i instances, visit the High Memory instances page.

 

​Starting today, Amazon EC2 High Memory U7i instances with 12TB of memory (u7i-12tb.224xlarge) are now available in the US Asia Pacific (Seoul) region. U7i-12tb instances are part of AWS 7th generation and are powered by custom fourth generation Intel Xeon Scalable Processors (Sapphire Rapids). U7i-12tb instances offer 12TiB of DDR5 memory enabling customers to scale transaction processing throughput in a fast-growing data environment. U7i-12tb instances offer 896 vCPUs, support up to 100Gbps Elastic Block Storage (EBS) for faster data loading and backups, deliver up to 100Gbps of network bandwidth, and support ENA Express. U7i instances are ideal for customers using mission-critical in-memory databases like SAP HANA, Oracle, and SQL Server. To learn more about U7i instances, visit the High Memory instances page.  

AWS HealthOmics introduces support for the Nextflow time directive, which enables customers to set task level timeout controls to limit run duration for specific tasks. With this launch, customers can now set fine-grained controls for their Nextflow workflow tasks to enable automated run cancellation if specific tasks take longer than expected. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows.

The Nextflow time directive is now supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv).

To learn more about workflows and the Nextflow time directive support, see the AWS HealthOmics documentation.

 

​AWS HealthOmics introduces support for the Nextflow time directive, which enables customers to set task level timeout controls to limit run duration for specific tasks. With this launch, customers can now set fine-grained controls for their Nextflow workflow tasks to enable automated run cancellation if specific tasks take longer than expected. AWS HealthOmics is a HIPAA-eligible service that helps healthcare and life sciences customers accelerate scientific breakthroughs with fully managed biological data stores and workflows. The Nextflow time directive is now supported in all regions where AWS HealthOmics is available: US East (N. Virginia), US West (Oregon), Europe (Frankfurt, Ireland, London), Asia Pacific (Singapore), and Israel (Tel Aviv). To learn more about workflows and the Nextflow time directive support, see the AWS HealthOmics documentation.  

Administrators can now control the Model Context Protocol (MCP) servers installed in Amazon Q Developer client applications directly within the AWS console. This provides organizations with the granular control needed to manage external resources safely and effectively.

With this launch an admin has the ability to enable or disable the MCP functionality for all the Q Developer clients in that organization. This means if an administrator disables the functionality, then users will not be allowed to add any MCP servers, nor will any previously defined servers be initialized. Q Developer checks and applies admin settings at the start of each session, and also every 24 hours while the client is running.

MCP admin control support for Amazon Q Developer applies to the Amazon Q Developer CLI, and all Amazon Q Developer plugins: VSCode, JetBrains, Visual Studio, and Eclipse. Check out the documentation to learn more.

 

​Administrators can now control the Model Context Protocol (MCP) servers installed in Amazon Q Developer client applications directly within the AWS console. This provides organizations with the granular control needed to manage external resources safely and effectively. With this launch an admin has the ability to enable or disable the MCP functionality for all the Q Developer clients in that organization. This means if an administrator disables the functionality, then users will not be allowed to add any MCP servers, nor will any previously defined servers be initialized. Q Developer checks and applies admin settings at the start of each session, and also every 24 hours while the client is running. MCP admin control support for Amazon Q Developer applies to the Amazon Q Developer CLI, and all Amazon Q Developer plugins: VSCode, JetBrains, Visual Studio, and Eclipse. Check out the documentation to learn more.  

Amazon Elastic Block Store (Amazon EBS), a high-performance block storage service, announces the general availability of snapshot copy for AWS Local Zones. This new feature helps you meet your business and compliance requirements by ensuring that your EBS Snapshots are copied to the AWS Region or AWS Local Zone.

Snapshot copy copies a point-in-time local snapshot of an EBS volume and stores it in Amazon S3 in the Region or to another Local Zone. Customers use EBS Snapshots to back up their EBS volumes and copy them across multiple AWS Regions and Local Zones for disaster recovery, data migration, and compliance purposes.

Amazon EBS snapshot copy is available in Local Zones that support local snapshots through the AWS Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, see the technical documentation for snapshot copy.

 

​Amazon Elastic Block Store (Amazon EBS), a high-performance block storage service, announces the general availability of snapshot copy for AWS Local Zones. This new feature helps you meet your business and compliance requirements by ensuring that your EBS Snapshots are copied to the AWS Region or AWS Local Zone. Snapshot copy copies a point-in-time local snapshot of an EBS volume and stores it in Amazon S3 in the Region or to another Local Zone. Customers use EBS Snapshots to back up their EBS volumes and copy them across multiple AWS Regions and Local Zones for disaster recovery, data migration, and compliance purposes. Amazon EBS snapshot copy is available in Local Zones that support local snapshots through the AWS Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, see the technical documentation for snapshot copy.  

Starting today, customers can enable two new capabilities for their EC2 Mac Dedicated Hosts: Host Recovery and Reboot-based Host Maintenance. Host Recovery automatically detects potential hardware issues on Mac Dedicated Hosts and seamlessly migrates Mac instances to a new replacement host, minimizing disruption to workloads. Reboot-based Host Maintenance automatically stops and restarts instances on replacement hosts when scheduled maintenance events occur, eliminating the need for manual intervention during planned maintenance windows. Together, these features significantly enhance the reliability and manageability of EC2 Mac instances, delivering improved uptime for macOS workloads in the cloud while reducing operational overhead and the need for continuous monitoring.

These features are available across all EC2 Mac instance families, including both Intel (x86) and Apple silicon platforms. Customers can access this feature in all AWS regions where EC2 Mac instances are currently supported. To learn more about Host recovery, please visit the documentation here. To learn more about Host maintenance, please visit the documentation here. To learn more about EC2 Mac instances, click here.

 

​Starting today, customers can enable two new capabilities for their EC2 Mac Dedicated Hosts: Host Recovery and Reboot-based Host Maintenance. Host Recovery automatically detects potential hardware issues on Mac Dedicated Hosts and seamlessly migrates Mac instances to a new replacement host, minimizing disruption to workloads. Reboot-based Host Maintenance automatically stops and restarts instances on replacement hosts when scheduled maintenance events occur, eliminating the need for manual intervention during planned maintenance windows. Together, these features significantly enhance the reliability and manageability of EC2 Mac instances, delivering improved uptime for macOS workloads in the cloud while reducing operational overhead and the need for continuous monitoring.
These features are available across all EC2 Mac instance families, including both Intel (x86) and Apple silicon platforms. Customers can access this feature in all AWS regions where EC2 Mac instances are currently supported. To learn more about Host recovery, please visit the documentation here. To learn more about Host maintenance, please visit the documentation here. To learn more about EC2 Mac instances, click here.  

Amazon Connect now offers new generative text-to-speech voices enabling you to deliver natural, human-like, and expressive conversations with your customers. With this launch, you now have access to 20 different generative-enhanced voices across languages such as English, French, Spanish, German, and Italian. These voices can be used to deliver text-to-speech experiences like welcome messages, policy information, or even power your dynamic conversational AI experiences. These capabilities can be configured directly in the drag-and-drop flow designer using the “Set Voice” flow block or through public APIs.

These new capabilities are included in unlimited AI Amazon Connect pricing or available individually priced. To learn more, see the Amazon Connect Administrator Guide or Amazon Connect pricing page. These features are available in US East (N. Virginia), Europe (Frankfurt), and US West (Oregon). To learn more about Amazon Connect, the AWS cloud-based contact center, please visit the Amazon Connect website or to learn more about unlimited AI in Amazon Connect read our blog post.

 

​Amazon Connect now offers new generative text-to-speech voices enabling you to deliver natural, human-like, and expressive conversations with your customers. With this launch, you now have access to 20 different generative-enhanced voices across languages such as English, French, Spanish, German, and Italian. These voices can be used to deliver text-to-speech experiences like welcome messages, policy information, or even power your dynamic conversational AI experiences. These capabilities can be configured directly in the drag-and-drop flow designer using the “Set Voice” flow block or through public APIs. These new capabilities are included in unlimited AI Amazon Connect pricing or available individually priced. To learn more, see the Amazon Connect Administrator Guide or Amazon Connect pricing page. These features are available in US East (N. Virginia), Europe (Frankfurt), and US West (Oregon). To learn more about Amazon Connect, the AWS cloud-based contact center, please visit the Amazon Connect website or to learn more about unlimited AI in Amazon Connect read our blog post.  

AWS is announcing the general availability of new general-purpose Amazon EC2 M8i and M8i-flex instances. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, delivering the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. The M8i and M8i-flex instances offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances. They deliver up to 20% better performance than M7i and M7i-flex instances, with even higher gains for specific workloads. The M8i and M8i-flex instances are up to 30% faster for PostgreSQL databases, up to 60% faster for NGINX web applications, and up to 40% faster for AI deep learning recommendation models compared to M7i and M7i-flex instances.

M8i-flex are the easiest way to get price performance benefits for a majority of general-purpose workloads like web and application servers, microservices, small and medium data stores, virtual desktops, and enterprise applications. They offer the most common sizes, from large to 16xlarge, and are a great first choice for applications that don’t fully utilize all compute resources.

M8i instances are a great choice for all general purpose workloads, especially for workloads that need the largest instance sizes or continuous high CPU usage. The SAP-certified M8i instances offer 13 sizes including 2 bare metal sizes and the new 96xlarge size for the largest applications.

M8i and M8i-flex instances are available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), and Europe (Spain).

To get started, sign in to the AWS Management Console. Customers can purchase these instances via Savings Plans, On-Demand instances, and Spot instances. For more information about the new M8i and M8i-flex instances visit the AWS News blog.

Product Tag(s): Amazon EC2, Intel Xeon 6 processor, M8i instance, M8i-flex instance.

 

​AWS is announcing the general availability of new general-purpose Amazon EC2 M8i and M8i-flex instances. These instances are powered by custom Intel Xeon 6 processors, available only on AWS, delivering the highest performance and fastest memory bandwidth among comparable Intel processors in the cloud. The M8i and M8i-flex instances offer up to 15% better price-performance, and 2.5x more memory bandwidth compared to previous generation Intel-based instances. They deliver up to 20% better performance than M7i and M7i-flex instances, with even higher gains for specific workloads. The M8i and M8i-flex instances are up to 30% faster for PostgreSQL databases, up to 60% faster for NGINX web applications, and up to 40% faster for AI deep learning recommendation models compared to M7i and M7i-flex instances. M8i-flex are the easiest way to get price performance benefits for a majority of general-purpose workloads like web and application servers, microservices, small and medium data stores, virtual desktops, and enterprise applications. They offer the most common sizes, from large to 16xlarge, and are a great first choice for applications that don’t fully utilize all compute resources. M8i instances are a great choice for all general purpose workloads, especially for workloads that need the largest instance sizes or continuous high CPU usage. The SAP-certified M8i instances offer 13 sizes including 2 bare metal sizes and the new 96xlarge size for the largest applications. M8i and M8i-flex instances are available in the following AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), and Europe (Spain). To get started, sign in to the AWS Management Console. Customers can purchase these instances via Savings Plans, On-Demand instances, and Spot instances. For more information about the new M8i and M8i-flex instances visit the AWS News blog. Product Tag(s): Amazon EC2, Intel Xeon 6 processor, M8i instance, M8i-flex instance.  

Amazon Virtual Private Cloud (Amazon VPC) Traffic Mirroring is now supported on additional instance types. Amazon VPC Traffic Mirroring allows you to replicate the network traffic from EC2 instances within your VPC to security and monitoring appliances for use cases such as content inspection, threat monitoring, and troubleshooting.

With this release, VPC Traffic Mirroring can be enabled on all Nitro v4 instances. You can see the complete list of instances that support VPC Traffic Mirroring in our documentation. You can see the complete list of instances built on different Nitro system versions in our AWS Nitro Systems documentation.

VPC Traffic Mirroring is supported on these additional instance types in all regions. To learn more about VPC Traffic Mirroring, please visit the VPC Traffic Mirroring documentation. 

 

​Amazon Virtual Private Cloud (Amazon VPC) Traffic Mirroring is now supported on additional instance types. Amazon VPC Traffic Mirroring allows you to replicate the network traffic from EC2 instances within your VPC to security and monitoring appliances for use cases such as content inspection, threat monitoring, and troubleshooting. With this release, VPC Traffic Mirroring can be enabled on all Nitro v4 instances. You can see the complete list of instances that support VPC Traffic Mirroring in our documentation. You can see the complete list of instances built on different Nitro system versions in our AWS Nitro Systems documentation. VPC Traffic Mirroring is supported on these additional instance types in all regions. To learn more about VPC Traffic Mirroring, please visit the VPC Traffic Mirroring documentation.