MySQL Endpoint
MySQL endpoints connect Eve to MySQL and MariaDB-compatible databases for governed SQL access, operational workflows, and migration planning.
Endpoint Kind
Use mysql as the endpoint kind when creating this endpoint through the API or dashboard.
What Eve Uses MySQL Endpoints For
- Run governed SQL queries through Eve.
- Apply RBAC, audit, and telemetry to application or agent access.
- Inspect database and table metadata for planning and governance.
- Coordinate MySQL data with Postgres, Snowflake, Databricks, and other endpoints in workflows.
Basic Endpoint Shape
json
{
"endpoint": "mysql-prod",
"kind": "mysql",
"config": {
"read_conn": {
"host": "mysql.internal",
"port": 3306,
"user": "app_user",
"password": "secret",
"database": "app"
}
},
"description": "Production MySQL database"
}Create it with the endpoint API:
bash
curl -sS -X POST "$EDEN/endpoints" \
-H "$AUTH_HEADER" \
-H "Content-Type: application/json" \
-d '{
"endpoint": "mysql-prod",
"kind": "mysql",
"config": {
"read_conn": {
"host": "mysql.internal",
"port": 3306,
"user": "app_user",
"password": "secret",
"database": "app"
}
},
"description": "Production MySQL database"
}'Configuration Fields
| Field | Purpose |
|---|---|
host | MySQL host. |
port | MySQL port, usually 3306. |
user | Database username. |
password | Database password. |
database | Default database/schema. |
Operating Notes
- Use a least-privilege database user for read-only and agent-facing workflows.
- Separate application credentials from administrative or migration credentials.
- Document server version, SQL mode, charset/collation, stored procedures, and trigger usage before migration planning.
Related
Last updated: October 20, 2018