Label resources so the right person can find them — Resource tags

Your goal

Give a bucket and a server the same project label and read both tags.

Why this matters

Resources from different services can share a project label. You will tag a bucket and an instance, then inspect both. Consistent labels help people organize work but do not grant permissions.

Words you will use

A tag is a key and value attached to a supported resource. An owner tag identifies responsibility. An environment tag distinguishes uses such as test and production.

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. Create two different resources

Create an S3 bucket and an EC2 instance record. These services have different APIs, but tags can give their resources a shared project label.

2. Tag both resources

Enter a project label and save it on both the bucket and instance. Tags help organize ownership and reporting. They are not a substitute for permissions, and a tag is not automatically an active billing category.

Practice label: This label is saved in the emulator. Use 1–80 characters. Suggested practice value: moonbase.

3. Check each service’s stored tags

Retrieve tags through both service APIs. Verify that the same Project value appears on both resources. This shows how a shared label can span different resource types.

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.