Skip to main content

Connect services to Aiven Runtime Limited availability

Connect your deployed application to Aiven services. You can connect an existing Aiven for Apache Kafka®, Aiven for PostgreSQL®, Aiven for OpenSearch®, or Aiven for Valkey™ service.

You can also define integrations when you create your application by using Compose files.

Connect an Aiven service​

  1. In your project, click Runtime.
  2. Open your application.
  3. In the Connected services section, click Connect service.
  4. Select the service to connect.
  5. Click Connect.

Connect a Karapace schema registry​

To connect services that are integrated with your application to a Karapace schema registry:

  • Connect the application to the Aiven for Apache Kafka® service.
  • Add the schema registry connection details as environment variables.

Prerequisites​

Connect a schema registry during application creation​

  1. In your project, click Runtime.
  2. Click Deploy application.
  3. Select or connect your GitHub account.
  4. Select your Account, Repository, and Branch.
  5. Click Next.
  6. Select your manifest file and click Scan. Aiven Runtime automatically detects what applications and services are needed.
  7. On the Kafka service, click Swap with an existing service.
  8. Select the Kafka service you created and click Apply.
  9. To configure the integration with the schema registry, click Configure and add the connection details as environment variables.
  10. To deploy the application, click Deploy.

Connect a schema registry to an existing application​

  1. In your project, click Runtime.
  2. Open your application.
  3. In the Environment variables section, click Edit.
  4. On the Variables tab, add the connection details as environment variables.
  5. Click Save.

Disconnect an Aiven service​

  1. In your project, click Runtime.
  2. Open your application.
  3. In the Connected services section, find the service to disconnect.
  4. Click Actions > Disconnect service.
  5. Click Disconnect to confirm.

Apply database schema changes​

Aiven Runtime does not automatically support pre-deploy commands or one-off task execution. To run database schema migrations, you can do one of the following:

  • Run migrations at container startup: You can update the CMD or entrypoint of your Containerfile or Dockerfile so that the database schema changes are applied every time the container starts up.

  • Run migrations in CI/CD before deploying: If you use a CI/CD pipeline, you can run migrations as a pipeline step before deployment.