Cloud Provider Integrations

​

Available Cloud Providers

​

Google Cloud Platform

​

Authentication Method

​

Setup Overview

1. 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
2. Configure Environment Variables
   CLIENT_ID=your-client-id.apps.googleusercontent.com
   CLIENT_SECRET=your-client-secret
   
3. Restart Aurora
   make down
   make dev
   
4. Connect via UI by completing the OAuth flow

​

Troubleshooting

​

Amazon Web Services

​

Authentication Method

​

Setup Overview

1. Create IAM User for Aurora
   • Create user with sts:AssumeRole permission
   • Generate access keys (programmatic access only)
2. Configure Aurora Environment
   AWS_ACCESS_KEY_ID=your-access-key-id
   AWS_SECRET_ACCESS_KEY=your-secret-access-key
   AWS_DEFAULT_REGION=us-east-1
   
3. Rebuild and Restart Aurora
   make down
   make dev-build
   make dev
   
4. 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
5. Complete Onboarding in Aurora UI
   • Enter your Role ARN
   • Aurora will assume the role using STS

​

How It Works

​

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

• 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

​

Setup Overview

1. 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
2. Grant Permissions
   • Add API permission: Azure Service Management > user_impersonation
   • Grant admin consent
3. Assign Role to Subscription
   • Go to Subscriptions > Access control (IAM)
   • Add role assignment: Contributor (or Reader)
   • Assign to your Aurora app
4. Connect via Aurora UI using the credentials

​

Troubleshooting

​

OVH Cloud

​

Authentication Method

​

Setup Overview

1. Create OAuth App in OVH
   • Go to API console for your region:
     • EU: https://eu.api.ovh.com/console/
     • CA: https://ca.api.ovh.com/console/
     • US: https://us.api.ovh.com/console/
   • Navigate to /me/api/oauth2/client and POST a new client:
     {
       "callbackUrls": [
         "https://your-domain.com/ovh/oauth2/callback"
       ],
       "description": "Aurora Cloud Platform",
       "flow": "AUTHORIZATION_CODE",
       "name": "Aurora"
     }
     
   • Copy Client ID and Client Secret
2. Configure Environment Variables (for each region)
   NEXT_PUBLIC_ENABLE_OVH=true
   
   # Europe region
   OVH_EU_CLIENT_ID=your-eu-client-id
   OVH_EU_CLIENT_SECRET=your-eu-client-secret
   OVH_EU_REDIRECT_URI=https://your-domain.com/ovh_api/ovh/oauth2/callback
   
   # Canada region (optional)
   OVH_CA_CLIENT_ID=your-ca-client-id
   OVH_CA_CLIENT_SECRET=your-ca-client-secret
   OVH_CA_REDIRECT_URI=https://your-domain.com/ovh_api/ovh/oauth2/callback
   
   # US region (optional)
   OVH_US_CLIENT_ID=your-us-client-id
   OVH_US_CLIENT_SECRET=your-us-client-secret
   OVH_US_REDIRECT_URI=https://your-domain.com/ovh_api/ovh/oauth2/callback
   
3. Restart Aurora
   make down
   make dev
   
4. Connect via UI by selecting your region and completing OAuth flow

​

Local Development

1. Start ngrok tunnel:
   ngrok http 5080
   
2. Copy the HTTPS URL (e.g., https://your-ngrok-url.ngrok-free.dev)
3. Update .env redirect URIs with the tunnel URL
4. Update OVH OAuth app callback URL via API console

​

Troubleshooting

​

Next Steps