# MariaDB The MariaDB integration enables you to securely manage just-in-time (JIT) access to roles, databases, and tables within your MariaDB instance. *** ### Prerequisite

Item	Description
Apono Connector	On-prem connection serving as a bridge between a MariaDB instance and Apono: AWS Azure GCP Kubernetes Minimum Required Version: 1.3.0 Learn how to update an existing AWS, Azure, GCP, or Kubernetes connector.

Item

Description

Apono Connector

On-prem connection serving as a bridge between a MariaDB instance and Apono:

Minimum Required Version: 1.3.0

Learn how to update an existing AWS, Azure, GCP, or Kubernetes connector.

*** ### Create a MariaDB user You must create a user in your MariaDB instance for the Apono connector and grant that user permissions to your databases. Follow these steps to create a user and grant it permissions: 1. In your preferred client tool, create a new user. Use *apono\_connector* or another name of your choosing for the username. Be sure to set a strong password for the user. ```sql CREATE USER 'apono_connector'@'%' IDENTIFIED BY 'password'; ``` 2. Grant the following access to the user. These permissions allow the connector to list databases, manage users, update internal tables, monitor sessions, reload privileges, and handle connection-related operations. ```sql GRANT SHOW DATABASES ON *.* TO 'apono_connector'@'%'; GRANT CREATE USER ON *.* TO 'apono_connector'@'%'; GRANT UPDATE ON mysql.* TO 'apono_connector'@'%'; GRANT PROCESS ON *.* TO 'apono_connector'@'%'; GRANT RELOAD ON *.* TO 'apono_connector'@'%'; GRANT CONNECTION ADMIN ON *.* TO 'apono_connector'@'%'; ``` 3. Grant the user **only one** of the following sets of permissions. The chosen set defines the highest level of permissions to provision with Apono.\ \ Click on each tab to reveal the SQL commands. {% tabs %} {% tab title="READ\_ONLY" %} Allows Apono to read data from databases ```sql GRANT SELECT ON *.* TO 'apono_connector'@'%'; GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%'; ``` {% endtab %} {% tab title="READ\_WRITE" %} Allows Apono to read and modify data {% code overflow="wrap" %} ```sql GRANT SELECT,ALTER,ALTER ROUTINE,CREATE,CREATE ROUTINE,CREATE TEMPORARY TABLES,CREATE VIEW,DELETE,INDEX,INSERT,TRIGGER,UPDATE ON *.* TO 'apono_connector'@'%'; GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%'; ``` {% endcode %} {% endtab %} {% tab title="ADMIN" %} Allows Apono administrative-level access, including the ability to execute and drop tables {% code overflow="wrap" %} ```sql GRANT EXECUTE,DROP,SELECT,ALTER,ALTER ROUTINE,CREATE,CREATE ROUTINE,CREATE TEMPORARY TABLES,CREATE VIEW,DELETE,INDEX,INSERT,TRIGGER,UPDATE ON *.* TO 'apono_connector'@'%'; GRANT GRANT OPTION ON *.* TO 'apono_connector'@'%'; ``` {% endcode %} {% endtab %} {% endtabs %} 4. [Create a secret](https://docs.apono.io/docs/connectors-and-secrets/apono-integration-secret) with the credentials from step **1**.\ \ Use the following key-value pair structure when generating the secret. Be sure to replace `#PASSWORD` with the actual value. If you used a different name for the user, replace `apono-connector` with the name you assigned to the user. ``` "username": "apono-connector", "password": "#PASSWORD" ``` {% hint style="success" %} You can also input the user credentials directly into the Apono UI during the integration process. {% endhint %} You can now [integrate your MariaDB database](#integrate-mariadb). *** ### Integrate MariaDB

{% hint style="success" %} You can also use the steps below to integrate with Apono using Terraform. In step **10**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance. {% endhint %} Follow these steps to complete the integration: 1. On the [**Catalog**](https://app.apono.io/catalog?search=mariadb) tab, click **MariaDB**. The **Connect Integration** page appears. 2. Under **Discovery**, click **Next**. The **Apono connector** section expands. 3. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located. {% hint style="success" %} If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a connector ([AWS](https://docs.apono.io/docs/aws-environment/apono-connector-for-aws), [Azure](https://docs.apono.io/docs/azure-environment/apono-connector-for-azure), [GCP](https://docs.apono.io/docs/gcp-environment/apono-connector-for-gcp), [Kubernetes](https://docs.apono.io/docs/kubernetes-environment/apono-connector-for-kubernetes)). {% endhint %} 4. Click **Next**. The **Integration Config** section expands. 5. Define the **Integration Config** settings.

Setting	Description
Integration Name	Unique, alphanumeric, user-friendly name used to identify the integration when constructing an access flow
Hostname	Hostname of the MariaDB instance to connect
Port	Port value for the instance By default, Apono sets this value to 3306.

6. Click **Next**. The **Secret Store** section expands. 7. [Associate the secret or credentials](https://docs.apono.io/docs/connectors-and-secrets/apono-integration-secret). 8. Click **Next**. The **Get more with Apono** section expands. 9. Define the **Get more with Apono** settings.

Setting	Description
Credential Rotation	(Optional) Number of days after which the database credentials must be rotated Learn more about the Credentials Rotation Policy.
User cleanup after access is revoked (in days)	(Optional) Defines the number of days after access has been revoked that the user should be deleted Learn more about Periodic User Cleanup & Deletion.
Custom Access Details	(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
Integration Owner	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform. From the Value dropdown menu, select one or multiple users or groups. NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: Enter a Key name. This value is the name of the tag created in your cloud environment. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono. NOTE: When this setting is defined, an Integration Owner must also be defined.

10. Click **Confirm**.

💡Are you integrating with Apono using Terraform?

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**: 1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code. 2. Click to copy the code. 3. Make any additional edits. 4. Deploy the code in your Terraform. Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config) for more details about the schema definition.

Now that you have completed this integration, you can [create access flows](https://docs.apono.io/docs/access-flows/access-flows) that grant permission to your MariaDB database. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.apono.io/docs/additional-integrations/databases-and-data-repositories/mariadb.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.