Amazon ECS and AWS Fargate now integrate with Amazon EBS

[Amazon Elastic Container Service](https://aws.amazon.com/ecs/) (Amazon ECS) and [AWS Fargate](https://aws.amazon.com/fargate/) now integrate with [Amazon Elastic Block Store](https://aws.amazon.com/ebs/) (EBS), allowing you to easily provision and attach EBS volumes to Amazon ECS tasks running on both AWS Fargate and [Amazon Elastic Cloud Compute](https://aws.amazon.com/ec2/) (EC2) using Amazon ECS APIs. This capability makes it easier for you to deploy storage and data intensive applications such as ETL jobs, media transcoding, and ML inference workloads using serverless containers. To use EBS volumes with your Amazon ECS tasks, simply configure the path you want the EBS volume to be mounted on in your task definition, and pass desired EBS volume attributes (e.g. size, type, IOPS, throughput), Amazon Key Management Service key, and snapshot-id (if you want the volume to be initialized from an existing EBS snapshot) in the RunTask, CreateService, or UpdateService API request. When you configure EBS volumes for your Amazon ECS tasks or services, Amazon ECS provisions an equal number of EBS volumes as the number of tasks and mounts one EBS volume to each task. By default, Amazon ECS automatically deletes the attached EBS volume when a task exits. This integration gives you access to all EBS features including configurable volume types and performance, snapshots, DataLifecycleManager, and encryption for your applications deployed with Amazon ECS. Amazon ECS support for EBS volumes is available in the [following AWS regions](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html#ebs-volume-regions). To get started, [view our documentation](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html) and [blog](https://aws.amazon.com/blogs/aws/amazon-ecs-supports-a-native-integration-with-amazon-ebs-volumes-for-data-intensive-workloads/).