Amazon EBS now provides additional visibility to monitor the average IOPS and average throughput of your Amazon EBS volumes with two new CloudWatch metrics - VolumeAvgIOPS and VolumeAvgThroughput. You can use the metrics to monitor the I/O being driven on your EBS volumes to track performance trends. With these new volume level metrics, you can troubleshoot performance bottlenecks and optimize your volume’s provisioned performance to meet your application needs. The metrics will provide per-minute visibility into the driven average IOPS and average throughput on your EBS volume. With Amazon CloudWatch, you can use the new metrics to create customized dashboards and set alarms that notify you or automatically perform actions based on the metrics. The VolumeAvgIOPS and VolumeAvgThroughput metrics are available by default at a 1-minute frequency at no additional charge and are supported for all EBS volumes attached to an EC2 Nitro instance in all Commercial AWS Regions, including the AWS GovCloud (US) Regions and AWS China Regions. To learn more about these new metrics, please visit the https://docs.aws.amazon.com/ebs/latest/userguide/using_cloudwatch_ebs.html.

Amazon EBS now provides additional visibility to monitor the average IOPS and average throughput of your Amazon EBS volumes with two new CloudWatch metrics - VolumeAvgIOPS and VolumeAvgThroughput. You can use the metrics to monitor the I/O being driven on your EBS volumes to track performance trends. With these new volume level metrics, you can troubleshoot performance bottlenecks and optimize your volume’s provisioned performance to meet your application needs. The metrics will provide per-minute visibility into the driven average IOPS and average throughput on your EBS volume. With Amazon CloudWatch, you can use the new metrics to create customized dashboards and set alarms that notify you or automatically perform actions based on the metrics. The VolumeAvgIOPS and VolumeAvgThroughput metrics are available by default at a 1-minute frequency at no additional charge and are supported for all EBS volumes attached to an EC2 Nitro instance in all Commercial AWS Regions, including the AWS GovCloud (US) Regions and AWS China Regions. To learn more about these new metrics, please visit the EBS CloudWatch Metrics documentation.

Today, Amazon announced two new Amazon CloudWatch metrics that provide insight into when your application exceeds the I/O performance limits for your EC2 instance with attached EBS volumes. These two metrics, Instance EBS IOPS Exceeded Check and Instance EBS Throughput Exceeded Check, monitor if the driven IOPS or throughput is exceeding the maximum EBS IOPS or throughput that your instance can support. With these two new metrics at the instance level, you can quickly identify and respond to application performance issues stemming from exceeding the https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-optimized.html. These metrics will return a value of 0 (performance not exceeded) or a 1 (performance exceeded) when your workload is exceeding the EBS-Optimized IOPS or throughput limit of the EC2 instance. With Amazon CloudWatch, you can use these new metrics to create customized dashboards and set alarms that notify you or automatically perform actions based on these metrics, such as moving to a larger instance size or a different instance type that supports higher EBS-Optimized limits. The Instance EBS IOPS Exceeded Check and Instance EBS Throughput Exceeded Check metrics are available by default at a 1-minute frequency at no additional charges, for all Nitro-based Amazon EC2 instances with EBS volumes attached. You can access these metrics via the EC2 console, CLI, or CloudWatch API in all Commercial AWS Regions, including the AWS GovCloud (US) Regions and China Regions. To learn more about these CloudWatch metrics, please visit the https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html#ebs-metrics-nitro.

Today, Amazon announced two new Amazon CloudWatch metrics that provide insight into when your application exceeds the I/O performance limits for your EC2 instance with attached EBS volumes. These two metrics, Instance EBS IOPS Exceeded Check and Instance EBS Throughput Exceeded Check, monitor if the driven IOPS or throughput is exceeding the maximum EBS IOPS or throughput that your instance can support. With these two new metrics at the instance level, you can quickly identify and respond to application performance issues stemming from exceeding the EBS-Optimized limits of your instance. These metrics will return a value of 0 (performance not exceeded) or a 1 (performance exceeded) when your workload is exceeding the EBS-Optimized IOPS or throughput limit of the EC2 instance. With Amazon CloudWatch, you can use these new metrics to create customized dashboards and set alarms that notify you or automatically perform actions based on these metrics, such as moving to a larger instance size or a different instance type that supports higher EBS-Optimized limits. The Instance EBS IOPS Exceeded Check and Instance EBS Throughput Exceeded Check metrics are available by default at a 1-minute frequency at no additional charges, for all Nitro-based Amazon EC2 instances with EBS volumes attached. You can access these metrics via the EC2 console, CLI, or CloudWatch API in all Commercial AWS Regions, including the AWS GovCloud (US) Regions and China Regions. To learn more about these CloudWatch metrics, please visit the EC2 CloudWatch Metrics documentation.

I’ve been inspired by all the activities that tech communities around the world have been hosting and participating in throughout the year. Here in the southern hemisphere we’re starting to dream about our upcoming summer breaks and closing out on some of the activities we’ve initiated this year. The tech community in South Africa is […]

AWS launched Amazon EBS Volume Clones, a new capability that allows users to create instant point-in-time copies of EBS volumes within the same Availability Zone with a single API call, eliminating the previous multi-step process of taking snapshots and creating volumes from them.

Amazon EBS io2 Block Express volumes are now available in Amazon Web Services China (Beijing) Region, operated by Sinnet and Amazon Web Services China (Ningxia) Region, operated by NWCD. io2 Block Express leverage the latest generation of EBS storage server architecture designed to deliver consistent sub-millisecond latency and 99.999% durability. With a single io2 Block Express volume, you can achieve 256,000 IOPS, 4GiB/s throughput, and 64TiB storage capacity. You can also attach an io2 Block Express volume to multiple instances in the same Availability Zone, supporting shared storage fencing through NVMe reservations for improved application availability and scalability. With the lowest p99.9 I/O latency among major cloud providers, io2 Block Express is the ideal choice for the most I/O-intensive, mission-critical deployments such as SAP HANA, Oracle, SQL Server, and IBM DB2. Customers using io1 volumes can upgrade to io2 Block Express without any downtime using the https://docs.amazonaws.cn/en_us/ebs/latest/userguide/ebs-modify-volume.html API to achieve 100x durability, consistent sub-millisecond latency, and significantly higher performance at the same or lower cost than io1. With io2 Block Express, you can drive up to 4x IOPS and 4x throughput at the same storage price as io1, and up to 50% cheaper IOPS cost for volumes over 32,000 IOPS. io2 Block Express is now available in all the Amazon Web Services regions. You can create and manage io2 Block Express volumes using the Amazon Web Services Management Console, Amazon Command Line Interface (CLI), or Amazon SDKs. For more information on io2 Block Express, see our https://docs.amazonaws.cn/en_us/ebs/latest/userguide/provisioned-iops.html#io2-block-express.

Amazon EBS io2 Block Express volumes are now available in Amazon Web Services China (Beijing) Region, operated by Sinnet and Amazon Web Services China (Ningxia) Region, operated by NWCD. io2 Block Express leverage the latest generation of EBS storage server architecture designed to deliver consistent sub-millisecond latency and 99.999% durability. With a single io2 Block Express volume, you can achieve 256,000 IOPS, 4GiB/s throughput, and 64TiB storage capacity. You can also attach an io2 Block Express volume to multiple instances in the same Availability Zone, supporting shared storage fencing through NVMe reservations for improved application availability and scalability. With the lowest p99.9 I/O latency among major cloud providers, io2 Block Express is the ideal choice for the most I/O-intensive, mission-critical deployments such as SAP HANA, Oracle, SQL Server, and IBM DB2. Customers using io1 volumes can upgrade to io2 Block Express without any downtime using the ModifyVolume API to achieve 100x durability, consistent sub-millisecond latency, and significantly higher performance at the same or lower cost than io1. With io2 Block Express, you can drive up to 4x IOPS and 4x throughput at the same storage price as io1, and up to 50% cheaper IOPS cost for volumes over 32,000 IOPS. io2 Block Express is now available in all the Amazon Web Services regions. You can create and manage io2 Block Express volumes using the Amazon Web Services Management Console, Amazon Command Line Interface (CLI), or Amazon SDKs. For more information on io2 Block Express, see our tech documentation.

Amazon Elastic Block Store (Amazon EBS) now supports higher volume-level limits for its General Purpose (gp3) volumes. With this update, gp3 volumes can scale up to 64 TiB in size (4X the previous 16 TiB limit), up to 80,000 IOPS (5X the previous 16,000 IOPS limit), and up to 2,000 MiB/s throughput (2X the previous 1,000 MiB/s limit). These expanded limits help reduce operational complexity for storage-intensive workloads by enabling gp3 volumes with larger capacity and higher performance. You can consolidate multiple striped volumes into a single gp3 volume, streamline architectures, and lower management overhead. The increased limits particularly benefit customers running containerized workloads with limited support for striping multiple volumes, applications that rely on single-volume architectures, and growing workloads approaching current gp3 limits. The pricing model remains unchanged: you pay for storage plus any additional IOPS and throughput provisioned beyond the baseline performance. The new gp3 limits are available in all AWS Commercial Regions and AWS GovCloud (US) Regions where gp3 volumes are available. To get started and learn more, please visit the https://docs.aws.amazon.com/ebs/latest/userguide/general-purpose.html.

Amazon Elastic Block Store (Amazon EBS) now supports higher volume-level limits for its General Purpose (gp3) volumes. With this update, gp3 volumes can scale up to 64 TiB in size (4X the previous 16 TiB limit), up to 80,000 IOPS (5X the previous 16,000 IOPS limit), and up to 2,000 MiB/s throughput (2X the previous 1,000 MiB/s limit). These expanded limits help reduce operational complexity for storage-intensive workloads by enabling gp3 volumes with larger capacity and higher performance. You can consolidate multiple striped volumes into a single gp3 volume, streamline architectures, and lower management overhead. The increased limits particularly benefit customers running containerized workloads with limited support for striping multiple volumes, applications that rely on single-volume architectures, and growing workloads approaching current gp3 limits. The pricing model remains unchanged: you pay for storage plus any additional IOPS and throughput provisioned beyond the baseline performance. The new gp3 limits are available in all AWS Commercial Regions and AWS GovCloud (US) Regions where gp3 volumes are available. To get started and learn more, please visit the Amazon EBS user guide.

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 https://docs.aws.amazon.com/ebs/latest/userguide/ebs-copy-snapshot.html.

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.

Today, AWS Transform introduced three enhancements to help you better assess and plan your migration and modernization journey. These new features include enhanced assessments to analyze EBS cost, .NET agent to analyze code complexity, and an expanded interactive chat interface for .NET modernization guidance. First, AWS Transform assessments now includes Amazon Elastic Block Storage (EBS) cost analysis, enabling you to better understand and plan for storage costs in your migration initiatives. This enhancement helps you make more informed decisions about resource allocation and budget planning for your transformation projects. Second, AWS Transform for .NET now supports enhanced code assessment capabilities that help you accelerate modernization planning with greater confidence, efficiency, and time savings. You can view repository transformation complexity, receive transformation group recommendations, and view transformation assessment reports with natural language summaries, all within a single, unified experience. Finally, AWS Transform now expands chat capability to provide an interactive chat experience that allows you to query specific aspects of your assessment and .NET transformation progress in natural language. You can quickly access relevant information about your modernization journey, get clarification on recommendations, and receive contextual guidance for specific use cases. These new features are now available in the following https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/: US East (N. Virginia) and Europe (Frankfurt). To learn more, visit the https://docs.aws.amazon.com/transform/latest/userguide/what-is-service.html and the https://aws.amazon.com/transform/faq.

Today, AWS Transform introduced three enhancements to help you better assess and plan your migration and modernization journey. These new features include enhanced assessments to analyze EBS cost, .NET agent to analyze code complexity, and an expanded interactive chat interface for .NET modernization guidance. First, AWS Transform assessments now includes Amazon Elastic Block Storage (EBS) cost analysis, enabling you to better understand and plan for storage costs in your migration initiatives. This enhancement helps you make more informed decisions about resource allocation and budget planning for your transformation projects. Second, AWS Transform for .NET now supports enhanced code assessment capabilities that help you accelerate modernization planning with greater confidence, efficiency, and time savings. You can view repository transformation complexity, receive transformation group recommendations, and view transformation assessment reports with natural language summaries, all within a single, unified experience. Finally, AWS Transform now expands chat capability to provide an interactive chat experience that allows you to query specific aspects of your assessment and .NET transformation progress in natural language. You can quickly access relevant information about your modernization journey, get clarification on recommendations, and receive contextual guidance for specific use cases. These new features are now available in the following AWS Regions: US East (N. Virginia) and Europe (Frankfurt). To learn more, visit the AWS Transform user guide and the frequently asked questions page.

You can now use Amazon EBS General Purpose SSD volumes (gp3) volumes with the second-generation AWS Outposts racks for your workloads that require local data processing and data residency. The latest generation of gp3 enables you to provision performance independently of storage capacity, delivering a baseline performance of 3,000 IOPS and 125 MB/s at any volume size. With gp3 volumes, you can scale up to 16,000 IOPS and 1,000 MB/s, delivering 4x the maximum throughput of the previously supported gp2 volumes. EBS gp3 volumes on second-generation AWS Outposts are ideal for a wide variety of performance-intensive applications, including MySQL, Cassandra, virtual desktops, and Hadoop analytics clusters. AWS Outposts racks offer the same AWS infrastructure, AWS services, APIs, and tools to virtually any on-premises data center or colocation space for a truly consistent hybrid experience. Second-generation AWS Outposts racks support the latest generation of x86-powered Amazon Elastic Compute Cloud (Amazon EC2) instances, starting with C7i, M7i, and R7i instances. These instances deliver twice the vCPU, memory, and network bandwidth, as well as up to 40% better performance compared to C5, M5, and R5 instances on first-generation AWS Outposts racks. You can manage gp3 volumes using the AWS Management Console, the AWS Command Line Interface (CLI), or the AWS SDKs in all Regions and countries/territories where second-generation AWS Outposts racks are supported. For more information on gp3 volumes, see the https://aws.amazon.com/ebs/volume-types/. For a current list of AWS Regions and countries/territories where second-generation AWS Outposts racks are supported, check out the https://aws.amazon.com/outposts/rack/faqs/#product-faqs%23in-which-countries-and-territories-is-outposts-rack-available-trigger  

You can now use Amazon EBS General Purpose SSD volumes (gp3) volumes with the second-generation AWS Outposts racks for your workloads that require local data processing and data residency. The latest generation of gp3 enables you to provision performance independently of storage capacity, delivering a baseline performance of 3,000 IOPS and 125 MB/s at any volume size. With gp3 volumes, you can scale up to 16,000 IOPS and 1,000 MB/s, delivering 4x the maximum throughput of the previously supported gp2 volumes. EBS gp3 volumes on second-generation AWS Outposts are ideal for a wide variety of performance-intensive applications, including MySQL, Cassandra, virtual desktops, and Hadoop analytics clusters. AWS Outposts racks offer the same AWS infrastructure, AWS services, APIs, and tools to virtually any on-premises data center or colocation space for a truly consistent hybrid experience. Second-generation AWS Outposts racks support the latest generation of x86-powered Amazon Elastic Compute Cloud (Amazon EC2) instances, starting with C7i, M7i, and R7i instances. These instances deliver twice the vCPU, memory, and network bandwidth, as well as up to 40% better performance compared to C5, M5, and R5 instances on first-generation AWS Outposts racks. You can manage gp3 volumes using the AWS Management Console, the AWS Command Line Interface (CLI), or the AWS SDKs in all Regions and countries/territories where second-generation AWS Outposts racks are supported. For more information on gp3 volumes, see the product overview page. For a current list of AWS Regions and countries/territories where second-generation AWS Outposts racks are supported, check out the AWS Outposts racks FAQs page.

Amazon Data Lifecycle Manager now offers customers the option to use Internet Protocol version 6 (IPv6) addresses for their new and existing endpoints. Customers moving to IPv6 can simplify their networks stack by running their Data Lifecycle Manager dual-stack endpoints on a network supporting both IPv4 and IPv6, depending on the protocol used by their network and client. Customers create Amazon Data Lifecycle Manager policies to automate the creation, retention, and management of EBS Snapshots and EBS-backed Amazon Machine Images (AMIs). The policies can also automatically copy created resources across AWS Regions, move EBS Snapshots to EBS Snapshots Archive tier, and manage Fast Snapshot Restore. Customers can also create policies to automate creation and retention of application-consistent EBS Snapshots via pre and post-scripts, as well as create Default Policies for comprehensive protection for their account or AWS Organization. Amazon Data Lifecycle Manager with IPv6, supported in all AWS Commercial Regions, is now available in the AWS GovCloud (US) Regions. To learn more about configuring Amazon Data Lifecycle Manager endpoints for IPv6, please refer to our https://docs.aws.amazon.com/ebs/latest/userguide/dlm-service-endpoints.html.  

Amazon Data Lifecycle Manager now offers customers the option to use Internet Protocol version 6 (IPv6) addresses for their new and existing endpoints. Customers moving to IPv6 can simplify their networks stack by running their Data Lifecycle Manager dual-stack endpoints on a network supporting both IPv4 and IPv6, depending on the protocol used by their network and client. Customers create Amazon Data Lifecycle Manager policies to automate the creation, retention, and management of EBS Snapshots and EBS-backed Amazon Machine Images (AMIs). The policies can also automatically copy created resources across AWS Regions, move EBS Snapshots to EBS Snapshots Archive tier, and manage Fast Snapshot Restore. Customers can also create policies to automate creation and retention of application-consistent EBS Snapshots via pre and post-scripts, as well as create Default Policies for comprehensive protection for their account or AWS Organization. Amazon Data Lifecycle Manager with IPv6, supported in all AWS Commercial Regions, is now available in the AWS GovCloud (US) Regions. To learn more about configuring Amazon Data Lifecycle Manager endpoints for IPv6, please refer to our documentation.

Today, Amazon Elastic Block Store (Amazon EBS), a high-performance block storage service, announces the general availability of Provisioned Rate for Volume Initialization. This feature helps you create fully performant Amazon EBS volumes from Amazon EBS Snapshots with predictability, helping speed up Amazon EC2 Instance launches at scale, disaster recovery, and volume copy workflows. You can use Amazon EBS volumes as durable, block-level storage devices attached to Amazon EC2 instances. With Provisioned Rate for Volume Initialization, you can launch hundreds of instances from Amazon EBS-backed Amazon Machine Images (AMIs) at the same time and know that the attached volumes will be fully performant within a predictable amount of time. This minimizes the amount of time before workloads can fully utilize the underlying storage. You use the feature by specifying a volume initialization rate when creating new volumes from snapshots, launching new instances from Amazon EBS-backed AMIs, replacing root volumes of instances, and provisioning volumes using the Amazon EBS Container Storage Interface (CSI) driver. You can also specify the rate of volume initialization in Launch Templates, applying the same rate to all instances launched by the template. This feature is available in all AWS commercial Regions and the AWS GovCloud (US) Regions, through the AWS Console, AWS Command Line Interface (CLI), AWS SDKs, and AWS CloudFormation. For pricing information, please visit the https://aws.amazon.com/ebs/pricing/. To learn more, visit the https://aws.amazon.com/blogs/aws/accelerate-the-transfer-of-data-from-an-amazon-ebs-snapshot-to-a-new-ebs-volume and refer to the https://docs.aws.amazon.com/ebs/latest/userguide/initalize-volume.html.

Today, Amazon Elastic Block Store (Amazon EBS), a high-performance block storage service, announces the general availability of Provisioned Rate for Volume Initialization. This feature helps you create fully performant Amazon EBS volumes from Amazon EBS Snapshots with predictability, helping speed up Amazon EC2 Instance launches at scale, disaster recovery, and volume copy workflows. You can use Amazon EBS volumes as durable, block-level storage devices attached to Amazon EC2 instances. With Provisioned Rate for Volume Initialization, you can launch hundreds of instances from Amazon EBS-backed Amazon Machine Images (AMIs) at the same time and know that the attached volumes will be fully performant within a predictable amount of time. This minimizes the amount of time before workloads can fully utilize the underlying storage. You use the feature by specifying a volume initialization rate when creating new volumes from snapshots, launching new instances from Amazon EBS-backed AMIs, replacing root volumes of instances, and provisioning volumes using the Amazon EBS Container Storage Interface (CSI) driver. You can also specify the rate of volume initialization in Launch Templates, applying the same rate to all instances launched by the template. This feature is available in all AWS commercial Regions and the AWS GovCloud (US) Regions, through the AWS Console, AWS Command Line Interface (CLI), AWS SDKs, and AWS CloudFormation. For pricing information, please visit the EBS pricing page. To learn more, visit the AWS News Blog and refer to the technical documentation.

Amazon EBS introduces a new Provisioned Rate for Volume Initialization to accelerate data transfer from EBS snapshots to new EBS volumes by specifying a consistent volume initialization rate, improving workflow efficiency and predictability.

Amazon Elastic Block Store (Amazon EBS) now supports additional resource-level permissions for https://docs.aws.amazon.com/ebs/latest/userguide/ebs-copy-snapshot.html. When moving your data across Regions, accounts, and Availability Zones, you can copy any snapshot accessible to you to another Region or account, including snapshots created by you or shared with you. With this launch, you have more granular controls to set resource-level permissions for the snapshot copy and selection of the source snapshot. This allows you to control the IAM identities that can copy EBS snapshot from source snapshots, and the conditions that they can use these source snapshots for the snapshot copy operation. To meet your specific permission needs on the source snapshots, you can also specify any of 6 EC2-specific condition keys for your https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonec2.html action in your IAM policy: ec2:Encrypted, ec2:VolumeSize, ec2:Owner, ec2:ParentVolume, ec2:SnapshotTime, and ec2:ParentSnapshot. Additionally, you can use https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.html for the source snapshot. This new resource-level permission model is available in all AWS Regions where EBS snapshots are available. To learn more about using resource-level permissions to copy EBS snapshot, or transitioning to the new resource-level permission model from previous permission model, please visit the https://aws.amazon.com/blogs/storage/enhancing-resource-level-permissions-for-copying-amazon-ebs-snapshots/. For more information about Amazon EBS, please visit the https://aws.amazon.com/ebs/.

Amazon Elastic Block Store (Amazon EBS) now supports additional resource-level permissions for copying EBS snapshots. When moving your data across Regions, accounts, and Availability Zones, you can copy any snapshot accessible to you to another Region or account, including snapshots created by you or shared with you. With this launch, you have more granular controls to set resource-level permissions for the snapshot copy and selection of the source snapshot. This allows you to control the IAM identities that can copy EBS snapshot from source snapshots, and the conditions that they can use these source snapshots for the snapshot copy operation. To meet your specific permission needs on the source snapshots, you can also specify any of 6 EC2-specific condition keys for your CopySnapshot action in your IAM policy: ec2:Encrypted, ec2:VolumeSize, ec2:Owner, ec2:ParentVolume, ec2:SnapshotTime, and ec2:ParentSnapshot. 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 snapshots are available. To learn more about using resource-level permissions to copy EBS snapshot, 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.

You can now use Amazon EBS gp3 and io1 volumes in AWShttps://aws.amazon.com/dedicatedlocalzones/. Dedicated Local Zones are a type of AWS infrastructure that are fully managed by AWS, built for exclusive use by you or your community, and placed in a location or data center specified by you to help you comply with regulatory requirements. In Dedicated Local Zones, these volumes are purpose-built to store data in a specific data perimeter, helping to support your data isolation and data residency use cases. The latest generation of General Purpose SSD volumes (gp3) enable customers to provision performance independently of storage capacity, providing up to 20% lower price point per GB than existing gp2 volumes. Provisioned IOPS SSD (io1) volumes are designed to meet the needs of I/O-intensive and latency-sensitive transactional workloads like databases. You can manage gp3 and io1 volumes using the AWS Management Console, the AWS Command Line Interface (CLI), or the AWS SDKs. For more information on gp3 and io1 volumes, see the https://aws.amazon.com/ebs/volume-types/.  

You can now use Amazon EBS gp3 and io1 volumes in AWS Dedicated Local Zones. Dedicated Local Zones are a type of AWS infrastructure that are fully managed by AWS, built for exclusive use by you or your community, and placed in a location or data center specified by you to help you comply with regulatory requirements. In Dedicated Local Zones, these volumes are purpose-built to store data in a specific data perimeter, helping to support your data isolation and data residency use cases. The latest generation of General Purpose SSD volumes (gp3) enable customers to provision performance independently of storage capacity, providing up to 20% lower price point per GB than existing gp2 volumes. Provisioned IOPS SSD (io1) volumes are designed to meet the needs of I/O-intensive and latency-sensitive transactional workloads like databases. You can manage gp3 and io1 volumes using the AWS Management Console, the AWS Command Line Interface (CLI), or the AWS SDKs. For more information on gp3 and io1 volumes, see the product overview page.