I'm setting up an AWS workflow and have more experience with Azure and on-prem systems. Should I learn the AWS CLI, or rely on a sandboxed MCP with scoped roles, budget controls, Terraform, and approval gates for production?
Is AWS CLI still worth learning if I use MCP and Terraform?
Answers
Yes, but aim for functional rather than encyclopedic knowledge. Learn how profiles and roles select credentials, how regions affect calls, how to find command help, and how to filter or format output. You can look up the exact flags when you need them.
That gives you a way to inspect resources and check what an MCP tool did. It also makes errors like AccessDenied easier to investigate when an abstraction gives you an unhelpful message. Start with read-only calls and use a suitably scoped role.
Reply to this answer
Think of these as different tools, not a replacement chain. Terraform describes and manages infrastructure through its providers. The CLI makes API calls directly. An MCP tool can provide another interface, but it doesn't make AWS permissions, resources, or service behavior disappear.
Terraform also isn't completely vendor agnostic. AWS resources and their settings still show through in the configuration. Knowing the underlying services helps you review both a Terraform plan and an automated tool's proposed actions.
Reply to this answer
CLI knowledge is especially handy when something breaks and you need to find out what's there right now. Listing resources or checking an error directly can be quicker than going through an agent or trying to reason from a failed pipeline.
That doesn't mean making production changes by hand whenever Terraform is inconvenient. Direct changes can leave the deployed environment out of sync with the configuration, so investigate first and follow the team's change process.
Reply to this answer
I wouldn't make CLI expertise the main goal. Understanding infrastructure and how to verify changes matters more. The console, an SDK, the CLI, or automation can all be useful depending on the task and what the team supports.
Keep development and test separate from production, review proposed changes, and test them before promoting them. A sandbox and scoped roles are useful safeguards, not a reason to skip checking the result.
6c~tarnel.82:
And check what the budget controls actually do. A budget alert isn't necessarily a hard spending limit.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_e52+ledgerpiston.9:
That sounds manageable. I was wondering if learning the CLI meant memorizing a lot of service-specific commands.