Ansible
Three automation systems. Each one is many playbooks, roles, job and workflow templates deep; each is one system.
Server Provisioning
Builds a server end to end from one request: name, address, DNS, the directory object, the virtual machine, tagging, agents and patching. A security gate has to pass before the build is accepted, and Windows and Linux run as separate phase chains behind the same request.
Impact Operator inputs become repeatable builds, with every infrastructure change executing inside AAP.
Server Deprovisioning
Retires a server in stages rather than deleting it: the first phase powers it down, moves it to a decommission folder and stamps a retention date, and a later sweep removes only what is past that date. Anything the sweep cannot settle holds the server back instead of letting it through.
Impact Retirement stays reversible for the whole retention window.
Certificate Lifecycle Automation
Takes an issued certificate and produces every form its consumers need — key, certificate, completed chain, bundle and Java keystore — then publishes them to the artifact repository. Service playbooks install from there, so IIS, Tomcat, nginx, MuleSoft and the Java truststores all update from one pipeline.
Impact One rotation replaces the per-service manual certificate work.