<a id="cc-mysql-sink"></a>

# MySQL Sink (JDBC) Connector for Confluent Cloud

The fully managed MySQL Sink connector for Confluent Cloud exports data from Kafka
topics to a MySQL database.

#### NOTE
- This Quick Start is for the fully managed Confluent Cloud connector. If you are
  installing the connector locally for Confluent Platform, see [JDBC Connector (Source and
  Sink) for Confluent Platform](https://docs.confluent.io/kafka-connectors/jdbc/current/).
- If you require private networking for fully managed connectors, make sure to set up the proper
  networking beforehand. For more information, see [Manage Networking for Confluent Cloud Connectors](networking/internet-resource.md#clusters-connect-cloud).

## Features

The MySQL Sink connector provides the following features:

* **Supports multiple tasks**: The connector supports running one or more tasks. More tasks may improve performance.
* **Table and column auto-creation**: `auto.create` and `auto-evolve` are supported. If tables or columns are missing, they can be created automatically. Table names are created based on Kafka topic names.
* **Database authentication:** Supports username/password authentication, Google service account impersonation,
  Microsoft Entra ID-based authentication, and AWS IAM role-based authentication using Confluent
  Provider Integration. For more information about provider integration setup, see the
  [connector authentication](#cc-mysql-sink-setup-connection) and
  [AWS IAM Authentication Setup](#cc-mysql-sink-aws-iam-auth).
* **Schemas**: The connector supports Avro, JSON Schema, and Protobuf input data formats. [Schema Registry](../get-started/schema-registry.md#cloud-sr-config) must be enabled to use a Schema Registry-based format.
* **Modes**: This connector inserts and upserts Kafka records into a MySQL database.
* **Primary key support**: Supported **PK modes** are `kafka`, `none`, `record_key`, and `record_value`. Used in conjunction with the **PK Fields** property.
* **Secret manager integration**: The connector supports secret manager integration. For `Password` based authentication, the connector can retrieve the following configurations from an integrated secret manager at runtime as needed.

  | **Secret manager managed configuration**   | **Type**   |
  |--------------------------------------------|------------|
  | `connection.user`                          | `STRING`   |
  | `connection.password`                      | `PASSWORD` |

  For more information, see [Create a secret manager integration in Confluent Cloud](secret-manager-integration/overview.md#cloud-secret-manager-quickstart).
* **SSL support**: Supports both one-way SSL for server CA certificate validation and
  mTLS, where the connector presents a client certificate so the database can
  authenticate the connector. See
  [How do I configure SSL/TLS connections to MySQL?](#cc-mysql-sink-ssl-tls-faq)
  for details.

For more information and examples to use with the Confluent Cloud API for Connect,
see the [Confluent Cloud API for Connect Usage Examples](connect-api-section.md#ccloud-connect-api) section.

## Limitations

Be sure to review the following information.

* For connector limitations, see [MySQL Sink Connector](limits.md#cc-mysql-sink-limits) limitations.
* If you plan to use one or more Single Message Transformations (SMTs), see [SMT Limitations](single-message-transforms.md#cc-single-message-transforms-limitations).

## Quick Start

Use this quick start to get up and running with the Confluent Cloud MySQL sink
connector. The quick start provides the basics of selecting the connector and
configuring it to stream events to a MySQL database.

<a id="cc-mysql-sink-prereqs"></a>

Prerequisites
: - Authorized access to a [Confluent Cloud](https://www.confluent.io/confluent-cloud/) cluster on Amazon Web Services (AWS), Microsoft Azure (Azure), or Google Cloud.
  - Access to a MySQL database.
  - The Confluent CLI installed and configured for the cluster. See [Install the Confluent CLI](https://docs.confluent.io/confluent-cli/current/install.html).
  - [Schema Registry](../get-started/schema-registry.md#cloud-sr-config) must be enabled to use a Schema Registry-based format (for example, Avro, JSON_SR (JSON Schema), or Protobuf).
  - For networking considerations, see [Networking and DNS](overview.md#connect-internet-access-resources). To use a set of public egress IP addresses, see [Public Egress IP Addresses for Confluent Cloud Connectors](static-egress-ip.md#cc-static-egress-ips).
  - [Schema Registry](../get-started/schema-registry.md#cloud-sr-config) must be enabled to use a Schema Registry-based format (for example, Avro, JSON_SR (JSON Schema), or Protobuf).
  <br/>
  - Kafka cluster credentials. The following lists the different ways you can provide credentials.
    - Enter an existing [service account](service-account.md#s3-cloud-service-account) resource ID.
    - Create a Confluent Cloud [service account](service-account.md#s3-cloud-service-account) for the connector. Make sure to review the ACL entries required in the [service account documentation](service-account.md#s3-cloud-service-account). Some connectors have specific ACL requirements.
    - Create a Confluent Cloud API key and secret. To create a key and secret, you can use [confluent api-key create](https://docs.confluent.io/confluent-cli/current/command-reference/api-key/confluent_api-key_create.html) *or* you can autogenerate the API key and secret directly in the Cloud Console when setting up the connector.

### Using the Confluent Cloud Console

#### Step 1: Launch your Confluent Cloud cluster

To create and launch a Kafka cluster in Confluent Cloud, see [Create a kafka cluster in Confluent Cloud](../get-started/index.md#cloud-create-kafka-cluster).

#### Step 2: Add a connector

In the left navigation menu, click **Connectors**. If you already have connectors in your cluster, click **+ Add
connector**.

#### Step 3: Select your connector

Click the **MySQL Sink** connector card.

![MySQL Sink Connector Card](images/ccloud-mysql-sink-icon.png)

<a id="cc-mysql-sink-setup-connection"></a>

#### Step 4: Enter the connector details

#### NOTE
* Ensure you have all your [prerequisites](#cc-mysql-sink-prereqs) completed.
* An asterisk ( \* ) designates a required entry.

At the **Add MySQL Sink Connector** screen, complete the following:

### Topic selection

If you’ve already populated your Kafka topics, select the topics you want
to connect from the **Topics** list.

To create a new topic, click **+Add new topic**.

### Kafka access

1. Select the way you want to provide **Kafka Cluster credentials**. You can
   choose one of the following options:
   - **My account**: This setting allows your connector to globally access everything
     that you have access to. With a user account, the connector uses an API key and
     secret to access the Kafka cluster. This option is not recommended for production.
   - **Service account**: This setting limits the access for your connector by using a
     [service account](service-account.md#s3-cloud-service-account). This option is recommended for
     production.
   - **Use an existing API key**: This setting allows you to specify an API key and a
     secret pair. You can use an existing pair or create a new one. This method is not
     recommended for production environments.

   #### NOTE
   Freight clusters support only service accounts for Kafka authentication.
2. Click **Continue**.

### Authentication

1. Configure the authentication properties:

   **Authentication method**
   - **Authentication method**: How Confluent Cloud authenticates with Azure or Google Cloud.

     Allowed values are:
     * `Password`
     * `Microsoft Entra ID application`
     * `Google service account impersonation`
   - **Use secret manager**: Fetch sensitive configuration values from a secret manager.
   - **Provider Integration**: The provider integration Confluent Cloud uses to access your resource.
   - **Database AWS region**: The AWS region of your RDS or Aurora database
     instance, for example `us-east-1`. Required
     when the authentication method is `IAM Roles`.

   **Secret manager configuration**
   - **Secret manager**: Select the secret manager to use for retrieving sensitive data.
   - **Configurations from Secret manager**: Select the configurations whose values
     Confluent Cloud should fetch from the secret manager.
   - **Provider Integration**: The provider integration Confluent Cloud uses to access your resource.

   **How should we connect to your database?**
   - **Connection host**: The JDBC connection host.
   - **Connection port**: The JDBC connection port.
   - **Connection user**: The JDBC connection user.
   - **Connection password**: The JDBC connection password.
   - **Database name**: The JDBC database name.
   - **SSL mode**: The SSL mode to use to connect to your database.
   - **Trust store**: The trust store file that contains the server CA
     certificate.
   - **Trust store password**: The password for the trust store file that contains the
     server CA certificate.
   - **Trust store type**: The key store type for trusted root certificates.
     Only required if using `verify-ca` or `verify-full` SSL mode.
     The connector supports files in `JKS` and `PKCS12` format.
   - **Client Certificate key store**: The binary key store file that contains
     the client’s certificate, used for mutual
     TLS authentication.

     The connector supports files in `JKS` and `PKCS12` format.
     For REST API usage, you must base64-encode the binary
     file and add the appropriate prefix.
     For JKS files, use `data:text/plain;base64,`, and
     for PKCS12 files, use `data:application/x-pkcs12;base64,`.

     For example, run `base64_clientstore=$(cat /path/to/keystore.jks | base64)`
     and then use `data:text/plain;base64,${base64_clientstore}` as the value.
   - **Client Certificate key store password**: The key store password for the client certificate key store.
   - **Client Certificate key store type**: The key store type for client certificate.
     The connector supports files in `JKS` and `PKCS12` format.
2. Click **Continue**.

### Configuration

#### NOTE
Configuration properties that are not shown in the
Cloud Console use the default values.  See
[Configuration Properties](#cc-mysql-sink-config-properties) for all property values and
definitions.

- **Input Kafka record value format**: Sets the input Kafka record value format. Valid entries are AVRO, JSON_SR, or PROTOBUF. Note that you need to have Confluent Cloud Schema Registry configured if using a schema-based message format like AVRO, JSON_SR, and PROTOBUF.
- **Insert mode**: The insertion mode to use. INSERT uses the standard INSERT row function. An error occurs if the row already exists in the table. UPSERT mode is similar to INSERT. However, if the row already exists, the UPSERT function overwrites column values with the new values provided.

### **Show advanced configurations**

- **Schema context**: Select a schema context to use for this connector, if using
  a schema-based data format. This property defaults to the **Default** context,
  which configures the connector to use the default schema set up for Schema Registry in your
  Confluent Cloud environment. A schema context allows you to use separate schemas (like
  schema sub-registries) tied to topics in different Kafka clusters that share the
  same Schema Registry environment. For example, if you select a non-default context, a
  **Source** connector uses only that schema context to register a schema and a
  **Sink** connector uses only that schema context to read from. For more
  information about setting up a schema context, see [What are schema contexts and when should you use them?](../sr/faqs-cc.md#faq-schema-contexts).
- **Auto create table**: Whether to automatically create the
  destination table if it is missing.
- **Auto add columns**: Whether to automatically add columns in the
  table if they are missing.
- **Database timezone**: Name of the JDBC timezone that should be
  used in the connector when inserting time-based values.
- **Table name format**: A format string for the destination table
  name that may contain `${topic}` as a placeholder for the
  originating topic name. For example, to create a table named
  `kafka-orders` based on a Kafka topic named `orders`, you would
  enter `kafka-${topic}` in this field.
- **Timezone used for Date**: Name of the JDBC timezone that should be used in the connector when inserting `DATE` type values. Defaults to `DB_TIMEZONE` that uses the timezone set for `db.timezeone` configuration (to maintain backward compatibility). It is recommended to set this to UTC to avoid conversion for `DATE` type values.
- **Timestamp Precision Mode**: Converts the timestamp with precision. If set to microseconds, the timestamp is converted to microsecond precision. If set to nanoseconds, the timestamp is converted to nanosecond precision.
- **Timestamp Fields**: List of comma-separated record value timestamp field names that should be converted to timestamps. These fields will be converted based on precision mode specified in Timestamp Precision Mode. The timestamp fields included here should be Long or String type and nested fields are not supported.
- **Table types**: The comma-separated types of database tables to
  which the sink connector can write.
- **Fields included**: List of comma-separated record value field
  names. If empty, all fields from the record value are used.
- **PK mode**: The primary key mode.
- **PK Fields**: List of comma-separated primary key field names.
- **When to quote SQL identifiers**: When to quote table names,
  column names, and other identifiers in SQL statements.
- **Max rows per batch**: Maximum number of rows to include in a
  single batch when polling for new data. This setting can be used
  to limit the amount of data buffered internally in the connector.
- **Input Kafka record key format**: Sets the input Kafka record key
  format. Valid values are AVRO, JSON_SR, PROTOBUF, STRING. A valid
  schema must be available in [Schema Registry](../get-started/schema-registry.md#cloud-sr-config) to use a schema-based record format.
- **Delete on null**: Whether to treat null record
  values as deletes. This requires `pk.mode` to be `record_key`.
- **String Value Column Name**: Name of the destination table column
  when the Kafka record value written using
  `StringConverter` is sinked to the DB table

  The raw string value is written into this column.
  If the destination table is auto-created,
  the column is created with the name specified
  in this field. If the table already exists and
  the column is missing, the column is added using
  `ALTER` when `auto.evolve` is set to `true`.

  #### NOTE
  Databases that treat quoted identifiers as case-sensitive,
  like PostgreSQL, ensure that the column name in the
  existing table exactly matches this value.

  Defaults to `record_value`.
- **Date Calendar System**: Conversion of time since epoch value in Kafka topic record to `DATE` or `TIMESTAMP` depends on the calendar used to interpret it. If `LEGACY` is used, it will use the hybrid Gregorian/Julian calendar which was the default in the older java date time APIs. However, if `PROLEPTIC_GREGORIAN` is used, then it will use the proleptic gregorian calendar which extends the Gregorian rules backward indefinitely and does not apply the 1582 cutover. This matches the behavior of modern Java date/time APIs (`java.time`). This is defaulted to `LEGACY` for backward compatibility. The ideal setting for this depends on whether the values in source topic were populated using old or new java date time APIs. Changing this configuration on an existing connector might lead to a drift in the `DATE`/`TIMESTAMP` column’s values populated in the sink database.

**Additional Configs**

- **Value Converter Replace Null With Default**: Specifies whether to replace fields that have a default value and that are null to the default value. When set to `true`, the connector uses the default value; otherwise, it uses `null`. Applies to the `JSON` converter.
- **Value Converter Schema ID Deserializer**: Sets the class name of the schema ID deserializer for values. The deserializer reads schema IDs from message headers.
- **Value Converter Reference Subject Name Strategy**: Sets the subject reference name strategy for values. Valid entries are `DefaultReferenceSubjectNameStrategy` or `QualifiedReferenceSubjectNameStrategy`. You can use this strategy only with `PROTOBUF` format; the default strategy is `DefaultReferenceSubjectNameStrategy`.
- **Schema ID For Value Converter**: Sets the schema ID to use for deserialization when using `ConfigSchemaIdDeserializer`. This lets you specify a fixed schema ID for deserializing message values. This property is applicable only when `value.converter.value.schema.id.deserializer` is set to `ConfigSchemaIdDeserializer`.
- **Value Converter Schemas Enable**: Includes schema within each of the serialized values. Input messages must contain `schema` and `payload` fields and must not contain additional fields. For plain `JSON` data, set this to `false`. Applies to the `JSON` converter.
- **Errors Tolerance**: Use this property to configure the connector’s error handling behavior.

  #### WARNING
  Use this property with caution for sink connectors, as it can lead to data loss. If you set this property to `all`, the connector does not fail on errant records, but logs them (and sends to DLQ for sink connectors) and continues processing. If you set this property to `none`, the connector task fails on errant records.
- **Value Converter Ignore Default For Nullables**: When set to `true`, this property ensures that the corresponding record in Kafka is `null`, instead of showing the default column value. Applies to the `AVRO`, `PROTOBUF`, and `JSON_SR` converters.
- **Key Converter Schema ID Deserializer**: Sets the class name of the schema ID deserializer for keys. The deserializer reads schema IDs from message headers.
- **Value Converter Decimal Format**: Specifies the `JSON` or `JSON_SR` serialization format for Connect `DECIMAL` logical type values with two allowed literals:
  `BASE64` to serialize `DECIMAL` logical types as base64 encoded binary data, and
  `NUMERIC` to serialize `DECIMAL` logical type values in `JSON` or `JSON_SR` as a number representing the decimal value.
- **Schema GUID For Key Converter**: Sets the schema GUID to use for deserialization when using `ConfigSchemaIdDeserializer`. This lets you specify a fixed schema GUID for deserializing message keys. This property is applicable only when `key.converter.key.schema.id.deserializer` is set to `ConfigSchemaIdDeserializer`.
- **Schema GUID For Value Converter**: Sets the schema GUID to use for deserialization when using `ConfigSchemaIdDeserializer`. This lets you specify a fixed schema GUID for deserializing message values. This property is applicable only when `value.converter.value.schema.id.deserializer` is set to `ConfigSchemaIdDeserializer`.
- **Value Converter Connect Meta Data**: Enables the Connect converter to add its metadata to the output schema. Applies to Avro converters.
- **Value Converter Value Subject Name Strategy**: Determines how to construct the subject name under which the value schema is registered with Schema Registry.
- **Key Converter Key Subject Name Strategy**: Determines how to construct the subject name for key schema registration.
- **Schema ID For Key Converter**: Sets the schema ID to use for deserialization when using `ConfigSchemaIdDeserializer`. This lets you specify a fixed schema ID for deserializing message keys. This property is applicable only when `key.converter.key.schema.id.deserializer` is set to `ConfigSchemaIdDeserializer`.

**Auto-restart policy**

- **Enable Connector Auto-restart**: Enables the auto-restart behavior of the connector and its
  task in the event of user-actionable errors. Defaults to `true`, enabling the connector to
  automatically restart in case of user-actionable errors. Set this property to `false` to
  disable auto-restart for failed connectors. If disabled, you must manually restart the connector.

**Consumer configuration**

- **Max poll interval(ms)**: Sets the maximum delay between subsequent consume requests to Kafka. Use this property to
  improve connector performance in cases when the connector cannot send records to the sink system.
  The default is 300,000 milliseconds (5 minutes).
- **Max poll records**: Sets the maximum number of records to consume from Kafka in a single request. Use this property to
  improve connector performance in cases when the connector cannot send records to the sink system.
  The default is 500 records.

**Transforms**

- **Single Message Transformations**: To add a new SMT, see [Add transforms](single-message-transforms.md#cc-single-message-transforms-ui).
  For more information about unsupported SMTs, see
  [Unsupported transformations](single-message-transforms.md#cc-single-message-transforms-unsupported-transforms).

**Processing position**

- **Set offsets**: Click **Set offsets** to define a specific offset for
  this connector to begin procession data from. For more information
  on managing offsets, see [Manage offsets](offsets.md#connect-custom-offsets).

For all property values and definitions, see [Configuration Properties](#cc-mysql-sink-config-properties).

- Click **Continue**.

### Sizing

Based on the number of topic partitions you select, you will be provided
with a recommended number of tasks.

1. To change the number of recommended tasks, enter the number of
   [tasks](/platform/current/connect/concepts.html#tasks) for the connector to use in
   the **Tasks** field.
2. Click **Continue**.

### Review and Launch

1. Verify the connection details.
2. Click **Launch**.

   The status for the connector should go from **Provisioning** to
   **Running**.

#### Step 5: Check the results in the database

Verify that new records are being added to the MySQL database.

For more information and examples to use with the Confluent Cloud API for Connect,
see the [Confluent Cloud API for Connect Usage Examples](connect-api-section.md#ccloud-connect-api) section.

### Using the Confluent CLI

Complete the following steps to set up and run the connector using the Confluent CLI.

#### NOTE
Make sure you have all your [prerequisites](#cc-mysql-sink-prereqs) completed.

#### Step 1: List the available connectors

Enter the following command to list available connectors:

```none
confluent connect plugin list
```

#### Step 2: List the connector configuration properties

Enter the following command to show the connector configuration properties:

```none
confluent connect plugin describe <connector-plugin-name>
```

The command output shows the required and optional configuration properties.

#### Step 3: Create the connector configuration file

Create a JSON file that contains the connector configuration properties. The
following examples show required and optional connector properties for both
password and IAM role-based authentication.

Using password authentication:

```none
{
  "connector.class": "MySqlSink",
  "name": "MySqlSinkConnector_0",
  "topics": "pageviews",
  "input.data.format": "AVRO",
  "input.key.format": "AVRO",
  "kafka.auth.mode": "KAFKA_API_KEY",
  "kafka.api.key": "****************",
  "kafka.api.secret": "****************************************************************",
  "connection.host": "dev-testing-temp.abcdefghijk.us-west-7.rds.amazonaws.com",
  "connection.port": "3306",
  "connection.user": "admin",
  "connection.password": "**********",
  "db.name": "test",
  "insert.mode": "INSERT",
  "auto.create": "true",
  "auto.evolve": "true",
  "tasks.max": "1"
}
```

Using IAM role-based authentication:

```none
{
  "connector.class": "MySqlSink",
  "name": "MySqlSinkConnector_0",
  "topics": "pageviews",
  "input.data.format": "AVRO",
  "input.key.format": "AVRO",
  "kafka.auth.mode": "KAFKA_API_KEY",
  "kafka.api.key": "****************",
  "kafka.api.secret": "****************************************************************",
  "connection.host": "dev-testing-temp.abcdefghijk.us-west-7.rds.amazonaws.com",
  "connection.port": "3306",
  "connection.user": "db_user_with_iam_login",
  "db.name": "test",
  "insert.mode": "INSERT",
  "auto.create": "true",
  "auto.evolve": "true",
  "tasks.max": "1",
  "authentication.method": "IAM Roles",
  "provider.integration.id": "dlz-f3a90de",
  "database.aws.region": "us-west-7"
}
```

Note the following property definitions:

* `"connector.class"`: Identifies the connector plugin name.
* `"name"`: Sets a name for your new connector.
* `"topics"`: Identifies the topic name or a comma-separated list of topic names.
* `"input.data.format"`:  Sets the input record value format (data coming from the Kafka topic). Valid entries are **AVRO**, **JSON_SR** (JSON Schema), **PROTOBUF**, **JSON**, or **STRING**. You must have Confluent Cloud Schema Registry configured if using a schema-based message format.
* `"input.key.format"`: Sets the input record key format (data coming from the Kafka topic). Valid entries are **AVRO**, **JSON_SR** (JSON Schema), **PROTOBUF**, or **STRING**. You must have Confluent Cloud Schema Registry configured if using a schema-based message format.
* `"delete.on.null"`: Whether to treat null record values as deletes. Requires `pk.mode` to be `record_key`. Defaults to `false`.
* `"authentication.method"`: Set to `"IAM Roles"` to use AWS IAM role-based authentication. Other supported values are `"Password"`, `"Microsoft Entra ID application"`, and `"Google service account impersonation"`.
* `"provider.integration.id"`: The ID of the provider integration resource that contains the IAM role, service account, or application configuration. Required for every authentication method except `"Password"`.
* `"database.aws.region"`: The AWS region of the MySQL database server for RDS/Aurora. Only applicable when using IAM role-based authentication.
* `"connection.password"`: Password of the MySQL database user that has the required authorization. Only applicable when using password-based authentication.

* `"kafka.auth.mode"`: Identifies the connector authentication mode you want to use. There are two options: `SERVICE_ACCOUNT` or `KAFKA_API_KEY` (the default). To use an API key and secret, specify the configuration properties `kafka.api.key` and `kafka.api.secret`, as shown in the example configuration (above).  To use a [service account](service-account.md#s3-cloud-service-account), specify the **Resource ID** in the property `kafka.service.account.id=<service-account-resource-ID>`. To list the available service account resource IDs, use the following command:
  ```bash
  confluent iam service-account list
  ```

  For example:
  ```bash
  confluent iam service-account list

     Id     | Resource ID |       Name        |    Description
  +---------+-------------+-------------------+-------------------
     123456 | sa-l1r23m   | sa-1              | Service account 1
     789101 | sa-l4d56p   | sa-2              | Service account 2
  ```

* `"insert.mode"`: Enter one of the following modes:
  - `INSERT`: Use the standard `INSERT` row function. An error occurs if the row already exists in the table.
  - `UPSERT`: This mode is similar to `INSERT`. However, if the row already exists, the `UPSERT` function overwrites column values with the new values provided.
* `"auto.create"` (tables) and `"auto-evolve"` (columns): (Optional) Sets whether to automatically create tables or columns if they are missing relative to the input record schema. If not entered in the configuration, both default to `false`.
* `"tasks.max"`: Maximum number of tasks the connector can run. See Confluent Cloud [connector limitations](limits.md#cc-mysql-sink-limits) for additional task information.

The following lists a few optional properties. See the [MySQL Sink
configuration properties](#cc-mysql-sink-config-properties) for other property
values and definitions.

* `"pk.mode"`: Supported modes are listed below:
  - `kafka`: Kafka coordinates are used as the primary key. Must be used with the **PK Fields**.
  - `none`: No primary keys used.
  - `record_key`: Fields from the record key are used. May be a primitive or a struct.
  - `record_value`: Fields from the Kafka record value are used. Must be a struct type.
* `"pk.fields"`: A list of comma-separated primary key field names. The runtime interpretation of this property depends on the `pk.mode` selected. Options are listed below:
  - `kafka`: Must be three values representing the Kafka coordinates. If left empty, the coordinates default to `__connect_topic,__connect_partition,__connect_offset`.
  - `none`: PK Fields not used.
  - `record_key`: If left empty, all fields from the key struct are used. Otherwise, this is used to extract the fields in the property. A single field name must be configured for a primitive key.
  - `record_value`: Used to extract fields from the record value. If left empty, all fields from the value struct are used.
* The following provides more information about how to use the `ssl.mode` property:
  - `prefer` (default): Attempts to use an encrypted connection. Falls back to
    an unencrypted connection if SSL is unavailable. Used when `ssl.mode` is not
    added to the connector configuration. Does not perform Certification Authority
    (CA) validation.
  - `require`: Uses a secure (encrypted) connection. The connector fails if a
    secure connection cannot be established. Does not perform Certification
    Authority (CA) validation.
  - `verify-ca`: Similar to `require`, but also verifies the server TLS certificate
    against the configured Certificate Authority (CA) certificates. Fails if no
    valid matching CA certificates are found.
  - `verify-full`: Similar to `verify-ca`, but also verifies that the server
    certificate matches the host to which the connection is attempted.

  If you choose `verify-ca` or `verify-full`, provide the server CA in a
  truststore using the `ssl.truststorefile`, `ssl.truststorepassword`, and
  `ssl.truststoretype` properties.

  To authenticate the connector to the database with mTLS, provide a client
  certificate keystore using the `ssl.clientstorefile`,
  `ssl.clientstorepassword`, and `ssl.clientstoretype` properties. Client
  authentication works with any `ssl.mode`.

  For details and examples, see
  [How do I configure SSL/TLS connections to MySQL?](#cc-mysql-sink-ssl-tls-faq).

**SMTs**: For details about adding SMTs using the Confluent CLI, see the [Single Message Transformations](single-message-transforms.md#cc-single-message-transforms) documentation.

See [Configuration Properties](#cc-mysql-sink-config-properties) for all property values and
definitions.

#### Step 4: Load the configuration file and create the connector

Enter the following command to load the configuration and start the connector:

```none
confluent connect cluster create --config-file <file-name>.json
```

For example:

```none
confluent connect cluster create --config-file mysql-server-sink-config.json
```

Example output:

```none
Created connector MySqlSinkConnector_0 lcc-ix4dl
```

#### Step 5: Check the connector status

Enter the following command to check the connector status:

```none
confluent connect cluster list
```

Example output:

```none
ID          |       Name              | Status  | Type
+-----------+-------------------------+---------+------+
lcc-ix4dl   | MySqlSinkConnector_0    | RUNNING | sink
```

#### Step 6: Check the results in the database.

Verify that new records are being added to the MySQL database.

For more information and examples to use with the Confluent Cloud API for Connect,
see the [Confluent Cloud API for Connect Usage Examples](connect-api-section.md#ccloud-connect-api) section.

<a id="cc-mysql-sink-aws-iam-auth"></a>

## AWS IAM Authentication Setup

To use AWS IAM role-based authentication with the MySQL Sink connector,
configure your MySQL database as described in the following steps.

### Common setup

1. Enable IAM authentication on your RDS or Aurora instance/cluster (the
   **Database authentication** option in the AWS Console, or set
   `--enable-iam-database-authentication` with the AWS CLI). For an
   existing instance/cluster, this change applies immediately.
2. Create a database user with AWS IAM authentication enabled:
   ```sql
   CREATE USER 'db-username'@'%' IDENTIFIED WITH AWSAuthenticationPlugin AS 'RDS';
   ```
3. Grant the necessary permissions to the database user:
   ```sql
   GRANT INSERT, UPDATE, DELETE, SELECT, CREATE, ALTER ON *.* TO 'db-username'@'%';
   ```

   Scope the grants down to the target schema/tables for your use case; `CREATE`/`ALTER` are only required if you rely on `auto.create`/`auto.evolve`.

### IAM permission policy

Attach the following IAM permission policy to the IAM role you have integrated
with provider integration. The same policy shape applies to both RDS instances
and Aurora clusters, only the resource identifier differs.

For RDS MySQL (use the per-instance `DbiResourceId`, an immutable string of
the form `db-XXXXXXXXXXXXXXXXXXXXXXXXXX`, not the human-friendly DB instance
identifier):

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "rds-db:connect",
      "Resource": [
        "arn:aws:rds-db:<region>:<account-id>:dbuser:<db-instance-resource-id>/<db-username>"
      ]
    }
  ]
}
```

For Aurora MySQL (use the cluster `DbClusterResourceId`, an immutable string
of the form `cluster-XXXXXXXXXXXXXXXXXXXXXXXXXX`, not the cluster identifier
or the writer-instance resource ID):

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "rds-db:connect",
      "Resource": [
        "arn:aws:rds-db:<region>:<account-id>:dbuser:<db-cluster-resource-id>/<db-username>"
      ]
    }
  ]
}
```

Replace the `region`, `account-id`, `db-instance-resource-id` (for RDS)
or `db-cluster-resource-id` (for Aurora), and `db-username` placeholders
with the values for your environment. You can find the resource ID on the
**Configuration** tab of your RDS instance or Aurora cluster in the AWS
Console, or by using `aws rds describe-db-instances --query
'DBInstances[].DbiResourceId'` / `aws rds describe-db-clusters --query
'DBClusters[].DbClusterResourceId'`. The IAM token the connector generates is
signed against the database hostname, so ensure the connector’s
`connection.host` is the canonical AWS-managed RDS or Aurora endpoint.

<a id="cc-mysql-sink-config-properties"></a>

## Configuration Properties

Use the following configuration properties with the fully managed connector. For
self-managed connector property definitions and other details, see the connector
docs in [Self-managed connectors for Confluent Platform](/platform/current/connect/kafka_connectors.html).

### Which topics do you want to get data from?

`topics.regex`
: A regular expression that matches the names of the topics to consume from. This is useful when you want to consume from multiple topics that match a certain pattern without having to list them all individually.
  <br/>
  * Type: string
  * Importance: low

`topics`
: Identifies the topic name or a comma-separated list of topic names.
  <br/>
  * Type: list
  * Importance: high

`errors.deadletterqueue.topic.name`
: The name of the topic to be used as the dead letter queue (DLQ) for messages that result in an error when processed by this sink connector, or its transformations or converters. Defaults to ‘dlq-${connector}’ if not set. The DLQ topic will be created automatically if it does not exist. You can provide `${connector}` in the value to use it as a placeholder for the logical cluster ID.
  <br/>
  * Type: string
  * Default: dlq-${connector}
  * Importance: low

### Schema Config

`schema.context.name`
: Add a schema context name. A schema context represents an independent scope in Schema Registry. It is a separate sub-schema tied to topics in different Kafka clusters that share the same Schema Registry instance. If not used, the connector uses the default schema configured for Schema Registry in your Confluent Cloud environment.
  <br/>
  * Type: string
  * Default: default
  * Importance: medium

### Input messages

`input.data.format`
: Sets the input Kafka record value format. Valid entries are AVRO, JSON_SR, PROTOBUF, JSON, or STRING. Note that you need to have Confluent Cloud Schema Registry configured if using a schema-based message format like AVRO, JSON_SR, and PROTOBUF. JSON and STRING formats do not require Schema Registry. When JSON is selected, value.converter.schemas.enable must be set to true.
  <br/>
  * Type: string
  * Importance: high

`input.key.format`
: Sets the input Kafka record key format. This need to be set to a proper format if using pk.mode=record_key. Valid entries are AVRO, JSON_SR, PROTOBUF, JSON, or STRING. Note that you need to have Confluent Cloud Schema Registry configured if using a schema-based message format like AVRO, JSON_SR, and PROTOBUF. JSON and STRING formats do not require Schema Registry. When pk.mode is set to record_key and JSON is selected, the record key must include an inline schema.
  <br/>
  * Type: string
  * Importance: high

`delete.enabled`
: Whether to treat null record values as deletes. Requires pk.mode to be record_key.
  <br/>
  * Type: boolean
  * Default: false
  * Importance: low

### How should we connect to your data?

`name`
: Sets a name for your connector.
  <br/>
  * Type: string
  * Valid Values: A string at most 64 characters long
  * Importance: high

### Kafka Cluster credentials

`kafka.auth.mode`
: Kafka Authentication mode. It can be one of KAFKA_API_KEY or SERVICE_ACCOUNT. It defaults to KAFKA_API_KEY mode, whenever possible.
  <br/>
  * Type: string
  * Valid Values: SERVICE_ACCOUNT, KAFKA_API_KEY
  * Importance: high

`kafka.api.key`
: Kafka API Key. Required when kafka.auth.mode==KAFKA_API_KEY.
  <br/>
  * Type: password
  * Importance: high

`kafka.service.account.id`
: The Service Account that will be used to generate the API keys to communicate with Kafka Cluster.
  <br/>
  * Type: string
  * Importance: high

`kafka.api.secret`
: Secret associated with Kafka API key. Required when kafka.auth.mode==KAFKA_API_KEY.
  <br/>
  * Type: password
  * Importance: high

### Authentication method

`authentication.method`
: How Confluent Cloud authenticates with the database. Allowed values - `Password`, `Microsoft Entra ID application`, `Google service account impersonation` and `IAM Roles`.
  <br/>
  * Type: string
  * Default: Password
  * Valid Values: Google service account impersonation, IAM Roles, Microsoft Entra ID application, Password
  * Importance: high

`secret.manager.enabled`
: Fetch sensitive configuration values from a secret manager.
  <br/>
  * Type: boolean
  * Default: false
  * Importance: high

`provider.integration.id`
: Select an existing integration that has access to your resource.
  <br/>
  * Type: string
  * Importance: high

`database.aws.region`
: The AWS region of your RDS or Aurora database instance, for example `us-east-1`. Required when the authentication method is `IAM Roles`.
  <br/>
  * Type: string
  * Default: “”
  * Importance: high

### Secret manager configuration

`secret.manager`
: Select the secret manager to use for retrieving sensitive data.
  <br/>
  * Type: string
  * Importance: high

`secret.manager.managed.configs`
: Select the configurations to fetch their values from the secret manager.
  <br/>
  * Type: list
  * Importance: high

`secret.manager.provider.integration.id`
: Select an existing provider integration that has access to your secret manager.
  <br/>
  * Type: string
  * Importance: high

### How should we connect to your database?

`connection.host`
: Depending on the service environment, certain network access limitations may exist. Make sure the connector can reach your service. Do not include [jdbc:xxxx://](jdbc:xxxx://) in the connection hostname property (e.g. database-1.abc234ec2.us-west.rds.amazonaws.com).
  <br/>
  * Type: string
  * Importance: high

`connection.port`
: JDBC connection port.
  <br/>
  * Type: int
  * Valid Values: [0,…,65535]
  * Importance: high

`connection.user`
: JDBC connection user.
  <br/>
  * Type: string
  * Importance: high

`connection.password`
: JDBC connection password.
  <br/>
  * Type: password
  * Importance: high

`db.name`
: JDBC database name.
  <br/>
  * Type: string
  * Importance: high

`ssl.mode`
: What SSL mode should we use to connect to your database. `prefer` allows for the connection to not be encrypted and `require` allows for the connection to be encrypted but does not do certificate validation on the server. `verify-ca` and `verify-full` require a file containing SSL CA certificate to be provided. The server’s certificate will be verified to be signed by one of these authorities.\`\`verify-ca\`\` will verify that the server certificate is issued by a trusted CA. `verify-full` will verify that the server certificate is issued by a trusted CA and that the server hostname matches that in the certificate. Client authentication is not performed.
  <br/>
  * Type: string
  * Default: prefer
  * Importance: high

`ssl.truststorefile`
: The binary trust store file that contains the server’s CA certificate. Only required if you use verify-ca or verify-full ssl mode. The connector supports files in JKS and PKCS12 format. For REST API usage, you must base64-encode the binary file and add the appropriate prefix: use `data:text/plain;base64,` for JKS files and `data:application/x-pkcs12;base64,` for PKCS12 files. For example, run `base64_truststore=$(cat /path/to/truststore.jks | base64)` and then use `data:text/plain;base64,${base64_truststore}` as the value.
  <br/>
  * Type: password
  * Default: [hidden]
  * Importance: low

`ssl.truststorepassword`
: The trust store password for the server CA trust store. Only required if using verify-ca or verify-full ssl mode.
  <br/>
  * Type: password
  * Default: [hidden]
  * Importance: low

`ssl.truststoretype`
: The key store type for trusted root certificates. Only required if using verify-ca or verify-full ssl mode. The connector supports files in JKS and PKCS12 format.
  <br/>
  * Type: string
  * Default: “”
  * Importance: low

`ssl.clientstorefile`
: The binary key store file that contains the client’s certificate, used for mutual TLS authentication. The connector supports files in JKS and PKCS12 format. For REST API usage, you must base64-encode the binary file and add the appropriate prefix: use `data:text/plain;base64,` for JKS files and `data:application/x-pkcs12;base64,` for PKCS12 files. For example, run `base64_clientstore=$(cat /path/to/keystore.jks | base64)` and then use `data:text/plain;base64,${base64_clientstore}` as the value.
  <br/>
  * Type: password
  * Default: [hidden]
  * Importance: low

`ssl.clientstorepassword`
: The key store password for the client certificate key store.
  <br/>
  * Type: password
  * Default: [hidden]
  * Importance: low

`ssl.clientstoretype`
: The key store type for client certificate. The connector supports files in JKS and PKCS12 format.
  <br/>
  * Type: string
  * Default: “”
  * Importance: low

### Database details

`insert.mode`
: The insertion mode to use. INSERT uses the standard INSERT row function. An error occurs if the row already exists in the table; UPSERT mode is similar to INSERT. However, if the row already exists, the UPSERT function overwrites column values with the new values provided.
  <br/>
  * Type: string
  * Default: INSERT
  * Importance: high

`table.name.format`
: A format string for the destination table name, which may contain ${topic} as a placeholder for the originating topic name.
  <br/>
  For example, kafka_${topic} for the topic ‘orders’ will map to the table name ‘kafka_orders’.
  <br/>
  * Type: string
  * Default: ${topic}
  * Importance: medium

`table.types`
: The comma-separated types of database tables to which the sink connector can write. By default this is `TABLE`, but any combination of `TABLE` and `VIEW` is allowed. Not all databases support writing to views, and when they do the sink connector will fail if the view definition does not match the records’ schemas (regardless of `auto.evolve`).
  <br/>
  * Type: list
  * Default: TABLE
  * Importance: low

`fields.whitelist`
: List of comma-separated record value field names. If empty, all fields from the record value are utilized, otherwise used to filter to the desired fields. Not applicable when input.data.format is set to STRING.
  <br/>
  * Type: list
  * Importance: medium

`timestamp.fields.list`
: List of comma-separated record value timestamp field names that should be converted to timestamps. These fields will be converted based on precision mode specified in Timestamp Precision Mode. The timestamp fields included here should be Long or String type and nested fields are not supported. Not applicable when input.data.format is set to STRING.
  <br/>
  * Type: list
  * Importance: medium

`string.output.value.column.name`
: Name of the destination table column to use when the Kafka record value written using StringConverter is sinked to the DB table (Input Kafka record value format = STRING). The raw string value is written into this single column. If the destination table is being auto-created, the column is created with this name; if the table already exists and the column is missing, the column is added via ALTER when ‘auto.evolve’ is true. Note: in databases that treat quoted identifiers as case-sensitive (e.g. PostgreSQL), make sure the column name in the existing table exactly matches this value (including case). Defaults to ‘record_value’.
  <br/>
  * Type: string
  * Default: record_value
  * Importance: low

`db.timezone`
: Name of the JDBC timezone used in the connector when querying with time-based criteria. Defaults to UTC.
  <br/>
  * Type: string
  * Default: UTC
  * Importance: medium

`date.timezone`
: Name of the JDBC timezone that should be used in the connector when inserting DATE type values. Defaults to DB_TIMEZONE that uses the timezone set for db.timzeone configuration (to maintain backward compatibility). It is recommended to set this to UTC to avoid conversion for DATE type values.
  <br/>
  * Type: string
  * Default: DB_TIMEZONE
  * Valid Values: DB_TIMEZONE, UTC
  * Importance: medium

`timestamp.precision.mode`
: Convert the Timestamp with precision. If set to microseconds the timestamp will be converted to microsecond precision. If set to nanoseconds the timestamp will be converted to nanoseconds precision. Not applicable when input.data.format is set to STRING.
  <br/>
  * Type: string
  * Default: microseconds
  * Importance: medium

`date.calendar.system`
: Conversion of time since epoch value in kafka topic record to DATE or TIMESTAMP depends on the calendar used to interpret it. If LEGACY is used, it will use the hybrid Gregorian/Julian calendar which was the default in the older java date time APIs. However, if ‘PROLEPTIC_GREGORIAN’ is used, then it will use the proleptic gregorian calendar which extends the Gregorian rules backward indefinitely and does not apply the 1582 cutover. This matches the behavior of modern Java date/time APIs (java.time). This is defaulted to LEGACY for backward compatibility. The ideal setting for this depends on whether the values in source topic were populated using old or new java date time APIs. Changing this configuration on an existing connector might lead to a drift in the DATE/TIMESTAMP column’s values populated in the sink database.
  <br/>
  * Type: string
  * Default: LEGACY
  * Importance: medium

### Primary Key

`pk.mode`
: The primary key mode, also refer to pk.fields documentation for interplay. Supported modes are:
  <br/>
  none: No keys utilized.
  <br/>
  kafka: Apache Kafka® coordinates are used as the PK.
  <br/>
  record_value: Field(s) from the record value are used, which must be a struct. This mode is not supported when input.data.format is set to STRING.
  <br/>
  record_key: Field(s) from the record key are used, which must be a struct.
  <br/>
  * Type: string
  * Valid Values: kafka, none, record_key, record_value
  * Importance: high

`pk.fields`
: List of comma-separated primary key field names. The runtime interpretation of this config depends on the pk.mode:
  <br/>
  none: Ignored as no fields are used as primary key in this mode.
  <br/>
  kafka: Must be a trio representing the Kafka coordinates, defaults to \_\_connect_topic,_\_connect_partition,_\_connect_offset if empty.
  <br/>
  record_value: If empty, all fields from the value struct will be used, otherwise used to extract the desired fields.
  <br/>
  * Type: list
  * Importance: high

### SQL/DDL Support

`auto.create`
: Whether to automatically create the destination table if it is missing.
  <br/>
  * Type: boolean
  * Default: false
  * Importance: medium

`auto.evolve`
: Whether to automatically add columns in the table if they are missing.
  <br/>
  * Type: boolean
  * Default: false
  * Importance: medium

`quote.sql.identifiers`
: When to quote table names, column names, and other identifiers in SQL statements. For backward compatibility, the default is ‘always’.
  <br/>
  * Type: string
  * Default: ALWAYS
  * Valid Values: ALWAYS, NEVER
  * Importance: medium

### Connection details

`batch.sizes`
: Maximum number of rows to include in a single batch when polling for new data. This setting can be used to limit the amount of data buffered internally in the connector.
  <br/>
  * Type: int
  * Default: 3000
  * Valid Values: [1,…,5000]
  * Importance: low

### Consumer configuration

`max.poll.interval.ms`
: The maximum delay between subsequent consume requests to Kafka. This configuration property may be used to improve the performance of the connector, if the connector cannot send records to the sink system. Defaults to 300000 milliseconds (5 minutes).
  <br/>
  * Type: long
  * Default: 300000 (5 minutes)
  * Valid Values: [60000,…,1800000] for non-dedicated clusters and [60000,…] for dedicated clusters
  * Importance: low

`max.poll.records`
: The maximum number of records to consume from Kafka in a single request. This configuration property may be used to improve the performance of the connector, if the connector cannot send records to the sink system. Defaults to 500 records.
  <br/>
  * Type: long
  * Default: 500
  * Valid Values: [1,…,500] for non-dedicated clusters and [1,…] for dedicated clusters
  * Importance: low

### Number of tasks for this connector

`tasks.max`
: Maximum number of tasks for the connector.
  <br/>
  * Type: int
  * Valid Values: [1,…]
  * Importance: high

### Additional Configs

`consumer.override.auto.offset.reset`
: Defines the behavior of the consumer when there is no committed position (which occurs when the group is first initialized) or when an offset is out of range. You can choose either to reset the position to the “earliest” offset (the default) or the “latest” offset. You can also select “none” if you would rather set the initial offset yourself and you are willing to handle out of range errors manually. More details: [https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html#auto-offset-reset](https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html#auto-offset-reset)
  <br/>
  * Type: string
  * Importance: low

`consumer.override.isolation.level`
: Controls how to read messages written transactionally. If set to read_committed, consumer.poll() will only return transactional messages which have been committed. If set to read_uncommitted (the default), consumer.poll() will return all messages, even transactional messages which have been aborted. Non-transactional messages will be returned unconditionally in either mode.  More details: [https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html#isolation-level](https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html#isolation-level)
  <br/>
  * Type: string
  * Importance: low

`header.converter`
: The converter class for the headers. This is used to serialize and deserialize the headers of the messages.
  <br/>
  * Type: string
  * Importance: low

`key.converter.use.schema.guid`
: The schema GUID to use for deserialization when using ConfigSchemaIdDeserializer. This allows you to specify a fixed schema GUID to be used for deserializing message keys. Only applicable when key.converter.key.schema.id.deserializer is set to ConfigSchemaIdDeserializer.
  <br/>
  * Type: string
  * Importance: low

`key.converter.use.schema.id`
: The schema ID to use for deserialization when using ConfigSchemaIdDeserializer. This allows you to specify a fixed schema ID to be used for deserializing message keys. Only applicable when key.converter.key.schema.id.deserializer is set to ConfigSchemaIdDeserializer.
  <br/>
  * Type: int
  * Importance: low

`value.converter.allow.optional.map.keys`
: Allow optional string map key when converting from Connect Schema to Avro Schema. Applicable for Avro Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.auto.register.schemas`
: Specify if the Serializer should attempt to register the Schema.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.connect.meta.data`
: Allow the Connect converter to add its metadata to the output schema. Applicable for Avro Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.enhanced.avro.schema.support`
: Enable enhanced schema support to preserve package information and Enums. Applicable for Avro Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.enhanced.protobuf.schema.support`
: Enable enhanced schema support to preserve package information. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.flatten.unions`
: Whether to flatten unions (oneofs). Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.generate.index.for.unions`
: Whether to generate an index suffix for unions. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.generate.struct.for.nulls`
: Whether to generate a struct variable for null values. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.int.for.enums`
: Whether to represent enums as integers. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.latest.compatibility.strict`
: Verify latest subject version is backward compatible when use.latest.version is true.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.object.additional.properties`
: Whether to allow additional properties for object schemas. Applicable for JSON_SR Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.optional.for.nullables`
: Whether nullable fields should be specified with an optional label. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.optional.for.proto2`
: Whether proto2 optionals are supported. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.scrub.invalid.names`
: Whether to scrub invalid names by replacing invalid characters with valid characters. Applicable for Avro and Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.use.latest.version`
: Use latest version of schema in subject for serialization when auto.register.schemas is false.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.use.optional.for.nonrequired`
: Whether to set non-required properties to be optional. Applicable for JSON_SR Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.use.schema.guid`
: The schema GUID to use for deserialization when using ConfigSchemaIdDeserializer. This allows you to specify a fixed schema GUID to be used for deserializing message values. Only applicable when value.converter.value.schema.id.deserializer is set to ConfigSchemaIdDeserializer.
  <br/>
  * Type: string
  * Importance: low

`value.converter.use.schema.id`
: The schema ID to use for deserialization when using ConfigSchemaIdDeserializer. This allows you to specify a fixed schema ID to be used for deserializing message values. Only applicable when value.converter.value.schema.id.deserializer is set to ConfigSchemaIdDeserializer.
  <br/>
  * Type: int
  * Importance: low

`value.converter.wrapper.for.nullables`
: Whether nullable fields should use primitive wrapper messages. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`value.converter.wrapper.for.raw.primitives`
: Whether a wrapper message should be interpreted as a raw primitive at root level. Applicable for Protobuf Converters.
  <br/>
  * Type: boolean
  * Importance: low

`errors.tolerance`
: Use this property if you would like to configure the connector’s error handling behavior. WARNING: This property should be used with CAUTION for SOURCE CONNECTORS as it may lead to dataloss. If you set this property to ‘all’, the connector will not fail on errant records, but will instead log them (and send to DLQ for Sink Connectors) and continue processing. If you set this property to ‘none’, the connector task will fail on errant records.
  <br/>
  * Type: string
  * Default: all
  * Importance: low

`key.converter.key.schema.id.deserializer`
: The class name of the schema ID deserializer for keys. This is used to deserialize schema IDs from the message headers.
  <br/>
  * Type: string
  * Default: io.confluent.kafka.serializers.schema.id.DualSchemaIdDeserializer
  * Importance: low

`key.converter.key.subject.name.strategy`
: How to construct the subject name for key schema registration.
  <br/>
  * Type: string
  * Default: TopicNameStrategy
  * Importance: low

`value.converter.decimal.format`
: Specify the JSON/JSON_SR serialization format for Connect DECIMAL logical type values with two allowed literals:
  <br/>
  BASE64 to serialize DECIMAL logical types as base64 encoded binary data and
  <br/>
  NUMERIC to serialize Connect DECIMAL logical type values in JSON/JSON_SR as a number representing the decimal value.
  <br/>
  * Type: string
  * Default: BASE64
  * Importance: low

`value.converter.flatten.singleton.unions`
: Whether to flatten singleton unions. Applicable for Avro and JSON_SR Converters.
  <br/>
  * Type: boolean
  * Default: false
  * Importance: low

`value.converter.ignore.default.for.nullables`
: When set to true, this property ensures that the corresponding record in Kafka is NULL, instead of showing the default column value. Applicable for AVRO,PROTOBUF and JSON_SR Converters.
  <br/>
  * Type: boolean
  * Default: false
  * Importance: low

`value.converter.reference.subject.name.strategy`
: Set the subject reference name strategy for value. Valid entries are DefaultReferenceSubjectNameStrategy or QualifiedReferenceSubjectNameStrategy. Note that the subject reference name strategy can be selected only for PROTOBUF format with the default strategy being DefaultReferenceSubjectNameStrategy.
  <br/>
  * Type: string
  * Default: DefaultReferenceSubjectNameStrategy
  * Importance: low

`value.converter.replace.null.with.default`
: Whether to replace fields that have a default value and that are null to the default value. When set to true, the default value is used, otherwise null is used. Applicable for JSON Converter.
  <br/>
  * Type: boolean
  * Default: true
  * Importance: low

`value.converter.schemas.enable`
: Must be set to true when input.data.format is JSON. Plain JSON without an inline schema is not supported. Applicable for JSON Converter.
  <br/>
  * Type: boolean
  * Default: false
  * Importance: low

`value.converter.value.schema.id.deserializer`
: The class name of the schema ID deserializer for values. This is used to deserialize schema IDs from the message headers.
  <br/>
  * Type: string
  * Default: io.confluent.kafka.serializers.schema.id.DualSchemaIdDeserializer
  * Importance: low

`value.converter.value.subject.name.strategy`
: Determines how to construct the subject name under which the value schema is registered with Schema Registry.
  <br/>
  * Type: string
  * Default: TopicNameStrategy
  * Importance: low

### Auto-restart policy

`auto.restart.on.user.error`
: Enable connector to automatically restart on user-actionable errors.
  <br/>
  * Type: boolean
  * Default: true
  * Importance: medium

<a id="cc-mysql-sink-faq"></a>

## Frequently asked questions

Find answers to frequently asked questions about the MySQL Sink connector for Confluent Cloud.

### How do I resolve duplicate key errors?

The connector fails with duplicate key constraint violations when attempting to insert records that already exist in the MySQL table.

You might encounter errors similar to:

```none
java.sql.BatchUpdateException: Duplicate entry '<value>' for key '<constraint>' (Error Code: 1062, SQLState: 23000)
at com.mysql.cj.jdbc.ClientPreparedStatement.executeBatch(ClientPreparedStatement.java:XXX)
Caused by: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '<value>' for key '<constraint>'
```

**Root cause:**

When using the default `insert.mode` of `INSERT`, the connector attempts to insert new rows into the MySQL table. If a record with the same primary key already exists, MySQL rejects the operation with a duplicate key error. This commonly occurs when:

* The connector is restarted and reprocesses records.
* The same data is sent multiple times due to retries or rebalancing.
* Multiple connectors or processes are writing to the same table.

**Solution:**

Change the `insert.mode` configuration from `INSERT` to `UPSERT`:

```json
{
  "insert.mode": "UPSERT"
}
```

The `UPSERT` mode uses MySQL’s `ON DUPLICATE KEY UPDATE` functionality to update existing rows instead of inserting duplicates. This allows the connector to handle records with existing primary keys by updating the values rather than failing.

Alternatively, use `UPDATE` mode when you only want to update existing rows. The connector issues SQL `UPDATE` statements. Records with keys that do not exist in the table fail.

For more information, see the `insert.mode` property in [Configuration Properties](#cc-mysql-sink-config-properties).

<a id="cc-mysql-sink-ssl-tls-faq"></a>

### How do I configure SSL/TLS connections to MySQL?

<!-- Shared mutual TLS guidance for the MySQL Source and Sink (JDBC) connectors. -->
<!-- Included by cc-mysql-source.rst and cc-mysql-sink.rst. -->

The MySQL connector supports several SSL modes for secure connections.
You configure SSL/TLS using connector properties, such as `ssl.mode` and the
truststore and client keystore properties, which the connector passes to the
underlying MySQL JDBC driver. You do not need to change a JDBC connection URL.

**Available SSL modes**:

* `prefer` (default): Attempts to use an encrypted connection. Falls back to
  unencrypted if SSL is unavailable.
* `require`: Uses a secure connection. The connector fails if a secure
  connection cannot be established. Does not perform Certificate Authority (CA) validation.
* `verify-ca`: Similar to `require`, but also verifies the server TLS
  certificate against configured CA certificates.
* `verify-full`: Similar to `verify-ca`, but also verifies that the server
  certificate matches the connection hostname.

**For \`\`verify-ca\`\` or \`\`verify-full\`\` modes**:

The connector validates the server against a truststore that you provide.
Supply the server CA in a `JKS` or `PKCS12` truststore using the
`ssl.truststorefile`, `ssl.truststorepassword`, and `ssl.truststoretype`
properties. Create the truststore from the server CA certificate with
`keytool`:

```bash
keytool -importcert -alias MySQLCACert -file server-ca.pem -keystore truststore -storepass <password>
```

When using `verify-full`, the server certificate hostname must match
`connection.host`. Connecting to a database by IP address (for example, a
Google Cloud Cloud SQL public IP) fails hostname verification, because the certificate
is issued for the instance DNS name, not the IP. Use `verify-ca` in that case.

**Mutual TLS:**

The truststore properties let the connector verify the MySQL server. Use
mTLS when you also want the MySQL server to authenticate the connector. The
connector presents a client certificate from a keystore that the server
validates before allowing the connection.

Client authentication is independent of `ssl.mode`. The connector presents
its client keystore in any SSL mode (including `prefer` and `require`)
whenever an SSL handshake occurs and the server requests a client certificate.
The MySQL server (not `ssl.mode`) decides whether to require a client
certificate.

You supply the client certificate and key as a `JKS` or `PKCS12` keystore.
To create a PKCS12 client keystore from a PEM certificate and key:

```bash
openssl pkcs12 -export -in client-cert.pem -inkey client-key.pem \
  -name "mysqlclient" -passout pass:<password> -out client-keystore.p12
```

To use a JKS keystore instead, convert the PKCS12 keystore with `keytool`:

```bash
keytool -importkeystore -srckeystore client-keystore.p12 -srcstoretype pkcs12 \
  -srcstorepass <password> -destkeystore keystore -deststoretype JKS -deststorepass <password>
```

Then provide the client keystore with these properties:

* `ssl.clientstorefile`: The client certificate keystore (`JKS` or `PKCS12`).
* `ssl.clientstorepassword`: The keystore password.
* `ssl.clientstoretype`: The keystore type, either `JKS` or `PKCS12`.

In the Confluent Cloud Console, upload the keystore file directly. When you configure
the connector with the Confluent CLI, REST API, or Terraform, pass the
keystore as a base64-encoded `data:` URL: use `data:application/x-pkcs12;base64,`
for PKCS12 keystores and `data:text/plain;base64,` for JKS keystores. For
example:

```bash
echo "data:application/x-pkcs12;base64,$(base64 -i client-keystore.p12 | tr -d '\n')"
```

Then set the resulting values in the connector configuration. The following
example uses `ssl.mode` `verify-ca`, which also validates the server with a
truststore:

```json
{
  "ssl.mode": "verify-ca",
  "ssl.truststorefile": "data:application/x-pkcs12;base64,MIIK...",
  "ssl.truststorepassword": "<password>",
  "ssl.truststoretype": "PKCS12",
  "ssl.clientstorefile": "data:application/x-pkcs12;base64,MIIK...",
  "ssl.clientstorepassword": "<password>",
  "ssl.clientstoretype": "PKCS12"
}
```

Configure your MySQL server to request and validate client certificates for
mTLS to take effect.

**Troubleshooting SSL/TLS issues:**

* **Verify MySQL server SSL configuration**: Ensure your MySQL instance has SSL enabled and the necessary certificates are properly configured.
* **Check connector SSL settings**: Confirm that `ssl.mode` and any truststore or client keystore properties are set appropriately for your MySQL deployment.
* **Database user requirements**: Ensure the database user account used by the connector is permitted to connect via SSL/TLS. Some MySQL configurations restrict users to SSL-only connections.
* **Keystore password was incorrect**: A `keystore password was incorrect` error means `ssl.clientstorepassword` (or `ssl.truststorepassword`) does not match the keystore. Verify the password you set when creating the store.
* **Cannot open keystore / wrong store type**: A `toDerInputStream rejects tag type` or `Cannot open file` error usually means `ssl.clientstoretype` (or `ssl.truststoretype`) does not match the actual store format, or the base64-encoded `data:` URL is malformed. Confirm the type is `JKS` or `PKCS12` to match the file, and regenerate the `data:` URL.
* **Client certificate rejected**: If the server refuses the connector’s client certificate, confirm that `ssl.clientstorefile` is base64-encoded with the correct data-URI prefix, that `ssl.clientstoretype` matches the keystore format, that `ssl.clientstorepassword` is correct, and that the client certificate is signed by a CA the MySQL server trusts for client authentication.

### How do I configure AWS IAM authentication for RDS MySQL?

The MySQL Sink connector supports Amazon IAM role-based authentication
for RDS and Aurora MySQL using Confluent Provider Integration. To use it,
set the following connector properties:

* Set **Authentication method** to `IAM Roles`.
* Select the **Provider Integration** that has access to your database.
* Set **Database AWS region** to the region of your RDS or Aurora instance.

Do not set the database password when using IAM authentication.

For the database user, IAM policy, and Provider Integration setup steps, see
[AWS IAM Authentication Setup](#cc-mysql-sink-aws-iam-auth).

### Why is `auto.create` or `auto.evolve` not creating tables or columns?

The connector fails to automatically create tables or add new columns even though `auto.create` or `auto.evolve` is set to `true`.

**Root cause:**

Table creation or schema evolution failures typically occur due to:

* **Insufficient database permissions**: The MySQL user account lacks `CREATE TABLE` or `ALTER TABLE` privileges.
* **Schema compatibility issues**: The Kafka topic record schema cannot be mapped to a valid MySQL table structure.
* **Field count limits**: MySQL has limits on the number of columns per table. If your schema exceeds this limit (typically around 1,000-4,096 columns depending on MySQL version and configuration), table creation fails.
* **Data type incompatibilities**: Some Kafka schema types might not have a direct MySQL equivalent.

**Solution:**

* **Grant required permissions**: Ensure the MySQL user has the necessary DDL privileges:
  ```sql
  GRANT CREATE, ALTER ON database_name.* TO 'username'@'%';
  FLUSH PRIVILEGES;
  ```
* **Pre-create tables**: For complex schemas or production environments, consider creating tables manually with the exact schema you need, then set both `auto.create` and `auto.evolve` to `false`.
* **Monitor field counts**: If your schema has many fields, check that you’re within MySQL’s column limit. Consider restructuring your data model if you exceed this limit.
* **Verify schema format**: Ensure you’re using a schema-based format (Avro, JSON Schema, or Protobuf) with [Schema Registry](../get-started/schema-registry.md#cloud-sr-config) enabled. The connector cannot auto-create tables from schemaless data.

### How do I configure primary keys correctly?

You need to understand how to configure `pk.mode` and `pk.fields` for your MySQL Sink connector.

**Configuration options:**

The `pk.mode` property determines how primary keys are assigned:

* `kafka`: Uses Kafka coordinates (topic, partition, offset) as the primary key. This guarantees uniqueness but doesn’t reflect your business logic.
  ```json
  {
    "pk.mode": "kafka",
    "pk.fields": "__connect_topic,__connect_partition,__connect_offset"
  }
  ```

  If `pk.fields` is not specified, these default field names are used automatically.
* `none`: No primary key is used. Rows are inserted without unique constraints.
  ```json
  {
    "pk.mode": "none"
  }
  ```

  Use this mode with caution as it can lead to duplicate records.
* `record_key`: Uses fields from the Kafka record key as the primary key.
  ```json
  {
    "pk.mode": "record_key",
    "pk.fields": "user_id"
  }
  ```

  For primitive keys, you must specify exactly one field name in `pk.fields`. For struct keys, specify the field names to use, or leave `pk.fields` empty to use all fields from the key.
* `record_value`: Uses fields from the Kafka record value as the primary key.
  ```json
  {
    "pk.mode": "record_value",
    "pk.fields": "order_id,line_item_id"
  }
  ```

  The record value must be a struct type. Specify comma-separated field names, or leave `pk.fields` empty to use all fields.

**Common errors:**

* **Mismatched field names**: If `pk.fields` references fields that don’t exist in the record key or value (depending on `pk.mode`), the connector fails.
* **Missing pk.fields with primitive keys**: When using `pk.mode=record_key` with a primitive key type (like String or Integer), you must specify exactly one field name in `pk.fields`.
* **Incompatible with delete.enabled**: The `delete.enabled` property (which treats null record values as deletes) requires `pk.mode=record_key`. Other modes are not compatible.

### How do I handle database connection failures?

The connector fails to connect to the MySQL database or experiences intermittent connection issues.

**Common connection errors:**

* **Network connectivity**: The connector cannot reach the MySQL host due to firewall rules, security groups, or network configuration.
* **Authentication failures**: Incorrect username or password, or the MySQL user is not permitted to connect from the connector’s IP address.
* **Database does not exist**: The database specified in `db.name` does not exist on the MySQL server.
* **Connection timeout**: The MySQL server is not responding within the expected timeout period.

**Troubleshooting steps:**

* **Review connector logs**: Check the connector logs in the Confluent Cloud Console for specific error messages that can help identify the root cause.
* **Verify network access**: Ensure the MySQL database is accessible from Confluent Cloud. For networking considerations, see [Networking and DNS](overview.md#connect-internet-access-resources). If using private networking, ensure it is properly configured.
* **Test credentials manually**: Use a MySQL client to verify the connection string, username, and password:
  ```bash
  mysql -h <connection.host> -P <connection.port> -u <connection.user> -p <db.name>
  ```
* **Check MySQL user permissions**: Ensure the user has the necessary permissions and is allowed to connect from remote hosts:
  ```sql
  CREATE USER 'username'@'%' IDENTIFIED BY 'password';
  GRANT ALL PRIVILEGES ON database_name.* TO 'username'@'%';
  FLUSH PRIVILEGES;
  ```

  The `'%'` wildcard allows connections from any host. For security, consider restricting this to specific IP ranges.
* **Verify database exists**: Confirm that the database specified in `db.name` exists:
  ```sql
  SHOW DATABASES;
  ```

### Why is my data not appearing in MySQL tables?

The connector is running, but data from Kafka topics is not being written to MySQL tables.

**Root cause:**

This issue typically occurs due to:

* **Schema mismatches**: The schema of the Kafka records doesn’t match the MySQL table schema, causing the connector to skip or fail processing records.
* **Serialization errors**: The connector cannot deserialize the Kafka records due to missing or incompatible schemas in Confluent Cloud Schema Registry.
* **Connector is paused or failed**: The connector status shows as paused or failed, preventing data flow.
* **Consumer lag**: The connector is not consuming messages from the topic due to consumer group issues or offset problems.
* **Filtering or transformations**: SMTs or filtering logic is dropping records before they reach MySQL.

**Solution:**

* **Verify connector status**: Check that the connector status is `Running` in the Confluent Cloud Console. If it shows `Failed` or `Paused`, review the error messages and restart the connector.
* **Check Schema Registry**: Ensure that the Kafka topic has a valid schema registered in [Schema Registry](../get-started/schema-registry.md#cloud-sr-config) that matches your `input.data.format` (Avro, JSON_SR, or Protobuf).
* **Validate table schema**: Confirm that the MySQL table schema is compatible with the Kafka record schema. Check column names, data types, and nullable constraints.
* **Review connector logs**: Look for serialization errors, schema compatibility issues, or other error messages in the connector logs.
* **Monitor consumer lag**: Check if the connector is consuming messages from the topic. High consumer lag can indicate processing issues.
* **Verify SMT configuration**: If you’re using [Single Message Transformations](single-message-transforms.md#cc-single-message-transforms), ensure they’re not inadvertently dropping records.
* **Check DLQ message headers**: If a Dead Letter Queue (DLQ) is configured, inspect the DLQ message headers to identify the exact exception and error details for failed records. See [View Connector Dead Letter Queue Errors in Confluent Cloud](dead-letter-queue.md#ccloud-dlq-topics) for information on DLQ configuration and header format.

### How do I handle schema evolution?

You need to add new fields to your Kafka topic schema and want them to be reflected in the MySQL table.

**Using auto.evolve:**

When `auto.evolve` is set to `true`, the connector automatically adds new columns to the MySQL table when it encounters new fields in the Kafka record schema:

```json
{
  "auto.evolve": "true"
}
```

**Important considerations:**

* **Backward compatibility**: The connector can add new columns but cannot remove existing columns or change column types. Schema changes must be backward compatible.
* **Default values**: New columns are added with NULL as the default value unless your schema specifies a default.
* **Database permissions**: The MySQL user must have `ALTER TABLE` privileges to evolve the schema.
* **Schema Registry**: Use [Schema Registry](../get-started/schema-registry.md#cloud-sr-config) with schema compatibility rules to ensure controlled schema evolution. The recommended compatibility modes are `BACKWARD` or `FULL`.

**Manual schema management:**

For production environments, consider managing schema changes manually:

1. Set `auto.evolve` to `false`.
2. Coordinate schema changes between your Kafka topics and MySQL tables.
3. Use Confluent Cloud Schema Registry with strict compatibility rules to prevent incompatible schema changes.
4. Apply schema changes to MySQL tables first, then update the Kafka topic schema.

This approach gives you more control and prevents unexpected schema changes in your database.

## Next Steps

For an example that shows fully managed Confluent Cloud connectors in action with
Confluent Cloud for Apache Flink, see the [Cloud ETL Demo](/platform/current/tutorials/examples/cloud-etl/docs/index.html).
This example also shows how to use Confluent CLI to manage your resources in
Confluent Cloud.

[![image](images/topology.png)](https://docs.confluent.io/platform/current/tutorials/examples/cloud-etl/docs/index.html)