What I appreciate most is how Ansible Automation Platform gives us a consistent way to automate tasks across differnet environments. Instead of everyone writing their own scripts, we can have a centralized, controlled approach that keeps things uniform and reduces errors.
Cloud services, on‑prem servers, or network devices, Ansible connects to everything without needing any agents. This flexibility has made it much easier to scale automation across the organization stacks.
Also, its write once-reuse anywhere motoo help us reuse across multiple projects or environments. This not only speeds up deployments but also ensures the same process runs the same way every time, which has noticeably improved our operational stability. Review collected by and hosted on G2.com.
Even though YAML is readable, getting comfortable with writing playbooks, structuring roles, and understanding best practices takes time. My new team members have often needed guidance before they can contribute effectively in our platform.
May be few cases where they struggeled are role structuring, output capturing and reusing andYAML Sensitivity are more prone to error.
UI is helpful, but it introduces extra complexity compared to using Ansible alone. Managing inventories, credentials, and job templates through the controller sometimes feels more complicated than necessary.
These are just my experiences, others may feel it easy though if the have already used CFT or TF. Review collected by and hosted on G2.com.
Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
Invitation from G2. This reviewer was not provided any incentive by G2 for completing this review.
