Configure AWS Secrets Manager

Configure and use AWS Secrets Manager as a secret provider in Aiven for Apache Kafka® Connect services.

Prerequisites

Aiven for Apache Kafka service with Apache Kafka Connect set up and running.
Aiven CLI.
Aiven Terraform Provider installed.
AWS Secrets Manager access key and secret key.

note

The integration with AWS Secrets Manager is not yet available on the Aiven Console.

Configure secret providers

Set up AWS Secrets Manager in your Aiven for Apache Kafka Connect service to manage and access sensitive information.

API
Terraform
CLI

Use the ServiceUpdate API to update your service configuration. Add the AWS Secrets Manager configuration to the user_config using the following API request:

curl --request PUT \
  --url https://api.aiven.io/v1/project/{PROJECT_NAME}/service/{SERVICE_NAME} \
  --header 'Authorization: Bearer YOUR_BEARER_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "user_config": {
      "secret_providers": [
        {
          "name": "aws",
          "aws": {
            "auth_method": "credentials",
            "region": "your-aws-region",
            "access_key": "your-aws-access-key",
            "secret_key": "your-aws-secret-key"
          }
        }
      ]
    }
  }'

Parameters:

url: API endpoint for updating the service configuration. Replace PROJECT_NAME and SERVICE_NAME with your project and service names.
Authorization: Token used for authentication. Replace YOUR_BEARER_TOKEN with your Aiven API token.
Content-Type: Specifies that the request body is in JSON format.
auth_method: Authentication method used by AWS Secrets Manager. In this case, it is credentials.
region: AWS region where your secrets are stored.
access_key: Your AWS access key.
secret_key: Your AWS secret key.

Configure AWS Secrets Manager using Terraform. Add this configuration to your main.tf file, or optionally create a secrets.tf file to manage secret providers:

Create the main.tf file for your resources:

 terraform {
 required_providers {
   aiven = {
     source  = "aiven/aiven"
     version = ">=4.0.0, < 5.0.0"
   }
 }
}

provider "aiven" {
api_token = var.aiven_api_token
}

resource "aiven_kafka_connect" "kafka_connect" {
 project      = var.project_name
 cloud_name   = "your-cloud-region"
 plan         = "startup-4"
 service_name = "kafka-connect"

 kafka_connect_user_config {
   secret_providers {
     name = "aws"
     aws {
       auth_method = "credentials"
       region      = var.aws_region
       access_key  = var.aws_access_key
       secret_key  = var.aws_secret_key
     }
   }
 }
}

Declare variables in a variables.tf file:

 variable "aiven_api_token" {
   description = "Aiven API token"
   type        = string
  }

 variable "project_name" {
   description = "Aiven project name"
   type        = string
  }

 variable "aws_region" {
   description = "AWS region"
   type        = string
  }

 variable "aws_access_key" {
   description = "AWS access key"
   type        = string
  }

 variable "aws_secret_key" {
   description = "AWS secret key"
   type        = string
   sensitive   = true
  }

Provide variable values in a terraform.tfvars file:

 aiven_api_token = "YOUR_AIVEN_API_TOKEN"
 project_name    = "YOUR_PROJECT_NAME"
 aws_region      = "your-aws-region"
 aws_access_key  = "your-aws-access-key"
 aws_secret_key  = "your-aws-secret-key"

Parameters:

project_name: Name of your Aiven project.
cloud_name: Cloud provider and region for hosting Aiven for Apache Kafka Connect service. Replace with the appropriate region, for example google-europe-west3.
plan: Service plan for Aiven for Apache Kafka Connect service.
service_name: Name of your Aiven for Kafka Connect service in Aiven.
auth_method: Authentication method used by AWS Secrets Manager. Set to credentials.
region: AWS region where your secrets are stored.
access_key: AWS access key for authentication.
secret_key: AWS secret key for authentication.
aiven_api_token:API token for authentication. Replace with your Aiven API token to manage resources.

Add AWS Secrets Manager using the Aiven CLI:

avn service update SERVICE_NAME \
  -c secret_providers='[
    {
      "name": "aws",
      "aws": {
        "auth_method": "credentials",
        "region": "your-aws-region",
        "access_key": "your-aws-access-key",
        "secret_key": "your-aws-secret-key"
      }
    }
  ]'

Parameters:

PROJECT_NAME: Name of your Aiven project.
SERVICE_NAME: Name of your Aiven Kafka service.
name: Name of the secret provider. In this case, aws.
auth_method: Authentication method used by AWS Secrets Manager. In this case, it is credentials.
region: AWS region where your secrets are stored.
access_key: Your AWS access key.
secret_key: Your AWS secret key.

Reference secrets in connector configurations

You can use secrets stored in AWS Secrets Manager with any connector. The examples below show how to configure secrets for JDBC connectors, but you can follow the same steps for other connectors.

JDBC sink connector

API
Terraform
CLI

Configure a JDBC sink connector using the API with secrets referenced from AWS Secrets Manager.

curl --request POST \
  --url https://api.aiven.io/v1/project/{PROJECT_NAME}/service/{SERVICE_NAME}/connectors \
  --header 'Authorization: Bearer YOUR_BEARER_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "YOUR_CONNECTOR_NAME",
    "connector.class": "io.aiven.connect.jdbc.JdbcSinkConnector",
    "connection.url": "jdbc:{DATABASE_TYPE}://{HOST}:{PORT}/{DATABASE_NAME}?user=${aws:PATH/TO/SECRET:USERNAME}&password=${aws:PATH/TO/SECRET:PASSWORD}&ssl=require",
    "topics": "YOUR_TOPIC",
    "auto.create": true
  }'

Parameters:

PROJECT_NAME: Name of your Aiven project.
SERVICE_NAME: Name of your Aiven Kafka service.
name: Name of the connector.
connector.class: Specifies the connector class to use, in this case, io.aiven.connect.jdbc.JdbcSinkConnector.
connection.url: JDBC connection URL with placeholders for DATABASE_TYPE, HOST, PORT, DATABASE_NAME, and the username and password retrieved from AWS Secrets Manager.
topics: Apache Kafka topic where the data can be sent.
auto.create: If true, the connector automatically creates the table in the target database if it does not exist.

Configure a JDBC sink connector using the Aiven Terraform Provider with secrets referenced from AWS Secrets Manager. Add this configuration to your main.tf file, or optionally create a dedicated connectors.tf file for managing Apache Kafka connectors:

resource "aiven_kafka_connector" "jdbc_sink_connector" {
  project        = var.project_name
  service_name   = aiven_kafka_connect.kafka_connect.service_name
  connector_name = "jdbc-sink-connector"

  config = {
    "connector.class"      = "io.aiven.connect.jdbc.JdbcSinkConnector"
    "connection.url"       = "jdbc:postgresql://{HOST}:{PORT}/{DATABASE_NAME}?user=${aws:PATH/TO/SECRET:USERNAME}&password=${aws:PATH/TO/SECRET:PASSWORD}&ssl=require"
    "topics"               = "your-topic"
    "auto.create"          = "true"
  }
}

Parameters:

project: Name of your Aiven project.
service_name: Name of the Aiven for Apache Kafka service where the connector is to be created.
connector_name: Name for your JDBC sink connector.
connector.class: Java class that implements the connector. For JDBC sink connectors, use "io.aiven.connect.jdbc.JdbcSinkConnector".
connection.url: JDBC URL for your database. Replace {HOST}, {PORT}, and {DATABASE_NAME} with your actual database details. The username and password are retrieved from AWS Secrets Manager using ${aws:PATH/TO/SECRET:USERNAME} and ${aws:PATH/TO/SECRET:PASSWORD}.
topics: Apache Kafka topics that the connector consumes data from.
auto.create: If true, the connector automatically creates the table in the target database if it does not exist.

Configure a JDBC sink connector using the Aiven CLI with secrets referenced from AWS Secrets Manager.

avn service connector create SERVICE_NAME '{
  "name": "jdbc-sink-connector",
  "connector.class": "io.aiven.connect.jdbc.JdbcSinkConnector",
  "connection.url": "jdbc:{DATABASE_TYPE}://{HOST}:{PORT}/{DATABASE_NAME}?user=${aws:PATH/TO/SECRET:USERNAME}&password=${aws:PATH/TO/SECRET:PASSWORD}&ssl=require",
  "topics": "your-topic",
  "auto.create": true
}'

Parameters:

SERVICE_NAME: Name of your Aiven for Apache Kafka service.
name: Name of the connector.
connector.class: Specifies the connector class to use, in this case, io.aiven.connect.jdbc.JdbcSinkConnector.
connection.url: JDBC connection URL with placeholders for DATABASE_TYPE, HOST, PORT, DATABASE_NAME, and the username and password retrieved from AWS Secrets Manager.
topics: Apache Kafka topic where the data can be sent.
auto.create: If true, the connector automatically creates the table in the target database if it does not exist.

JDBC source connector

API
Terraform
CLI

Configure a JDBC source connector using the API with secrets referenced from AWS Secrets Manager.

curl -X POST https://api.aiven.io/v1/project/{PROJECT_NAME}/service/{SERVICE_NAME}/connectors \
  -H "Authorization: Bearer YOUR_BEARER_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
        "name": "your-source-connector-name",
        "connector.class": "io.aiven.connect.jdbc.JdbcSourceConnector",
        "connection.url": "jdbc:{DATABASE_TYPE}://{HOST}:{PORT}/{DATABASE_NAME}?ssl=require",
        "connection.user": "${aws:PATH/TO/SECRET:USERNAME}",
        "connection.password": "${aws:PATH/TO/SECRET:PASSWORD}",
        "incrementing.column.name": "id",
        "mode": "incrementing",
        "table.whitelist": "your-table",
        "topic.prefix": "your-prefix_",
        "auto.create": "true"
      }'

Parameters:

PROJECT_NAME: Name of your Aiven project.
SERVICE_NAME: Name of your Aiven for Apache Kafka service.
name: Name of the connector.
connector.class: Specifies the connector class to use, in this case, io.aiven.connect.jdbc.JdbcSinkConnector.
connection.url: JDBC connection URL with placeholders for DATABASE_TYPE, HOST, PORT, DATABASE_NAME, and the username and password retrieved from AWS Secrets Manager.
connection.user: Database username retrieved from AWS Secrets Manager
connection.password: Database password retrieved from AWS Secrets Manager.
incrementing.column.name: Column used for incrementing mode.
mode: Mode of operation, in this case, incrementing.
table.whitelist: Tables to include.
topic.prefix: Prefix for Apache Kafka topics.
auto.create: If true, the connector automatically creates the table in the target database if it does not exist.

Configure a JDBC source connector using the Aiven Terraform Provider with secrets referenced from AWS Secrets Manager. Add this configuration to your main.tf file, or optionally create a dedicated connectors.tf file for managing Apache Kafka connectors:

resource "aiven_kafka_connector" "jdbc_source_connector" {
  project        = var.project_name
  service_name   = aiven_kafka_connect.kafka_connect.service_name
  connector_name = "jdbc-source-connector"

  config = {
    "connector.class"      = "io.aiven.connect.jdbc.JdbcSourceConnector"
    "connection.url"       = "jdbc:postgresql://{HOST}:{PORT}/{DATABASE_NAME}?ssl=require"
    "connection.user"      = "${aws:PATH/TO/SECRET:USERNAME}"
    "connection.password"  = "${aws:PATH/TO/SECRET:PASSWORD}"
    "incrementing.column.name" = "id"
    "mode"                 = "incrementing"
    "table.whitelist"      = "your-table"
    "topic.prefix"         = "your-prefix_"
    "auto.create"          = "true"
  }
}

Parameters:

project: Name of your Aiven project.
service_name: Name of the Aiven for Apache Kafka service where the connector is to be created.
connector_name: Name for your JDBC source connector.
connector.class: Java class that implements the connector. For JDBC source connectors, use "io.aiven.connect.jdbc.JdbcSourceConnector".
connection.url: JDBC URL for your database. Replace {HOST}, {PORT}, and {DATABASE_NAME} with your actual database details. The username and password are retrieved from AWS Secrets Manager using ${aws:PATH/TO/SECRET:USERNAME} and ${aws:PATH/TO/SECRET:PASSWORD}.
connection.user: Username for connecting to the database, retrieved from AWS Secrets Manager.
connection.password: Password for connecting to the database, retrieved from AWS Secrets Manager.
incrementing.column.name: Name of the column used for incrementing mode, typically a primary key column.
mode: Mode of operation for the connector. incrementing mode reads data incrementally based on the specified column.
table.whitelist: List of tables that the connector includes when reading data from the database.
topic.prefix: Prefix that the connector adds to the Kafka topic names it produces data to.
auto.create: If set to true, the connector automatically creates the target table in the database if it does not exist.

Configure a JDBC source connector using the Aiven CLI with secrets referenced from AWS Secrets Manager.

avn service connector create SERVICE_NAME '{
  "name": "jdbc-source-connector",
  "connector.class": "io.aiven.connect.jdbc.JdbcSourceConnector",
  "connection.url": "jdbc:{DATABASE_TYPE}://{HOST}:{PORT}/{DATABASE_NAME}?ssl=require",
  "connection.user": "${aws:PATH/TO/SECRET:USERNAME}",
  "connection.password": "${aws:PATH/TO/SECRET:PASSWORD}",
  "incrementing.column.name": "id",
  "mode": "incrementing",
  "table.whitelist": "your-table",
  "topic.prefix": "your-prefix_",
  "auto.create": true
}'

Parameters:

SERVICE_NAME: Name of your Aiven for Apache Kafka service.
name: Name of the connector.
connector.class: Specifies the connector class to use, in this case, io.aiven.connect.jdbc.JdbcSinkConnector.
connection.url:JDBC connection URL with placeholders for DATABASE_TYPE, HOST, PORT, DATABASE_NAME, and the username and password retrieved from AWS Secrets Manager.
connection.user: Database username retrieved from AWS Secrets Manager
connection.password: Database password retrieved from AWS Secrets Manager.
incrementing.column.name: Column used for incrementing mode.
mode: Mode of operation, in this case, incrementing.
table.whitelist: Tables to include.
topic.prefix: Prefix for Apache Kafka topics.
auto.create: If true, the connector automatically creates the table in the target database if it does not exist.

Prerequisites​

Configure secret providers​

Reference secrets in connector configurations​

JDBC sink connector​

JDBC source connector​

Prerequisites

Configure secret providers

Reference secrets in connector configurations

JDBC sink connector

JDBC source connector