Skip to content

Qovery Migration AI Agent to Automate and Ease the Migration From Cloud Providers with Qovery

License

Notifications You must be signed in to change notification settings

Qovery/qovery-migration-ai-agent

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Qovery Migration AI Agent

Qovery Migration AI Agent is an app designed to facilitate the migration of applications from various platforms to Qovery. Currently, it supports migrating Heroku applications to AWS, GCP, or Scaleway using Qovery.

demo video

Why this tool?

Migrating applications from one platform to another can be a time-consuming, error-prone process and super costly $$$. Qovery Migration AI Agent aims to simplify this process by automating the generation of Terraform configurations, Dockerfiles, and other necessary files for deploying applications on Qovery.

Features

Note: This project is still in development and may not support all features yet.

  • Migrate Heroku/Render applications to AWS, GCP, Azure or Scaleway via Qovery
  • Generate Terraform configurations for Qovery deployments
  • Create Dockerfiles for migrated applications

Structure

The project is structured as follows:

  • CLI: Contains the command-line interface for the migration agent (can be used on your local machine)
  • Web: Contains the web interface for the migration agent (can be deployed on a server)

Environment Variables

The following environment variables are required to run the application:

Environment Variable Description Required
AWS_ACCESS_KEY_ID AWS access key ID for Bedrock service Yes
AWS_SECRET_ACCESS_KEY AWS secret access key for Bedrock service Yes
AWS_REGION AWS region where Bedrock service is available (e.g., us-east-1, us-west-2) Yes
HEROKU_API_KEY Heroku API key Yes if you used it
GITHUB_TOKEN GitHub token to avoid being rate limited No

Note: Make sure your AWS credentials have the necessary permissions to access the Bedrock service and the Claude model.

How it works

The migration agent uses the Heroku (or other provider) API to fetch information about the application to be migrated. It then uses Claude AI via AWS Bedrock to generate Terraform configurations for deploying the application on Qovery. The generated Terraform configurations include the necessary resources such as the application, environment, database, and other services.

graph TD
    A[Start] --> B[AI Migration Agent fetches app data from Heroku API]
    B --> C[AI Migration Agent filters out sensitive data]
    C --> D[AI Migration Agent sends non-sensitive app data to Claude AI via AWS Bedrock]
    D --> E[Claude AI generates Dockerfiles]
    E --> F[AI Migration Agent receives Dockerfiles]
    F --> G[AI Migration Agent sends non-sensitive app data to Claude AI via AWS Bedrock]
    G --> H[Claude AI generates Qovery Terraform files]
    H --> I[AI Migration Agent receives Terraform files]
    I --> J[AI Migration Agent reintegrates sensitive data as Terraform secrets]
    J --> K[Validate Terraform manifest]
    K --> L{Is manifest valid?}
    L -->|Yes| M[AI Migration Agent generates output for user review]
    L -->|No| N[Auto-remediation process]
    N --> O[Claude AI fixes Terraform errors]
    O --> K
    M --> P[User reviews and uses output]
    P --> Q[End]

    subgraph "Data Sources"
        R[Heroku API]
        S[GitHub Examples]
    end

    subgraph "Security Measure"
        T[Sensitive data kept locally]
    end

    B -.-> R
    H -.-> S
    C -.-> T
    J -.-> T

Loading

Security

  • This application does not store any user credentials.
  • All code is open-source and can be audited.
  • AWS credentials are only used locally and are never transmitted to third parties.
  • For more information, see the Security page in the application.

Contributing

We welcome contributions! Please see our Contributing Guide for more details.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

If you encounter any issues or have questions, please file an issue on the GitHub repository or contact [email protected].