|
Immediately 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 to your ECS duties operating on AWS Fargate and Amazon Elastic Compute Cloud (Amazon EC2) while not having to handle storage or compute.
Many organizations select to deploy their purposes as containerized packages, and with the introduction of Amazon ECS integration with Amazon EBS, organizations can now run extra forms of workloads than earlier than.
You’ll be able to run information workloads requiring storage that helps excessive transaction volumes and throughput, comparable to extract, rework, and cargo (ETL) jobs for giant 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 are actually extra resilient whereas concurrently requiring much less effort to handle.
Now you possibly can select from quite a lot of storage choices to your containerized purposes operating on Amazon ECS:
- Your Fargate duties get 20 GiB of ephemeral storage by default. For purposes that want extra cupboard space to obtain giant container photographs or for scratch work, you possibly can configure as much as 200 GiB of ephemeral storage to your Fargate duties.
- For purposes that span many duties that want concurrent entry to a shared dataset, you possibly can configure Amazon ECS to mount the Amazon Elastic File System (Amazon EFS) file system to your ECS duties operating on each EC2 and Fargate. Frequent examples of such workloads embrace net purposes comparable to content material administration techniques, inner 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 purposes that want high-performance, low-cost storage that doesn’t should be shared throughout duties, you possibly can configure Amazon ECS to provision and fasten Amazon EBS storage to your duties operating on each Amazon EC2 and Fargate. Amazon EBS is designed to offer block storage with low latency and excessive efficiency inside an Availability Zone.
To be taught 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 amount mount level to your container within the job definition and go Amazon EBS storage necessities to your Amazon ECS job at runtime. For many use circumstances, you may get began by merely offering the dimensions of the amount wanted for the duty. Optionally, you possibly can configure all EBS quantity attributes and the file system you need the amount formatted with.
1. Create a job definition
Go to the Amazon ECS console, navigate to Process 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 techniques.
If you select Configure at job definition creation, you possibly can configure current storage choices comparable to bind mounts, Docker volumes, EFS volumes, Amazon FSx for Home windows File Server volumes, or Fargate ephemeral storage.
Now you possibly can choose a container within the job definition, the supply EBS quantity, and supply a mount path the place the amount might be mounted within the job.
You can even 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"
],
"identify": "nginx",
"picture": "nginx"
],
"volumes": [
"name": "/foo",
"configuredAtRuntime": true
]
2. Deploy and run your job with EBS quantity
Go to your ECS cluster and select Run new job. Be aware which you can choose the compute choices, the launch kind, and your job definition.
Be aware: Whereas this instance goes via 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 have got a brand new Quantity part the place you possibly can configure the extra storage. The amount identify, kind, and mount factors are those who you outlined in your job definition. Select your EBS quantity sorts, sizes (GiB), IOPS, and the specified throughput.
You can not connect an current EBS quantity to an ECS job. However if you wish to create a quantity from an current snapshot, you’ve gotten the choice to decide on your snapshot ID. If you wish to create a brand new quantity, then you possibly can depart this discipline empty. You’ll be able to select the file system kind: ext3, ext4, or xfs file techniques on Linux.
By default, when a job is terminated, Amazon ECS deletes the connected quantity. In case you want the info within the EBS quantity to be retained after the duty exits, uncheck Delete on termination. Additionally, it’s essential to create an AWS Id and Entry Administration (IAM) function for quantity administration that incorporates 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 can even configure encryption by default in your EBS volumes utilizing both Amazon managed keys and buyer managed keys. To be taught 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 possibly can see the amount data on the duty particulars web page. Select a job and choose the Volumes tab to seek out your created EBS quantity particulars.
Your staff can manage the event and operations of EBS volumes extra effectively. For instance, software builders can configure the trail the place your software 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 permits DevOps engineers to deploy the identical job definition to completely 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 obtainable 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 be taught extra, see the Amazon EBS pricing web page and Amazon EBS volumes in ECS within the AWS documentation.
Give it a strive now and ship suggestions to our public roadmap, AWS re:Publish for Amazon ECS, or via your normal AWS Assist contacts.
— Channy
P.S. Particular due to Maish Saidel-Keesing, a senior enterprise developer advocate at AWS for his contribution in penning this weblog put up.
A correction was made on January 12, 2024: An earlier model of this put up misstated: I modified 1) from “both ext3 or ext4” to “ext3, ext4, or xfs”, 2) from “examine Delete on termination” to “uncheck Delete on termination”, 3) from “configure encryption”, “by default configure encryption”, and 4) from “job definition particulars web page” to “job particulars web page”.
