Aurora supports all major cloud providers, allowing you to manage resources across multiple clouds from a single interface.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Arvo-AI/aurora/llms.txt
Use this file to discover all available pages before exploring further.
Available Cloud Providers
Google Cloud Platform
OAuth 2.0 authentication
Amazon Web Services
IAM Role with External ID
Microsoft Azure
Service Principal authentication
OVH Cloud
OAuth 2.0 (multi-region support)
Google Cloud Platform
Authentication Method
OAuth 2.0Setup Overview
-
Create OAuth Credentials in GCP Console > Credentials
- Configure OAuth consent screen (External, add test users)
- Create OAuth client ID (Web application)
- Set redirect URI:
http://localhost:5000/callback
-
Configure Environment Variables
-
Restart Aurora
- Connect via UI by completing the OAuth flow
Troubleshooting
“Redirect URI mismatch” — EnsureNEXT_PUBLIC_BACKEND_URL matches exactly what’s configured in GCP Console.
Amazon Web Services
Authentication Method
IAM Role with External ID for cross-account accessSetup Overview
-
Create IAM User for Aurora
- Create user with
sts:AssumeRolepermission - Generate access keys (programmatic access only)
- Create user with
-
Configure Aurora Environment
-
Rebuild and Restart Aurora
-
Create IAM Role in Your Account
- Trusted entity: Another AWS account
- Require external ID (displayed in Aurora UI)
- Attach permissions (PowerUserAccess or ReadOnlyAccess)
- Copy the Role ARN
-
Complete Onboarding in Aurora UI
- Enter your Role ARN
- Aurora will assume the role using STS
How It Works
Aurora uses its own AWS credentials to callsts:AssumeRole with your Role ARN and External ID. AWS returns temporary credentials that Aurora uses to access your resources.
Security Best Practices
- External ID prevents the “confused deputy” problem
- Least Privilege: Attach only required permissions to the role
- Role Permissions: Aurora inherits permissions from the assumed role
Troubleshooting
“Aurora cannot assume this role”- Wait 5 minutes after creating/updating IAM role (AWS propagation delay)
- Verify trust policy has correct Account ID and External ID
- Check External ID matches exactly (case-sensitive)
- Ensure credentials are set in
.env - Verify credentials with:
aws sts get-caller-identity - Rebuild and restart Aurora
Microsoft Azure
Authentication Method
Service Principal (App Registration)Setup Overview
-
Create App Registration
- Go to Azure Portal > App registrations
- Create new registration with redirect URI:
http://localhost:5000/azure/callback - Copy Application (client) ID and Directory (tenant) ID
- Create client secret and copy the value
-
Grant Permissions
- Add API permission: Azure Service Management > user_impersonation
- Grant admin consent
-
Assign Role to Subscription
- Go to Subscriptions > Access control (IAM)
- Add role assignment: Contributor (or Reader)
- Assign to your Aurora app
- Connect via Aurora UI using the credentials
Troubleshooting
“No enabled subscription found” — Assign Contributor/Reader role to the app in your subscription’s IAM.OVH Cloud
Authentication Method
OAuth 2.0 (multi-region support: EU, CA, US)Setup Overview
-
Create OAuth App in OVH
- Go to API console for your region:
- Navigate to
/me/api/oauth2/clientand POST a new client: - Copy Client ID and Client Secret
-
Configure Environment Variables (for each region)
-
Restart Aurora
- Connect via UI by selecting your region and completing OAuth flow
Local Development
To run locally with OVH OAuth:-
Start ngrok tunnel:
-
Copy the HTTPS URL (e.g.,
https://your-ngrok-url.ngrok-free.dev) -
Update
.envredirect URIs with the tunnel URL - Update OVH OAuth app callback URL via API console
Troubleshooting
“OAuth2 credentials not configured for [region]” — SetOVH_[REGION]_CLIENT_ID and OVH_[REGION]_CLIENT_SECRET.
“OVH connector not enabled” — Ensure NEXT_PUBLIC_ENABLE_OVH=true and restart Aurora.
Next Steps
Set up Observability
Connect monitoring and alerting tools to track your cloud resources