neo4j-aura-provisioning-skill

Automate Neo4j Aura provisioning by using OAuth2 client-credentials for REST API authentication or aura-cli credential setup, then poll instance status asynchronously until the target state is reached. This enables repeatable infrastructure automation for creating and managing database instances.

Neo4j Aura credentials require immediate secure handling upon instance creation. You must capture the one-time credentials and connection details instantly, then write them to a secure local .env file for connecting with Neo4j.

Neo4j Aura lifecycle operations including pause, resume, resize, and delete are fully supported via the Aura REST API and aura-cli. These operations use safe state transitions with async polling to validate the instance reaches the target status.

OAuth2 client-credentials authentication is required to authenticate with the Neo4j Aura REST API for infrastructure automation. For CLI-based workflows, you must complete the aura-cli credential setup instead to securely manage instances.

Align Terraform provisioning with Neo4j Aura instance readiness by implementing state-validated async polling. Poll the Aura REST API until the instance reaches the running status, ensuring downstream infrastructure resources connect only when the database is fully operational.

Neo4j Aura provisioning workflows require correct tenant and project selection along with accurate region and instance type parameters. Failing to specify valid tier or type configurations for your target environment causes the REST API or aura-cli request to fail.