Registering a Fargate Task
Introduction and Goal
In the previous lessons, you've built a solid foundation with ECS clusters and learned how to configure capacity providers for optimal cost and performance. However, having a cluster is just the first step — you still need to tell ECS what containers to run and how to configure them. This is where task definitions come into play. A task definition is essentially a blueprint that describes one or more containers that should run together as a unit, telling ECS exactly what image to use, how much CPU and memory to allocate, which ports to expose, and how to handle logging.
In this lesson, you'll create your first production-ready task definition that pulls a container image from Amazon Elastic Container Registry (ECR), exposes port 3000 for web traffic, and ships application logs to CloudWatch for monitoring and debugging. This represents a realistic scenario where you're deploying a custom web application that needs secure image storage, network connectivity, and centralized logging.
Your main goal is to register a Fargate task definition using the AWS CLI that incorporates these three critical components: ECR integration for private container images, port mapping for network access, and CloudWatch logging for operational visibility. By the end of this lesson, you'll have a registered task definition ready to run on your Fargate cluster, bridging the gap between infrastructure and actual application deployment.
Create the CloudWatch Logs Group
Before your task definition can send logs to CloudWatch, the log group must exist. CloudWatch Logs organizes log data into groups, which act as containers for log streams from your running containers. Each container instance will create its own log stream within the group, making it easy to track logs from multiple instances of the same application.
You'll create the log group using a command that's safe to run multiple times. This idempotent approach means you can execute the command repeatedly without causing errors, which is useful when automating deployments or when multiple team members are working with the same infrastructure.
Run this command in your terminal:
The command creates a log group at /ecs/my-web-app. The 2>/dev/null || true portion handles the case where the log group already exists — it suppresses the error message and ensures the command always exits successfully.
When you run this command for the first time, CloudWatch will create the log group and you won't see any output. If you run it again, the command will attempt to create the log group, receive an error that it already exists, suppress that error, and continue successfully. This pattern is commonly used in infrastructure automation where you want commands to be safe to run repeatedly.
You can verify that your log group was created by listing all log groups with a specific prefix:
This will show you all log groups that start with /ecs/, including the one you just created.
