Requires a self-hosted AWX or Ansible Automation Platform (Controller / Tower) instance reachable from CloudThinker. Authentication uses an AWX access token.
Supported Platforms
| Platform | Support |
|---|---|
| AWX | Open-source, recent releases |
| Ansible Automation Platform | Controller / Tower |
Setup
Sign in to AWX
Sign in to your AWX web interface. Use a dedicated user scoped to only the organizations and inventories CloudThinker needs.
Create a Token
Go to Access → Users, open your user, select the Tokens tab, and click Add:
- Application: leave empty
- Scope: Write for full operations, or Read for monitoring only
Agent Capabilities
What an agent can do depends on the token’s scope. A Read token covers the monitoring and inspection actions below; a Write token adds the operational actions on top. Read — monitoring & inspection:- Monitor jobs — list jobs and workflow runs, check status, and read output
- Inspect inventories — view inventories, hosts, and groups; spot unreachable or disabled hosts
- Check project status — review sync status and source-control state
- Review schedules — list schedules and upcoming runs
- Inspect configuration — view job templates, workflow templates, inventory sources, and credential types
- Launch jobs — run job templates with extra variables and monitor them to completion
- Run ad-hoc commands — execute one-off
command/shellmodules against hosts without a template - Control running jobs — cancel in-flight jobs and relaunch failed ones
- Sync projects & inventory — pull project updates from source control and refresh dynamic inventory
- Manage hosts, groups & schedules — add, update, or remove them and toggle host enablement
- Orchestrate workflows — launch and monitor workflow job templates, and approve or deny approval nodes
Example Prompts
Troubleshooting
Connection or authentication failed
Connection or authentication failed
- Verify the AWX URL is reachable from CloudThinker over HTTPS
- Confirm the token has not expired or been revoked
Permission denied
Permission denied
- Use a Write-scoped token for launch, sync, or management actions
- Confirm the user has access to the target organization or inventory
Empty results
Empty results
- The token’s user may lack visibility — grant access to the relevant organizations and inventories
Security Best Practices
- Dedicated user - Create a dedicated AWX user for CloudThinker
- Least privilege - Use a Read-scoped token when write access isn’t needed
- Token rotation - Set an expiration and rotate tokens periodically
- HTTPS only - Always use an HTTPS AWX URL
Related
ArgoCD Connection
GitOps operations and application management
Jenkins Connection
CI/CD pipeline monitoring and job operations