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.

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 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  

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 is now available in all AWS commercial Regions. To learn more about configuring Amazon Data Lifecycle Manager endpoints for IPv6, please refer to our documentation.

Amazon Data Lifecycle Manager now supports https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html to connect directly to the Amazon Data Lifecycle Manager APIs in your virtual private cloud (VPC) instead of connecting over the internet. Customers create Amazon Data Lifecycle Manager policies to automate the creation, retention, and management of EBS Snapshots and EBS-backed Amazon Machine Images (AMIs). When you use AWS PrivateLink to access Amazon Data Lifecycle Manager APIs, communication between your VPC and Amazon Data Lifecycle Manager API is conducted privately within the AWS network, providing a secure pathway for your data. An AWS PrivateLink endpoint connects your VPC directly to the Amazon Data Lifecycle Manager API. This feature is available in all AWS Regions where Amazon Data Lifecycle Manager is available. You can create an AWS PrivateLink to connect to Amazon Data Lifecycle Manager using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands. To learn more about using AWS PrivateLink, please refer to our https://docs.aws.amazon.com/ebs/latest/userguide/dlm-vpc-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 is now available in all AWS commercial 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.  

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.

You can now use Amazon EBS Local Snapshots 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. Customers use EBS Snapshots to back up their EBS volumes for disaster recovery, data migration, and compliance purposes. With Local Snapshots, you can now create backups of your EBS volumes in Dedicated Local Zones and store them within the same geographical boundary as your EBS volumes, helping you meet your data isolation and data residency use cases. You can also create Identity and Access Management (IAM) policies for your account to enforce that snapshots are stored within the Dedicated Local Zone. Additionally, you can use Amazon Data Lifecycle Manager (DLM) to automate the creation and retention of local snapshots. Local Snapshots are available through the AWS Console, AWS Command Line Interface (CLI), and AWS SDKs. To learn more, see the https://docs.aws.amazon.com/ebs/latest/userguide/snapshots-localzones.html on Local Snapshots.

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.

Today, Amazon Elastic Block Store (Amazon EBS), a high-performance block storage service, announces the general availability of Time-based Copy. This new feature helps you meet your business and compliance requirements by ensuring that your EBS Snapshots are copied within and across AWS Regions within a specified timeframe. Customers use EBS Snapshots to back up their EBS volumes, and copy them across multiple AWS Regions and accounts, for disaster recovery, data migration and compliance purposes. Time-based Copy gives you predictability when copying your snapshots across Regions. With this feature, you can specify a desired completion duration, ranging from 15 minutes to 48 hours, for individual copy requests, ensuring that your EBS Snapshots meet their duration requirements or Recovery Point Objectives (RPOs). You can now also monitor your Copy operations via EventBridge and the new SnapshotCopyBytesTransferred CloudWatch metric, available by default at a 1-minute frequency at no additional charge. Amazon EBS Time-based Copy is available in all AWS commercial Regions and the AWS GovCloud (US) Regions, through the AWS Console, AWS Command Line Interface (CLI), and AWS SDKs. For pricing information, please visit the https://aws.amazon.com/ebs/pricing/. To learn more, see the technical documentation for Time-based Copy for https://docs.aws.amazon.com/ebs/latest/userguide/time-based-copies.html.  

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 Elastic Block Store (Amazon EBS) now supports additional resource-level permissions for creating https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volumes.html from https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html. 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 https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVolume.html 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 usehttps://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 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 https://aws.amazon.com/blogs/storage/enhancing-resource-level-permission-for-creating-an-amazon-ebs-volume-from-a-snapshot/. For more information about Amazon EBS, please visit the https://aws.amazon.com/ebs/.

Amazon Elastic Block Store (Amazon EBS) now displays the full snapshot size for EBS Snapshots. With this enhancement, customers can now retrieve full snapshot sizes programmatically through the DescribeSnapshots API using the new field, full-snapshot-size-in-bytes. The full snapshot size is also displayed in the EBS Snapshots console under the new 'Full snapshot size' column. Since EBS Snapshots are incremental in nature, if you take multiple snapshots of a volume over time, each snapshot only stores the new or modified blocks while maintaining references to unchanged blocks from previous snapshots. The ‘full snapshot size’ field shows you the total size of all blocks that make up a snapshot, including both the blocks stored directly in that snapshot and all blocks referenced from previous snapshots. For instance, if you have a 100 GB volume with 50 GB of data, the ‘full snapshot size’ would show 50 GB regardless of whether it's the first snapshot or a subsequent one. The ‘full snapshot size’ field provides crucial information about your EBS snapshot storage, such as the total size of the snapshot in the archived tier or the amount of data written to the source volume at the time the snapshot was created. Please note that this is different from the incremental snapshot size, which only refers to the size of newly changed blocks stored in that specific snapshot. This feature is now generally available in all commercial AWS regions and the AWS GovCloud (US) Regions. To get started, see the EBS Snapshots user guide and API specification.

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/.  

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.

Customers can now further customize Recycle Bin rules to exclude EBS Snapshots and EBS-backed Amazon Machine Images (AMIs) based on tags. Customers use Recycle Bin to protect their resources from accidental deletion by retaining them for a time period that customers specify before being permanently deleted. The newly launched feature helps customers save cost by customizing their Recycle Bin rules for delete protection of only critical data in their resources, while excluding non-critical data that do not require delete protection. Creating Region-level retention rules is a simple way to have peace of mind that all EBS Snapshots and EBS-backed AMIs in an AWS Region are protected from accidental deletion by Recycle Bin. However, in some cases, customers have security scanning workflows that create temporary EBS Snapshots that are not used for recovery. Customers may also have backup automation that do not require additional delete protection. The newly added feature to add resource exclusion tags in Recycle Bin can help you reduce storage costs by excluding the resources that do not require deletion protection from moving to Recycle Bin. This feature is now available in all AWS commercial Regions and AWS GovCloud (US) Regions. Customers can add exclusion tags to their Recycle Bin rules via EC2 Console, API/CLI, or SDK. To learn more about using Recycle Bin with exclusion tags, please refer to the technical documentation.

With time-based copying, critical EBS snapshots and AMIs can now meet crucial RPOs by specifying exact completion durations from 15 minutes to 48 hours for disaster recovery, testing, development, and operations.

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 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.

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.

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) now displays the full snapshot size for EBS Snapshots. With this enhancement, customers can now retrieve full snapshot sizes programmatically through the DescribeSnapshots API using the new field, full-snapshot-size-in-bytes. The full snapshot size is also displayed in the EBS Snapshots console under the new 'Full snapshot size' column. Since EBS Snapshots are incremental in nature, if you take multiple snapshots of a volume over time, each snapshot only stores the new or modified blocks while maintaining references to unchanged blocks from previous snapshots. The ‘full snapshot size’ field shows you the total size of all blocks that make up a snapshot, including both the blocks stored directly in that snapshot and all blocks referenced from previous snapshots. For instance, if you have a 100 GB volume with 50 GB of data, the ‘full snapshot size’ would show 50 GB regardless of whether it's the first snapshot or a subsequent one. The ‘full snapshot size’ field provides crucial information about your EBS snapshot storage, such as the total size of the snapshot in the archived tier or the amount of data written to the source volume at the time the snapshot was created. Please note that this is different from the incremental snapshot size, which only refers to the size of newly changed blocks stored in that specific snapshot. This feature is now generally available in all commercial AWS regions and the AWS GovCloud (US) Regions. To get started, see the https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html and https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DescribeSnapshots.html.

Today, Amazon Elastic Block Store (Amazon EBS), a high-performance block storage service, announces the general availability of Time-based Copy. This new feature helps you meet your business and compliance requirements by ensuring that your EBS Snapshots are copied within and across AWS Regions within a specified timeframe. Customers use EBS Snapshots to back up their EBS volumes, and copy them across multiple AWS Regions and accounts, for disaster recovery, data migration and compliance purposes. Time-based Copy gives you predictability when copying your snapshots across Regions. With this feature, you can specify a desired completion duration, ranging from 15 minutes to 48 hours, for individual copy requests, ensuring that your EBS Snapshots meet their duration requirements or Recovery Point Objectives (RPOs). You can now also monitor your Copy operations via EventBridge and the new SnapshotCopyBytesTransferred CloudWatch metric, available by default at a 1-minute frequency at no additional charge. Amazon EBS Time-based Copy is available in all AWS commercial Regions and the AWS GovCloud (US) Regions, through the AWS Console, AWS Command Line Interface (CLI), and AWS SDKs. For pricing information, please visit the EBS pricing page. To learn more, see the technical documentation for Time-based Copy for Snapshots.

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.