Resource Groups & Tagging

In the cloud, you don't create "Servers". You create "Resources". Resource Groups act as logical containers to manage lifecycle, billing, and access control for related items.

๐Ÿข The Hierarchy (Azure Model)

Management Group
Subscription
(Billing & Quota Boundary)
Resource Group
(Lifecycle Boundary)
Resource (VM, DB, etc.)

๐Ÿ—‚๏ธ Why organize?

Lifecycle Management

If you delete a Resource Group, everything inside it is deleted. This is perfect for temporary environments. "Delete the Dev Project" becomes one click.

Cost Allocation

You can generate a bill filtered by "Tag: CostCenter=Marketing". This tells you exactly how much the Marketing team is spending, separate from Engineering.

Access Control (RBAC)

Grant permission to the Group, not the individual items. "John is an Admin of the Website Group" automatically gives him access to the VM, Load Balancer, and DB inside.

๐Ÿ•น๏ธ Cloud Organizer Simulator

Mission: The account is a mess. Drag resources into their correct Project Groups.
Bonus: Once a group is full, try the "Delete Group" button to see the power of lifecycle management.

Unsorted Resources
๐Ÿ—„๏ธ
prod-db-01
Tag: Env=Prod
๐Ÿงช
dev-test-vm
Tag: Env=Dev
โš–๏ธ
prod-lb-main
Tag: Env=Prod
๐Ÿ—‘๏ธ
dev-temp-storage
Tag: Env=Dev
rg-production
rg-development
Drag items to organize them.

โš”๏ธ Platform Differences

Feature Azure (Resource Groups) AWS (Resource Groups / Tags)
Structure Mandatory. Every resource MUST be in exactly one RG. Optional. Resources are loose but can be grouped by Tags.
Lifecycle Deleting the RG deletes everything inside. (Strong coupling) Deleting a "Resource Group" usually just deletes the view, not the resources (unless using Stacks).