At present 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 knowledge processing workloads. You may provision Amazon EBS storage to your ECS duties operating on AWS Fargate and Amazon Elastic Compute Cloud (Amazon EC2) with no need 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 varieties of workloads than earlier than.
You may run information workloads requiring storage that helps excessive transaction volumes and throughput, similar to extract, rework, and cargo (ETL) jobs for giant information, which must fetch present 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 must construct any further scaffolding to handle infrastructure updates, and in consequence, your information processing workloads at the moment are extra resilient whereas concurrently requiring much less effort to handle.
Now you’ll be able to select from quite a lot of storage choices to your containerized functions operating on Amazon ECS:
- Your Fargate duties get 20 GiB of ephemeral storage by default. For functions that want further cupboard space to obtain giant container pictures or for scratch work, you’ll be able to configure as much as 200 GiB of ephemeral storage to your Fargate duties.
- For functions that span many duties that want concurrent entry to a shared dataset, you’ll be able to configure Amazon ECS to mount the Amazon Elastic File System (Amazon EFS) file system to your ECS duties operating on each EC2 and Fargate. Widespread examples of such workloads embody net functions similar to content material administration techniques, inside DevOps instruments, and machine studying (ML) frameworks. Amazon EFS is designed to be obtainable throughout a Area and could be concurrently connected to many duties.
- For functions that want high-performance, low-cost storage that doesn’t must be shared throughout duties, you’ll be able to configure Amazon ECS to provision and connect 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 may configure the quantity mount level to your container within the activity definition and go Amazon EBS storage necessities to your Amazon ECS activity at runtime. For many use instances, you will get began by merely offering the dimensions of the quantity wanted for the duty. Optionally, you’ll be able to configure all EBS quantity attributes and the file system you need the quantity formatted with.
1. Create a activity definition
Go to the Amazon ECS console, navigate to Job definitions, and select Create new activity definition.
Within the Storage part, select Configure at deployment to set EBS quantity as a brand new configuration kind. You may provision and connect one quantity per activity for Linux file techniques.
If you select Configure at activity definition creation, you’ll be able to configure present storage choices similar to bind mounts, Docker volumes, EFS volumes, Amazon FSx for Home windows File Server volumes, or Fargate ephemeral storage.
Now you’ll be able to choose a container within the activity definition, the supply EBS quantity, and supply a mount path the place the quantity will likely be mounted within the activity.
You too can use $aws ecs register-task-definition --cli-input-json file://instance.json
command line to register a activity definition so as to add an EBS quantity. The next snippet is a pattern, and activity 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 activity with EBS quantity
Now you’ll be able to run a activity by deciding on your activity in your ECS cluster. Go to your ECS cluster and select Run new activity. Observe which you can choose the compute choices, the launch kind, and your activity definition.
Observe: Whereas this instance goes via deploying a standalone activity with an connected EBS quantity, it’s also possible to configure a brand new or present ECS service to make use of EBS volumes with the specified configuration.
You will have a brand new Quantity part the place you’ll be able to configure the extra storage. The quantity title, kind, and mount factors are people who you outlined in your activity definition. Select your EBS quantity varieties, sizes (GiB), IOPs, and the specified throughput.
You can not connect an present EBS quantity to an ECS activity. However if you wish to create a quantity from an present snapshot, you may have the choice to decide on your snapshot ID. If you wish to create a brand new quantity, then you’ll be able to go away this subject empty. You may select the file system kind, both ext3 or ext4 file techniques on Linux.
By default, when a activity is terminated, Amazon ECS deletes the connected quantity. For those who want the information within the EBS quantity to be retained after the duty exits, test Delete on termination. Additionally, you might want to create an AWS Identification and Entry Administration (IAM) position for quantity administration that incorporates the related permissions to permit Amazon ECS to make API calls in your behalf. For extra info on this coverage, see infrastructure position within the AWS documentation.
You too can configure encryption in your EBS volumes utilizing both Amazon managed keys and buyer managed keys. To be taught extra concerning the choices, see our Amazon EBS encryption within the AWS documentation.
After configuring all activity settings, select Create to begin your activity.
3. Deploy and run your activity with EBS quantity
As soon as your activity has began, you’ll be able to see the quantity info on the duty definition particulars web page. Select a activity and choose the Volumes tab to seek out your created EBS quantity particulars.
Your workforce can set up 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 activity 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 activity 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 accessible 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 attempt now and ship suggestions to our public roadmap, AWS re:Submit for Amazon ECS, or via your common AWS Help contacts.
— Channy
P.S. Particular because of Maish Saidel-Keesing, a senior enterprise developer advocate at AWS for his contribution in scripting this weblog submit.