Thursday, July 4, 2024

Amazon ECS helps a local integration with Amazon EBS volumes for data-intensive workloads

Voiced by Polly

Right this moment 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’ll be able to provision Amazon EBS storage in 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 purposes 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’ll be able to run information workloads requiring storage that helps excessive transaction volumes and throughput, resembling extract, remodel, and cargo (ETL) jobs for large 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 extra scaffolding to handle infrastructure updates, and consequently, your information processing workloads are actually extra resilient whereas concurrently requiring much less effort to handle.

Now you’ll be able to select from a wide range of storage choices in 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 pictures or for scratch work, you’ll be able to configure as much as 200 GiB of ephemeral storage in your Fargate duties.
  • For purposes 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 purposes resembling content material administration techniques, inner DevOps instruments, and machine studying (ML) frameworks. Amazon EFS is designed to be obtainable throughout a Area and might be concurrently connected to many duties.
  • For purposes that want high-performance, low-cost storage that doesn’t have to be shared throughout duties, you’ll be able to 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 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 greatest 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 in your container within the activity definition and go Amazon EBS storage necessities in your Amazon ECS activity at runtime. For many use instances, you may get began by merely offering the scale of the amount wanted for the duty. Optionally, you’ll be able to configure all EBS quantity attributes and the file system you need the amount formatted with.

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

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

Whenever you select Configure at activity definition creation, you’ll be able to configure present storage choices resembling 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 amount will probably be mounted within the activity.

It’s also possible to 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. Be aware that you could choose the compute choices, the launch sort, and your activity definition.

Be aware: Whereas this instance goes by deploying a standalone activity with an connected EBS quantity, you may as well configure a brand new or present ECS service to make use of EBS volumes with the specified configuration.

You’ve gotten a brand new Quantity part the place you’ll be able to configure the extra storage. The amount title, sort, and mount factors are those 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’ve gotten the choice to decide on your snapshot ID. If you wish to create a brand new quantity, then you’ll be able to depart this discipline empty. You’ll be able to select the file system sort, both ext3 or ext4 file techniques on Linux.

By default, when a activity 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, that you must create an AWS Id 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 info on this coverage, see infrastructure function within the AWS documentation.

It’s also possible to configure encryption in your EBS volumes utilizing both Amazon managed keys and buyer managed keys. To study extra concerning the choices, see our Amazon EBS encryption within the AWS documentation.

After configuring all activity settings, select Create to start out 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 amount 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 staff 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 appliance is deployed.

This permits DevOps engineers to deploy the identical activity definition to totally different environments with differing EBS quantity configurations, for instance, gp3 volumes within the improvement 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 employ, 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 strive now and ship suggestions to our public roadmap, AWS re:Put up for Amazon ECS, or by your ordinary 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 submit.



Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles