I typed the wrong profile name and took production down

I typed the wrong profile name and took production down.

AWS CLI-style profiles can save you from mistakes like that. When you work with multiple environments, credentials, and endpoints, switching by hand is a risk. Structured profiles give you speed, clarity, and safety. With AWS CLI-style profiles for Radius, you can define clean boundaries between dev, staging, and production. One command moves you to the right environment. No guessing. No silent misconfigurations.

Radius supports profiles that feel familiar if you’ve ever run aws --profile. You can store multiple credential sets, each tied to a different Radius environment, tenant, or cluster. The CLI reads the profile you point to and uses the right keys, endpoints, and defaults. You write once, use forever.

Set them up in ~/.radius/config. Each profile can have name, auth token, and endpoint. The CLI supports switching instantly:

radius --profile staging services list
radius --profile prod deploy

This prevents accidental writes to the wrong location. Your workflow becomes safer and more predictable, even when juggling many projects or orgs.

Use clear, human-readable names. Keep credentials scoped tightly. Profiles are plain text, so they can live in secure storage or be templated for onboarding new teammates. You can integrate them with scripts and CI pipelines without changing your tool commands—just pass the right profile flag.

The result: a frictionless path to precise commands, no more copy-paste chaos, and less mental load. You get confidence in every deploy.

You can see AWS CLI-style profiles in action with Radius in minutes. Go to hoop.dev and run it live.