In the present day we’re asserting that Amazon Elastic Container Service (Amazon ECS) helps an integration with Amazon Elastic Block Retailer (Amazon EBS), making it simpler to run a wider vary of information processing workloads. You’ll be able to provision Amazon EBS storage in your ECS duties working on AWS Fargate and Amazon Elastic Compute Cloud (Amazon EC2) without having to handle storage or compute.

Many organizations select to deploy their functions as containerized packages, and with the introduction of Amazon ECS integration with Amazon EBS, organizations can now run extra sorts of workloads than earlier than.

You’ll be able to run information workloads requiring storage that helps excessive transaction volumes and throughput, resembling extract, rework, and cargo (ETL) jobs for large information, which have to fetch current information, carry out processing, and retailer this processed information for downstream use. As a result of the storage lifecycle is absolutely managed by Amazon ECS, you don’t have to construct any extra scaffolding to handle infrastructure updates, and because of this, your information processing workloads at the moment are extra resilient whereas concurrently requiring much less effort to handle.

Now you may select from a wide range of storage choices in your containerized functions working on Amazon ECS:

• Your Fargate duties get 20 GiB of ephemeral storage by default. For functions that want extra cupboard space to obtain massive container pictures or for scratch work, you may configure as much as 200 GiB of ephemeral storage in your Fargate duties.
• For functions that span many duties that want concurrent entry to a shared dataset, you may configure Amazon ECS to mount the Amazon Elastic File System (Amazon EFS) file system to your ECS duties working on each EC2 and Fargate. Frequent examples of such workloads embody net functions resembling content material administration methods, inside DevOps instruments, and machine studying (ML) frameworks. Amazon EFS is designed to be obtainable throughout a Area and may be concurrently connected to many duties.
• For functions that want high-performance, low-cost storage that doesn’t must be shared throughout duties, you may configure Amazon ECS to provision and fasten Amazon EBS storage to your duties working on each Amazon EC2 and Fargate. Amazon EBS is designed to supply block storage with low latency and excessive efficiency inside an Availability Zone.

To study extra, see Utilizing information volumes in Amazon ECS duties and persistent storage finest practices within the AWS documentation.

Getting began with EBS quantity integration to your ECS duties
You’ll be able to configure the quantity mount level in your container within the job definition and cross Amazon EBS storage necessities in your Amazon ECS job at runtime. For many use circumstances, you may get began by merely offering the dimensions of the quantity wanted for the duty. Optionally, you may configure all EBS quantity attributes and the file system you need the quantity formatted with.

1. Create a job definition
Go to the Amazon ECS console, navigate to Job definitions, and select Create new job definition.

Within the Storage part, select Configure at deployment to set EBS quantity as a brand new configuration kind. You’ll be able to provision and fasten one quantity per job for Linux file methods.

If you select Configure at job definition creation, you may configure current storage choices resembling bind mounts, Docker volumes, EFS volumes, Amazon FSx for Home windows File Server volumes, or Fargate ephemeral storage.

Now you may choose a container within the job definition, the supply EBS quantity, and supply a mount path the place the quantity might be mounted within the job.

You may also use $aws ecs register-task-definition --cli-input-json file://instance.json command line to register a job definition so as to add an EBS quantity. The next snippet is a pattern, and job definitions are saved in JSON format.

{
    "household": "nginx"
    ...
    "containerDefinitions": [
        {
            ...
            "mountPoints": [
                "containerPath": "/foo",
                "sourceVolume": "new-ebs-volume"
            ],
            "title": "nginx",
            "picture": "nginx"
        }
    ],
    "volumes": [
       {
           "name": "/foo",
           "configuredAtRuntime": true
       }
    ]
}

2. Deploy and run your job with EBS quantity
Now you may run a job by deciding on your job in your ECS cluster. Go to your ECS cluster and select Run new job. Observe you can choose the compute choices, the launch kind, and your job definition.

Observe: Whereas this instance goes by means of deploying a standalone job with an connected EBS quantity, you may also configure a brand new or current ECS service to make use of EBS volumes with the specified configuration.

You’ve gotten a brand new Quantity part the place you may configure the extra storage. The quantity title, kind, and mount factors are people who you outlined in your job definition. Select your EBS quantity varieties, sizes (GiB), IOPs, and the specified throughput.

You can’t connect an current EBS quantity to an ECS job. However if you wish to create a quantity from an current snapshot, you’ve got the choice to decide on your snapshot ID. If you wish to create a brand new quantity, then you may depart this subject empty. You’ll be able to select the file system kind, both ext3 or ext4 file methods on Linux.

By default, when a job is terminated, Amazon ECS deletes the connected quantity. If you happen to want the information within the EBS quantity to be retained after the duty exits, verify Delete on termination. Additionally, you have to create an AWS Identification and Entry Administration (IAM) function for quantity administration that accommodates the related permissions to permit Amazon ECS to make API calls in your behalf. For extra data on this coverage, see infrastructure function within the AWS documentation.

You may also configure encryption in your EBS volumes utilizing both Amazon managed keys and buyer managed keys. To study extra in regards to the choices, see our Amazon EBS encryption within the AWS documentation.

After configuring all job settings, select Create to start out your job.

3. Deploy and run your job with EBS quantity
As soon as your job has began, you may see the quantity data on the duty definition particulars web page. Select a job and choose the Volumes tab to seek out your created EBS quantity particulars.

Your workforce can manage the event and operations of EBS volumes extra effectively. For instance, utility builders can configure the trail the place your utility expects storage to be obtainable within the job definition, and DevOps engineers can configure the precise EBS quantity attributes at runtime when the applying is deployed.

This enables DevOps engineers to deploy the identical job definition to totally different environments with differing EBS quantity configurations, for instance, gp3 volumes within the growth environments and io2 volumes in manufacturing.

Now obtainable
Amazon ECS integration with Amazon EBS is out there in 9 AWS Areas: US East (Ohio), US East (N. Virginia), US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Eire), and Europe (Stockholm). You solely pay for what you utilize, together with EBS volumes and snapshots. To study extra, see the Amazon EBS pricing web page and Amazon EBS volumes in ECS within the AWS documentation.

Give it a attempt now and ship suggestions to our public roadmap, AWS re:Publish for Amazon ECS, or by means of your standard AWS Assist contacts.

— Channy

P.S. Particular due to Maish Saidel-Keesing, a senior enterprise developer advocate at AWS for his contribution in scripting this weblog publish.