Set bounds for a growing container service — ECS and Application Auto Scaling

Your goal

Register an ECS scaling target and save its maximum task capacity.

Why this matters

An app needs room to grow without an unlimited task count. You will register an ECS service as a scaling target and inspect its minimum and maximum bounds. This does not simulate demand or automatic scaling.

Words you will use

A task runs containers. Desired count is the number the service tries to run. Minimum and maximum capacity bound automatic scaling.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Prepare the container service

Create the ECS service configuration used by this experiment. Its cluster and service names identify the scaling target. No actual containers are started by this emulator lab.

2. Register scaling bounds

Choose the maximum task count, with a minimum of one. Register that range for the service’s desired count. Scaling policies and usable compute capacity are additional concerns in a real deployment.

Maximum task capacity: Choose a maximum from 2 to 10 tasks. Suggested practice value: 4.

3. Inspect the allowed range

Describe the scalable target and check its resource identity, minimum, and maximum. This confirms the bounds you saved; it does not claim a scaling event occurred.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.