Today, we are excited to announce that Amazon Elastic Container Service (Amazon ECS) now supports integration with Amazon Elastic Block Store (Amazon EBS). This integration makes it easier for you to run a wider range of data processing workloads. With this integration, you can provision Amazon EBS storage for your ECS tasks running on AWS Fargate and Amazon Elastic Compute Cloud (Amazon EC2) without the need to manage storage or compute.
Many organizations choose to deploy their applications as containerized packages. With the introduction of Amazon ECS integration with Amazon EBS, these organizations can now run more types of workloads than before. For example, you can run data workloads that require storage supporting high transaction volumes and throughput, such as extract, transform, and load (ETL) jobs for big data. These workloads need to fetch existing data, perform processing, and store the processed data for downstream use.
By fully managing the storage lifecycle, Amazon ECS eliminates the need for additional infrastructure updates and reduces the effort required to manage data processing workloads. Now, you have a variety of storage options for your containerized applications running on Amazon ECS.
For Fargate tasks, you get 20 GiB of ephemeral storage by default. If your applications need additional storage space, you can configure up to 200 GiB of ephemeral storage for your Fargate tasks.
If your applications span many tasks that require concurrent access to a shared dataset, you can configure Amazon ECS to mount the Amazon Elastic File System (Amazon EFS) file system to your ECS tasks running on both EC2 and Fargate. This is useful for web applications like content management systems, internal DevOps tools, and machine learning (ML) frameworks.
If your applications require high-performance, low-cost storage that doesn’t need to be shared across tasks, you can configure Amazon ECS to provision and attach Amazon EBS storage to your tasks running on both Amazon EC2 and Fargate. Amazon EBS provides block storage with low latency and high performance within an Availability Zone.
To get started with EBS volume integration to your ECS tasks, you can configure the volume mount point and pass the Amazon EBS storage requirements in the task definition at runtime. You can create a task definition in the Amazon ECS console or use the AWS CLI to register a task definition with an EBS volume.
Once you have created a task definition with an EBS volume, you can deploy and run your task with the EBS volume by selecting the compute options, launch type, and task definition in your ECS cluster. You can configure additional storage options for the EBS volume, such as volume type, size, IOPS, throughput, file system type, and encryption.
After you have configured all the task settings, you can create and start your task. Once the task has started, you can view the volume information on the task details page. This integration allows your team to organize the development and operations of EBS volumes more efficiently. Application developers can configure the storage path in the task definition, while DevOps engineers can configure the EBS volume attributes at runtime.
Amazon ECS integration with Amazon EBS is available in nine AWS Regions. You only pay for what you use, including EBS volumes and snapshots. To learn more about pricing and availability, please refer to the Amazon EBS pricing page and the Amazon EBS volumes in ECS documentation. We encourage you to give it a try and provide feedback through our public roadmap, AWS re:Post for Amazon ECS, or your usual AWS Support contacts.
Source link
