G2

Atharva P.

Cloud BI Engineer

Enterprise (> 1000 emp.)

7/24/2026

"Fast, Consistent Terminal Control Across Nearly Every AWS Service"

5/5

What do you like best about AWS Command Line Interface?

What I like most about the AWS CLI is that it gives me direct, terminal-based access to nearly every AWS service. It lets me automate and script workflows, manage infrastructure, and handle day-to-day operational tasks without having to rely on the AWS Management Console. Whether I’m provisioning resources, managing IAM policies, querying CloudWatch logs, or working with S3, the CLI delivers a fast, consistent experience.

I also appreciate how well it integrates with AWS SSO, IAM roles, and shell scripting. That combination makes it an indispensable tool for DevOps, platform engineering, and cloud administration. Review collected by and hosted on G2.com.

What do you dislike about AWS Command Line Interface?

The learning curve can feel steep for new users due to the sheer number of services and commands. Remembering the exact command syntax, parameters, and JSON structures often means having to refer back to the documentation, especially when working with services you don’t use very often. Review collected by and hosted on G2.com.

What problems is AWS Command Line Interface solving and how is that benefiting you?

The AWS CLI helps eliminate repetitive manual work and makes it easier to automate infrastructure.

For example, we used it to automate S3 bucket management, deploy CloudFormation stacks, manage IAM roles, pull CloudWatch logs, troubleshoot ECS services, and administer Amazon Q Business applications. By combining multiple AWS CLI commands into shell scripts, we created repeatable operational workflows that reduced manual effort and helped minimize configuration mistakes.

Overall, this improved our operational efficiency and supported more consistent infrastructure management across environments. Review collected by and hosted on G2.com.