VMware Aria Automation (formerly vRealize Automation)

While VMware Aria Automation Orchestrator 8.x includes a plug-in, workflows, and actions for automating VMware Aria Automation, I often find these workflows and actions to be simple and nowhere close to supporting the extensibility outcomes I require. Instead, I frequently must work directly with the VMware Aria Automation REST API. At first, the idea of writing code to utilize the API seemed a bit daunting, but with the help of the Aria Automation 8.

VMware released the latest update to the VMware Aria Suite, VMware Aria Automation 8.11.1, on February 21, 2023. This release focuses primarily on customized notifications in Service Broker, CPU/Storage capacity enhancements, Google Cloud Platform (GCP) improvements, minor product enhancements, and bug fixes.

VMware released the latest update to the VMware Aria Suite, VMware Aria Automation 8.11, on January 20, 2023. This release focuses primarily on improvements to public cloud support, Guardrails improvements (SaaS offering only), minor product enhancements, and bug fixes.

Aria Automation Orchestrator + Node.js Introduction With the release of VMware vRealize Orchestrator 8.1 in April 2020, VMware added the ability to utilize new languages within your workflows and actions. These new languages included PowerShell, Node.js, and Python. Since then, I have seen very few documents detailing the use of this capability. Recently though, while attempting to migrate some legacy scripts from a vRealize Orchestrator 7.6 deployment to vRealize Orchestrator 8.

In my previous post titled Introduction to VMware vRealize Automation SaltStack SecOps, I provided an introduction to VMware Aria Automation SaltStack Automation SecOps, as well as a brief history and overview of the product’s capabilities. In this post, I’ll dive deeper into the product’s compliance management capabilities. Compliance Checks Compliance checks are at the foundation of VMware Aria Automation SaltStack SecOps compliance management. These checks provide the information necessary to identify the purpose of the check, the operating systems it applies to, the rationale for the check, and, more importantly, the state file responsible for implementing/remediating the check.