Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Highlight mysql direct access trade-off #105

Merged
merged 2 commits into from
Dec 15, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions content/doc/addons/mysql/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,12 +39,14 @@ If you need to import a very large dump, please send an email to <support@clever

## Direct access

{{< callout type="warning">}}
Keep in mind that using direct access is a trade-off: if you migrate your addon, you will need to generate the hostname and port again, so your application will need to update that environment, while using a proxy does not change anything.
{{< /callout>}}

All our dedicated MySQL databases are served via a proxy. To reduce the latency you can bypass this proxy by generating direct hostname and port for the addon. You can do it by clicking the "Generate direct hostname and port" on the addon dashboard.

This action will add new environment variables to reach the addon without any proxy.

Keep in mind that usage of direct access is a trade-off: when you migrate your addon, you will need to to generate hostname and port again so your application must update these environment while proxy usage changes nothing.

## Encryption at rest

Encryption at rest is available on MySQL. You can have more information on the [dedicated page]({{< ref "doc/administrate/encryption-at-rest.md" >}})
Expand Down
Loading