# Table of Contents - [docs.elest.io](#docs-elest-io) - [Shelves | docs.elest.io](#shelves-docs-elest-io) - [docs.elest.io](#docs-elest-io) - [Books | docs.elest.io](#books-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Tags | docs.elest.io](#tags-docs-elest-io) - [Elestio Data Processin... | docs.elest.io](#elestio-data-processin-docs-elest-io) - [BYOVM (Bring Your Own VM) | docs.elest.io](#byovm-bring-your-own-vm-docs-elest-io) - [Netcup | docs.elest.io](#netcup-docs-elest-io) - [Managed DB Overview | docs.elest.io](#managed-db-overview-docs-elest-io) - [BYOVM with AWS EC2 (Be... | docs.elest.io](#byovm-with-aws-ec2-be-docs-elest-io) - [Domains | docs.elest.io](#domains-docs-elest-io) - [How Does Elestio’s Pri... | docs.elest.io](#how-does-elestio-s-pri-docs-elest-io) - [How can project owners... | docs.elest.io](#how-can-project-owners-docs-elest-io) - [DB Migrations | docs.elest.io](#db-migrations-docs-elest-io) - [How to secure your app... | docs.elest.io](#how-to-secure-your-app-docs-elest-io) - [David Alimi | docs.elest.io](#david-alimi-docs-elest-io) - [Elestio API | docs.elest.io](#elestio-api-docs-elest-io) - [Amit | docs.elest.io](#amit-docs-elest-io) - [Joseph Benguira | docs.elest.io](#joseph-benguira-docs-elest-io) - [Cloud Providers | docs.elest.io](#cloud-providers-docs-elest-io) - [Recently Updated Pages | docs.elest.io](#recently-updated-pages-docs-elest-io) - [Upgrade support plan | docs.elest.io](#upgrade-support-plan-docs-elest-io) - [Legal & Compliance | docs.elest.io](#legal-compliance-docs-elest-io) - [Keycloak | docs.elest.io](#keycloak-docs-elest-io) - [Overview | docs.elest.io](#overview-docs-elest-io) - [Frequently Asked Quest... | docs.elest.io](#frequently-asked-quest-docs-elest-io) - [Elestio Terraform prov... | docs.elest.io](#elestio-terraform-prov-docs-elest-io) - [Introduction | docs.elest.io](#introduction-docs-elest-io) - [Backups | docs.elest.io](#backups-docs-elest-io) - [docs.elest.io](#docs-elest-io) - [Load balancers | docs.elest.io](#load-balancers-docs-elest-io) - [Billing | docs.elest.io](#billing-docs-elest-io) - [Databases | docs.elest.io](#databases-docs-elest-io) - [Getting started | docs.elest.io](#getting-started-docs-elest-io) - [CI/CD Pipelines | docs.elest.io](#ci-cd-pipelines-docs-elest-io) - [Valkey | docs.elest.io](#valkey-docs-elest-io) - [KeyDB | docs.elest.io](#keydb-docs-elest-io) - [TimescaleDB | docs.elest.io](#timescaledb-docs-elest-io) - [Redis | docs.elest.io](#redis-docs-elest-io) - [PostgreSQL | docs.elest.io](#postgresql-docs-elest-io) - [ClickHouse | docs.elest.io](#clickhouse-docs-elest-io) - [MySQL | docs.elest.io](#mysql-docs-elest-io) - [Getting Started | docs.elest.io](#getting-started-docs-elest-io) - [Legal & Billing | docs.elest.io](#legal-billing-docs-elest-io) - [docs.elest.io](#docs-elest-io) - [How it works | docs.elest.io](#how-it-works-docs-elest-io) - [Overview | docs.elest.io](#overview-docs-elest-io) - [Managed Databases | docs.elest.io](#managed-databases-docs-elest-io) - [Service protection | docs.elest.io](#service-protection-docs-elest-io) - [What is Elestio? | docs.elest.io](#what-is-elestio-docs-elest-io) - [Tools | docs.elest.io](#tools-docs-elest-io) - [Create a new service | docs.elest.io](#create-a-new-service-docs-elest-io) - [Power Management | docs.elest.io](#power-management-docs-elest-io) - [Supported Softwares | docs.elest.io](#supported-softwares-docs-elest-io) - [Admin UI | docs.elest.io](#admin-ui-docs-elest-io) - [Search for [book] | docs.elest.io](#search-for-book-docs-elest-io) - [Database credentials | docs.elest.io](#database-credentials-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Security | docs.elest.io](#security-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for [book] {type:page} | docs.elest.io](#search-for-book-type-page-docs-elest-io) - [Services Dashboard | docs.elest.io](#services-dashboard-docs-elest-io) - [Projects & Teams | docs.elest.io](#projects-teams-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Books | docs.elest.io](#books-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for [book] {type:chapter} | docs.elest.io](#search-for-book-type-chapter-docs-elest-io) - [Search for [book] {type:book} | docs.elest.io](#search-for-book-type-book-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Page Revisions for Netcup | docs.elest.io](#page-revisions-for-netcup-docs-elest-io) - [Page Revisions for Upgrade support plan | docs.elest.io](#page-revisions-for-upgrade-support-plan-docs-elest-io) - [Page Revisions for Introduction | docs.elest.io](#page-revisions-for-introduction-docs-elest-io) - [docs.elest.io](#docs-elest-io) - [Page Revisions for BYOVM with AWS EC2 (Be... | docs.elest.io](#page-revisions-for-byovm-with-aws-ec2-be-docs-elest-io) - [Page Revisions for Elestio Data Processin... | docs.elest.io](#page-revisions-for-elestio-data-processin-docs-elest-io) - [Page Revisions for BYOVM (Bring Your Own VM) | docs.elest.io](#page-revisions-for-byovm-bring-your-own-vm-docs-elest-io) - [Page Revisions for How Does Elestio’s Pri... | docs.elest.io](#page-revisions-for-how-does-elestio-s-pri-docs-elest-io) - [Page Revisions for Overview | docs.elest.io](#page-revisions-for-overview-docs-elest-io) - [Page Revisions for How to secure your app... | docs.elest.io](#page-revisions-for-how-to-secure-your-app-docs-elest-io) - [How to Create AWS Acce... | docs.elest.io](#how-to-create-aws-acce-docs-elest-io) - [Cloning a Service to A... | docs.elest.io](#cloning-a-service-to-a-docs-elest-io) - [Cloning a Service to A... | docs.elest.io](#cloning-a-service-to-a-docs-elest-io) - [Database Migration | docs.elest.io](#database-migration-docs-elest-io) - [Restoring a Backup | docs.elest.io](#restoring-a-backup-docs-elest-io) - [Creating a Database | docs.elest.io](#creating-a-database-docs-elest-io) - [Delete a Cluster | docs.elest.io](#delete-a-cluster-docs-elest-io) - [Overview | docs.elest.io](#overview-docs-elest-io) - [Cluster Management | docs.elest.io](#cluster-management-docs-elest-io) - [Adding a Node | docs.elest.io](#adding-a-node-docs-elest-io) - [Removing a Node | docs.elest.io](#removing-a-node-docs-elest-io) - [Create your own templa... | docs.elest.io](#create-your-own-templa-docs-elest-io) - [Cluster Management | docs.elest.io](#cluster-management-docs-elest-io) - [Node Management | docs.elest.io](#node-management-docs-elest-io) - [Promoting a Node | docs.elest.io](#promoting-a-node-docs-elest-io) - [Backups and Restores | docs.elest.io](#backups-and-restores-docs-elest-io) - [Database Migration Ser... | docs.elest.io](#database-migration-ser-docs-elest-io) - [Unknown](#unknown) - [Privacy policies | docs.elest.io](#privacy-policies-docs-elest-io) - [Custom domain and auto... | docs.elest.io](#custom-domain-and-auto-docs-elest-io) - [Unknown](#unknown) - [Is it possible to rest... | docs.elest.io](#is-it-possible-to-rest-docs-elest-io) - [Connecting with keydb-cli | docs.elest.io](#connecting-with-keydb-cli-docs-elest-io) - [Checking Database Size... | docs.elest.io](#checking-database-size-docs-elest-io) - [Using Cloudflare | docs.elest.io](#using-cloudflare-docs-elest-io) - [MariaDB Database Migra... | docs.elest.io](#mariadb-database-migra-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Page Revisions for Cloning a Service to A... | docs.elest.io](#page-revisions-for-cloning-a-service-to-a-docs-elest-io) - [Page Revisions for Admin UI | docs.elest.io](#page-revisions-for-admin-ui-docs-elest-io) - [Page Revisions for Cloning a Service to A... | docs.elest.io](#page-revisions-for-cloning-a-service-to-a-docs-elest-io) - [docs.elest.io](#docs-elest-io) - [Update AWS Account Acc... | docs.elest.io](#update-aws-account-acc-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Detect and terminate l... | docs.elest.io](#detect-and-terminate-l-docs-elest-io) - [Database Migrations | docs.elest.io](#database-migrations-docs-elest-io) - [Restricting Access by IP | docs.elest.io](#restricting-access-by-ip-docs-elest-io) - [Installing or Updating... | docs.elest.io](#installing-or-updating-docs-elest-io) - [Creating a Database | docs.elest.io](#creating-a-database-docs-elest-io) - [Connecting with pgAdmin | docs.elest.io](#connecting-with-pgadmin-docs-elest-io) - [Connecting with PHP | docs.elest.io](#connecting-with-php-docs-elest-io) - [Deleting a Cluster | docs.elest.io](#deleting-a-cluster-docs-elest-io) - [Connecting with Node.js | docs.elest.io](#connecting-with-node-js-docs-elest-io) - [Restoring a Backup | docs.elest.io](#restoring-a-backup-docs-elest-io) - [Upgrading to a Major V... | docs.elest.io](#upgrading-to-a-major-v-docs-elest-io) - [Connecting with Java | docs.elest.io](#connecting-with-java-docs-elest-io) - [Cluster Resynchronization | docs.elest.io](#cluster-resynchronization-docs-elest-io) - [Connecting with Python | docs.elest.io](#connecting-with-python-docs-elest-io) - [Connecting with psql | docs.elest.io](#connecting-with-psql-docs-elest-io) - [Connecting with Go | docs.elest.io](#connecting-with-go-docs-elest-io) - [Cloning a Service to A... | docs.elest.io](#cloning-a-service-to-a-docs-elest-io) - [Creating Manual Backups | docs.elest.io](#creating-manual-backups-docs-elest-io) - [Manual Migration Using... | docs.elest.io](#manual-migration-using-docs-elest-io) - [Database Migration Ser... | docs.elest.io](#database-migration-ser-docs-elest-io) - [Page Revisions for Database Migrations | docs.elest.io](#page-revisions-for-database-migrations-docs-elest-io) - [Page Revisions for Deleting a Cluster | docs.elest.io](#page-revisions-for-deleting-a-cluster-docs-elest-io) - [Page Revisions for Restricting Access by IP | docs.elest.io](#page-revisions-for-restricting-access-by-ip-docs-elest-io) - [Page Revisions for Connecting with Node.js | docs.elest.io](#page-revisions-for-connecting-with-node-js-docs-elest-io) - [Page Revisions for Cluster Resynchronization | docs.elest.io](#page-revisions-for-cluster-resynchronization-docs-elest-io) - [Page Revisions for Connecting with PHP | docs.elest.io](#page-revisions-for-connecting-with-php-docs-elest-io) - [Page Revisions for Connecting with Java | docs.elest.io](#page-revisions-for-connecting-with-java-docs-elest-io) - [Page Revisions for Connecting with Go | docs.elest.io](#page-revisions-for-connecting-with-go-docs-elest-io) - [Page Revisions for Connecting with psql | docs.elest.io](#page-revisions-for-connecting-with-psql-docs-elest-io) - [Page Revisions for Connecting with Python | docs.elest.io](#page-revisions-for-connecting-with-python-docs-elest-io) - [Page Revisions for Database Migration Ser... | docs.elest.io](#page-revisions-for-database-migration-ser-docs-elest-io) - [Page Revisions for Detect and terminate l... | docs.elest.io](#page-revisions-for-detect-and-terminate-l-docs-elest-io) - [Page Revisions for Installing or Updating... | docs.elest.io](#page-revisions-for-installing-or-updating-docs-elest-io) - [Page Revisions for Creating a Database | docs.elest.io](#page-revisions-for-creating-a-database-docs-elest-io) - [Page Revisions for Connecting with pgAdmin | docs.elest.io](#page-revisions-for-connecting-with-pgadmin-docs-elest-io) - [Page Revisions for Restoring a Backup | docs.elest.io](#page-revisions-for-restoring-a-backup-docs-elest-io) - [Page Revisions for Upgrading to a Major V... | docs.elest.io](#page-revisions-for-upgrading-to-a-major-v-docs-elest-io) - [Page Revisions for Cloning a Service to A... | docs.elest.io](#page-revisions-for-cloning-a-service-to-a-docs-elest-io) - [Page Revisions for Creating Manual Backups | docs.elest.io](#page-revisions-for-creating-manual-backups-docs-elest-io) - [Page Revisions for Manual Migration Using... | docs.elest.io](#page-revisions-for-manual-migration-using-docs-elest-io) - [Overview | docs.elest.io](#overview-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Identifying Slow Queries | docs.elest.io](#identifying-slow-queries-docs-elest-io) - [Preventing Full Disk I... | docs.elest.io](#preventing-full-disk-i-docs-elest-io) - [Checking Database Size... | docs.elest.io](#checking-database-size-docs-elest-io) - [Overview | docs.elest.io](#overview-docs-elest-io) - [Adding a Node | docs.elest.io](#adding-a-node-docs-elest-io) - [Deploying a New Cluster | docs.elest.io](#deploying-a-new-cluster-docs-elest-io) - [Node Management | docs.elest.io](#node-management-docs-elest-io) - [Promoting a Node | docs.elest.io](#promoting-a-node-docs-elest-io) - [Removing a Node | docs.elest.io](#removing-a-node-docs-elest-io) - [Backups and Restores | docs.elest.io](#backups-and-restores-docs-elest-io) - [Page Revisions for Overview | docs.elest.io](#page-revisions-for-overview-docs-elest-io) - [Page Revisions for Identifying Slow Queries | docs.elest.io](#page-revisions-for-identifying-slow-queries-docs-elest-io) - [Page Revisions for Preventing Full Disk I... | docs.elest.io](#page-revisions-for-preventing-full-disk-i-docs-elest-io) - [Page Revisions for Overview | docs.elest.io](#page-revisions-for-overview-docs-elest-io) - [Page Revisions for Checking Database Size... | docs.elest.io](#page-revisions-for-checking-database-size-docs-elest-io) - [Page Revisions for Adding a Node | docs.elest.io](#page-revisions-for-adding-a-node-docs-elest-io) - [Page Revisions for Deploying a New Cluster | docs.elest.io](#page-revisions-for-deploying-a-new-cluster-docs-elest-io) - [Page Revisions for Node Management | docs.elest.io](#page-revisions-for-node-management-docs-elest-io) - [Page Revisions for Removing a Node | docs.elest.io](#page-revisions-for-removing-a-node-docs-elest-io) - [Page Revisions for Promoting a Node | docs.elest.io](#page-revisions-for-promoting-a-node-docs-elest-io) - [Page Revisions for Backups and Restores | docs.elest.io](#page-revisions-for-backups-and-restores-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) - [Search for | docs.elest.io](#search-for-docs-elest-io) --- # docs.elest.io [Skip to main content](https://docs.elest.io/#main-content) Info Content Books ===== Sort Name * [Name](https://docs.elest.io/#) * [Created Date](https://docs.elest.io/#) * [Updated Date](https://docs.elest.io/#) [Backups\ -------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/backups) [Billing\ -------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/billing) [CI/CD Pipelines\ ---------------\ \ Go from source code to production with CI/CD Pipelines. We support Github, Gitlab & docker registries as source. Pipelines can ...\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/cicd-pipelines) [ClickHouse\ ----------\ \ Created 6 months ago\ \ Updated 6 months ago](https://docs.elest.io/books/clickhouse) [Cloud Providers\ ---------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/cloud-providers) [Databases\ ---------\ \ We currently support cluster mode for MySQL & KeyDB (Redis compatible). We are working hard on adding cluster mode support for ...\ \ Created 3 years ago\ \ Updated 1 year ago](https://docs.elest.io/books/databases) [DB Migrations\ -------------\ \ Need help to migrate to Elestio? Follow the simple steps in the documentation here and get started.\ \ Created 2 years ago\ \ Updated 9 months ago](https://docs.elest.io/books/db-migrations) [Domains\ -------\ \ Domains\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/domains) [Elestio API\ -----------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/elestio-api) [Elestio Terraform provider\ --------------------------\ \ The Elestio Terraform provider is a plugin that enables users to manage resources on the Elestio platform using Terraform. T...\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/elestio-terraform-provider) [Frequently Asked Questions\ --------------------------\ \ Here are some most commonly asked questions\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/frequently-asked-questions) [Getting started\ ---------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/getting-started) [Hydra\ -----\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/hydra) [Keycloak\ --------\ \ Created 6 months ago\ \ Updated 6 months ago](https://docs.elest.io/books/keycloak) [KeyDB\ -----\ \ Created 5 months ago\ \ Updated 5 months ago](https://docs.elest.io/books/keydb) [Legal & Compliance\ ------------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/legal-compliance) [Load balancers\ --------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/load-balancers) [Managed DB Overview\ -------------------\ \ Created 9 months ago\ \ Updated 9 months ago](https://docs.elest.io/books/managed-db-overview) Back to top --- # Shelves | docs.elest.io [Skip to main content](https://docs.elest.io/shelves#main-content) Info Content Shelves ======= Sort Name * [Name](https://docs.elest.io/shelves#) * [Created Date](https://docs.elest.io/shelves#) * [Updated Date](https://docs.elest.io/shelves#) [Getting Started\ ---------------\ \ https://www.youtube.com/watch?v=zWyM6m3cWxE\ \ Created 3 years ago\ \ Updated 9 months ago](https://docs.elest.io/shelves/getting-started) [How it works\ ------------\ \ Created 3 years ago\ \ Updated 9 months ago](https://docs.elest.io/shelves/how-it-works) [Legal & Billing\ ---------------\ \ Created 3 years ago\ \ Updated 3 years ago](https://docs.elest.io/shelves/legal-billing) [Managed Databases\ -----------------\ \ Created 9 months ago\ \ Updated 9 months ago](https://docs.elest.io/shelves/managed-databases) Back to top --- # docs.elest.io [Skip to main content](https://docs.elest.io/login#main-content) Log In ====== Email Password [Forgot Password?](https://docs.elest.io/password/email) Remember Me Log In Back to top --- # Books | docs.elest.io [Skip to main content](https://docs.elest.io/books#main-content) Info Content Books ===== Sort Name * [Name](https://docs.elest.io/books#) * [Created Date](https://docs.elest.io/books#) * [Updated Date](https://docs.elest.io/books#) [Backups\ -------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/backups) [Billing\ -------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/billing) [CI/CD Pipelines\ ---------------\ \ Go from source code to production with CI/CD Pipelines. We support Github, Gitlab & docker registries as source. Pipelines can ...\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/cicd-pipelines) [ClickHouse\ ----------\ \ Created 6 months ago\ \ Updated 6 months ago](https://docs.elest.io/books/clickhouse) [Cloud Providers\ ---------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/cloud-providers) [Databases\ ---------\ \ We currently support cluster mode for MySQL & KeyDB (Redis compatible). We are working hard on adding cluster mode support for ...\ \ Created 3 years ago\ \ Updated 1 year ago](https://docs.elest.io/books/databases) [DB Migrations\ -------------\ \ Need help to migrate to Elestio? Follow the simple steps in the documentation here and get started.\ \ Created 2 years ago\ \ Updated 9 months ago](https://docs.elest.io/books/db-migrations) [Domains\ -------\ \ Domains\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/domains) [Elestio API\ -----------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/elestio-api) [Elestio Terraform provider\ --------------------------\ \ The Elestio Terraform provider is a plugin that enables users to manage resources on the Elestio platform using Terraform. T...\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/elestio-terraform-provider) [Frequently Asked Questions\ --------------------------\ \ Here are some most commonly asked questions\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/frequently-asked-questions) [Getting started\ ---------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/getting-started) [Hydra\ -----\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/hydra) [Keycloak\ --------\ \ Created 6 months ago\ \ Updated 6 months ago](https://docs.elest.io/books/keycloak) [KeyDB\ -----\ \ Created 5 months ago\ \ Updated 5 months ago](https://docs.elest.io/books/keydb) [Legal & Compliance\ ------------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/legal-compliance) [Load balancers\ --------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/load-balancers) [Managed DB Overview\ -------------------\ \ Created 9 months ago\ \ Updated 9 months ago](https://docs.elest.io/books/managed-db-overview) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Getting started](https://docs.elest.io/books/getting-started) [#### Getting Started\ \ https://www.youtube.com/watch?v=zWyM6m3cWxE](https://docs.elest.io/shelves/getting-started) [#### Overview\ \ Services Dashboard](https://docs.elest.io/books/services-dashboard/chapter/overview) [#### Service protection\ \ Services Dashboard Overview\ \ Elestio services can be protected against accidental deletion by enabling the Termination protection feature: When Termination protection is enabled for a service, it can't be terminated or powered down. In order to terminate or power off a protected serv...](https://docs.elest.io/books/services-dashboard/page/service-protection) [#### Services Dashboard](https://docs.elest.io/books/services-dashboard) [#### How it works](https://docs.elest.io/shelves/how-it-works) [#### Tools\ \ Services Dashboard](https://docs.elest.io/books/services-dashboard/chapter/tools) [#### Power Management\ \ Services Dashboard Overview\ \ You may manage power management on an elestio by using the Reboot, Reset, Shutdown, Power On, and Power Off buttons. Reboot service:- Sends an ACPI request to restart a server gracefully. Otherwise, the Server won't reboot. This requires that the Server...](https://docs.elest.io/books/services-dashboard/page/power-management) [#### Cloud Providers](https://docs.elest.io/books/cloud-providers) [#### Legal & Billing](https://docs.elest.io/shelves/legal-billing) [#### Admin UI\ \ Services Dashboard Overview\ \ Most supported softwares have an administrative web interface. Selecting the Display Admin UI button will display the URL, user name and password used to connect to a service's administrative UI. Some software, especially databases, do not have a web managem...](https://docs.elest.io/books/services-dashboard/page/admin-ui) [#### Supported Softwares\ \ Our catalog is comprised of over 350+ open source software services. We plan to continue adding to our catalog each month, so keep checking back for new additions!For each supported software we prepare a fully managed lifecycle process.This includes:Setup scri...](https://docs.elest.io/books/supported-softwares) [#### Database credentials\ \ Services Dashboard Overview\ \ This only applies to database software. You can view your database software in your service Dashboard in the Overview tab, by selecting the Display DB Credentials button. You'll find all the details you'll need to connect to your database directly: host ad...](https://docs.elest.io/books/services-dashboard/page/database-credentials) [#### Backups](https://docs.elest.io/books/backups) [#### Managed Databases](https://docs.elest.io/shelves/managed-databases) [#### What is Elestio?\ \ Getting started\ \ Elestio is the simplest way to run Open Source Software. Deploy any one of over 350+ supported open-source software distributions on a dedicated instance in less than 5 minutes. Elestio's platform takes care of installation, configuration, encryption, backup...](https://docs.elest.io/books/getting-started/page/what-is-elestio) [#### Projects & Teams](https://docs.elest.io/books/projects-teams) [#### Create a new service\ \ Getting started\ \ 1\. To create a new service, first open Elestio Dashboard Use the category tabs to filter the selection of software. Choose the template you want to deploy and click the select button for the next step. If you want to learn more about that template, cli...](https://docs.elest.io/books/getting-started/page/create-a-new-service) [#### Security](https://docs.elest.io/books/security) [#### Billing](https://docs.elest.io/books/billing) Back to top --- # Tags | docs.elest.io [Skip to main content](https://docs.elest.io/tags#main-content) Tags ==== Tags can be applied to content within the system to apply a flexible form of categorization. Tags can have both a key and value, with the value being optional. Once applied, content can then be queried using the tag name and value. Sort Name * [Name](https://docs.elest.io/tags#) * [Total tag usages](https://docs.elest.io/tags#) [book](https://docs.elest.io/search?term=%5Bbook%5D) [1](https://docs.elest.io/search?term=%5Bbook%5D "Total tag usages") [0](https://docs.elest.io/search?term=%5Bbook%5D+{type:page} "Assigned to Pages") [0](https://docs.elest.io/search?term=%5Bbook%5D+{type:chapter} "Assigned to Chapters") [1](https://docs.elest.io/search?term=%5Bbook%5D+{type:book} "Assigned to Books") [0](https://docs.elest.io/search?term=%5Bbook%5D+{type:bookshelf} "Assigned to Shelves") [1 unique values](https://docs.elest.io/tags?name=book) [question](https://docs.elest.io/search?term=%5Bquestion%5D) [1](https://docs.elest.io/search?term=%5Bquestion%5D "Total tag usages") [0](https://docs.elest.io/search?term=%5Bquestion%5D+{type:page} "Assigned to Pages") [0](https://docs.elest.io/search?term=%5Bquestion%5D+{type:chapter} "Assigned to Chapters") [1](https://docs.elest.io/search?term=%5Bquestion%5D+{type:book} "Assigned to Books") [0](https://docs.elest.io/search?term=%5Bquestion%5D+{type:bookshelf} "Assigned to Shelves") [1 unique values](https://docs.elest.io/tags?name=question) Back to top --- # Elestio Data Processin... | docs.elest.io [Skip to main content](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement#main-content) Info Content Elestio Data Processing Agreement ================================= _Last Modified: Feb 06, 2025_ **1\. Background** This Data Processing Agreement (‘’DPA’’) is attached to the General Terms (available at https://elest.io/terms and forms an inseparable part of the Agreement entered into by Elestio limited (hereinafter “Elestio”) and the Customer. This DPA shall set out the terms and conditions for the processing of Personal Data by Elestio on behalf of the Customer under the Agreement. **2\. Scope and conflict of rules** To the extent the Customer inputs Personal Data into the Cloud Services and Elestio processes such Personal Data, the Parties acknowledge that the Customer acts as a Data Controller and Elestio is a Data Processor processing Personal Data on behalf of the Customer for the purpose of providing the Cloud Services.  In the event of any discrepancy between this DPA and the Agreement, this DPA prevails. **3\. Definitions** Unless otherwise defined in this DPA or in the Agreement, terms used in this DPA, such as "Data Controller", "Data Processor", "Data Subject" and "Personal Data" have the meanings as defined in the Data Protection Regulation.  Data Protection Regulation means all applicable laws relating to data protection, including without limitation the GDPR and the laws implementing EU Directive 2002/58/EC and any amendments to or replacements for such laws and regulations. GDPR means the General Data Protection Regulation (EU) 2016/679. Personal Data Breach means a breach of security leading to accidental or unlawful destruction, loss, alteration, unuthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise processed. Standard Contractual Clauses means the contractual clauses issued by the European Commission by the decision 2021/914/EU for international transfers of Personal Data. Subprocessor means third parties: i) providing back-end services for Elestio and/or ii) selected by the Customer to provide the hosting services for the data Customer inputs to the Cloud Services. The Subprocessors and their services are listed on the Website. Website means Elestio's website available at Elest.io and the Elestio console through which the Customer may use the Cloud Services. **4\. Processing of personal data** Processing of Personal Data under this DPA is for the purpose of providing the Cloud Services to the Customer. Processing of Personal Data in this context refers to storage, maintenance and other processing activities initiated by the Customer, depending on which Cloud Services the Customer has chosen to order from time to time. The categories of Data Subjects and the types of Personal Data processed are defined in the Appendix 1 (Details of processing). Personal Data may be processewed as long as the Cloud Services are provided under the Agreement and after that if required by applicable law or contractual obligations or rights of either Party. **5\. Customer's instructions** The Elestio shall process Personal Data in accordance with the Customer's written instructions as established in this DPA. The Parties agree that this DPA is the Customer's complete written instruction to the Elestio in the Customer's role as the Data Controller. Additional instructions require prior written agreement between the Parties. **6\. Elestio’s general obligations** Elestio shall, at the Customer's written request and the Customer's sole cost and expense, assist the Customer by providing such readily available information, or creating such information, as the Customer may reasonably require and which the Customer does not have, in complying with the requests of the Data Subjects or supervisory authority or any other law enforcement or regulatory authority. Elestio shall inform the Customer, as soon as reasonably practicable, if it receives a request from a Data Subject seeking to exercise his or her rights under the Data Protection Regulation. Elestio shall maintain records of processing activities under its responsibility to ensure Elestio's own compliance as a Data Processor with the Data Protection Regulation, and upon the Customer's written request Elestio shall make available to the Customer such records to the extent necessary to demonstrate compliance with Elestio’s obligations set out in this DPA and in the Data Protection Regulation. **7\. Data security** Elestio shall implement and maintain appropriate technical and organisational measures to ensure an appropriate level of security of the Personal Data and to protect the Personal Data against unuthorised or unlawful processing and against accidental loss, destruction, damage, alteration, or disclosure for the purposes of the Cloud Services.  In the event of a Personal Data Breach, Elestio shall notify the Customer without undue delay and at least within 48 hours after becoming aware of the Personal Data Breach and take reasonable steps to mitigate any damage resulting from such breach. The notification shall contain information Elestio is reasonably able to disclose to the Customer, including following information: 1. a description of the nature of the Personal Data breach, including where possible the categories of Data Subjects and the Personal Data concerned; 2. the name and contact details of contact point where more information can be obtained; 3. a description of likely consequences of the Personal Data Breach; and 4. a description of the measures taken or proposed to be taken to address the Personal Data Breach. The information may be provided in phases if it is not possible to provide the information at the same time. Elestio shall cooperate with and assist the Customer, at the Customer's written request, in relation to the Personal Data Breach notifications made to supervisory authority as required under the Data Protection Regulation. Elestio shall document the Personal Data Breaches and have the documentation available to the Customer upon the Customer's written request. **8\. Controlled Support Access and Data Transfers** **8.1 Customer-Controlled Access** Elestio ensures that personal data remains hosted and processed within the EU. Access to customer data is never granted by default—neither Elestio employees inside the EU nor those outside the EU have access unless explicitly authorized by the Customer. Support access is governed by the following conditions: **Customer-Initiated Access Grant:** No Elestio employee, whether inside or outside the EU, can access customer data unless the Customer submits a support ticket and explicitly checks the box labeled "Grant Elestio Support team access to your project throughout the duration of this support ticket." **Temporary and Limited Scope:** Support access is strictly limited to the duration of the specific support ticket and is automatically revoked upon resolution or ticket closure. **Minimal Necessary Access:** Only personnel required for issue resolution will receive access, following the principle of least privilege. **8.2 Legal Basis for Support Access and Non-EU Transfers** In cases where the Customer grants access and Elestio’s support personnel—including those outside the EU—access personal data, such access is considered a restricted transfer under GDPR. Elestio ensures compliance through the following measures: **Standard Contractual Clauses (SCCs):** Elestio has implemented SCCs between its EU and non-EU entities or partners, ensuring GDPR-compliant safeguards for data transfers. **Security and Logging:** All access requests are logged, monitored, and reviewed to ensure transparency and compliance. **Encryption & Data Protection:** Where applicable, personal data remains encrypted at rest and in transit to minimize risks during support access. **8.3 Customer’s Control and Revocation Rights** The Customer retains full control over granting and revoking support access. If the Customer does not explicitly grant access, no Elestio employee—whether inside or outside the EU—can access customer data. The Customer may also request an audit log of access events related to their support tickets. **9\. Subprocessors** Elestio is entitled to use Subprocessors for the purposes of providing the Cloud Services under the Agreement. Elestio provides information on its Subprocessors at its Website. The Customer can choose a Subprocessor to provide the hosting for the Cloud Services from the options provided by Elestio. Elestio shall inform the Customer in writing of any intended changes of the hosting service provider Subprocessor at least fourteen (14) days in advance, giving the Customer sufficient time to be able to object to such change. The Customer hereby consents to Elestio's use of Subprocessors as described in this section. Elestio shall use its commercially reasonable efforts to reasonably ensure that its Subprocessors are subject to equivalent requirements regarding data protection, as set out in this DPA. Elestio remains responsible for its Subprocessors and their compliance with the obligations of this DPA. **10\. Transfers of personal data** The Customer may choose where the Cloud Services will be hosted. If the Customer has selected a Subprocessor to provide the hosting within the European Economic Area (‘’EEA’’), Elestio shall store the Personal Data within the EEA and transfers outside the EEA are subject to the Customer's prior approval, instruction or request thereto.  If the Customer selects a Subprocessor to provide the hosting services outside the EEA, the Customer accepts that Elestio; (i) performs the international data transfer of Personal Data in accordance with the Standard Contractual Clauses (processor-to-processor module) entered into by Elestio (as a data exporter) and the Subprocessor (as a data importer) or; (ii) agrees the Subprocessor to carry out the transfer in accordance with the Standard Contractual Clauses (processor-to-processor module) entered into by the Subprocessor group companies (Subprocessor’s EEA entity as a data exporter and third country entity as a data importer), as applicable, depending on the Subprocessor the Customer chooses.  The Customer warrants to have used reasonable efforts to determine that the Subprocessor acting as data importer, and chosen by Customer, is able through the implementation of appropriate technical and organisational measures, to satisfy data importer’s obligations under the Standard Contractual Clauses for the transfer to be performed as agreed in this DPA. In the event of discrepancies between the Standard Contractual Clauses and this DPA, the Standard Contractual Clauses prevail.  Notwithstanding the foregoing, the Standard Contractual Clauses will not apply if Elestio has adopted alternative safeguards in accordance with Data Protection Regulation for the lawful transfer of Personal Data outside the EEA. **11\. Auditing** At the Customer's written request and the Customer's sole cost and expense, the Customer is entitled, once every twelve (12) months, to audit Elestio's compliance with its obligations under the Data Protection Regulation and this DPA. The audit report and related information shall at all times be deemed as Elestio's confidential information. **12\. Data confidentiality** Elestio will not access or use, have visibility or disclose to any third party, any data that the Customer has input into the Cloud Services, except, if specifically requested in writing by the Customer in order to provide customer-specific support services as requested and instructed by the Customer.  If a governmental body sends Elestio a demand for the data input into the Cloud Services, Elestio will do its best efforts to redirect the governmental body to request that data directly from the Customer. If compelled to disclose Customer Data to a governmental body, then Elestio will only disclose the Personal Data strictly to the extent it is legally required to do so and shall give the Customer reasonable notice of the demand to allow the Customer to seek a protective order or other appropriate remedy unless Elestio is legally prohibited from doing so. **13\. Term and termination** This DPA shall become effective in parallel with the Agreement and shall continue in force until the termination of the Agreement or as long as Elestio processes Personal Data on behalf of the Customer. If not instructed otherwise in writing by the Customer and unless legally required to keep the Personal Data, Elestio shall delete and destroy the Personal Data processed hereunder the latest within ninety (90) days' of the termination of the Agreement or after the maximum data retention period permitted by the technology of the relevant Cloud Service. In case the Customer demands that the Personal Data are returned to the Customer or to a third party, the Customer will pay Elestio for any additional costs and expenses arising out of such return of the Personal Data. ##### **Appendix 1 - Details of processing** This Appendix 1 forms part of this DPA describing the details of personal data to be processed by Elestio.  The Customer has full control of what personal data will be processed by uploading such personal data into the Cloud Services. Elestio has no visibility to such personal data provided and uploaded by the Customer. Data subjects * Prospects, customers, business partners, and vendors of the Customer (who are natural persons) * Employees or contact persons of the Customer’s prospects, customers, business partners and vendors * Employees, agents, advisors, and freelancers of the Customer (who are natural persons) * Individuals uthorised by the Customer under the Agreement Categories of personal data * Full name * Title, position * Email address, address * Phone number Special categories of personal data - No special categories of Personal Data are processed.  Subject matter of the processing - Hosting, storing and maintenance for the data Customer has input to the Cloud Services. For clarity, the Customer is the Data Controller of, and this DPA is only applied to, the Personal Data input to the Cloud Services by Customer. ##### **Appendix 2 - Elestio’s technical and organisational safety measures** This Appendix 2 forms a part of this DPA describing Elestio’s technical and organisational safety measures. Description of the technical and organisational security measures implemented by Elestio. Elestio will maintain administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of Personal Data processed on the Cloud Services as applicable to the specific Cloud Service purchased by the Customer. Elestio must report, in an internal document, to be kept updated and available upon request of the Data Controller or the Guarantor Authority, the identification details of the natural persons who have been assigned the role of System Administrator, with the list of functions assigned to them. We maintain ISO 27001 and SOC 2 certifications, demonstrating our commitment to industry-leading security standards. These certifications validate our implementation of robust security controls, ensuring the confidentiality, integrity, and availability of personal data. In accordance with Article 32 of the GDPR, Elestio implements the following security measures to ensure the protection of Personal Data processed through its Cloud Services. **1\. Organisational Security Measures** * **Data Protection Policy:** A documented Data Protection Policy is maintained and regularly reviewed. * **Security Awareness & Training:** All personnel with access to Personal Data undergo mandatory data protection training upon onboarding and annually thereafter. * **Access Control & Role-Based Authorization:** * Access to Personal Data is restricted to authorized personnel based on the principle of least privilege (PoLP). * All access permissions are reviewed periodically. * Administrative access is subject to multi-factor authentication (MFA). * **Third-Party Risk Management:** Subprocessors undergo security risk assessments and contractual safeguards are implemented, including data processing agreements. * **Incident Response Plan:** A formalized incident response plan is in place, detailing responsibilities, detection, containment, eradication, and recovery steps for data breaches. **2\. Physical Security Measures** * **Data Center Security:** * Cloud Services are hosted in secure data centers certified with **ISO 27001, SOC 2, and/or equivalent standards**. * Physical access to servers is restricted to authorized personnel only, with biometric and keycard access controls. * Continuous surveillance (CCTV) and intrusion detection systems are implemented. **3\. Technical Security Measures** * **Encryption:** * Personal Data is encrypted **at rest** using AES-256. * Personal Data is encrypted **in transit** using TLS 1.2/1.3. * **Logging & Monitoring:** * Access to Personal Data is logged, monitored, and audited for anomalies. * System logs are retained for **12 months**. * **Data Minimization & Anonymization:** * Where applicable, Personal Data is pseudonymized or anonymized to reduce risk. * **Secure Development & Vulnerability Management:** * Regular security audits and penetration testing are conducted. * Software updates and patches are applied in a timely manner. **4\. Business Continuity & Backup** * **Data Backup & Disaster Recovery:** * Backups are performed daily and retained for **180 days**. * Disaster recovery procedures are tested at least annually. **5\. Data Subject Rights & Compliance Measures** * **Handling of Data Subject Requests:** * Procedures are in place to respond to requests for data access, rectification, erasure, and portability. * **Legal & Compliance Audits:** Elestio undergoes periodic external audits to ensure compliance with GDPR and applicable regulations. Enter section select mode [Previous\ \ Subcontractors](https://docs.elest.io/books/legal-compliance/page/subcontractors) Back to top --- # BYOVM (Bring Your Own VM) | docs.elest.io [Skip to main content](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm#main-content) Info Content BYOVM (Bring Your Own VM) ========================= You can also deploy into your own cloud account from any cloud provider (Azure, GCP, Alibaba, Oracle, etc.) or from an VM hosted on-premise. In these instances, you are responsible for the relationship with your provider while we take care of the management side of things. [![Screenshot 2025-10-08 181456.png](https://docs.elest.io/uploads/images/gallery/2025-10/screenshot-2025-10-08-181456.png)](https://docs.elest.io/uploads/images/gallery/2024-06/0Qcimage.png) ### Pricing Pricing is based on the specification of the VM you are connecting to:  **$5 per vCPU + $2.5 per GB of RAM + $0.25 per 10 GB of disk.** Example: if you are connecting a VM with 2 vCPU + 4GB RAM + 40GB Disk, the cost per month will be (5\*2) +  (2.5\*4) + (0.25\*4) = ~$21/mo Price per hour is then calculated like this: $21/730h = $0.02876/h Enter section select mode [Previous\ \ Linode](https://docs.elest.io/books/cloud-providers/page/linode) [Next\ \ BYOVM with AWS EC2](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2) Back to top --- # Netcup | docs.elest.io [Skip to main content](https://docs.elest.io/books/cloud-providers/page/netcup#main-content) Info Content Netcup ====== Netcup is a well-established German hosting provider known for their high-performance virtual servers at competitive prices. They offer powerful AMD EPYC-based infrastructure with excellent value, especially in Europe. Netcup provides fully managed services with included remote backups, making them a solid choice for teams looking for reliability without the operational overhead. 20 TB of bandwidth is included with all VM sizes. * * * Supported Services ------------------ | Service | Status | | --- | --- | | Compute | ✅ | | Private Network | ✅ | | Firewall | ✅ | | Volumes | ❌ | | Floating IP | ❌ | | Snapshots | ❌ | | Remote Backups | ✅ (7 included) | * * * Supported Regions ----------------- | Continent | Country | City | Datacenter | | --- | --- | --- | --- | | Europe | Germany | Nuremberg | NBG | | North America | United States | Manassas, Virginia | MNS | * * * VM Sizes -------- All VMs run on **AMD EPYC 9645** processors and include **20 TB bandwidth** and **7 remote backups**. ### Europe (Germany - Nuremberg) | Size | Cores | RAM | Storage | Monthly Price | | --- | --- | --- | --- | --- | | MEDIUM-2C-4G | 2 | 4 GB | 60 GB NVMe | $14 | | LARGE-4C-8G | 4 | 8 GB | 100 GB NVMe | $26 | | XLARGE-8C-16G ⭐ | 8 | 16 GB | 200 GB NVMe | $49 | | 2XLARGE-16C-32G | 16 | 32 GB | 400 GB NVMe | $99 | | 3XLARGE-16C-64G | 16 | 64 GB | 600 GB NVMe | $149 | ### North America (United States - Manassas) | Size | Cores | RAM | Storage | Monthly Price | | --- | --- | --- | --- | --- | | MEDIUM-2C-4G | 2 | 4 GB | 60 GB NVMe | $16 | | LARGE-4C-8G | 4 | 8 GB | 100 GB NVMe | $29 | | XLARGE-8C-16G ⭐ | 8 | 16 GB | 200 GB NVMe | $59 | | 2XLARGE-16C-32G | 16 | 32 GB | 400 GB NVMe | $119 | | 3XLARGE-16C-64G | 16 | 64 GB | 600 GB NVMe | $179 | ⭐ = Best Value * * * Features -------- * **Fully Managed**: All servers come with full management included * **AMD EPYC 9645**: Latest generation AMD server processors * **7 Remote Backups**: Automatic backup retention included * **20 TB Bandwidth**: Generous bandwidth allocation on all plans * **NVMe Storage**: Fast SSD storage on all VM sizes Enter section select mode [Previous\ \ Hetzner](https://docs.elest.io/books/cloud-providers/page/hetzner) [Next\ \ Digital Ocean](https://docs.elest.io/books/cloud-providers/page/digital-ocean) Back to top --- # Managed DB Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/managed-db-overview#main-content) Info Content Managed DB Overview =================== [#### Global\ \ Elestio offers comprehensive services, including various support plans, support for multiple data...](https://docs.elest.io/books/managed-db-overview/page/global) ### Search Results Clear Search Back to top --- # BYOVM with AWS EC2 (Be... | docs.elest.io [Skip to main content](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui#main-content) Info Content BYOVM with AWS EC2 (Beta AWS UI) ================================ > This approach is outdated. Instead, you can use our [**Bring Your Own AWS Account(BYO-AWS)**](https://docs.elest.io/books/getting-started/page/create-a-new-service-with-bring-your-own-aws-account-byoaws) > provider option. You can deploy an Elestio service on your own AWS account with BYOVM To do it, you will need to create a VM on AWS EC2, first connect to the AWS EC2 dashboard:  [https://console.aws.amazon.com/ec2/v2/home#Instances:instanceState=running](https://console.aws.amazon.com/ec2/v2/home#Instances:instanceState=running) [![image-1648551097629.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551097629.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551097629.png) There click on **"Launch instances"** button and select **Ubuntu 20** [![image-1648551214266.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551214266.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551214266.png) Scroll down to **Instance type** to select your VM size based on your needs [![image-1648551260900.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551260900.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551260900.png) then scroll down to configure **network settings** and **storage** [![image-1648551341376.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551341376.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551341376.png) In network settings you should check the 3 checkboxes to allow SSH, HTTP and HTTPS traffic from the internet. In Storage, you can indicate any disk size above 20GB If you need to provision multiple VMs, you can change the number of instances in the top right column Finally click on **Launch instance** button [![image-1648551520084.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551520084.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551520084.png) If it's your first time deploying a VM you will be asked to create a new key pair [![image-1648551559491.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551559491.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551559491.png) give any key pair name then click on "Create key pair" and SAVE the PEM file preciously on your computer After a few seconds you will see a confirmation message: [![image-1648551657247.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551657247.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551657247.png) There click on **View all instances** button [![image-1648551707674.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551707674.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551707674.png) We recommend that you allocate & attach an Elastic IP address to your instance, so the IP address will never change in case you stop the server. [Click here](https://console.aws.amazon.com/ec2/v2/home#Addresses:) to allocate an Elastic IP and then attach it to your VM in EC2. We are now back on the list of all VMs in EC2, from here right click on your new instance and click on **Connect** in the sub menu [![image-1648551813396.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551813396.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551813396.png) There change the user name to **root,** then click on Connect button [![image-1648551863875.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551863875.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551863875.png)  You should then see a terminal shell like this [![image-1648551921125.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648551921125.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648551921125.png) There paste this command into the terminal to activate the remote management for Elestio (This is a temporary key used for the deployment phase, it's automatically removed from the VM right after the deployment) **sudo mkdir -p /root/.ssh/ && sudo echo "ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAmAlfBn8fy00sHq4DV2lUDNJ73XNwCtSDgHAAEjVt8lVcPOyb+drHK7TmHtF6mIhax/qeFdS/27bqmuu2/+QyXuvG98WL47cJinVkuUNR1bqKfpjwvlGtPkVQTiz2aN9ktY8+RaKoJUg6YrL23wiRgqibRuRYJgG1tIx7O4pUAK8XPsIVw2kvTuaVWu+iQq968KozJP8t1C6U8eqwbV2H8xpMLAsuIA82S1vGkqx42TBLo8XOgQo1ZIoY4dsO+ElvJZ5sqxAg4GB57OIgpaav/2SkKau6Oh4ndkKTJms5kTc2wUm96VVea2eOrOL0TPNQOhb1uy2MgxS9LLFxm2psmQ== elestio-prod-key" >> /root/.ssh/authorized\_keys** We also need to allow all traffic to the VM in the AWS EC2 instance list click on your instance, then click on the **security** tab [![image-1648555261405.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648555261405.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648555261405.png) There click on the Security group in blue (launch-wizard-1 in the screenshot above) [![image-1648555516835.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648555516835.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648555516835.png) Click on "Edit inbound rules" to be able to allow all traffic on the VM [![image-1648556736479.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648556736479.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648556736479.png) Here change the rule to allow ALL TCP traffic & ALL UDP traffic from anywhere Alternatively, you can open just a selection of ports based on your needs, at least ports **TCP:** **22, 80, 443** for basic usage. To allow Elestio tools (File Explorer, VS Code, web terminal) you should also open ports **TCP: 18345,18374,18445.** If you want to use our global private ip network you should also allow port **UDP: 4242** Finally, some specific ports are required based on the template you have selected; you can find them in the activation email of the software or in our documentation [here](https://doc.elest.io/books/supported-softwares) . Then go back to Elestio Dashboard to create a new BYOVM service [![image-1648553680058.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648553680058.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648553680058.png) Indicate the provider name, region name and Public IPV4 found in the AWS dashboard then click on "Test my VM." [![image-1648553849491.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648553849491.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648553849491.png) You'll see the pricing calculated based on the number of CPU/RAM/DISK of your AWS EC2 VM; You can then click on "Create service," and you are done! Your service will be deployed in less than 3 minutes and you will receive an email with instructions but of course the service is also accessible in the dashboard. [![image-1648557473027.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648557473027.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648557473027.png) From there we will take care of backups, monitoring/alerts, OS/software updates and security for you. [![image-1648557512849.png](https://docs.elest.io/uploads/images/gallery/2022-03/scaled-1680-/image-1648557512849.png)](https://docs.elest.io/uploads/images/gallery/2022-03/image-1648557512849.png) Enter section select mode [Previous\ \ BYOVM with AWS EC2](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2) [Next\ \ AWS EC2 or (BYOAWS) Bring Your Own AWS Account](https://docs.elest.io/books/cloud-providers/page/aws-ec2-or-byoaws-bring-your-own-aws-account) Back to top --- # Domains | docs.elest.io [Skip to main content](https://docs.elest.io/books/domains#main-content) Info Content Domains ======= Domains [#### Buying a Domain from Elest.io\ \ Great brand names are like magnets that people gravitate towards. Try https://elest.io/domains ...](https://docs.elest.io/books/domains/page/buying-a-domain-from-elestio) [#### How to Transfer your Domains from GoDaddy /others to elestio\ \ If you desire to transfer your domain to Elestio, here is a comprehensive, step-by-step guide tha...](https://docs.elest.io/books/domains/page/how-to-transfer-your-domains-from-godaddy-others-to-elestio) [#### How to Renew a Domain on Elestio?\ \ It is always best to renew a domain name before it expires so there is no interruption in service...](https://docs.elest.io/books/domains/page/how-to-renew-a-domain-on-elestio) [#### How can I change the name server for elestio domains?\ \ Nameservers are the first thing domain names look to when they need to know where the content of ...](https://docs.elest.io/books/domains/page/how-can-i-change-the-name-server-for-elestio-domains) [#### Locking/unlocking a domain\ \ The domain lock is an added layer of security to guard against unauthorized domain transfers. You...](https://docs.elest.io/books/domains/page/lockingunlocking-a-domain) ### Search Results Clear Search Back to top --- # How Does Elestio’s Pri... | docs.elest.io [Skip to main content](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work#main-content) Info Content How Does Elestio’s Pricing Work? ================================ Elestio offers a flexible cloud hosting platform that allows you to deploy and manage applications with ease. Unlike traditional cloud providers, Elestio's pricing is based on an **hourly billing system** with **prepaid credits**, providing transparency and control over your expenses. * * * 1\. Hourly Billing with Prepaid Credits --------------------------------------- Elestio operates on an **hourly billing model**, meaning you are charged for every hour a service exists on your account. * **Billing continues until deletion:** Shutting down or powering off a service does **not** stop billing. * **Prepaid credits:** You must add prepaid credits to your account. The hourly costs are automatically deducted. * **Service plan determines cost**: Pricing is fixed by the plan and does not depend on usage, traffic, or resource consumption. * * * 2\. Service Plans and Pricing ----------------------------- Elestio offers a variety of service plans to cater to different workloads. Each plan specifies the number of CPUs, RAM, storage, and the associated **hourly cost**. ##### Netcup Plans (Hourly & Monthly Approximate Cost) | Plan | CPUs | RAM | Storage | Hourly Cost | Monthly Cost\* | | --- | --- | --- | --- | --- | --- | | NC-MEDIUM-2C-4G | 2 | 4 GB | 60 GB | $0.019 | $14 | | NC-LARGE-4C-8G | 4 | 8 GB | 100 GB | $0.036 | $26 | | NC-XLARGE-8C-16G | 8 | 16 GB | 200 GB | $0.067 | $49 | | NC-2XLARGE-16C-32G | 16 | 32 GB | 400 GB | $0.136 | $99 | | NC-3XLARGE-16C-64G | 16 | 64 GB | 600 GB | $0.204 | $149 | \*Monthly cost is an approximation assuming continuous usage. > Note: Pricing is **fixed per plan** and does **not** depend on traffic, CPU usage, or number of users. * * * 3\. Support Plans ----------------- Support plans are also **charged hourly** and can **change once a month**. * **Support Levels:** Level 1 (Free), Level 2 ($50/service/month), Level 3 ($200/service/month). * **Minimum Period for Level 2 & 3**: * For Level 2 and Level 3 support plans, you must keep your service for at least **two weeks**. * If you delete a service **within the first two weeks**, you will be charged a fee: * Level 2: $25 * Level 3: $100 * Support plans provide features such as service support, high retention periods, automated Borg backups, snapshots, uptime guarantees, and priority assistance. * * * 4\. Billing Continuity ---------------------- * **Hourly billing** continues regardless of the service power state. * **Deleting a service** is the only way to stop charges. * **Partial hours are billed as full hours**, ensuring predictable costs. * * * 5\. Cost Management Tips ------------------------ 1. **Choose the right service plan** – avoid over-provisioning. 2. **Track prepaid credits** – refill before running out. 3. **Delete unused services** – to stop hourly charges. 4. **Plan support subscriptions** – consider the minimum two-week period for Level 2 and 3 plans. * * * 6\. Conclusion -------------- Elestio’s pricing model provides **flexibility, predictability, and control**. By understanding hourly billing, prepaid credits, service plans, and support plan rules, you can manage your cloud resources efficiently and avoid unexpected charges. For detailed pricing and plans, visit the **[Elestio Pricing Page](https://elest.io/pricing#pricing)**. Enter section select mode [Previous\ \ How can project ownership or service billing ...](https://docs.elest.io/books/frequently-asked-questions/page/how-can-project-ownership-or-service-billing-be-transferred-to-another-users-account) Back to top --- # How can project owners... | docs.elest.io [Skip to main content](https://docs.elest.io/books/frequently-asked-questions/page/how-can-project-ownership-or-service-billing-be-transferred-to-another-users-account#main-content) Info Content How can project ownership or service billing be transferred to another user's account? ====================================================================================== This guide explains how to transfer a project ownership from one Elestio account to another. Prerequisites ------------- Before starting the transfer: * The new owner must have an active Elestio account * The new owner must be added as a member in the project with **Admin** or **Billing Admin** role * The new owner must have sufficient credit for at least 1 month of service * Each project can only have one owner Transfer Steps -------------- ### Step 1: Access Project Settings Log in to your Elestio account and select the project you want to transfer. Click on the **Project Settings** tab. [![Screenshot 2025-09-07 at 13.28.00.png](https://docs.elest.io/uploads/images/gallery/2025-09/scaled-1680-/screenshot-2025-09-07-at-13-28-00.png)](https://docs.elest.io/uploads/images/gallery/2025-09/screenshot-2025-09-07-at-13-28-00.png) ### Step 2: Start the Transfer In the top right corner of the Project Settings page, click the **Transfer project** button. [![Screenshot 2025-09-07 at 15.21.02.png](https://docs.elest.io/uploads/images/gallery/2025-09/scaled-1680-/screenshot-2025-09-07-at-15-21-02.png)](https://docs.elest.io/uploads/images/gallery/2025-09/screenshot-2025-09-07-at-15-21-02.png) ### Step 3: Enter New Owner Email A popup window will appear. Enter the email address of the new owner in the **New Owner Email** field. [![Screenshot 2025-09-07 at 15.21.45.png](https://docs.elest.io/uploads/images/gallery/2025-09/scaled-1680-/screenshot-2025-09-07-at-15-21-45.png)](https://docs.elest.io/uploads/images/gallery/2025-09/screenshot-2025-09-07-at-15-21-45.png) ### Step 4: Confirm Your Identity For security, you'll need to: 1. Enter your current account password 2. Enter the verification code sent to your email [![Screenshot 2025-09-07 at 13.32.25.png](https://docs.elest.io/uploads/images/gallery/2025-09/scaled-1680-/71yscreenshot-2025-09-07-at-13-32-25.png)](https://docs.elest.io/uploads/images/gallery/2025-09/71yscreenshot-2025-09-07-at-13-32-25.png) ### [![Screenshot 2025-09-07 at 13.38.04.png](https://docs.elest.io/uploads/images/gallery/2025-09/scaled-1680-/screenshot-2025-09-07-at-13-38-04.png)](https://docs.elest.io/uploads/images/gallery/2025-09/screenshot-2025-09-07-at-13-38-04.png) ### Step 5: New Owner Confirmation The new owner will receive an email notification. They must accept the transfer to complete the process. [![Screenshot 2025-09-07 at 15.13.37.png](https://docs.elest.io/uploads/images/gallery/2025-09/scaled-1680-/screenshot-2025-09-07-at-15-13-37.png)](https://docs.elest.io/uploads/images/gallery/2025-09/screenshot-2025-09-07-at-15-13-37.png) Important Notes --------------- * The transfer is not complete until the new owner accepts it via email * Once transferred, all billing responsibilities move to the new owner * Make sure the new owner has enough credit before initiating the transfer Enter section select mode [Previous\ \ Why did the payment fail when I was attemptin...](https://docs.elest.io/books/frequently-asked-questions/page/why-did-the-payment-fail-when-i-was-attempting-to-add-credits) [Next\ \ How Does Elestio’s Pricing Work?](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) Back to top --- # DB Migrations | docs.elest.io [Skip to main content](https://docs.elest.io/books/db-migrations#main-content) Info Content DB Migrations ============= Need help to migrate to Elestio? Follow the simple steps in the documentation here and get started. [#### Migrate to Elestio managed services\ \ This migration document focuses on the migration of the applications supported by Elestio. Find t...](https://docs.elest.io/books/db-migrations/page/migrate-to-elestio-managed-services) [#### Migrate your customized application to Elestio\ \ This migration document is only for services that are not being supported by Elestio as a fully m...](https://docs.elest.io/books/db-migrations/page/migrate-your-customized-application-to-elestio) [#### Migrate Wordpress to Elestio\ \ This migration document focuses on the migration of the applications supported by Elestio. Find t...](https://docs.elest.io/books/db-migrations/page/migrate-wordpress-to-elestio) [#### Migrate MySQL Database to Elestio\ \ This migration document focuses on the migration of the applications supported by Elestio. Find t...](https://docs.elest.io/books/db-migrations/page/migrate-mysql-database-to-elestio) [#### Migrate Jenkins Pipeline to Elestio\ \ This migration document focuses on the migration of the applications supported by Elestio. Find t...](https://docs.elest.io/books/db-migrations/page/migrate-jenkins-pipeline-to-elestio) [#### Migrate Superset to Elestio\ \ This migration document focuses on the migration of the applications supported by Elestio. Find t...](https://docs.elest.io/books/db-migrations/page/migrate-superset-to-elestio) [#### Migrate Mastodon server to Elestio\ \ This migration document focuses on the migration of the applications supported by Elestio. Find t...](https://docs.elest.io/books/db-migrations/page/migrate-mastodon-server-to-elestio) ### Search Results Clear Search Back to top --- # How to secure your app... | docs.elest.io [Skip to main content](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel#main-content) Info Content How to secure your application with Cloudflare Tunnel ===================================================== What is Cloudflare Tunnel? -------------------------- Cloudflare Tunnel is a secure solution that connects your web applications to Cloudflare's global network without exposing your server's IP address or opening inbound ports. It creates an encrypted tunnel between your origin server and Cloudflare's edge, providing enhanced security and performance for your applications. Why Use Cloudflare Tunnel? -------------------------- ### Key Benefits: * No exposed IP addresses: Your server's IP remains completely hidden * No open inbound ports: Eliminates common attack vectors * Built-in DDoS protection: Leverages Cloudflare's network * End-to-end encryption: Secure communication throughout * Easy setup: No complex firewall configurations needed * Global performance: Benefits from Cloudflare's CDN Getting Started with Cloudflare Tunnel -------------------------------------- ### Prerequisites * A Cloudflare account (free tier is sufficient) * A domain configured in Cloudflare * Access to your server or application host * Basic command-line knowledge Step-by-Step Installation Guide ------------------------------- ### Step 1: Access Zero Trust Dashboard Navigate to your Cloudflare dashboard and click on **Zero Trust** in the sidebar. This is where all tunnel management happens. When installing Cloudflare on your Elestio service, make sure to select **Debian** as the operating system. Next, open your **Elestio Terminal**. Once inside, install Cloudflare and set up the service to run your tunnel by copying and pasting the commands provided by Cloudflare. ![](https://blog.elest.io/content/images/2025/10/image--12--1.png) ![](https://blog.elest.io/content/images/2025/10/image--13-.png) ### Step 2: Navigate to Tunnels Under the **Networks** section, click on **Tunnels**. This is your central hub for creating and managing all your tunnels. Click **"Create a tunnel"** to begin the setup process. You'll be presented with two options: * **Cloudflared (Recommended)**: The standard option for most use cases * **WARP Connector**: For advanced networking scenarios Select **Cloudflared** for this guide. ![](https://blog.elest.io/content/images/2025/10/image--2-.png) Choose a descriptive name for your tunnel. This helps you identify it later, especially if you manage multiple tunnels. ![](https://blog.elest.io/content/images/2025/10/image--3-.png) Click **"Save tunnel"** to proceed. ![](https://blog.elest.io/content/images/2025/10/image--4-.png) ### Step 3: Configure Your Application Route ![](https://blog.elest.io/content/images/2025/10/image--16-.png) Hostname Configuration: * **Subdomain**: Choose your desired subdomain (e.g., "app", "api", "blog") * **Domain**: Select from your Cloudflare-managed domains * **Path**: Optional path prefix for routing #### Service Configuration: You can easily find the correct port by clicking **Update Config** in the **Overview** tab of your service, then checking the **Ports** section to see which port your application is bound to. Click **"Save"** to finalize your configuration. Your tunnel is now active and routing traffic! Cloudflare Tunnel revolutionizes how we expose applications to the internet. By eliminating the need for public IP addresses and open ports, it significantly reduces attack surface while providing enterprise-grade performance and security. Combining Elestio's managed infrastructure with Cloudflare Tunnel gives you professional-grade deployment with minimal complexity - perfect for securing your applications, APIs, and services behind Cloudflare's global network. Enter section select mode [Previous\ \ How to configure NGINX to Listen on IPv6](https://docs.elest.io/books/security/page/how-to-configure-nginx-to-listen-on-ipv6) Back to top --- # David Alimi | docs.elest.io [Skip to main content](https://docs.elest.io/user/david-alimi#main-content) ##### Recent Activity ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) updated page [Netcup](https://docs.elest.io/books/cloud-providers/page/netcup) 1 week ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) created page [Netcup](https://docs.elest.io/books/cloud-providers/page/netcup) 1 week ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) updated page [How to secure your application with Cloudflare Tunnel](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel) 2 months ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) created page [How to secure your application with Cloudflare Tunnel](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel) 2 months ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) updated page [How can project ownership or service billing be transferred to another user's account?](https://docs.elest.io/books/frequently-asked-questions/page/how-can-project-ownership-or-service-billing-be-transferred-to-another-users-account) 3 months ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) updated page [How to configure NGINX to Listen on IPv6](https://docs.elest.io/books/security/page/how-to-configure-nginx-to-listen-on-ipv6) 7 months ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) created page [How to configure NGINX to Listen on IPv6](https://docs.elest.io/books/security/page/how-to-configure-nginx-to-listen-on-ipv6) 7 months ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) created page [Hydra Database Migration to Elestio](https://docs.elest.io/books/databases/page/hydra-database-migration-to-elestio) 1 year ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) updated page [TimescaleDB Database Migration to Elestio](https://docs.elest.io/books/databases/page/timescaledb-database-migration-to-elestio) 1 year ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) created page [TimescaleDB Database Migration to Elestio](https://docs.elest.io/books/databases/page/timescaledb-database-migration-to-elestio) 1 year ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) created page [MongoDB Database Migration to Elestio](https://docs.elest.io/books/databases/page/mongodb-database-migration-to-elestio) 1 year ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) created page [Valkey Database Migration to Elestio](https://docs.elest.io/books/databases/page/valkey-database-migration-to-elestio) 1 year ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) [David Alimi](https://docs.elest.io/user/david-alimi) updated page [KeyDB Database Migration to Elestio](https://docs.elest.io/books/databases/page/keydb-database-migration-to-elestio) 1 year ago ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-120-120/4-avatar.png) #### David Alimi User for 3 years Created Content [22 Pages](https://docs.elest.io/user/david-alimi#recent-pages) [3 Chapters](https://docs.elest.io/user/david-alimi#recent-chapters) [2 Books](https://docs.elest.io/user/david-alimi#recent-books) [0 Shelves](https://docs.elest.io/user/david-alimi#recent-shelves) Recently Created Pages [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Adavid-alimi%7D+%7Btype%3Apage%7D) ---------------------------------------------------------------------------------------------------------------------- [#### Netcup\ \ Netcup is a well-established German hosting provider known for their high-performance virtual ser...](https://docs.elest.io/books/cloud-providers/page/netcup) [#### How to secure your application with Cloudflare Tunnel\ \ What is Cloudflare Tunnel? Cloudflare Tunnel is a secure solution that connects your web appli...](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel) [#### How to configure NGINX to Listen on IPv6\ \ IPv6 is quickly becoming standard. If your VM already supports it, you just need to tell NGINX to...](https://docs.elest.io/books/security/page/how-to-configure-nginx-to-listen-on-ipv6) [#### Hydra Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/hydra-database-migration-to-elestio) [#### TimescaleDB Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/timescaledb-database-migration-to-elestio) Recently Created Chapters [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Adavid-alimi%7D+%7Btype%3Achapter%7D) ---------------------------------------------------------------------------------------------------------------------------- [#### DB Migration service](https://docs.elest.io/books/databases/chapter/db-migration-service) [#### Tools](https://docs.elest.io/books/services-dashboard/chapter/tools) [#### Overview](https://docs.elest.io/books/services-dashboard/chapter/overview) Recently Created Books [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Adavid-alimi%7D+%7Btype%3Abook%7D) ---------------------------------------------------------------------------------------------------------------------- [#### Services Dashboard](https://docs.elest.io/books/services-dashboard) [#### Getting started](https://docs.elest.io/books/getting-started) Recently Created Shelves ------------------------ David Alimi has not created any shelves Back to top --- # Elestio API | docs.elest.io [Skip to main content](https://docs.elest.io/books/elestio-api#main-content) Info Content Elestio API =========== [#### API Documentation\ \ Elestio is an API first company, everything we do is through API's. Everything we do on our dashb...](https://docs.elest.io/books/elestio-api/page/api-documentation) ### Search Results Clear Search Back to top --- # Amit | docs.elest.io [Skip to main content](https://docs.elest.io/user/amit#main-content) ##### Recent Activity ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [Upgrade support plan](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan) 1 month ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [Introduction](https://docs.elest.io/books/databases/page/introduction) 1 month ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [BYOVM with AWS EC2 (Beta AWS UI)](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui) 2 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [How Does Elestio’s Pricing Work?](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) 2 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [BYOVM (Bring Your Own VM)](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm) 2 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [How Does Elestio’s Pricing Work?](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) 2 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) created page [How Does Elestio’s Pricing Work?](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) 2 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [BYOVM (Bring Your Own VM)](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm) 2 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [Free trial](https://docs.elest.io/books/billing/page/free-trial) 5 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [Elestio Free Trial Policy & Fair Use Statement](https://docs.elest.io/books/billing/page/elestio-free-trial-policy-fair-use-statement) 5 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [Free trial](https://docs.elest.io/books/billing/page/free-trial) 5 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [Elestio Free Trial Policy & Fair Use Statement](https://docs.elest.io/books/billing/page/elestio-free-trial-policy-fair-use-statement) 5 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) created page [Elestio Free Trial Policy & Fair Use Statement](https://docs.elest.io/books/billing/page/elestio-free-trial-policy-fair-use-statement) 5 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) [Amit](https://docs.elest.io/user/amit) updated page [Bandwidth Billing](https://docs.elest.io/books/billing/page/bandwidth-billing) 6 months ago ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-120-120/70rvyvrpfb-avatar.png) #### Amit User for 3 years Created Content [44 Pages](https://docs.elest.io/user/amit#recent-pages) [0 Chapters](https://docs.elest.io/user/amit#recent-chapters) [3 Books](https://docs.elest.io/user/amit#recent-books) [0 Shelves](https://docs.elest.io/user/amit#recent-shelves) Recently Created Pages [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Aamit%7D+%7Btype%3Apage%7D) --------------------------------------------------------------------------------------------------------------- [#### How Does Elestio’s Pricing Work?\ \ Elestio offers a flexible cloud hosting platform that allows you to deploy and manage application...](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) [#### Elestio Free Trial Policy & Fair Use Statement\ \ At Elestio, we’re committed to empowering users by providing a fast, reliable and flexible platfo...](https://docs.elest.io/books/billing/page/elestio-free-trial-policy-fair-use-statement) [#### Bandwidth Billing\ \ At Elestio, we're committed to transparency and simplicity when it comes to billing. One area whe...](https://docs.elest.io/books/billing/page/bandwidth-billing) [#### How to Enable or Disable IPv6 on a Linux Virtual Machine\ \ IPv6 is the latest version of the Internet Protocol, designed to address the limitations of IPv4....](https://docs.elest.io/books/security/page/how-to-enable-or-disable-ipv6-on-a-linux-virtual-machine) [#### SEPA Direct Debit Payment Option on Elestio\ \ At Elestio, we aim to make payment processing as convenient and accessible as possible for our cu...](https://docs.elest.io/books/billing/page/sepa-direct-debit-payment-option-on-elestio) Recently Created Chapters ------------------------- Amit has not created any chapters Recently Created Books [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Aamit%7D+%7Btype%3Abook%7D) --------------------------------------------------------------------------------------------------------------- [#### Domains\ \ Domains](https://docs.elest.io/books/domains) [#### Frequently Asked Questions\ \ Here are some most commonly asked questions](https://docs.elest.io/books/frequently-asked-questions) [#### Volumes\ \ Elestio has the top 6 cloud partners in 110 locations across 29 countries (AWS Lightsail, Digital...](https://docs.elest.io/books/volumes) Recently Created Shelves ------------------------ Amit has not created any shelves Back to top --- # Joseph Benguira | docs.elest.io [Skip to main content](https://docs.elest.io/user/joseph-benguira#main-content) ##### Recent Activity ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated page [Elestio Data Processing Agreement](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement) 1 month ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated page [Overview](https://docs.elest.io/books/keycloak/page/overview-VG3) 2 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated page [Privacy policies](https://docs.elest.io/books/legal-compliance/page/privacy-policies) 4 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated page [Overview](https://docs.elest.io/books/cicd-pipelines/page/overview) 7 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated page [Subcontractors](https://docs.elest.io/books/legal-compliance/page/subcontractors) 8 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated page [Can I migrate/clone my service to another cloud or region?](https://docs.elest.io/books/frequently-asked-questions/page/can-i-migrateclone-my-service-to-another-cloud-or-region) 8 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated page [Nginx advanced configuration](https://docs.elest.io/books/security/page/nginx-advanced-configuration) 9 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) created page [Nginx advanced configuration](https://docs.elest.io/books/security/page/nginx-advanced-configuration) 9 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) [Joseph Benguira](https://docs.elest.io/user/joseph-benguira) updated shelf [Getting Started](https://docs.elest.io/shelves/getting-started) 9 months ago ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-120-120/moi.jpg) #### Joseph Benguira User for 3 years Created Content [72 Pages](https://docs.elest.io/user/joseph-benguira#recent-pages) [3 Chapters](https://docs.elest.io/user/joseph-benguira#recent-chapters) [11 Books](https://docs.elest.io/user/joseph-benguira#recent-books) [3 Shelves](https://docs.elest.io/user/joseph-benguira#recent-shelves) Recently Created Pages [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Ajoseph-benguira%7D+%7Btype%3Apage%7D) -------------------------------------------------------------------------------------------------------------------------- [#### Nginx advanced configuration\ \ Edit the website nginx configuration From the service overview screen it's possible to edit the ...](https://docs.elest.io/books/security/page/nginx-advanced-configuration) [#### Deploy a new cluster\ \ How to deploy a new cluster 1) Go to the Elestio Clusters tab. 2) Click on Deploy My First Cl...](https://docs.elest.io/books/databases/page/deploy-a-new-cluster) [#### Can I use OUTFILE in Managed MySQL?\ \ Yes it's possible on Elestio. Since we are running MySQL inside a docker container you will have ...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-use-outfile-in-managed-mysql) [#### Elestio Data Processing Agreement\ \ Last Modified: Feb 06, 2025 1. Background This Data Processing Agreement (‘’DPA’’) is attached ...](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement) [#### Free trial\ \ Elestio offers a 3-day free trial with $20 in credits, during which you can launch up to 2 servic...](https://docs.elest.io/books/billing/page/free-trial) Recently Created Chapters [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Ajoseph-benguira%7D+%7Btype%3Achapter%7D) -------------------------------------------------------------------------------------------------------------------------------- [#### DB Clusters](https://docs.elest.io/books/databases/chapter/db-clusters) [#### Teams](https://docs.elest.io/books/projects-teams/chapter/teams) [#### Projects](https://docs.elest.io/books/projects-teams/chapter/projects) Recently Created Books [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Ajoseph-benguira%7D+%7Btype%3Abook%7D) -------------------------------------------------------------------------------------------------------------------------- [#### CI/CD Pipelines\ \ Go from source code to production with CI/CD Pipelines. We support Github, Gitlab & docker regist...](https://docs.elest.io/books/cicd-pipelines) [#### Elestio API](https://docs.elest.io/books/elestio-api) [#### Load balancers](https://docs.elest.io/books/load-balancers) [#### Databases\ \ We currently support cluster mode for MySQL & KeyDB (Redis compatible). We are working hard on ad...](https://docs.elest.io/books/databases) [#### Legal & Compliance](https://docs.elest.io/books/legal-compliance) Recently Created Shelves [View All](https://docs.elest.io/search?term=%7Bcreated_by%3Ajoseph-benguira%7D+%7Btype%3Abookshelf%7D) --------------------------------------------------------------------------------------------------------------------------------- [#### Legal & Billing](https://docs.elest.io/shelves/legal-billing) [#### How it works](https://docs.elest.io/shelves/how-it-works) [#### Getting Started\ \ https://www.youtube.com/watch?v=zWyM6m3cWxE](https://docs.elest.io/shelves/getting-started) Back to top --- # Cloud Providers | docs.elest.io [Skip to main content](https://docs.elest.io/books/cloud-providers#main-content) Info Content Cloud Providers =============== [#### Hetzner\ \ Hetzner is an award-winning provider, born and based in Germany. They are one of our favorite pro...](https://docs.elest.io/books/cloud-providers/page/hetzner) [#### Netcup\ \ Netcup is a well-established German hosting provider known for their high-performance virtual ser...](https://docs.elest.io/books/cloud-providers/page/netcup) [#### Digital Ocean\ \ Digital Ocean is a great cloud provider with a large number of regions and datacenters available....](https://docs.elest.io/books/cloud-providers/page/digital-ocean) [#### AWS Lightsail\ \ AWS is the largest cloud provider with one of the best network available and a large number of re...](https://docs.elest.io/books/cloud-providers/page/aws-lightsail) [#### Vultr\ \ VULTR is a great cloud provider with a large number of regions and datacenters available. They pr...](https://docs.elest.io/books/cloud-providers/page/vultr) [#### Linode\ \ Linode is a great cloud provider with a large number of regions and datacenters available. They p...](https://docs.elest.io/books/cloud-providers/page/linode) [#### BYOVM (Bring Your Own VM)\ \ You can also deploy into your own cloud account from any cloud provider (Azure, GCP, Alibaba, Ora...](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm) [#### BYOVM with AWS EC2\ \ You can deploy an Elestio service on your own AWS account with BYOVM To do it, you will need...](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2) [#### BYOVM with AWS EC2 (Beta AWS UI)\ \ This approach is outdated. Instead, you can use our Bring Your Own AWS Account(BYO-AWS) provide...](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui) [#### AWS EC2 or (BYOAWS) Bring Your Own AWS Account\ \ AWS is the largest cloud provider with one of the best networks available and a large number of r...](https://docs.elest.io/books/cloud-providers/page/aws-ec2-or-byoaws-bring-your-own-aws-account) ### Search Results Clear Search Back to top --- # Recently Updated Pages | docs.elest.io [Skip to main content](https://docs.elest.io/pages/recently-updated#main-content) Recently Updated Pages ====================== [#### Netcup\ \ Cloud Providers\ \ Netcup is a well-established German hosting provider known for their high-performance virtual ser...\ \ Updated 1 week ago by David Alimi](https://docs.elest.io/books/cloud-providers/page/netcup) [#### Elestio Data Processing Agreement\ \ Legal & Compliance\ \ Last Modified: Feb 06, 2025 1. Background This Data Processing Agreement (‘’DPA’’) is attached ...\ \ Updated 1 month ago by Joseph Benguira](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement) [#### Upgrade support plan\ \ Services Dashboard Overview\ \ From the service overview, click on "Upgrade plan" on the support plan row to change your support...\ \ Updated 1 month ago by Amit](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan) [#### Introduction\ \ Databases DB Clusters\ \ Clustered databases are essential for ensuring high availability, scalability, and fault toleranc...\ \ Updated 1 month ago by Amit](https://docs.elest.io/books/databases/page/introduction) [#### BYOVM with AWS EC2 (Beta AWS UI)\ \ Cloud Providers\ \ This approach is outdated. Instead, you can use our Bring Your Own AWS Account(BYO-AWS) provide...\ \ Updated 2 months ago by Amit](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui) [#### Overview\ \ Keycloak Cluster Management\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...\ \ Updated 2 months ago by Joseph Benguira](https://docs.elest.io/books/keycloak/page/overview-VG3) [#### How Does Elestio’s Pricing Work?\ \ Frequently Asked Questions\ \ Elestio offers a flexible cloud hosting platform that allows you to deploy and manage application...\ \ Updated 2 months ago by Amit](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) [#### How to secure your application with Cloudflare Tunnel\ \ Security\ \ What is Cloudflare Tunnel? Cloudflare Tunnel is a secure solution that connects your web appli...\ \ Updated 2 months ago by David Alimi](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel) [#### BYOVM (Bring Your Own VM)\ \ Cloud Providers\ \ You can also deploy into your own cloud account from any cloud provider (Azure, GCP, Alibaba, Ora...\ \ Updated 2 months ago by Amit](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm) [#### How can project ownership or service billing be transferred to another user's account?\ \ Frequently Asked Questions\ \ This guide explains how to transfer a project ownership from one Elestio account to another. Pre...\ \ Updated 3 months ago by David Alimi](https://docs.elest.io/books/frequently-asked-questions/page/how-can-project-ownership-or-service-billing-be-transferred-to-another-users-account) [#### Privacy policies\ \ Legal & Compliance\ \ Elestio (“Elestio” / “We”) is aware that users of Elest.io and its related applications (“Users” ...\ \ Updated 4 months ago by Joseph Benguira](https://docs.elest.io/books/legal-compliance/page/privacy-policies) [#### Free trial\ \ Billing\ \ Elestio offers a 3-day free trial with $20 in credits, during which you can launch up to 2 servic...\ \ Updated 5 months ago by Amit](https://docs.elest.io/books/billing/page/free-trial) [#### Elestio Free Trial Policy & Fair Use Statement\ \ Billing\ \ At Elestio, we’re committed to empowering users by providing a fast, reliable and flexible platfo...\ \ Updated 5 months ago by Amit](https://docs.elest.io/books/billing/page/elestio-free-trial-policy-fair-use-statement) [#### Connecting with keydb-cli\ \ Valkey How to Connect\ \ This guide explains how to establish a connection between valkey-cli and a Valkey database instan...\ \ Updated 5 months ago by kaiwalya](https://docs.elest.io/books/valkey/page/connecting-with-keydb-cli) [#### Connecting with RedisInsight\ \ Valkey How to Connect\ \ This guide explains how to establish a connection between RedisInsight and a Valkey database inst...\ \ Updated 5 months ago by kaiwalya](https://docs.elest.io/books/valkey/page/connecting-with-redisinsight) [#### Connecting with Java\ \ Valkey How to Connect\ \ This guide explains how to establish a connection between a Java application and a Valkey databas...\ \ Updated 5 months ago by kaiwalya](https://docs.elest.io/books/valkey/page/connecting-with-java) [#### Connecting with Go\ \ Valkey How to Connect\ \ This guide explains how to establish a connection between a Go application and a Valkey database ...\ \ Updated 5 months ago by kaiwalya](https://docs.elest.io/books/valkey/page/connecting-with-go) [#### Connecting with PHP\ \ Valkey How to Connect\ \ This guide explains how to establish a connection between a PHP application and a Valkey database...\ \ Updated 5 months ago by kaiwalya](https://docs.elest.io/books/valkey/page/connecting-with-php) [#### Connecting with Python\ \ Valkey How to Connect\ \ This guide explains how to connect a Python application to a Valkey database using the redis libr...\ \ Updated 5 months ago by kaiwalya](https://docs.elest.io/books/valkey/page/connecting-with-python) [#### Connecting with Node.js\ \ Valkey How to Connect\ \ This guide explains how to establish a connection between a Node.js application and a Valkey data...\ \ Updated 5 months ago by kaiwalya](https://docs.elest.io/books/valkey/page/connecting-with-nodejs) Back to top --- # Upgrade support plan | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan#main-content) Info Content Upgrade support plan ==================== From the service overview, click on "Upgrade plan" on the support plan row to change your support plan: [![Screenshot 2022-09-29 145653.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-29-145653.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1641922430484.png) There you can switch to any other support plan [![Screenshot 2025-11-05 175134.png](https://docs.elest.io/uploads/images/gallery/2025-11/screenshot-2025-11-05-175134.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1641922399252.png) While it's possible to change support plans, it's important to note this is only possible once every 30 days. Support plans are billed per hour like all our other services. Enter section select mode [Previous\ \ Upgrade service plan](https://docs.elest.io/books/services-dashboard/page/upgrade-service-plan) [Next\ \ Delete a service](https://docs.elest.io/books/services-dashboard/page/delete-a-service) Back to top --- # Legal & Compliance | docs.elest.io [Skip to main content](https://docs.elest.io/books/legal-compliance#main-content) Info Content Legal & Compliance ================== [#### Terms & Conditions\ \ Elest.io is a website owned by ELESTIO LIMITED, a company based in Ireland with its registered of...](https://docs.elest.io/books/legal-compliance/page/terms-conditions) [#### Privacy policies\ \ Elestio (“Elestio” / “We”) is aware that users of Elest.io and its related applications (“Users” ...](https://docs.elest.io/books/legal-compliance/page/privacy-policies) [#### Subcontractors\ \ Subcontractors & Sub-processors A sub-processor is a third-party data processor engaged by Elest...](https://docs.elest.io/books/legal-compliance/page/subcontractors) [#### Elestio Data Processing Agreement\ \ Last Modified: Feb 06, 2025 1. Background This Data Processing Agreement (‘’DPA’’) is attached ...](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement) ### Search Results Clear Search Back to top --- # Keycloak | docs.elest.io [Skip to main content](https://docs.elest.io/books/keycloak#main-content) Info Content Keycloak ======== [#### Overview\ \ Keycloak is an open-source identity and access management (IAM) solution aimed at modern applicat...](https://docs.elest.io/books/keycloak/page/overview) [#### How to Connect](https://docs.elest.io/books/keycloak/chapter/how-to-connect) 8 Pages [#### Connecting with Node.js\ \ This guide explains how to establish a secure connection between a Node.js application and a Keyc...](https://docs.elest.io/books/keycloak/page/connecting-with-nodejs) [#### Connecting with Python\ \ This guide explains how to establish a connection between a Python Flask application and a Keyclo...](https://docs.elest.io/books/keycloak/page/connecting-with-python) [#### Connecting with PHP\ \ This guide explains how to establish a connection between a PHP application and a Keycloak identi...](https://docs.elest.io/books/keycloak/page/connecting-with-php) [#### Connecting with Go\ \ This guide explains how to establish a connection between a Go application and a Keycloak identit...](https://docs.elest.io/books/keycloak/page/connecting-with-go) [#### Connecting with Java\ \ This guide explains how to establish a connection between a Java Spring Boot application and a Ke...](https://docs.elest.io/books/keycloak/page/connecting-with-java) [#### Connecting with Frontend Applications\ \ This guide explains how to establish a connection between a frontend single-page application (SPA...](https://docs.elest.io/books/keycloak/page/connecting-with-frontend-applications) [#### Connecting with Keycloak Admin Rest API\ \ This guide explains how to authenticate with and use the Keycloak Admin REST API from a backend a...](https://docs.elest.io/books/keycloak/page/connecting-with-keycloak-admin-rest-api) [#### Connecting External Identity Providers\ \ This guide explains how to integrate external identity providers (IdPs) like Google, GitHub, Face...](https://docs.elest.io/books/keycloak/page/connecting-external-identity-providers) [#### How-To Guides](https://docs.elest.io/books/keycloak/chapter/how-to-guides) 7 Pages [#### Creating a Realm in Keycloak\ \ A realm in Keycloak is the top-level container for managing users, roles, groups, identity provid...](https://docs.elest.io/books/keycloak/page/creating-a-realm-in-keycloak) [#### Adding and Managing Users in Keycloak\ \ Users in Keycloak represent the individuals or system accounts that authenticate and interact wit...](https://docs.elest.io/books/keycloak/page/adding-and-managing-users-in-keycloak) [#### Creating and Configuring Clients in Keycloak\ \ A client in Keycloak represents an application or service that uses Keycloak to authenticate user...](https://docs.elest.io/books/keycloak/page/creating-and-configuring-clients-in-keycloak) [#### Setting Up Roles and Permissions in Keycloak\ \ Roles and permissions in Keycloak define what users and applications are allowed to do. Roles can...](https://docs.elest.io/books/keycloak/page/setting-up-roles-and-permissions-in-keycloak) [#### Enabling Identity Federation in Keycloak\ \ Identity federation allows you to delegate authentication to external identity providers (IdPs) l...](https://docs.elest.io/books/keycloak/page/enabling-identity-federation-in-keycloak) [#### Enabling Two-Factor Authentication (2FA) in Keycloak\ \ Two-Factor Authentication (2FA) adds an extra layer of security to user logins by requiring somet...](https://docs.elest.io/books/keycloak/page/enabling-two-factor-authentication-2fa-in-keycloak) [#### Resetting User Passwords in KeycloakNew Page\ \ Password resets are a critical part of account lifecycle management. Keycloak provides multiple s...](https://docs.elest.io/books/keycloak/page/resetting-user-passwords-in-keycloaknew-page) [#### Realm & Configuration Migration](https://docs.elest.io/books/keycloak/chapter/realm-configuration-migration) 3 Pages [#### Exporting and Importing Realms\ \ Elestio enables seamless migration of Keycloak realms by supporting realm exports and imports. Th...](https://docs.elest.io/books/keycloak/page/exporting-and-importing-realms) [#### Migrating from Another IAM Provider to Keycloak\ \ Migrating to Keycloak from other IAM platforms such as Auth0, Okta, Firebase Auth, or custom-buil...](https://docs.elest.io/books/keycloak/page/migrating-from-another-iam-provider-to-keycloak) [#### Cloning a Realm to a New Cluster or Region\ \ In scenarios where high availability, regional redundancy, or environment separation (e.g., stagi...](https://docs.elest.io/books/keycloak/page/cloning-a-realm-to-a-new-cluster-or-region) [#### Cluster Management](https://docs.elest.io/books/keycloak/chapter/cluster-management) 10 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/keycloak/page/overview-VG3) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/keycloak/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/keycloak/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/keycloak/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/keycloak/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/keycloak/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/keycloak/page/backups-and-restores) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/keycloak/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/keycloak/page/cluster-resynchronization) [#### Deleting a Cluster\ \ When a cluster is no longer needed—whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/keycloak/page/deleting-a-cluster) ### Search Results Clear Search Back to top --- # Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/keycloak/page/overview-VG3#main-content) Info Content Overview ======== Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the system fails. Elestio supports different cluster setups to handle various technical needs like load balancing, failover, and data replication. #### **Supported Software for Clustering:** Elestio supports clustering for a wide range of open-source software. Each is designed to support different use cases like databases, caching, and analytics: * **MySQL**: Supports Single Node, Primary/Replica, and Multi-Master cluster types. These allow users to create simple setups or more advanced ones where reads and writes are distributed across nodes. In a Primary/Replica setup, replicas are updated continuously through replication. These configurations are useful for high-traffic applications that need fast and reliable access to data. * **PostgreSQL**: PostgreSQL clusters can be configured for read scalability and failover protection. Replication ensures that data written to the primary node is copied to replicas. Clustering PostgreSQL also improves query throughput by offloading read queries to replicas. Elestio handles replication setup and node failover automatically. * **Redis/KeyDB/Valkey**: These in-memory data stores support clustering to improve speed and fault tolerance. Clustering divides data across multiple nodes (sharding), allowing horizontal scaling. These tools are commonly used for caching and real-time applications, so fast failover and data availability are critical. * **Hydra and TimescaleDB**: These support distributed and time-series workloads, respectively. Clustering helps manage large datasets spread across many nodes. TimescaleDB, built on PostgreSQL, benefits from clustering by distributing time-based data for fast querying. Hydra uses clustering to process identity and access management workloads more efficiently in high-load environments. * **Keycloak:** Keycloak clustering allows you to scale identity and access management services horizontally. In a clustered setup, Keycloak nodes share session and login state using a distributed cache (e.g., Infinispan), ensuring high availability and session failover. This is especially important for applications that depend on SSO, OAuth2, and federated login across microservices. Elestio’s managed Keycloak clusters handle the complexity of configuration, secure communication between nodes, and high availability out of the box. * **Clickhouse** * **Opensearch** * **Vaultwarden** * **RKE2** * **N8N** * **RabbitMQ** * **VAULT** ![image.png](https://docs.elest.io/uploads/images/gallery/2025-10/scaled-1680-/image.png) **Note**: Elestio is frequently adding support for more clustered software like OpenSearch, Kafka, and ClickHouse. Always check the Elestio catalogue for the latest supported services. #### **Cluster Configurations:** Elestio offers several clustering modes, each designed for a different balance between simplicity, speed, and reliability: * **Single Node**: This setup has only one node and is easy to manage. It acts as a standalone Primary node. It’s good for testing, development, or low-traffic applications. Later, you can scale to more nodes without rebuilding the entire setup. Elestio lets you expand this node into a full cluster with just a few clicks. * **Primary/Replica**: One node (Primary) handles all write operations, and one or more Replicas handle read queries. Replication is usually asynchronous and ensures data is copied to all replicas. This improves read performance and provides redundancy if the primary node fails. Elestio manages automatic data syncing and failover setup. #### **Cluster Management Features:** Elestio’s cluster dashboard includes tools for managing, monitoring, and securing your clusters. These help ensure stability and ease of use: * **Node Management**: You can scale your cluster by adding or removing nodes as your app grows. Adding a node increases capacity; removing one helps reduce costs. Elestio handles provisioning and configuring nodes automatically, including replication setup. This makes it easier to scale horizontally without downtime. * **Backups and Restores**: Elestio provides scheduled and on-demand backups for all nodes. Backups are stored securely and can be restored if something goes wrong. You can also create a snapshot before major changes to your system. This helps protect against data loss due to failures, bugs, or human error. * **Access Control**: You can limit access to your cluster using IP allowlists, ensuring only trusted sources can connect. Role-based access control (RBAC) can be applied for managing different user permissions. SSH and database passwords are generated securely and can be rotated easily from the dashboard. These access tools help reduce the risk of unauthorized access. * **Monitoring and Alerts**: Real-time metrics like CPU, memory, disk usage, and network traffic are available through the dashboard. You can also check logs for troubleshooting and set alerts for high resource usage or failure events. Elestio uses built-in observability tools to monitor the health of your cluster and notify you if something needs attention. This allows you to catch problems early and take action. Enter section select mode [Previous\ \ Cluster Management](https://docs.elest.io/books/keycloak/chapter/cluster-management) [Next\ \ Deploying a New Cluster](https://docs.elest.io/books/keycloak/page/deploying-a-new-cluster) Back to top --- # Frequently Asked Quest... | docs.elest.io [Skip to main content](https://docs.elest.io/books/frequently-asked-questions#main-content) Info Content Frequently Asked Questions ========================== Here are some most commonly asked questions [#### Why am I receiving a low credit warning even though auto recharge is enabled?\ \ Users who have credits remaining for less than 7 days receive a low credit warning email once per...](https://docs.elest.io/books/frequently-asked-questions/page/why-am-i-receiving-a-low-credit-warning-even-though-auto-recharge-is-enabled) [#### Can I install more than one software on the same VM?\ \ Our dedicated services are running in complete isolation, so one service equals one VM. Using our...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-install-more-than-one-software-on-the-same-vm) [#### Can I migrate/clone my service to another cloud or region?\ \ Yes, you can migrate or clone a running service to any other target cloud or region by simply cli...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-migrateclone-my-service-to-another-cloud-or-region) [#### Is it possible to restrict access to my virtual machine (with a firewall)?\ \ Yes, every service has a pre-configured firewall that allows access to the internet through ports...](https://docs.elest.io/books/frequently-asked-questions/page/is-it-possible-to-restrict-access-to-my-virtual-machine-with-a-firewall) [#### What type of support does Elestio offer?\ \ Email and community support via our forum is available to everyone with our Test plan, with no SL...](https://docs.elest.io/books/frequently-asked-questions/page/what-type-of-support-does-elestio-offer) [#### Can my software services communicate between different cloud providers safely?\ \ Every Elestio project establishes a unique and secure encrypted virtual network, allowing service...](https://docs.elest.io/books/frequently-asked-questions/page/can-my-software-services-communicate-between-different-cloud-providers-safely) [#### Can I deploy Elestio services on-premise or on my existing cloud infrastructure?\ \ Yes, you can connect any on-premises or cloud VM managed services dashboard with our "Bring Your ...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-deploy-elestio-services-on-premise-or-on-my-existing-cloud-infrastructure) [#### I'm trying to add AWS keys to Elestio but getting an error "You are not authorized to perform this operation" in BYOAWS\ \ This error will appear when adding AWS Access and Secret Credentials keys if your keys do not hav...](https://docs.elest.io/books/frequently-asked-questions/page/im-trying-to-add-aws-keys-to-elestio-but-getting-an-error-you-are-not-authorized-to-perform-this-operation-in-byoaws) [#### Can I use OUTFILE in Managed MySQL?\ \ Yes it's possible on Elestio. Since we are running MySQL inside a docker container you will have ...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-use-outfile-in-managed-mysql) [#### How can I automatically remove system log files in order to free up disk space?\ \ By default, new instances are automatically configured to delete log files on a daily basis. How...](https://docs.elest.io/books/frequently-asked-questions/page/how-can-i-automatically-remove-system-log-files-in-order-to-free-up-disk-space) [#### How to resolve the Borg acquire lock in remote backups.\ \ If you see the following error when listing, restoring, or taking manual backups for your Borg re...](https://docs.elest.io/books/frequently-asked-questions/page/how-to-resolve-the-borg-acquire-lock-in-remote-backups) [#### How to resolve the Borg cache error in remote backups.\ \ If you see the following error related to the Borg cache when listing, restoring, or taking manua...](https://docs.elest.io/books/frequently-asked-questions/page/how-to-resolve-the-borg-cache-error-in-remote-backups) [#### I added fund to my elestio account, but my service is still not running\ \ If your service was suspended due to lack of credits and now it is still inactive even after ad...](https://docs.elest.io/books/frequently-asked-questions/page/i-added-fund-to-my-elestio-account-but-my-service-is-still-not-running) [#### Elestio Domain shows SSL expired or Deceptive Site ahead\ \ Current Status: Resolved @ 2023-11-04, 07:11 Resolution: Google unflagged our domain in less tha...](https://docs.elest.io/books/frequently-asked-questions/page/elestio-domain-shows-ssl-expired-or-deceptive-site-ahead) [#### How are operating system(OS) upgrades managed?\ \ Automatic Minor OS Updates: Minor operating system updates are automatically performed eve...](https://docs.elest.io/books/frequently-asked-questions/page/how-are-operating-systemos-upgrades-managed) [#### Why did the payment fail when I was attempting to add credits?\ \ Encountering difficulties with payment failures while attempting to add credits? Fear not, as we'...](https://docs.elest.io/books/frequently-asked-questions/page/why-did-the-payment-fail-when-i-was-attempting-to-add-credits) [#### How can project ownership or service billing be transferred to another user's account?\ \ This guide explains how to transfer a project ownership from one Elestio account to another. Pre...](https://docs.elest.io/books/frequently-asked-questions/page/how-can-project-ownership-or-service-billing-be-transferred-to-another-users-account) [#### How Does Elestio’s Pricing Work?\ \ Elestio offers a flexible cloud hosting platform that allows you to deploy and manage application...](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) ### Search Results Clear Search Back to top --- # Elestio Terraform prov... | docs.elest.io [Skip to main content](https://docs.elest.io/books/elestio-terraform-provider#main-content) Info Content Elestio Terraform provider ========================== The Elestio Terraform provider is a plugin that enables users to manage resources on the Elestio platform using Terraform. Terraform is a tool that allows users to define and manage infrastructure as code, enabling them to automate the process of creating, updating, and deleting resources such as virtual machines, networks, and containers. It is open-source and developed by HashiCorp. [#### Documentation\ \ With Elestio’s Terraform provider, you can use an open-source infrastructure as code software too...](https://docs.elest.io/books/elestio-terraform-provider/page/documentation) [#### Get started\ \ Build your first Elestio Terraform project This exemple shows the setup for a Terraform projec...](https://docs.elest.io/books/elestio-terraform-provider/page/get-started) [#### Providers, datacenters and server types\ \ This guide explain how to find available options for provider\_name, datacenter and server\_type ...](https://docs.elest.io/books/elestio-terraform-provider/page/providers-datacenters-and-server-types) [#### Import an existing resource\ \ You can use the terraform import command to import in the Elestio state an existing project or se...](https://docs.elest.io/books/elestio-terraform-provider/page/import-an-existing-resource) ### Search Results Clear Search Back to top --- # Introduction | docs.elest.io [Skip to main content](https://docs.elest.io/books/databases/page/introduction#main-content) Info Content Introduction ============ Clustered databases are essential for ensuring **high availability**, **scalability**, and **fault tolerance** in modern systems. By distributing data across multiple nodes, they can handle larger workloads, prevent single points of failure, and ensure that services remain accessible even during hardware or network issues. Clusters are critical for businesses that need reliable, fast, and scalable database solutions to support growing demands. [![Screenshot 2025-11-05 174427.png](https://docs.elest.io/uploads/images/gallery/2025-11/screenshot-2025-11-05-174427.png)](https://docs.elest.io/uploads/images/gallery/2025-01/FYp001.png) **Supported Software** Elestio supports clustering for a wide range of software, making it adaptable to various use cases: * **MySQL** * **PostgreSQL** * **Hydra** * **TimescaleDB** * **Redis** * **KeyDB** * **Valkey** * **ClickHouse** * **OpenSearch** * **Vaultwarden** * **Keycloak** * **rke2** * **N8N** * **RabbitMQ** * **Vault** More DB clusters will be added soon; Enter section select mode [Previous\ \ DB Clusters](https://docs.elest.io/books/databases/chapter/db-clusters) [Next\ \ Deploy a new cluster](https://docs.elest.io/books/databases/page/deploy-a-new-cluster) Back to top --- # Backups | docs.elest.io [Skip to main content](https://docs.elest.io/books/backups#main-content) Info Content Backups ======= [#### Overview\ \ A robust backup strategy is fundamental to keeping data safe. By default, Elest.io automates a 3...](https://docs.elest.io/books/backups/page/overview) [#### Manual Local backups\ \ Local backups are useful if you need to take a quick backup of a small dataset locally and want t...](https://docs.elest.io/books/backups/page/manual-local-backups) [#### Automated Remote Backups (Borg)\ \ Remote backups are sent to another datacenter in the same continent that your service (Ashburn US...](https://docs.elest.io/books/backups/page/automated-remote-backups-borg) [#### Automated VM Snapshots\ \ VM snapshots are made using the provider's snapshot API and are stored in the same region where y...](https://docs.elest.io/books/backups/page/automated-vm-snapshots) [#### Automated External Backups (S3)\ \ External backups are stored in your S3 bucket, so you own your backups directly. Elestio's extern...](https://docs.elest.io/books/backups/page/automated-external-backups-s3) [#### How to Create AWS Access and Secret Key for External backups (S3)\ \ To create your AWS Access and Secret Key, follow these steps. Step 1:- Use your AWS account ID...](https://docs.elest.io/books/backups/page/how-to-create-aws-access-and-secret-key-for-external-backups-s3) [#### How to Create Bucket in AWS for External backups (S3)\ \ To create your bucket for backups, follow these steps. Step 1:- Use your AWS account ID or acc...](https://docs.elest.io/books/backups/page/how-to-create-bucket-in-aws-for-external-backups-s3) ### Search Results Clear Search Back to top --- # docs.elest.io [Skip to main content](https://docs.elest.io/?page=2#main-content) Info Content Books ===== Sort Name * [Name](https://docs.elest.io/?page=2#) * [Created Date](https://docs.elest.io/?page=2#) * [Updated Date](https://docs.elest.io/?page=2#) [MySQL\ -----\ \ Created 8 months ago\ \ Updated 8 months ago](https://docs.elest.io/books/mysql) [PostgreSQL\ ----------\ \ Created 9 months ago\ \ Updated 9 months ago](https://docs.elest.io/books/postgresql) [Projects & Teams\ ----------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/projects-teams) [Redis\ -----\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/redis) [Security\ --------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/security) [Services Dashboard\ ------------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/services-dashboard) [Supported Softwares\ -------------------\ \ Our catalog is comprised of over 350+ open source software services. We plan to continue adding to our catalog each month, so k...\ \ Created 3 years ago\ \ Updated 1 year ago](https://docs.elest.io/books/supported-softwares) [TimescaleDB\ -----------\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/timescaledb) [Valkey\ ------\ \ Created 5 months ago\ \ Updated 5 months ago](https://docs.elest.io/books/valkey) [Volumes\ -------\ \ Elestio has the top 6 cloud partners in 110 locations across 29 countries (AWS Lightsail, Digital Ocean, Scaleway, Vultr, Linod...\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/volumes) Back to top --- # Load balancers | docs.elest.io [Skip to main content](https://docs.elest.io/books/load-balancers#main-content) Info Content Load balancers ============== [#### Overview\ \ Load balancers are essential to achieve High Availability (HA) and horizontal scalability.  Most...](https://docs.elest.io/books/load-balancers/page/overview) [#### Create a new load balancer\ \ To create a new load balancer, go to the dashboard and click on Load Balancer on the left side h...](https://docs.elest.io/books/load-balancers/page/create-a-new-load-balancer) [#### Update load balancer configuration\ \ Once your load balancer is deployed, you will be able to edit its configuration at any time from ...](https://docs.elest.io/books/load-balancers/page/update-load-balancer-configuration) ### Search Results Clear Search Back to top --- # Billing | docs.elest.io [Skip to main content](https://docs.elest.io/books/billing#main-content) Info Content Billing ======= [#### Overview\ \ All billable resources are attached to a project. At the beginning of each hour, your resources w...](https://docs.elest.io/books/billing/page/overview) [#### Add credits\ \ Add money to your elestio balance You can easily add credits to your elestio account from your U...](https://docs.elest.io/books/billing/page/add-credits) [#### Per project details\ \ To view a project's billing details, select Billing from the left menu, where you'll find a recap...](https://docs.elest.io/books/billing/page/per-project-details) [#### Payment options\ \ Never worry about your elestio account balance running out or being too low anymore by using our ...](https://docs.elest.io/books/billing/page/payment-options) [#### Invoices\ \ Easily view, open or download your invoices in one place via your User Profile.Navigate to your U...](https://docs.elest.io/books/billing/page/invoices) [#### Free trial\ \ Elestio offers a 3-day free trial with $20 in credits, during which you can launch up to 2 servic...](https://docs.elest.io/books/billing/page/free-trial) [#### SEPA Direct Debit Payment Option on Elestio\ \ At Elestio, we aim to make payment processing as convenient and accessible as possible for our cu...](https://docs.elest.io/books/billing/page/sepa-direct-debit-payment-option-on-elestio) [#### Bandwidth Billing\ \ At Elestio, we're committed to transparency and simplicity when it comes to billing. One area whe...](https://docs.elest.io/books/billing/page/bandwidth-billing) [#### Elestio Free Trial Policy & Fair Use Statement\ \ At Elestio, we’re committed to empowering users by providing a fast, reliable and flexible platfo...](https://docs.elest.io/books/billing/page/elestio-free-trial-policy-fair-use-statement) ### Search Results Clear Search Back to top --- # Databases | docs.elest.io [Skip to main content](https://docs.elest.io/books/databases#main-content) Info Content Databases ========= We currently support cluster mode for MySQL & KeyDB (Redis compatible). We are working hard on adding cluster mode support for more databases. [#### DB Migration service](https://docs.elest.io/books/databases/chapter/db-migration-service) 10 Pages [#### MySQL Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/mysql-database-migration-to-elestio) [#### PostgreSQL Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/postgresql-database-migration-to-elestio) [#### MariaDB Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/mariadb-database-migration-to-elestio-jV6) [#### ColumnStore Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/columnstore-database-migration-to-elestio-aZl) [#### Redis Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/redis-database-migration-to-elestio) [#### KeyDB Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/keydb-database-migration-to-elestio) [#### Valkey Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/valkey-database-migration-to-elestio) [#### MongoDB Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/mongodb-database-migration-to-elestio) [#### TimescaleDB Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/timescaledb-database-migration-to-elestio) [#### Hydra Database Migration to Elestio\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamle...](https://docs.elest.io/books/databases/page/hydra-database-migration-to-elestio) [#### DB Clusters](https://docs.elest.io/books/databases/chapter/db-clusters) 14 Pages [#### Introduction\ \ Clustered databases are essential for ensuring high availability, scalability, and fault toleranc...](https://docs.elest.io/books/databases/page/introduction) [#### Deploy a new cluster\ \ How to deploy a new cluster 1) Go to the Elestio Clusters tab. 2) Click on Deploy My First Cl...](https://docs.elest.io/books/databases/page/deploy-a-new-cluster) [#### Overview\ \ Once your cluster is deployed, you can access it through the Clusters tab on the left. Here, you ...](https://docs.elest.io/books/databases/page/overview) [#### Nodes management\ \ If you click on the Nodes tab, you will see a list of all your nodes with detailed information,...](https://docs.elest.io/books/databases/page/nodes-management) [#### Add a node\ \ If you want to add a new node to your cluster, you can: Click on the Add Node button in the to...](https://docs.elest.io/books/databases/page/add-a-node) [#### Remove a node\ \ If you want to remove a node from your cluster, you can: Click on the Delete button with the t...](https://docs.elest.io/books/databases/page/remove-a-node) [#### Promote a node\ \ If you want to promote a node to Primary in your cluster, follow these steps: Go to the Nodes ...](https://docs.elest.io/books/databases/page/promote-a-node) [#### Backups and restores\ \ Elestio offers a Backup section specifically for managing backups.For clusters, only the backups ...](https://docs.elest.io/books/databases/page/backups-and-restores) [#### Limit access per IP\ \ If you want to restrict your cluster to specific IPs for enhanced security, follow these steps: ...](https://docs.elest.io/books/databases/page/limit-access-per-ip) [#### Cluster resynchronization\ \ If one or more Replica nodes are unhealthy or desynchronized, you can resynchronize them with the...](https://docs.elest.io/books/databases/page/cluster-resynchronization) [#### Database migrations\ \ If you want to migrate an existing database to your cluster, you can do so easily by following th...](https://docs.elest.io/books/databases/page/database-migrations) [#### Delete a cluster\ \ If you want to delete your cluster, follow these steps: Go to the Overview tab of your cluster...](https://docs.elest.io/books/databases/page/delete-a-cluster) [#### MySQL cluster with Multi-master or Replica mode\ \ If you can’t afford for your database to be down for even a few minutes, a Multi-Master cluster i...](https://docs.elest.io/books/databases/page/mysql-cluster-with-multi-master-or-replica-mode) [#### KeyDB (Redis compatible) with Multi-master or Replica mode\ \ If you can’t afford for your database to be down for even a few minutes, you need a Multi-Master ...](https://docs.elest.io/books/databases/page/keydb-redis-compatible-with-multi-master-or-replica-mode) ### Search Results Clear Search Back to top --- # Getting started | docs.elest.io [Skip to main content](https://docs.elest.io/books/getting-started#main-content) Info Content Getting started =============== [#### What is Elestio?\ \ Elestio is the simplest way to run Open Source Software. Deploy any one of over 350+ supported o...](https://docs.elest.io/books/getting-started/page/what-is-elestio) [#### Create an account\ \ To create a new account, first, go to elestio signup page Securely connect elestio to your exist...](https://docs.elest.io/books/getting-started/page/create-an-account) [#### Create a new service\ \ 1\. To create a new service, first open Elestio Dashboard Use the category tabs to filter the...](https://docs.elest.io/books/getting-started/page/create-a-new-service) [#### Newsletter\ \ You can get the most recent information about Elestio features, supported software, and tips by s...](https://docs.elest.io/books/getting-started/page/newsletter) [#### Create a new service with Bring your own AWS Account (BYOAWS)\ \  To create a new service, first, open Elestio Dashboard, then go to services from the left sideba...](https://docs.elest.io/books/getting-started/page/create-a-new-service-with-bring-your-own-aws-account-byoaws) [#### How to Create AWS Access and Secret Key for BYOAWS\ \ To create your AWS Access and Secret Key, follow these steps. Step 1:- Use your AWS account ID...](https://docs.elest.io/books/getting-started/page/how-to-create-aws-access-and-secret-key-for-byoaws) [#### How to Deploy or Integrate a Service with Tor Onion on Elestio\ \ To make your services accessible over Tor, you can configure a Tor service within your service Do...](https://docs.elest.io/books/getting-started/page/how-to-deploy-or-integrate-a-service-with-tor-onion-on-elestio) ### Search Results Clear Search Back to top --- # CI/CD Pipelines | docs.elest.io [Skip to main content](https://docs.elest.io/books/cicd-pipelines#main-content) Info Content CI/CD Pipelines =============== Go from source code to production with CI/CD Pipelines. We support Github, Gitlab & docker registries as source. Pipelines can be deployed on any cloud, even on-premise. [#### Overview\ \ Elestio is the simplest and fastest way to deploy your source code from github/gitlab/docker regi...](https://docs.elest.io/books/cicd-pipelines/page/overview) [#### Deploy your first CI/CD pipeline on Elestio\ \ You are about to learn how to deploy an application from a Git repository to production on any cl...](https://docs.elest.io/books/cicd-pipelines/page/deploy-your-first-cicd-pipeline-on-elestio) [#### Deploy docker-compose apps (Wordpress, MySQL, Redis, Keycloak ...)\ \ You are about to learn how to deploy docker-compose applications to a CI/CD target. This is usefu...](https://docs.elest.io/books/cicd-pipelines/page/deploy-docker-compose-apps-wordpress-mysql-redis-keycloak) [#### Deploy own docker-compose image using Elestio "Custom docker-compose"\ \ This tutorial will walk you through the process of deploying your own custom Docker image to the ...](https://docs.elest.io/books/cicd-pipelines/page/deploy-own-docker-compose-image-using-elestio-custom-docker-compose) [#### How to Deploy React App on Elestio\ \ So you made a React web application and want to deploy it to the cloud 🚀 You probably heard abou...](https://docs.elest.io/books/cicd-pipelines/page/how-to-deploy-react-app-on-elestio) [#### How to Deploy NodeJs-express app with a static front-end in a pug on Elestio\ \ So you made a static full stack frontend pug with nodejs backend application and want to deploy i...](https://docs.elest.io/books/cicd-pipelines/page/how-to-deploy-nodejs-express-app-with-a-static-front-end-in-a-pug-on-elestio) [#### Deploy examples & apps on Elestio using the "clone template" feature\ \ This tutorial will show you how to use our clone template feature in CI/CD. We're going to use a ...](https://docs.elest.io/books/cicd-pipelines/page/deploy-examples-apps-on-elestio-using-the-clone-template-feature) [#### Custom domains on CI/CD pipelines\ \ You can add any number of custom domain names on your CI/CD pipeline, Elestio will automatically ...](https://docs.elest.io/books/cicd-pipelines/page/custom-domains-on-cicd-pipelines) [#### Create your own template (elestio.yml)\ \ You can create your own template to be deployed on Elestio for yourself (private repo) or for any...](https://docs.elest.io/books/cicd-pipelines/page/create-your-own-template-elestioyml) [#### Clone CI/CD pipeline\ \ When distributing your project pipeline across the Production, Staging, and Test environments, yo...](https://docs.elest.io/books/cicd-pipelines/page/clone-cicd-pipeline) [#### Pipelines migration, move pipelines between CI/CD targets safely\ \ In several situations, you might want to move a deployed CI/CD pipeline from one target to anothe...](https://docs.elest.io/books/cicd-pipelines/page/pipelines-migration-move-pipelines-between-cicd-targets-safely) [#### Deploy examples & apps on Elestio using the "Import Third-Party Git Repository" feature\ \ This tutorial will walk you through the process of deploying GitHub, GitLab, or Bitbucket public ...](https://docs.elest.io/books/cicd-pipelines/page/deploy-examples-apps-on-elestio-using-the-import-third-party-git-repository-feature) [#### How to Create a Pipeline for Git Submodule Repo\ \ Deploying code from a repository that includes Git submodules can be a bit more complex than a st...](https://docs.elest.io/books/cicd-pipelines/page/how-to-create-a-pipeline-for-git-submodule-repo) [#### How to Run a Nuxt App with preinstall script in Elestio\ \ When running a Nuxt.js application using runtime NodeJs, particularly with a preinstall script, y...](https://docs.elest.io/books/cicd-pipelines/page/how-to-run-a-nuxt-app-with-preinstall-script-in-elestio) ### Search Results Clear Search Back to top --- # Valkey | docs.elest.io [Skip to main content](https://docs.elest.io/books/valkey#main-content) Info Content Valkey ====== [#### Overview\ \ Valkey is an open-source, high-performance in-memory data store designed for building real-time, ...](https://docs.elest.io/books/valkey/page/overview) [#### How to Connect](https://docs.elest.io/books/valkey/chapter/how-to-connect) 7 Pages [#### Connecting with Node.js\ \ This guide explains how to establish a connection between a Node.js application and a Valkey data...](https://docs.elest.io/books/valkey/page/connecting-with-nodejs) [#### Connecting with Python\ \ This guide explains how to connect a Python application to a Valkey database using the redis libr...](https://docs.elest.io/books/valkey/page/connecting-with-python) [#### Connecting with PHP\ \ This guide explains how to establish a connection between a PHP application and a Valkey database...](https://docs.elest.io/books/valkey/page/connecting-with-php) [#### Connecting with Go\ \ This guide explains how to establish a connection between a Go application and a Valkey database ...](https://docs.elest.io/books/valkey/page/connecting-with-go) [#### Connecting with Java\ \ This guide explains how to establish a connection between a Java application and a Valkey databas...](https://docs.elest.io/books/valkey/page/connecting-with-java) [#### Connecting with RedisInsight\ \ This guide explains how to establish a connection between RedisInsight and a Valkey database inst...](https://docs.elest.io/books/valkey/page/connecting-with-redisinsight) [#### Connecting with keydb-cli\ \ This guide explains how to establish a connection between valkey-cli and a Valkey database instan...](https://docs.elest.io/books/valkey/page/connecting-with-keydb-cli) [#### How-To Guides](https://docs.elest.io/books/valkey/chapter/how-to-guides) 9 Pages [#### Creating a Database\ \ Valkey is a high-performance fork of Redis that emphasizes open governance and continued compatib...](https://docs.elest.io/books/valkey/page/creating-a-database) [#### Upgrading to Major Version\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing...](https://docs.elest.io/books/valkey/page/upgrading-to-major-version) [#### Installing and Updating an Extension\ \ Valkey supports Redis-compatible modules to extend core database functionality with custom data t...](https://docs.elest.io/books/valkey/page/installing-and-updating-an-extension) [#### Creating Manual Backups\ \ Regular backups are essential when running a Valkey deployment, especially if you’re using it for...](https://docs.elest.io/books/valkey/page/creating-manual-backups) [#### Restoring a Backup\ \ Restoring Valkey backups is critical for disaster recovery, staging environment replication, or r...](https://docs.elest.io/books/valkey/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Slow commands can impact Valkey performance, especially under high concurrency or when inefficien...](https://docs.elest.io/books/valkey/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ Optimizing memory usage in Valkey is essential for maintaining performance, especially in product...](https://docs.elest.io/books/valkey/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk\ \ Running out of disk space in a Valkey environment can result in failed writes, background save er...](https://docs.elest.io/books/valkey/page/preventing-full-disk) [#### Checking Database Size and Related Issues\ \ As your Valkey data grows especially when using persistence modes like RDB or AOF it’s essential ...](https://docs.elest.io/books/valkey/page/checking-database-size-and-related-issues) [#### Database Migration](https://docs.elest.io/books/valkey/chapter/database-migration) 3 Pages [#### Database Migration Service for Valkey\ \ Elestio provides a structured approach for migrating Valkey databases from various environments, ...](https://docs.elest.io/books/valkey/page/database-migration-service-for-valkey) [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of ...](https://docs.elest.io/books/valkey/page/cloning-a-service-to-another-provider-or-region) [#### Manual Migration Using valkey-cli and Dump Files\ \ Manual migrations using Valkey’s native tools are ideal for users who prefer full control over da...](https://docs.elest.io/books/valkey/page/manual-migration-using-valkey-cli-and-dump-files) [#### Cluster Management](https://docs.elest.io/books/valkey/chapter/cluster-management) 11 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/valkey/page/overview-QYk) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/valkey/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/valkey/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/valkey/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/valkey/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/valkey/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/valkey/page/backups-and-restores) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/valkey/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure th...](https://docs.elest.io/books/valkey/page/cluster-resynchronization) [#### Database Migrations\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/valkey/page/database-migrations) [#### Deleting a Cluster\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/valkey/page/deleting-a-cluster) ### Search Results Clear Search Back to top --- # KeyDB | docs.elest.io [Skip to main content](https://docs.elest.io/books/keydb#main-content) Info Content KeyDB ===== [#### Overview\ \ KeyDB is an open-source, high-performance in-memory database solution designed for real-time appl...](https://docs.elest.io/books/keydb/page/overview) [#### How to Connect](https://docs.elest.io/books/keydb/chapter/how-to-connect) 7 Pages [#### Connecting with Node.js\ \ This guide explains how to establish a connection between a Node.js application and a KeyDB datab...](https://docs.elest.io/books/keydb/page/connecting-with-nodejs) [#### Connecting with Python\ \ This guide explains how to connect a Python application to a KeyDB database using the redis libra...](https://docs.elest.io/books/keydb/page/connecting-with-python) [#### Connecting with PHP\ \ This guide explains how to establish a connection between a PHP application and a KeyDB database ...](https://docs.elest.io/books/keydb/page/connecting-with-php) [#### Connecting with Go\ \ This guide explains how to establish a connection between a Go application and a KeyDB database u...](https://docs.elest.io/books/keydb/page/connecting-with-go) [#### Connecting with Java\ \ This guide explains how to establish a connection between a Java application and a KeyDB database...](https://docs.elest.io/books/keydb/page/connecting-with-java) [#### Connecting with RedisInsight\ \ This guide explains how to establish a connection between RedisInsight and a KeyDB database insta...](https://docs.elest.io/books/keydb/page/connecting-with-redisinsight) [#### Connecting with keydb-cli\ \ This guide explains how to establish a connection between keydb-cli and a KeyDB database instance...](https://docs.elest.io/books/keydb/page/connecting-with-keydb-cli) [#### How-To Guides](https://docs.elest.io/books/keydb/chapter/how-to-guides) 9 Pages [#### Creating a Database\ \ KeyDB is a high-performance fork of Redis that offers multithreading, active-active replication, ...](https://docs.elest.io/books/keydb/page/creating-a-database) [#### Upgrading to Major Version\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing...](https://docs.elest.io/books/keydb/page/upgrading-to-major-version) [#### Installing and Updating an Extension\ \ KeyDB supports Redis-compatible modules to extend core database functionality with custom data ty...](https://docs.elest.io/books/keydb/page/installing-and-updating-an-extension) [#### Creating Manual Backups\ \ Regular backups are essential when running a KeyDB deployment, especially if you’re using it for ...](https://docs.elest.io/books/keydb/page/creating-manual-backups) [#### Restoring a Backup\ \ Restoring KeyDB backups is critical for disaster recovery, staging environment replication, or ro...](https://docs.elest.io/books/keydb/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Slow commands can impact KeyDB performance, especially under high concurrency or when inefficient...](https://docs.elest.io/books/keydb/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ Optimizing memory usage in KeyDB is essential for maintaining performance, especially in producti...](https://docs.elest.io/books/keydb/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk\ \ Running out of disk space in a KeyDB environment can result in failed writes, background save err...](https://docs.elest.io/books/keydb/page/preventing-full-disk) [#### Checking Database Size and Related Issues\ \ As your KeyDB data grows especially when using persistence modes like RDB or AOF—it’s essential t...](https://docs.elest.io/books/keydb/page/checking-database-size-and-related-issues) [#### Database Migration](https://docs.elest.io/books/keydb/chapter/database-migration) 3 Pages [#### Database Migration Service for KeyDB\ \ Elestio provides a structured approach for migrating KeyDB databases from various environments, s...](https://docs.elest.io/books/keydb/page/database-migration-service-for-keydb) [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of ...](https://docs.elest.io/books/keydb/page/cloning-a-service-to-another-provider-or-region) [#### Manual Migration Using keydb-cli and Dump Files\ \ Manual migrations using KeyDB’s native tools are ideal for users who prefer full control over dat...](https://docs.elest.io/books/keydb/page/manual-migration-using-keydb-cli-and-dump-files) [#### Cluster Management](https://docs.elest.io/books/keydb/chapter/cluster-management) 11 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/keydb/page/overview-QjM) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/keydb/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/keydb/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/keydb/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/keydb/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/keydb/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/keydb/page/backups-and-restores) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/keydb/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/keydb/page/cluster-resynchronization) [#### Database Migrations\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/keydb/page/database-migrations) [#### Deleting a Cluster\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/keydb/page/deleting-a-cluster) ### Search Results Clear Search Back to top --- # TimescaleDB | docs.elest.io [Skip to main content](https://docs.elest.io/books/timescaledb#main-content) Info Content TimescaleDB =========== [#### Overview\ \ TimescaleDB is an open-source time-series database engineered for fast, scalable ingestion and co...](https://docs.elest.io/books/timescaledb/page/overview) [#### How to Connect](https://docs.elest.io/books/timescaledb/chapter/how-to-connect) 7 Pages [#### Connecting with Node.js\ \ This guide walks you through the process of connecting a Node.js application to a TimescaleDB dat...](https://docs.elest.io/books/timescaledb/page/connecting-with-nodejs) [#### Connecting with Python\ \ This guide explains how to connect a Python application to a TimescaleDB database using the psyco...](https://docs.elest.io/books/timescaledb/page/connecting-with-python) [#### Connecting with PHP\ \ This guide explains how to connect a PHP application to a TimescaleDB database using the PDO exte...](https://docs.elest.io/books/timescaledb/page/connecting-with-php) [#### Connecting with Go\ \ This guide walks you through setting up a Go application to connect to a TimescaleDB database, us...](https://docs.elest.io/books/timescaledb/page/connecting-with-go) [#### Connecting with Java\ \ This guide shows how to connect your Java app to a TimescaleDB database using the PostgreSQL JDBC...](https://docs.elest.io/books/timescaledb/page/connecting-with-java) [#### Connecting with psql\ \ This guide explains how to connect to a TimescaleDB database using the psql command-line tool. It...](https://docs.elest.io/books/timescaledb/page/connecting-with-psql) [#### Connecting with pgAdmin\ \ pgAdmin is a widely used graphical interface for TimescaleDB that allows you to manage, connect t...](https://docs.elest.io/books/timescaledb/page/connecting-with-pgadmin) [#### How-To Guides](https://docs.elest.io/books/timescaledb/chapter/how-to-guides) 9 Pages [#### Creating a Database\ \ TimescaleDB allows you to create databases using different methods, including the PostgreSQL inte...](https://docs.elest.io/books/timescaledb/page/creating-a-database) [#### Upgrading to a Major Version\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing...](https://docs.elest.io/books/timescaledb/page/upgrading-to-a-major-version) [#### Installing or Updating an Extension\ \ TimescaleDB supports a growing range of PostgreSQL-compatible extensions that add extra functiona...](https://docs.elest.io/books/timescaledb/page/installing-or-updating-an-extension) [#### Creating Manual Backups\ \ Regular backups are a key part of managing a TimescaleDB deployment. While Elestio provides autom...](https://docs.elest.io/books/timescaledb/page/creating-manual-backups) [#### Restoring a Backup\ \ Restoring backups is essential for recovery, environment duplication, or rollback scenarios. Eles...](https://docs.elest.io/books/timescaledb/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Slow queries can significantly affect application performance and user experience. TimescaleDB of...](https://docs.elest.io/books/timescaledb/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ Long-running queries can significantly impact database performance by consuming CPU, memory, and ...](https://docs.elest.io/books/timescaledb/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ Running out of disk space in a database environment can lead to failed writes, service downtime, ...](https://docs.elest.io/books/timescaledb/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ As your TimescaleDB database grows over time, it’s important to monitor its size and identify wha...](https://docs.elest.io/books/timescaledb/page/checking-database-size-and-related-issues) [#### Database Migration](https://docs.elest.io/books/timescaledb/chapter/database-migration) 3 Pages [#### Database Migration Service for TimescaleDB\ \ Elestio provides a structured approach for migrating TimescaleDB databases from various environme...](https://docs.elest.io/books/timescaledb/page/database-migration-service-for-timescaledb) [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of ...](https://docs.elest.io/books/timescaledb/page/cloning-a-service-to-another-provider-or-region) [#### Manual Migration Using pg\_dump and pg\_restore\ \ Manual Migrations using TimescaleDB's built-in tools pg\_dump and pg\_restore are ideal for users w...](https://docs.elest.io/books/timescaledb/page/manual-migration-using-pg-dump-and-pg-restore) [#### Cluster Management](https://docs.elest.io/books/timescaledb/chapter/cluster-management) 11 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/timescaledb/page/overview-sRt) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/timescaledb/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/timescaledb/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/timescaledb/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/timescaledb/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/timescaledb/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/timescaledb/page/backups-and-restores) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/timescaledb/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/timescaledb/page/cluster-resynchronization) [#### Database Migrations\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/timescaledb/page/database-migrations) [#### Deleting a Cluster\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/timescaledb/page/deleting-a-cluster) ### Search Results Clear Search Back to top --- # Redis | docs.elest.io [Skip to main content](https://docs.elest.io/books/redis#main-content) Info Content Redis ===== [#### Overview\ \ Redis is an open-source, in-memory key-value data store widely used as a database, cache, and mes...](https://docs.elest.io/books/redis/page/overview) [#### How to Connect](https://docs.elest.io/books/redis/chapter/how-to-connect) 7 Pages [#### Connecting with Node.js\ \ This guide explains how to establish a connection between a Node.js application and a Redis datab...](https://docs.elest.io/books/redis/page/connecting-with-nodejs) [#### Connecting with Python\ \ This guide explains how to connect a Python application to a Redis database using the redis libra...](https://docs.elest.io/books/redis/page/connecting-with-python) [#### Connecting with PHP\ \ This guide explains how to establish a connection between a PHP application and a Redis database ...](https://docs.elest.io/books/redis/page/connecting-with-php) [#### Connecting with Go\ \ This guide explains how to establish a connection between a Go application and a Redis database u...](https://docs.elest.io/books/redis/page/connecting-with-go) [#### Connecting with Java\ \ This guide explains how to establish a connection between a Java application and a Redis database...](https://docs.elest.io/books/redis/page/connecting-with-java) [#### Connecting with RedisInsight\ \ This guide explains how to establish a connection between RedisInsight and a Redis database insta...](https://docs.elest.io/books/redis/page/connecting-with-redisinsight) [#### Connecting with redis-cli\ \ This guide explains how to establish a connection between redis-cli and a Redis database instance...](https://docs.elest.io/books/redis/page/connecting-with-redis-cli) [#### How-To Guides](https://docs.elest.io/books/redis/chapter/how-to-guides) 9 Pages [#### Creating a Database\ \ Redis is a popular in-memory key-value data store known for its speed, flexibility, and support f...](https://docs.elest.io/books/redis/page/creating-a-database) [#### Upgrading to Major Version\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing...](https://docs.elest.io/books/redis/page/upgrading-to-major-version) [#### Installing and Updating an Extension\ \ Redis supports modules to extend core functionality with new data types, commands, or algorithms....](https://docs.elest.io/books/redis/page/installing-and-updating-an-extension) [#### Creating Manual Backups\ \ Regular backups are essential when running a Redis deployment especially if you’re using it for p...](https://docs.elest.io/books/redis/page/creating-manual-backups) [#### Restoring a Backup\ \ Restoring Redis backups is essential for disaster recovery, staging environment duplication, or r...](https://docs.elest.io/books/redis/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Slow commands can impact Redis performance, especially under high load or when poorly optimized o...](https://docs.elest.io/books/redis/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ Long-running commands in Redis can block the single-threaded event loop, causing delayed response...](https://docs.elest.io/books/redis/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ Running out of disk space in a Redis environment can lead to failed writes, snapshot errors, and ...](https://docs.elest.io/books/redis/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ As your Redis data grows especially when using persistence modes like RDB or AOF it’s important t...](https://docs.elest.io/books/redis/page/checking-database-size-and-related-issues) [#### Database Migration](https://docs.elest.io/books/redis/chapter/database-migration) 3 Pages [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of ...](https://docs.elest.io/books/redis/page/cloning-a-service-to-another-provider-or-region) [#### Database Migration Services for Redis\ \ Elestio provides a streamlined and reliable approach for migrating Redis instances from various e...](https://docs.elest.io/books/redis/page/database-migration-services-for-redis) [#### Manual Redis Migration Using redis-cli and RDB Files\ \ Manual migrations using Redis’s built-in tools, such as redis-cli and RDB (Redis Database) files,...](https://docs.elest.io/books/redis/page/manual-redis-migration-using-redis-cli-and-rdb-files) [#### Cluster Management](https://docs.elest.io/books/redis/chapter/cluster-management) 11 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/redis/page/overview-Yo0) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/redis/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/redis/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/redis/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/redis/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/redis/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/redis/page/backups-and-restores) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/redis/page/cluster-resynchronization) [#### Database Migrations\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/redis/page/database-migrations) [#### Delete a Cluster\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/redis/page/delete-a-cluster) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/redis/page/restricting-access-by-ip) ### Search Results Clear Search Back to top --- # PostgreSQL | docs.elest.io [Skip to main content](https://docs.elest.io/books/postgresql#main-content) Info Content PostgreSQL ========== [#### Overview\ \ PostgreSQL is an open-source relational database management system. It supports SQL language and ...](https://docs.elest.io/books/postgresql/page/overview) [#### How to Connect](https://docs.elest.io/books/postgresql/chapter/how-to-connect) 7 Pages [#### Connecting with Node.js\ \ This guide explains how to establish a connection between a Node.js application and a PostgreSQL ...](https://docs.elest.io/books/postgresql/page/connecting-with-nodejs) [#### Connecting with Python\ \ This guide explains how to establish a connection between a Python application and a PostgreSQL d...](https://docs.elest.io/books/postgresql/page/connecting-with-python) [#### Connecting with PHP\ \ This guide explains how to establish a connection between a PHP application and a PostgreSQL data...](https://docs.elest.io/books/postgresql/page/connecting-with-php) [#### Connecting with Go\ \ This guide explains how to establish a connection between a Go (Golang) application and a Postgre...](https://docs.elest.io/books/postgresql/page/connecting-with-go) [#### Connecting with Java\ \ This guide explains how to establish a connection between a Java application and a PostgreSQL dat...](https://docs.elest.io/books/postgresql/page/connecting-with-java) [#### Connecting with psql\ \ This guide explains how to connect to a PostgreSQL database using the psql command-line tool. It ...](https://docs.elest.io/books/postgresql/page/connecting-with-psql) [#### Connecting with pgAdmin\ \ pgAdmin is a widely used graphical interface for PostgreSQL that allows you to manage, connect to...](https://docs.elest.io/books/postgresql/page/connecting-with-pgadmin) [#### How-To Guides](https://docs.elest.io/books/postgresql/chapter/how-to-guides) 9 Pages [#### Creating a Database\ \ PostgreSQL allows you to create databases using different methods, including the PostgreSQL inter...](https://docs.elest.io/books/postgresql/page/creating-a-database) [#### Upgrading to a Major Version\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing...](https://docs.elest.io/books/postgresql/page/upgrading-to-a-major-version) [#### Installing or Updating an Extension\ \ PostgreSQL supports a wide range of extensions that add extra functionality to the core database ...](https://docs.elest.io/books/postgresql/page/installing-or-updating-an-extension) [#### Creating Manual Backups\ \ Regular backups are a key part of managing a PostgreSQL deployment. While Elestio provides automa...](https://docs.elest.io/books/postgresql/page/creating-manual-backups) [#### Restoring a Backup\ \ Restoring backups is essential for recovery, environment duplication, or rollback scenarios. Eles...](https://docs.elest.io/books/postgresql/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Slow queries can significantly affect application performance and user experience. PostgreSQL off...](https://docs.elest.io/books/postgresql/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ Long-running queries can significantly impact database performance by consuming CPU, memory, and ...](https://docs.elest.io/books/postgresql/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ Running out of disk space in a database environment can lead to failed writes, service downtime, ...](https://docs.elest.io/books/postgresql/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ As your PostgreSQL database grows over time, it’s important to monitor its size and identify what...](https://docs.elest.io/books/postgresql/page/checking-database-size-and-related-issues) [#### Database Migration](https://docs.elest.io/books/postgresql/chapter/database-migration) 3 Pages [#### Database Migration Service for PostgreSQL\ \ Elestio provides a structured approach for migrating PostgreSQL databases from various environmen...](https://docs.elest.io/books/postgresql/page/database-migration-service-for-postgresql) [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of ...](https://docs.elest.io/books/postgresql/page/cloning-a-service-to-another-provider-or-region) [#### Manual Migration Using pg\_dump and pg\_restore\ \ Manual Migrations using PostgreSQL’s built-in tools pg\_dump and pg\_restore are ideal for users wh...](https://docs.elest.io/books/postgresql/page/manual-migration-using-pg-dump-and-pg-restore) [#### Cluster Management](https://docs.elest.io/books/postgresql/chapter/cluster-management) 11 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/postgresql/page/overview-kcl) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/postgresql/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/postgresql/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/postgresql/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/postgresql/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/postgresql/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/postgresql/page/backups-and-restores) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/postgresql/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/postgresql/page/cluster-resynchronization) [#### Database Migrations\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/postgresql/page/database-migrations) [#### Deleting a Cluster\ \ When a cluster is no longer needed—whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/postgresql/page/deleting-a-cluster) ### Search Results Clear Search Back to top --- # ClickHouse | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse#main-content) Info Content ClickHouse ========== [#### Overview\ \ ClickHouse is an open-source columnar database management system designed for online analytical p...](https://docs.elest.io/books/clickhouse/page/overview) [#### How to Connect](https://docs.elest.io/books/clickhouse/chapter/how-to-connect) 1 Page [#### Connecting with ClickHouse GUI\ \ Tabix is a lightweight browser-based GUI for ClickHouse that lets you browse tables, write querie...](https://docs.elest.io/books/clickhouse/page/connecting-with-clickhouse-gui) [#### How-To Guides](https://docs.elest.io/books/clickhouse/chapter/how-to-guides) 9 Pages [#### Creating a Database\ \ ClickHouse is a high-performance columnar database designed for real-time analytical processing. ...](https://docs.elest.io/books/clickhouse/page/creating-a-database) [#### Upgrading to Major Version\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing...](https://docs.elest.io/books/clickhouse/page/upgrading-to-major-version) [#### Installing and Updating an Extension\ \ ClickHouse supports custom extensions via \[User Defined Functions (UDFs)\], external dictionaries,...](https://docs.elest.io/books/clickhouse/page/installing-and-updating-an-extension) [#### Creating Manual Backups\ \ Regular backups are essential when running a ClickHouse deployment, especially if you’re using it...](https://docs.elest.io/books/clickhouse/page/creating-manual-backups) [#### Restoring a Backup\ \ Restoring ClickHouse backups is essential for disaster recovery, staging environment duplication,...](https://docs.elest.io/books/clickhouse/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Slow queries can impact ClickHouse performance, especially under high load or with inefficient qu...](https://docs.elest.io/books/clickhouse/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ ClickHouse is a high-performance, column-oriented OLAP database, but poorly optimized or long-run...](https://docs.elest.io/books/clickhouse/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ Running out of disk space in a ClickHouse environment can cause query failures, part merge errors...](https://docs.elest.io/books/clickhouse/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ As your ClickHouse data grows especially with large analytical workloads or high-ingestion pipeli...](https://docs.elest.io/books/clickhouse/page/checking-database-size-and-related-issues) [#### Database Migration](https://docs.elest.io/books/clickhouse/chapter/database-migration) 3 Pages [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning ClickHouse across cloud providers or geographic regions is essential for opt...](https://docs.elest.io/books/clickhouse/page/cloning-a-service-to-another-provider-or-region) [#### Database Migration Services for ClickHouse\ \ Elestio provides a easy and reliable approach for migrating ClickHouse instances from various env...](https://docs.elest.io/books/clickhouse/page/database-migration-services-for-clickhouse) [#### Manual ClickHouse Migration Using clickhouse-backup\ \ Manual migrations using ClickHouse’s native tools, such as clickhouse-client, clickhouse-backup, ...](https://docs.elest.io/books/clickhouse/page/manual-clickhouse-migration-using-clickhouse-backup) [#### Cluster Management](https://docs.elest.io/books/clickhouse/chapter/cluster-management) 11 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/clickhouse/page/overview-Ys0) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide ...](https://docs.elest.io/books/clickhouse/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/clickhouse/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/clickhouse/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/clickhouse/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/clickhouse/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/clickhouse/page/backups-and-restores) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/clickhouse/page/cluster-resynchronization) [#### Database Migration\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/clickhouse/page/database-migration) [#### Delete a Cluster\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/clickhouse/page/delete-a-cluster) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/clickhouse/page/restricting-access-by-ip) ### Search Results Clear Search Back to top --- # MySQL | docs.elest.io [Skip to main content](https://docs.elest.io/books/mysql#main-content) Info Content MySQL ===== [#### Overview\ \ MySQL is an open-source relational database management system. It supports SQL language and offer...](https://docs.elest.io/books/mysql/page/overview) [#### How to Connect](https://docs.elest.io/books/mysql/chapter/how-to-connect) 7 Pages [#### Connecting with Node.js\ \ This guide explains how to establish a connection between a Node.js application and a MySQL datab...](https://docs.elest.io/books/mysql/page/connecting-with-nodejs) [#### Connecting with Python\ \ This guide explains how to establish a connection between a Python application and a MySQL databa...](https://docs.elest.io/books/mysql/page/connecting-with-python) [#### Connecting with PHP\ \ This guide explains how to establish a connection between a PHP application and a MySQL database ...](https://docs.elest.io/books/mysql/page/connecting-with-php) [#### Connecting with Go\ \ This guide explains how to establish a connection between a Go application and a MySQL database u...](https://docs.elest.io/books/mysql/page/connecting-with-go) [#### Connecting with Java\ \ This guide explains how to establish a connection between a Java application and a MySQL database...](https://docs.elest.io/books/mysql/page/connecting-with-java) [#### Connecting with phpMyAdmin\ \ phpMyAdmin is a widely used web-based interface for MySQL that allows you to manage databases, ru...](https://docs.elest.io/books/mysql/page/connecting-with-phpmyadmin) [#### Connecting with mysql\ \ This guide explains how to connect to a MySQL database using the mysql command-line tool. It walk...](https://docs.elest.io/books/mysql/page/connecting-with-mysql) [#### How-To Guides](https://docs.elest.io/books/mysql/chapter/how-to-guides) 9 Pages [#### Creating a Database\ \ MySQL is a leading open-source relational database management system (RDBMS) known for its reliab...](https://docs.elest.io/books/mysql/page/creating-a-database) [#### Upgrading to a Major Version\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing...](https://docs.elest.io/books/mysql/page/upgrading-to-a-major-version) [#### Installing and Updating an Extension\ \ MySQL supports a variety of plugins that extend the functionality of the database engine. These p...](https://docs.elest.io/books/mysql/page/installing-and-updating-an-extension) [#### Creating Manual Backups\ \ Regular backups are a key part of managing a MySQL deployment. While Elestio provides automated b...](https://docs.elest.io/books/mysql/page/creating-manual-backups) [#### Restoring a Backup\ \ Restoring backups is essential for recovery, environment duplication, or rollback scenarios. Eles...](https://docs.elest.io/books/mysql/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Slow queries can degrade the performance of your MySQL-based application, leading to lag, timeout...](https://docs.elest.io/books/mysql/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ Long-running queries in MySQL can degrade database performance by consuming system resources like...](https://docs.elest.io/books/mysql/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ Running out of disk space in a MySQL environment can result in failed writes, temporary unavailab...](https://docs.elest.io/books/mysql/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ As your MySQL database grows, it’s crucial to track how space is being used across schemas, table...](https://docs.elest.io/books/mysql/page/checking-database-size-and-related-issues) [#### Database Migration](https://docs.elest.io/books/mysql/chapter/database-migration) 3 Pages [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of ...](https://docs.elest.io/books/mysql/page/cloning-a-service-to-another-provider-or-region) [#### Database Migration Service for MySQL\ \ Elestio provides a structured approach for migrating MySQL databases from various environments, s...](https://docs.elest.io/books/mysql/page/database-migration-service-for-mysql) [#### Manual Migration Using mysqldump and mysql\ \ Manual migrations using MySQL’s built-in tools mysqldump and mysql, are ideal for users who requi...](https://docs.elest.io/books/mysql/page/manual-migration-using-mysqldump-and-mysql) [#### Cluster Management](https://docs.elest.io/books/mysql/chapter/cluster-management) 11 Pages [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/mysql/page/overview-cMx) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/mysql/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/mysql/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/mysql/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/mysql/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/mysql/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/mysql/page/backups-and-restores) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/mysql/page/cluster-resynchronization) [#### Database Migrations\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/mysql/page/database-migrations) [#### Deleting a Cluster\ \ When a cluster is no longer needed—whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/mysql/page/deleting-a-cluster) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/mysql/page/restricting-access-by-ip) ### Search Results Clear Search Back to top --- # Getting Started | docs.elest.io [Skip to main content](https://docs.elest.io/shelves/getting-started#main-content) Info Content Getting Started =============== Sort Default * [Default](https://docs.elest.io/shelves/getting-started#) * [Name](https://docs.elest.io/shelves/getting-started#) * [Created Date](https://docs.elest.io/shelves/getting-started#) * [Updated Date](https://docs.elest.io/shelves/getting-started#) https://www.youtube.com/watch?v=zWyM6m3cWxE [Getting started\ ---------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/getting-started) [Services Dashboard\ ------------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/services-dashboard) [Cloud Providers\ ---------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/cloud-providers) [Supported Softwares\ -------------------\ \ Our catalog is comprised of over 350+ open source software services. We plan to continue adding to our catalog each month, so k...\ \ Created 3 years ago\ \ Updated 1 year ago](https://docs.elest.io/books/supported-softwares) [Databases\ ---------\ \ We currently support cluster mode for MySQL & KeyDB (Redis compatible). We are working hard on adding cluster mode support for ...\ \ Created 3 years ago\ \ Updated 1 year ago](https://docs.elest.io/books/databases) [DB Migrations\ -------------\ \ Need help to migrate to Elestio? Follow the simple steps in the documentation here and get started.\ \ Created 2 years ago\ \ Updated 9 months ago](https://docs.elest.io/books/db-migrations) [Load balancers\ --------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/load-balancers) [CI/CD Pipelines\ ---------------\ \ Go from source code to production with CI/CD Pipelines. We support Github, Gitlab & docker registries as source. Pipelines can ...\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/cicd-pipelines) [Volumes\ -------\ \ Elestio has the top 6 cloud partners in 110 locations across 29 countries (AWS Lightsail, Digital Ocean, Scaleway, Vultr, Linod...\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/volumes) [Frequently Asked Questions\ --------------------------\ \ Here are some most commonly asked questions\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/frequently-asked-questions) [Domains\ -------\ \ Domains\ \ Created 2 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/domains) Back to top --- # Legal & Billing | docs.elest.io [Skip to main content](https://docs.elest.io/shelves/legal-billing#main-content) Info Content Legal & Billing =============== Sort Default * [Default](https://docs.elest.io/shelves/legal-billing#) * [Name](https://docs.elest.io/shelves/legal-billing#) * [Created Date](https://docs.elest.io/shelves/legal-billing#) * [Updated Date](https://docs.elest.io/shelves/legal-billing#) [Billing\ -------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/billing) [Legal & Compliance\ ------------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/legal-compliance) Back to top --- # docs.elest.io [Skip to main content](https://docs.elest.io/password/email#main-content) Reset Password ============== Enter your email below and you will be sent an email with a password reset link. Email Send Reset Link Back to top --- # How it works | docs.elest.io [Skip to main content](https://docs.elest.io/shelves/how-it-works#main-content) Info Content How it works ============ Sort Default * [Default](https://docs.elest.io/shelves/how-it-works#) * [Name](https://docs.elest.io/shelves/how-it-works#) * [Created Date](https://docs.elest.io/shelves/how-it-works#) * [Updated Date](https://docs.elest.io/shelves/how-it-works#) [Backups\ -------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/backups) [Security\ --------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/security) [Projects & Teams\ ----------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/projects-teams) [Elestio API\ -----------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/elestio-api) Back to top --- # Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/chapter/overview#main-content) Info Content Overview ======== [#### Service protection\ \ Elestio services can be protected against accidental deletion by enabling the Termination protect...](https://docs.elest.io/books/services-dashboard/page/service-protection) [#### Power Management\ \ You may manage power management on an elestio by using the Reboot, Reset, Shutdown, Power On, and...](https://docs.elest.io/books/services-dashboard/page/power-management) [#### Admin UI\ \ Most supported softwares have an administrative web interface. Selecting the Display Admin UI bu...](https://docs.elest.io/books/services-dashboard/page/admin-ui) [#### Database credentials\ \ This only applies to database software. You can view your database software in your service Dash...](https://docs.elest.io/books/services-dashboard/page/database-credentials) [#### Service Support Plans\ \ Elestio offers 3 levels of support.Our Level 1 Support plan is included for free with all deploye...](https://docs.elest.io/books/services-dashboard/page/service-support-plans) [#### Selected / change software version\ \ You can select another version of your deployed software in your service's Dashboard Overview.1. ...](https://docs.elest.io/books/services-dashboard/page/selected-change-software-version) [#### Bandwidth & Networks\ \ In the service Dashboard Overview tab, you will also find a recap of your bandwidth usage for the...](https://docs.elest.io/books/services-dashboard/page/bandwidth-networks) [#### Move a Service to Another Project\ \ You can easily move your services between projects.1. From the service Dashboard Overview tab, se...](https://docs.elest.io/books/services-dashboard/page/move-a-service-to-another-project) [#### Software & OS Updates configuration\ \ OS & Software updates are enabled by default when you create a new service. You can configure ...](https://docs.elest.io/books/services-dashboard/page/software-os-updates-configuration) [#### Upgrade service plan\ \ In the service overview, disable the termination protection then shut down the service, once done...](https://docs.elest.io/books/services-dashboard/page/upgrade-service-plan) [#### Upgrade support plan\ \ From the service overview, click on "Upgrade plan" on the support plan row to change your support...](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan) [#### Delete a service\ \ To delete a service, ensure that termination protection is disabled then click on "Delete service...](https://docs.elest.io/books/services-dashboard/page/delete-a-service) [#### Software logs, configuration, restart app, change version\ \ From the service overview, you can open live logs with the "View app logs" button You can ch...](https://docs.elest.io/books/services-dashboard/page/software-logs-configuration-restart-app-change-version) [#### Resync\ \ After cloning a service, you will have a new option visible in the service overview: Resync From...](https://docs.elest.io/books/services-dashboard/page/resync) [#### Increase AWS Main (Disk Or Volume) Size\ \ Your AWS provider instance disc size can be changed at any time between 10 GB and 10 TB. On AWS ...](https://docs.elest.io/books/services-dashboard/page/increase-aws-main-disk-or-volume-size) ### Search Results Clear Search [Next\ \ Service protection](https://docs.elest.io/books/services-dashboard/page/service-protection) Back to top --- # Managed Databases | docs.elest.io [Skip to main content](https://docs.elest.io/shelves/managed-databases#main-content) Info Content Managed Databases ================= Sort Default * [Default](https://docs.elest.io/shelves/managed-databases#) * [Name](https://docs.elest.io/shelves/managed-databases#) * [Created Date](https://docs.elest.io/shelves/managed-databases#) * [Updated Date](https://docs.elest.io/shelves/managed-databases#) [Managed DB Overview\ -------------------\ \ Created 9 months ago\ \ Updated 9 months ago](https://docs.elest.io/books/managed-db-overview) [PostgreSQL\ ----------\ \ Created 9 months ago\ \ Updated 9 months ago](https://docs.elest.io/books/postgresql) [MySQL\ -----\ \ Created 8 months ago\ \ Updated 8 months ago](https://docs.elest.io/books/mysql) [Hydra\ -----\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/hydra) [TimescaleDB\ -----------\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/timescaledb) [Redis\ -----\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/redis) [ClickHouse\ ----------\ \ Created 6 months ago\ \ Updated 6 months ago](https://docs.elest.io/books/clickhouse) [Keycloak\ --------\ \ Created 6 months ago\ \ Updated 6 months ago](https://docs.elest.io/books/keycloak) [KeyDB\ -----\ \ Created 5 months ago\ \ Updated 5 months ago](https://docs.elest.io/books/keydb) [Valkey\ ------\ \ Created 5 months ago\ \ Updated 5 months ago](https://docs.elest.io/books/valkey) Back to top --- # Service protection | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/page/service-protection#main-content) Info Content Service protection ================== Elestio services can be protected against accidental deletion by enabling the _Termination protection_ feature: [![Screenshot 2022-09-28 204650.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-28-204650.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1641899911827.png) When _Termination protection_ is enabled for a service, it can't be terminated or powered down. In order to terminate or power off a protected service, you will need to disable _Termination protection_. Running out of credits will cause your service to be powered down even if Termination protection is activated. Enter section select mode [Previous\ \ Overview](https://docs.elest.io/books/services-dashboard/chapter/overview) [Next\ \ Power Management](https://docs.elest.io/books/services-dashboard/page/power-management) Back to top --- # What is Elestio? | docs.elest.io [Skip to main content](https://docs.elest.io/books/getting-started/page/what-is-elestio#main-content) Info Content What is Elestio? ================ **Elestio** is the simplest way to run Open Source Software. ------------------------------------------------------------ ##### Deploy any one of over 350+ supported open-source software distributions on a dedicated instance in less than 5 minutes. Elestio's platform takes care of installation, configuration, encryption, backups, software & OS updates, live monitoring, alerts, and more! Some companies pay hundreds to thousands of dollars per month in DevOps costs to maintain open-source software projects. Unless you have a top-notch team, it's still an error-prone process: bad updates and migrations happen more often than anyone wants. Even skilled administrators use our managed services, saving hours and days of work needed each month to maintain their services while avoiding the risks related to manual migrations (downtime, human error, loss of data). With **Elestio** you can easily manage your fleet of open source software solutions on **autopilot.** [![dashboard-full2.png](https://docs.elest.io/uploads/images/gallery/2022-09/scaled-1680-/dashboard-full2.png)](https://docs.elest.io/uploads/images/gallery/2022-09/dashboard-full2.png) Elestio guarantees your backups are up to date, and that you can restore your OS or data from a backup at any time to get back up and running in a worst-case scenario. This "Get Started" video series is the best method to learn how to Deploy Open-Source Software on Elestio: Enter section select mode [Next\ \ Create an account](https://docs.elest.io/books/getting-started/page/create-an-account) Back to top --- # Tools | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/chapter/tools#main-content) Info Content Tools ===== [#### VSCode\ \ From the Tools tab in the service overview, click on VS Code button to start VS Code in the brows...](https://docs.elest.io/books/services-dashboard/page/vscode) [#### File Explorer\ \ From the Tools tab in the service overview, click on the "File Explorer" button. The first launc...](https://docs.elest.io/books/services-dashboard/page/file-explorer) [#### Web Terminal\ \ From the Tools tab in the service overview, click on the "Terminal" button The first launch can ...](https://docs.elest.io/books/services-dashboard/page/web-terminal) [#### Reset SSH/SFTP Password\ \ By default, password authentication is disabled. For security reasons, we recommend using SSH Pub...](https://docs.elest.io/books/services-dashboard/page/reset-sshsftp-password) ### Search Results Clear Search [Previous\ \ Increase AWS Main (Disk Or Volume) Size](https://docs.elest.io/books/services-dashboard/page/increase-aws-main-disk-or-volume-size) [Next\ \ VSCode](https://docs.elest.io/books/services-dashboard/page/vscode) Back to top --- # Create a new service | docs.elest.io [Skip to main content](https://docs.elest.io/books/getting-started/page/create-a-new-service#main-content) Info Content Create a new service ==================== ##### 1\. To create a new service, first open **[Elestio Dashboard](https://dash.elest.io/ "Elestio Dashboard")** [![dashboard-full2.png](https://docs.elest.io/uploads/images/gallery/2022-09/scaled-1680-/tO0dashboard-full2.png)](https://docs.elest.io/uploads/images/gallery/2022-09/tO0dashboard-full2.png) **Use the category tabs to filter the selection of software.** [![Screenshot 2022-09-25 at 11.37.39.png](https://docs.elest.io/uploads/images/gallery/2022-09/scaled-1680-/screenshot-2022-09-25-at-11-37-39.png)](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-25-at-11-37-39.png) ##### Choose the template you want to deploy and click the _select_ button for the next step. If you want to learn more about that template, click the _details_ button. ##### 2\. Select a provider, region, and data center in which to deploy your service If you want to deploy the service on AWS, please see our [_**documentation**_](https://docs.elest.io/books/getting-started/page/create-a-new-service-with-bring-your-own-aws-account-byoaws "https://docs.elest.io/books/getting-started/page/create-a-new-service-with-bring-your-own-aws-account-byoaws") on how to do so. [![Screenshot 2023-03-31 123735.png](https://docs.elest.io/uploads/images/gallery/2023-03/screenshot-2023-03-31-123735.png)](https://docs.elest.io/uploads/images/gallery/2023-02/screenshot-2023-02-20-180020.png) ##### 3\. Select the instance size that works for you [![Screenshot 2022-09-25 at 11.45.10.png](https://docs.elest.io/uploads/images/gallery/2022-09/scaled-1680-/screenshot-2022-09-25-at-11-45-10.png)](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-25-at-11-45-10.png) ##### 5\. Set the support plans, and maintenance windows for OS & software updates and give a name to your new service OS updates include updates to the Linux kernel, security patches, and other important maintenance to keep your instance running smoothly. Software updates update the code of the open-source application itself. We respect semantic versioning, so we will only implement minor and patch updates, in order to avoid non-breaking changes. Maintenance windows are specified in UTC [![Screenshot 2022-09-25 at 11.46.45.png](https://docs.elest.io/uploads/images/gallery/2022-09/scaled-1680-/screenshot-2022-09-25-at-11-46-45.png)](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-25-at-11-46-45.png) ##### 6\. Click the "Create Service" button on the right when you are ready to deploy [![Screenshot 2023-11-28 235134.png](https://docs.elest.io/uploads/images/gallery/2023-11/scaled-1680-/screenshot-2023-11-28-235134.png)](https://docs.elest.io/uploads/images/gallery/2023-11/screenshot-2023-11-28-235134.png) [![Screenshot 2022-09-29 173747.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-29-173747.png)](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-25-at-11-47-56.png) ##### 7\. After a few seconds your new service will appear in the list with a status: "Service is in deployment". It should only take 2-3 minutes before your service will be ready to use. [![Screenshot 2022-09-29 174701.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-29-174701.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1641899401774.png) ##### Once your service is ready you will get an email with details about the deployment of your software. ##### The URL and credentials to access the web UI or database application are also available in the **[Service Overview](https://docs.elest.io/books/service-dashboard/chapter/overview "Overview")** ##### **[Get started on the elestio dashboard,](https://dash.elest.io/) or [read more about it in our documentation.](https://docs.elest.io/shelves/getting-started) ** Enter section select mode [Previous\ \ Create an account](https://docs.elest.io/books/getting-started/page/create-an-account) [Next\ \ Newsletter](https://docs.elest.io/books/getting-started/page/newsletter) Back to top --- # Power Management | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/page/power-management#main-content) Info Content Power Management ================ You may manage power management on an elestio by using the Reboot, Reset, Shutdown, Power On, and Power Off buttons. [![power.png](https://docs.elest.io/uploads/images/gallery/2022-09/scaled-1680-/power.png)](https://docs.elest.io/uploads/images/gallery/2022-09/power.png) * **Reboot service:-** Sends an ACPI request to restart a server gracefully. Otherwise, the Server won't reboot. This requires that the Server operating system support ACPI and respond to the request. * **Reset service:-** Turns off the power to a service and then restarts it. This abruptly terminates it without allowing the Service operating system to gently terminate it. Comparable to unplugging and replugging an electrical device, this might result in data loss.  When rebooting does not work, use Reset. * **Shutdown service:-** Sends an ACPI shutdown request to gracefully shut down a server. Otherwise, the Server won't shut down since the Server operating system doesn't support ACPI or respond to the request. * **TURN / Power off:-** It cuts off the Service's power. This abruptly terminates it without allowing the Service operating system to gently terminate it. Data loss may occur if the power cable is unplugged. When shutdown does not function, use the power off. * **Power on:-** It simply starts your stopped service. Shutting down and powering off the service will not stop the billing because the IP address and storage are still reserved, the only way to stop the billing is to delete the services. > The power off and shutdown feature is not available during the free trial period, therefore if you try to power off and shutdown the service, the delete service dialogue will appear. However, once the free trial period has expired, you will be able to power off and shut down the service.  > > If you need to quickly turn off and on the service, you can utilise the reboot button. Enter section select mode [Previous\ \ Service protection](https://docs.elest.io/books/services-dashboard/page/service-protection) [Next\ \ Admin UI](https://docs.elest.io/books/services-dashboard/page/admin-ui) Back to top --- # Supported Softwares | docs.elest.io [Skip to main content](https://docs.elest.io/books/supported-softwares#main-content) Info Content Supported Softwares =================== Our catalog is comprised of over 350+ open source software services. We plan to continue adding to our catalog each month, so keep checking back for new additions! For each supported software we prepare a fully managed lifecycle process. This includes: Setup script based on docker-compose Scripts for several phases: pre-backup / post-backup / pre-restore / post-restore (this is to ensure that backups are consistent and correctly backed up and restored). Tests / Benchmark / Maintenance / Upgrade scripts We focus on software that's: Web UI available API access available Safe and secure Frequently updated and well-maintained Popular and in-demand You can find the full list of software we support here: https://elest.io/fully-managed-services * * * No pages or chapters have been created for this book. ### Search Results Clear Search Back to top --- # Admin UI | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/page/admin-ui#main-content) Info Content Admin UI ======== Most supported softwares have an administrative web interface. Selecting the _Display Admin UI_ button will display the URL, user name and password used to connect to a service's administrative UI. Some software, especially databases, do not have a web management UI. Use the credentials, and the specified port to connect. Certain applications do not allow for the pre-creation of administrative users. If the password field appears blank in the service dashboard, visit the given administrative URL to begin the setup process. [![Screenshot 2022-09-28 205715.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-28-205715.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1641921415519.png) Enter section select mode [Previous\ \ Power Management](https://docs.elest.io/books/services-dashboard/page/power-management) [Next\ \ Database credentials](https://docs.elest.io/books/services-dashboard/page/database-credentials) Back to top --- # Search for [book] | docs.elest.io [Skip to main content](https://docs.elest.io/search?term=%5Bbook%5D#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 1 result found [#### DB Migrations\ \ Need help to migrate to Elestio? Follow the simple steps in the documentation here and get started.\ \ book\ \ migrations](https://docs.elest.io/books/db-migrations) Back to top --- # Database credentials | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/page/database-credentials#main-content) Info Content Database credentials ==================== This only applies to database software. You can view your database software in your service Dashboard in the _Overview_ tab, by selecting the _Display DB Credentials_ button. [![Screenshot 2022-09-29 140621.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-29-140621.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1641905834784.png) You'll find all the details you'll need to connect to your database directly: host address, port, username and password, and CLI. [![Screenshot 2022-09-29 140722.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-29-140722.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1641905882602.png) Enter section select mode [Previous\ \ Admin UI](https://docs.elest.io/books/services-dashboard/page/admin-ui) [Next\ \ Service Support Plans](https://docs.elest.io/books/services-dashboard/page/service-support-plans) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=3#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Reset SSH/SFTP Password\ \ Services Dashboard Tools\ \ By default, password authentication is disabled. For security reasons, we recommend using SSH Pubkeys instead. From the Tools tab in the service overview, click on the "Reset Password" button](https://docs.elest.io/books/services-dashboard/page/reset-sshsftp-password) [#### Domains\ \ Domains](https://docs.elest.io/books/domains) [#### How to Connect\ \ PostgreSQL](https://docs.elest.io/books/postgresql/chapter/how-to-connect) [#### DB Migrations\ \ Need help to migrate to Elestio? Follow the simple steps in the documentation here and get started.\ \ book\ \ migrations](https://docs.elest.io/books/db-migrations) [#### How-To Guides\ \ PostgreSQL](https://docs.elest.io/books/postgresql/chapter/how-to-guides) [#### Managed DB Overview](https://docs.elest.io/books/managed-db-overview) [#### Database Migration\ \ PostgreSQL](https://docs.elest.io/books/postgresql/chapter/database-migration) [#### Backups\ \ Services Dashboard\ \ Please check the Backups details page](https://docs.elest.io/books/services-dashboard/page/backups) [#### PostgreSQL](https://docs.elest.io/books/postgresql) [#### Cluster Management\ \ PostgreSQL](https://docs.elest.io/books/postgresql/chapter/cluster-management) [#### Metrics\ \ Services Dashboard\ \ Metrics tabs allow you to view your service's metrics in real-time.You can configure the update period to as low as a 1-second interval. Enabling additional metrics in real-time will use additional CPU while you are viewing the Dashboard. To limit CPU usage...](https://docs.elest.io/books/services-dashboard/page/metrics) [#### MySQL](https://docs.elest.io/books/mysql) [#### How to Connect\ \ MySQL](https://docs.elest.io/books/mysql/chapter/how-to-connect) [#### Notes\ \ Services Dashboard\ \ The notes tab is useful to save textual notes about service, for yourself or other team members](https://docs.elest.io/books/services-dashboard/page/notes) [#### Hydra](https://docs.elest.io/books/hydra) [#### How-To Guides\ \ MySQL](https://docs.elest.io/books/mysql/chapter/how-to-guides) [#### AWS Lightsail\ \ Cloud Providers\ \ AWS is the largest cloud provider with one of the best network available and a large number of regions and datacenters. Supported Services Compute ✅ Private network ✅ Firewall ✅ Volumes ✅ Floating IP ✅ Snapshots ✅ ...](https://docs.elest.io/books/cloud-providers/page/aws-lightsail) [#### TimescaleDB](https://docs.elest.io/books/timescaledb) [#### Database Migration\ \ MySQL](https://docs.elest.io/books/mysql/chapter/database-migration) [#### Digital Ocean\ \ Cloud Providers\ \ Digital Ocean is a great cloud provider with a large number of regions and datacenters available. They provide good network and overall reliability. Supported Services Compute ✅ High Frequency CPU Private network ✅ Firewall ✅ Volumes ...](https://docs.elest.io/books/cloud-providers/page/digital-ocean) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=2#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Selected / change software version\ \ Services Dashboard Overview\ \ You can select another version of your deployed software in your service's Dashboard Overview.1. Click the Change version button2. Choose the software version you'd like to update or change to3. Don't forget to save! To apply these new settings, select Update...](https://docs.elest.io/books/services-dashboard/page/selected-change-software-version) [#### Legal & Compliance](https://docs.elest.io/books/legal-compliance) [#### Upgrade service plan\ \ Services Dashboard Overview\ \ In the service overview, disable the termination protection then shut down the service, once done you will be able to click on the "Upgrade plan" button and select another service size. To be able to upgrade your service plan, you must first shutdown yo...](https://docs.elest.io/books/services-dashboard/page/upgrade-service-plan) [#### Databases\ \ We currently support cluster mode for MySQL & KeyDB (Redis compatible). We are working hard on adding cluster mode support for more databases.](https://docs.elest.io/books/databases) [#### Projects\ \ Projects & Teams](https://docs.elest.io/books/projects-teams/chapter/projects) [#### Bandwidth & Networks\ \ Services Dashboard Overview\ \ In the service Dashboard Overview tab, you will also find a recap of your bandwidth usage for the current month.     Bandwidth usage includes In&Out traffic.](https://docs.elest.io/books/services-dashboard/page/bandwidth-networks) [#### Load balancers](https://docs.elest.io/books/load-balancers) [#### Teams\ \ Projects & Teams](https://docs.elest.io/books/projects-teams/chapter/teams) [#### Move a Service to Another Project\ \ Services Dashboard Overview\ \ You can easily move your services between projects.1. From the service Dashboard Overview tab, select Move Service.2. Click Move to successfully move your service. You can only move services to projects you own.](https://docs.elest.io/books/services-dashboard/page/move-a-service-to-another-project)  [#### Elestio API](https://docs.elest.io/books/elestio-api) [#### Software & OS Updates configuration\ \ Services Dashboard Overview\ \ OS & Software updates are enabled by default when you create a new service. You can configure when updates are applied - by the minute, hour, or day. All times configured in the dashboard are UTC (Coordinated Universal Time). It's also possible to start a...](https://docs.elest.io/books/services-dashboard/page/software-os-updates-configuration) [#### CI/CD Pipelines\ \ Go from source code to production with CI/CD Pipelines. We support Github, Gitlab & docker registries as source. Pipelines can be deployed on any cloud, even on-premise.](https://docs.elest.io/books/cicd-pipelines) [#### VSCode\ \ Services Dashboard Tools\ \ From the Tools tab in the service overview, click on VS Code button to start VS Code in the browser directly in the context of your service.From there you can edit the configuration, download or upload files with drag&drop on the left column or open a terminal...](https://docs.elest.io/books/services-dashboard/page/vscode) [#### Volumes\ \ Elestio has the top 6 cloud partners in 110 locations across 29 countries (AWS Lightsail, Digital Ocean, Scaleway, Vultr, Linode, and Hetzner).](https://docs.elest.io/books/volumes) [#### File Explorer\ \ Services Dashboard Tools\ \ From the Tools tab in the service overview, click on the "File Explorer" button. The first launch can take 1-2 minutes because File Explorer is installed on your service. The next launch is nearly instant. This will open a pop-up window, providing you with...](https://docs.elest.io/books/services-dashboard/page/file-explorer) [#### Elestio Terraform provider\ \ The Elestio Terraform provider is a plugin that enables users to manage resources on the Elestio platform using Terraform. Terraform is a tool that allows users to define and manage infrastructure as code, enabling them to automate the process of creating, ...](https://docs.elest.io/books/elestio-terraform-provider) [#### DB Migration service\ \ Databases](https://docs.elest.io/books/databases/chapter/db-migration-service) [#### Web Terminal\ \ Services Dashboard Tools\ \ From the Tools tab in the service overview, click on the "Terminal" button The first launch can take 1-2 minutes because the Web terminal is installed on your service. The next launch is nearly instant.](https://docs.elest.io/books/services-dashboard/page/web-terminal) [#### Frequently Asked Questions\ \ Here are some most commonly asked questions\ \ question](https://docs.elest.io/books/frequently-asked-questions) [#### DB Clusters\ \ Databases](https://docs.elest.io/books/databases/chapter/db-clusters) Back to top --- # Security | docs.elest.io [Skip to main content](https://docs.elest.io/books/security#main-content) Info Content Security ======== [#### Overview\ \ We automatically setup all services with several layers of security activated by default.This inc...](https://docs.elest.io/books/security/page/overview) [#### Custom domain and automated encryption (SSL/TLS)\ \ If you have activated the firewall on your service ensure port 80 is open or else certificate cre...](https://docs.elest.io/books/security/page/custom-domain-and-automated-encryption-ssltls) [#### Nginx advanced configuration\ \ Edit the website nginx configuration From the service overview screen it's possible to edit the ...](https://docs.elest.io/books/security/page/nginx-advanced-configuration) [#### Using Cloudflare\ \ Cloudflare DNS: If you wish to use Cloudflare for DNS ONLY, you can configure it just like any o...](https://docs.elest.io/books/security/page/using-cloudflare) [#### Network Firewall\ \ By default, we only open the ports necessary for the application you have deployed.  How can I r...](https://docs.elest.io/books/security/page/network-firewall) [#### IP rate limiter\ \ From the Dashboard, click on Security then Rate Limiter > Show Options.From here, you can easily ...](https://docs.elest.io/books/security/page/ip-rate-limiter) [#### Output Cache\ \ From the Dashboard, navigate to the Security tab and select Show Options under Output Cache.From ...](https://docs.elest.io/books/security/page/output-cache) [#### Termination protection & grace period\ \ You can enable or disable the Termination protection option from your Dashboard Overview, using t...](https://docs.elest.io/books/security/page/termination-protection-grace-period) [#### Manage SSH Keys\ \ From the Dashboard, navigate to the Security tab and select the Show Options button to Manage SSH...](https://docs.elest.io/books/security/page/manage-ssh-keys) [#### How to connect to an Elestio service with SSH keys\ \ Connecting to an Elestio service Using Existing SSH Keys from a Mac/Linux Machine Step 1: Check ...](https://docs.elest.io/books/security/page/how-to-connect-to-an-elestio-service-with-ssh-keys) [#### SMTP service\ \ All deployed services include a basic preconfigured SMTP service, useful for sending alerts and n...](https://docs.elest.io/books/security/page/smtp-service) [#### Multi-factor authentication\ \ By default, Elestio uses Email-based MFA, each time you log in to Elestio we will send you an ema...](https://docs.elest.io/books/security/page/multi-factor-authentication) [#### How to Enable or Disable IPv6 on a Linux Virtual Machine\ \ IPv6 is the latest version of the Internet Protocol, designed to address the limitations of IPv4....](https://docs.elest.io/books/security/page/how-to-enable-or-disable-ipv6-on-a-linux-virtual-machine) [#### How to configure NGINX to Listen on IPv6\ \ IPv6 is quickly becoming standard. If your VM already supports it, you just need to tell NGINX to...](https://docs.elest.io/books/security/page/how-to-configure-nginx-to-listen-on-ipv6) [#### How to secure your application with Cloudflare Tunnel\ \ What is Cloudflare Tunnel? Cloudflare Tunnel is a secure solution that connects your web appli...](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel) ### Search Results Clear Search Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=7#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Invoices\ \ Billing\ \ Easily view, open or download your invoices in one place via your User Profile.Navigate to your User Profile via the user icon at the top left of the Dashboard above the Main menu.Select the Invoices tabInvoices are generated when you add credits to your accou...](https://docs.elest.io/books/billing/page/invoices) [#### Terms & Conditions\ \ Legal & Compliance\ \ Elest.io is a website owned by ELESTIO LIMITED, a company based in Ireland with its registered office at 66 Fitzwilliam Square, Dublin 2 D02 AT27, Company Registration Number 755058. We provide our users with access to certain tools that allow them to deploy ...](https://docs.elest.io/books/legal-compliance/page/terms-conditions) [#### Privacy policies\ \ Legal & Compliance\ \ Elestio (“Elestio” / “We”) is aware that users of Elest.io and its related applications (“Users” / “You”) value their privacy. The purpose of this Privacy Statement is to provide You with relevant information regarding the use and disclosure of personal inform...](https://docs.elest.io/books/legal-compliance/page/privacy-policies) [#### Service Support Plans\ \ Services Dashboard Overview\ \ Elestio offers 3 levels of support.Our Level 1 Support plan is included for free with all deployed services.Levels 2 and 3 are recommended for important workloads where you need a guaranteed response time, longer backup retention, and priority support through ...](https://docs.elest.io/books/services-dashboard/page/service-support-plans) [#### Manage SSH Keys\ \ Security\ \ From the Dashboard, navigate to the Security tab and select the Show Options button to Manage SSH Keys.From here, you can add or remove SSH keys allowed on the server.Add an SSH keyClick on the Add key. Simply give your key a title and save!Deleting an SSH key...](https://docs.elest.io/books/security/page/manage-ssh-keys) [#### Per project details\ \ Billing\ \ To view a project's billing details, select Billing from the left menu, where you'll find a recap and details of all billable items.](https://docs.elest.io/books/billing/page/per-project-details) [#### Payment options\ \ Billing\ \ Never worry about your elestio account balance running out or being too low anymore by using our auto refill option to automatically top it up.To Enable auto-refill. Select the Account tab from the left sidebar menu. Select the Payment Options tab. Toggle...](https://docs.elest.io/books/billing/page/payment-options) [#### Leave a project\ \ Projects & Teams Projects\ \ Read-only users are able to leave projects. 1. Select Members in the left menu2. Select the Leave Project icon to the right of the project you wish to leave](https://docs.elest.io/books/projects-teams/page/leave-a-project) [#### Add a member\ \ Projects & Teams Teams\ \ Want to invite someone to your team?To invite a member:1. Select Members from the Main menu on the left of the Dashboard2. Press the Add Member button3. Enter the member's email address and select their access level4. Press Send Invitation Admins are authoriz...](https://docs.elest.io/books/projects-teams/page/add-a-member) [#### Delete a member\ \ Projects & Teams Teams\ \ You can easily delete a member from your project when and if you need to.Only admins can delete other members.To delete a member:1. Select Members from the Main menu tab on the left of the Dashboard.2. Click on the user icon to the right of the user you wish t...](https://docs.elest.io/books/projects-teams/page/delete-a-member) [#### MySQL cluster with Multi-master or Replica mode\ \ Databases DB Clusters\ \ If you can’t afford for your database to be down for even a few minutes, a Multi-Master cluster is a great option to ensure high availability. A multi-master scenario means that one node can be taken offline (e.g. for maintenance or upgrade purposes) without ...](https://docs.elest.io/books/databases/page/mysql-cluster-with-multi-master-or-replica-mode) [#### KeyDB (Redis compatible) with Multi-master or Replica mode\ \ Databases DB Clusters\ \ If you can’t afford for your database to be down for even a few minutes, you need a Multi-Master cluster to ensure high availability. This means that one node can be taken offline (e.g. for maintenance or upgrade purposes) without impacting availability, as th...](https://docs.elest.io/books/databases/page/keydb-redis-compatible-with-multi-master-or-replica-mode) [#### Automated External Backups (S3)\ \ Backups\ \ External backups are stored in your S3 bucket, so you own your backups directly. Elestio's external backup service is compatible with AWS S3 and any S3-compatible provider. To enable external backups from the service dashboard click on the Backups tab, then c...](https://docs.elest.io/books/backups/page/automated-external-backups-s3) [#### Software logs, configuration, restart app, change version\ \ Services Dashboard Overview\ \ From the service overview, you can open live logs with the "View app logs" button You can change the .env & docker-compose.yml configuration if you click on "Update config" button If you click on "Update Config" you will be able to edit the configuration...](https://docs.elest.io/books/services-dashboard/page/software-logs-configuration-restart-app-change-version) [#### BYOVM with AWS EC2\ \ Cloud Providers\ \ You can deploy an Elestio service on your own AWS account with BYOVM To do it, you will need to create a VM on AWS EC2, first connect to AWS EC2 dashboard:  https://console.aws.amazon.com/ec2/v2/home#Instances:instanceState=running There click on "Lau...](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2) [#### BYOVM with AWS EC2 (Beta AWS UI)\ \ Cloud Providers\ \ This approach is outdated. Instead, you can use our Bring Your Own AWS Account(BYO-AWS) provider option. You can deploy an Elestio service on your own AWS account with BYOVM To do it, you will need to create a VM on AWS EC2, first connect to the AWS ...](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui) [#### Overview\ \ Load balancers\ \ Load balancers are essential to achieve High Availability (HA) and horizontal scalability.  Most load balancers from cloud providers are limited to balance traffic only inside network of the cloud provider, also to get SSL termination for your custom domains ...](https://docs.elest.io/books/load-balancers/page/overview) [#### Create a new load balancer\ \ Load balancers\ \ To create a new load balancer, go to the dashboard and click on Load Balancer on the left side https://dash.elest.io/default/Elestio-services/load-balancer There, select your cloud provider (or BYOVM) then select your preferred region. Then select one o...](https://docs.elest.io/books/load-balancers/page/create-a-new-load-balancer) [#### Update load balancer configuration\ \ Load balancers\ \ Once your load balancer is deployed, you will be able to edit its configuration at any time from the UI After making changes to your configuration (targets, forwarding rules, advanced configuration), click on the "Apply changes" button, this should take 5-1...](https://docs.elest.io/books/load-balancers/page/update-load-balancer-configuration) [#### API Documentation\ \ Elestio API\ \ Elestio is an API first company, everything we do is through API's. Everything we do on our dashboard can be done through our API. We have created an OpenAPI 3 definition with swagger. Open the Elestio API documentation](https://docs.elest.io/books/elestio-api/page/api-documentation) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=4#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Redis](https://docs.elest.io/books/redis) [#### Cluster Management\ \ MySQL](https://docs.elest.io/books/mysql/chapter/cluster-management) [#### Vultr\ \ Cloud Providers\ \ VULTR is a great cloud provider with a large number of regions and datacenters available. They provide good network and overall reliability. Supported Services Compute ✅ High Frequency CPU Private network ✅ Firewall ✅ Volumes ✅ ...](https://docs.elest.io/books/cloud-providers/page/vultr) [#### ClickHouse](https://docs.elest.io/books/clickhouse) [#### How to Connect\ \ Hydra](https://docs.elest.io/books/hydra/chapter/how-to-connect) [#### Linode\ \ Cloud Providers\ \ Linode is a great cloud provider with a large number of regions and datacenters available. They provide good network and overall reliability. Supported Services Compute ✅ Private network ✅ Firewall ✅ Volumes ✅ Floating IP ✅ ...](https://docs.elest.io/books/cloud-providers/page/linode) [#### Keycloak](https://docs.elest.io/books/keycloak) [#### How-To Guides\ \ Hydra](https://docs.elest.io/books/hydra/chapter/how-to-guides) [#### Hetzner\ \ Cloud Providers\ \ Hetzner is an award-winning provider, born and based in Germany. They are one of our favorite providers because they are reliable and cost effective. Most of the time, you get twice the CPU & RAM for the same price compared to other providers.We also love Hetz...](https://docs.elest.io/books/cloud-providers/page/hetzner) [#### KeyDB](https://docs.elest.io/books/keydb) [#### Database Migration\ \ Hydra](https://docs.elest.io/books/hydra/chapter/database-migration) [#### BYOVM (Bring Your Own VM)\ \ Cloud Providers\ \ You can also deploy into your own cloud account from any cloud provider (Azure, GCP, Alibaba, Oracle, etc.) or from an VM hosted on-premise. In these instances, you are responsible for the relationship with your provider while we take care of the management si...](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm) [#### Valkey](https://docs.elest.io/books/valkey) [#### Cluster Management\ \ Hydra](https://docs.elest.io/books/hydra/chapter/cluster-management) [#### How to Connect\ \ TimescaleDB](https://docs.elest.io/books/timescaledb/chapter/how-to-connect) [#### Overview\ \ Backups\ \ A robust backup strategy is fundamental to keeping data safe. By default, Elest.io automates a 3-2-1 backup strategy for all new services.3 copies of your data exist at all times.2 are kept in geographically distinct data centers in your selected region.1 bac...](https://docs.elest.io/books/backups/page/overview) [#### How-To Guides\ \ TimescaleDB](https://docs.elest.io/books/timescaledb/chapter/how-to-guides) [#### Manual Local backups\ \ Backups\ \ Local backups are useful if you need to take a quick backup of a small dataset locally and want to download the backup to your computer, or just be able to restore it later quickly. Local backups only contain the software's data volume, not the OS or software...](https://docs.elest.io/books/backups/page/manual-local-backups) [#### Database Migration\ \ TimescaleDB](https://docs.elest.io/books/timescaledb/chapter/database-migration) [#### Automated Remote Backups (Borg)\ \ Backups\ \ Remote backups are sent to another datacenter in the same continent that your service (Ashburn USA for the US, Germany for EU zone and rest of the world). We use Borg Backups to do incremental backups with deduplication. It's very fast and efficient. This kind...](https://docs.elest.io/books/backups/page/automated-remote-backups-borg) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=5#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Cluster Management\ \ TimescaleDB](https://docs.elest.io/books/timescaledb/chapter/cluster-management) [#### Automated VM Snapshots\ \ Backups\ \ VM snapshots are made using the provider's snapshot API and are stored in the same region where you have your service. It is only available under Support Plans Levels 2 and 3. It's a full snapshot of the VM, meaning it contains everything: OS, Apps, data, et...](https://docs.elest.io/books/backups/page/automated-vm-snapshots) [#### How to Connect\ \ Redis](https://docs.elest.io/books/redis/chapter/how-to-connect) [#### How-To Guides\ \ Redis](https://docs.elest.io/books/redis/chapter/how-to-guides) [#### Overview\ \ Projects & Teams Projects\ \ Project is a collection of services. It's useful to group your services by project name. All services are billed to the owner of the project. You can invite coworkers as read-only or admins of your projects, this way they can use the different resources safel...](https://docs.elest.io/books/projects-teams/page/overview) [#### Database Migration\ \ Redis](https://docs.elest.io/books/redis/chapter/database-migration) [#### Manage projects\ \ Projects & Teams Projects\ \ Changing project settings Select Settings from the left menu.You can easily rename your project, change the technical email target and update the project description. Don't forget to press Save to store your update!](https://docs.elest.io/books/projects-teams/page/manage-projects) [#### Cluster Management\ \ Redis](https://docs.elest.io/books/redis/chapter/cluster-management) [#### How to Connect\ \ ClickHouse](https://docs.elest.io/books/clickhouse/chapter/how-to-connect) [#### Delete a project\ \ Projects & Teams Projects\ \ How do I delete a project? Only owners and admins of projects have permission to delete a project.1. Click on Project Settings in the left menu2. Select Delete Project A user must always have at least one project. In order to delete a project, it must be fr...](https://docs.elest.io/books/projects-teams/page/delete-a-project) [#### How-To Guides\ \ ClickHouse](https://docs.elest.io/books/clickhouse/chapter/how-to-guides) [#### Database Migration\ \ ClickHouse](https://docs.elest.io/books/clickhouse/chapter/database-migration) [#### Overview\ \ Projects & Teams Teams\ \ Creating a project assigns you an administrator role as the project owner. As an administrator (Admin) you can invite people to a project and assign them specific access.To invite a member:1. Select Members from the left menu2. Press the Add Member button3. En...](https://docs.elest.io/books/projects-teams/page/overview-6Hh) [#### Cluster Management\ \ ClickHouse](https://docs.elest.io/books/clickhouse/chapter/cluster-management) [#### How to Connect\ \ Keycloak](https://docs.elest.io/books/keycloak/chapter/how-to-connect) [#### How-To Guides\ \ Keycloak](https://docs.elest.io/books/keycloak/chapter/how-to-guides) [#### Overview\ \ Security\ \ We automatically setup all services with several layers of security activated by default.This includes: Automated SSL / TLS Network Firewall IP Rate Limiter Output Cache Accidental termination protection & Grace period Manage SSH Keys Each of these ...](https://docs.elest.io/books/security/page/overview) [#### Realm & Configuration Migration\ \ Keycloak](https://docs.elest.io/books/keycloak/chapter/realm-configuration-migration) [#### Custom domain and automated encryption (SSL/TLS)\ \ Security\ \ If you have activated the firewall on your service ensure port 80 is open or else certificate creation/renewal will fail Access the "Manage SSL Domains" option within the "Custom Domain Names" row located in the overview tab of the service dashboard. From ...](https://docs.elest.io/books/security/page/custom-domain-and-automated-encryption-ssltls) [#### Cluster Management\ \ Keycloak](https://docs.elest.io/books/keycloak/chapter/cluster-management) Back to top --- # Search for [book] {type:page} | docs.elest.io [Skip to main content](https://docs.elest.io/search?term=%5Bbook%5D+{type:page}#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 0 total results found No items available Back to top --- # Services Dashboard | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard#main-content) Info Content Services Dashboard ================== [#### Overview](https://docs.elest.io/books/services-dashboard/chapter/overview) 15 Pages [#### Service protection\ \ Elestio services can be protected against accidental deletion by enabling the Termination protect...](https://docs.elest.io/books/services-dashboard/page/service-protection) [#### Power Management\ \ You may manage power management on an elestio by using the Reboot, Reset, Shutdown, Power On, and...](https://docs.elest.io/books/services-dashboard/page/power-management) [#### Admin UI\ \ Most supported softwares have an administrative web interface. Selecting the Display Admin UI bu...](https://docs.elest.io/books/services-dashboard/page/admin-ui) [#### Database credentials\ \ This only applies to database software. You can view your database software in your service Dash...](https://docs.elest.io/books/services-dashboard/page/database-credentials) [#### Service Support Plans\ \ Elestio offers 3 levels of support.Our Level 1 Support plan is included for free with all deploye...](https://docs.elest.io/books/services-dashboard/page/service-support-plans) [#### Selected / change software version\ \ You can select another version of your deployed software in your service's Dashboard Overview.1. ...](https://docs.elest.io/books/services-dashboard/page/selected-change-software-version) [#### Bandwidth & Networks\ \ In the service Dashboard Overview tab, you will also find a recap of your bandwidth usage for the...](https://docs.elest.io/books/services-dashboard/page/bandwidth-networks) [#### Move a Service to Another Project\ \ You can easily move your services between projects.1. From the service Dashboard Overview tab, se...](https://docs.elest.io/books/services-dashboard/page/move-a-service-to-another-project) [#### Software & OS Updates configuration\ \ OS & Software updates are enabled by default when you create a new service. You can configure ...](https://docs.elest.io/books/services-dashboard/page/software-os-updates-configuration) [#### Upgrade service plan\ \ In the service overview, disable the termination protection then shut down the service, once done...](https://docs.elest.io/books/services-dashboard/page/upgrade-service-plan) [#### Upgrade support plan\ \ From the service overview, click on "Upgrade plan" on the support plan row to change your support...](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan) [#### Delete a service\ \ To delete a service, ensure that termination protection is disabled then click on "Delete service...](https://docs.elest.io/books/services-dashboard/page/delete-a-service) [#### Software logs, configuration, restart app, change version\ \ From the service overview, you can open live logs with the "View app logs" button You can ch...](https://docs.elest.io/books/services-dashboard/page/software-logs-configuration-restart-app-change-version) [#### Resync\ \ After cloning a service, you will have a new option visible in the service overview: Resync From...](https://docs.elest.io/books/services-dashboard/page/resync) [#### Increase AWS Main (Disk Or Volume) Size\ \ Your AWS provider instance disc size can be changed at any time between 10 GB and 10 TB. On AWS ...](https://docs.elest.io/books/services-dashboard/page/increase-aws-main-disk-or-volume-size) [#### Tools](https://docs.elest.io/books/services-dashboard/chapter/tools) 4 Pages [#### VSCode\ \ From the Tools tab in the service overview, click on VS Code button to start VS Code in the brows...](https://docs.elest.io/books/services-dashboard/page/vscode) [#### File Explorer\ \ From the Tools tab in the service overview, click on the "File Explorer" button. The first launc...](https://docs.elest.io/books/services-dashboard/page/file-explorer) [#### Web Terminal\ \ From the Tools tab in the service overview, click on the "Terminal" button The first launch can ...](https://docs.elest.io/books/services-dashboard/page/web-terminal) [#### Reset SSH/SFTP Password\ \ By default, password authentication is disabled. For security reasons, we recommend using SSH Pub...](https://docs.elest.io/books/services-dashboard/page/reset-sshsftp-password) [#### Backups\ \ Please check the Backups details page](https://docs.elest.io/books/services-dashboard/page/backups) [#### Metrics\ \ Metrics tabs allow you to view your service's metrics in real-time.You can configure the update p...](https://docs.elest.io/books/services-dashboard/page/metrics) [#### Alerts\ \ Alerts are enabled by default on all new services. You can enable or completely disable alerts. ...](https://docs.elest.io/books/services-dashboard/page/alerts) [#### Notes\ \ The notes tab is useful to save textual notes about service, for yourself or other team members](https://docs.elest.io/books/services-dashboard/page/notes) ### Search Results Clear Search Back to top --- # Projects & Teams | docs.elest.io [Skip to main content](https://docs.elest.io/books/projects-teams#main-content) Info Content Projects & Teams ================ [#### Projects](https://docs.elest.io/books/projects-teams/chapter/projects) 6 Pages [#### Overview\ \ Project is a collection of services. It's useful to group your services by project name. All ser...](https://docs.elest.io/books/projects-teams/page/overview) [#### Create a project\ \ Click on Project dropdown and Create new Project 2. Project information - Give a name to yo...](https://docs.elest.io/books/projects-teams/page/create-a-project) [#### Manage projects\ \ Changing project settings Select Settings from the left menu.You can easily rename your project,...](https://docs.elest.io/books/projects-teams/page/manage-projects) [#### Delete a project\ \ How do I delete a project? Only owners and admins of projects have permission to delete a projec...](https://docs.elest.io/books/projects-teams/page/delete-a-project) [#### Leave a project\ \ Read-only users are able to leave projects. 1. Select Members in the left menu2. Select the Leav...](https://docs.elest.io/books/projects-teams/page/leave-a-project) [#### Update AWS Account Access and Secret Credentials\ \ You can update your AWS Access and Secret Credentials at any time inside your project settings. ...](https://docs.elest.io/books/projects-teams/page/update-aws-account-access-and-secret-credentials) [#### Teams](https://docs.elest.io/books/projects-teams/chapter/teams) 3 Pages [#### Overview\ \ Creating a project assigns you an administrator role as the project owner. As an administrator (A...](https://docs.elest.io/books/projects-teams/page/overview-6Hh) [#### Add a member\ \ Want to invite someone to your team?To invite a member:1. Select Members from the Main menu on th...](https://docs.elest.io/books/projects-teams/page/add-a-member) [#### Delete a member\ \ You can easily delete a member from your project when and if you need to.Only admins can delete o...](https://docs.elest.io/books/projects-teams/page/delete-a-member) ### Search Results Clear Search Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=8#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Resync\ \ Services Dashboard Overview\ \ After cloning a service, you will have a new option visible in the service overview: Resync From the service overview, click on "Resync" button to resynchronize your cloned service from the orgin. After a confirmation, the process will start and will do: C...](https://docs.elest.io/books/services-dashboard/page/resync) [#### Subcontractors\ \ Legal & Compliance\ \ Subcontractors & Sub-processors A sub-processor is a third-party data processor engaged by Elestio who has or potentially will have access to or process Protected Data. Elestio engages different types of sub-processors to perform various functions as explaine...](https://docs.elest.io/books/legal-compliance/page/subcontractors) [#### Overview\ \ CI/CD Pipelines\ \ Elestio is the simplest and fastest way to deploy your source code from github/gitlab/docker registry to production. In 3 steps you can deploy any kind of project, frontend, backend, API, DB, you name it. Select your source code in Github / Gitlab or fro...](https://docs.elest.io/books/cicd-pipelines/page/overview) [#### Deploy your first CI/CD pipeline on Elestio\ \ CI/CD Pipelines\ \ You are about to learn how to deploy an application from a Git repository to production on any cloud. First, open the Elestio dashboard and click on CI/CD  1) Select your source From there click on Github or Gitlab, and you will be asked to provide author...](https://docs.elest.io/books/cicd-pipelines/page/deploy-your-first-cicd-pipeline-on-elestio) [#### Deploy docker-compose apps (Wordpress, MySQL, Redis, Keycloak ...)\ \ CI/CD Pipelines\ \ You are about to learn how to deploy docker-compose applications to a CI/CD target. This is useful when you don't need a Git workflow and your images are already available on a public or private docker registry.  Use cases: Deploy one or multiple instances...](https://docs.elest.io/books/cicd-pipelines/page/deploy-docker-compose-apps-wordpress-mysql-redis-keycloak) [#### Create your own template (elestio.yml)\ \ CI/CD Pipelines\ \ You can create your own template to be deployed on Elestio for yourself (private repo) or for anyone (public repo). We recommend that you fork one of our sample repositories as a base and modify it to meet your requirements:  Samples repositories for the mos...](https://docs.elest.io/books/cicd-pipelines/page/create-your-own-template-elestioyml) [#### Pipelines migration, move pipelines between CI/CD targets safely\ \ CI/CD Pipelines\ \ In several situations, you might want to move a deployed CI/CD pipeline from one target to another one. On Elestio, you can safely move a pipeline between targets even if the pipeline contains data. Let's consider a few situations: Your CI/CD target is ove...](https://docs.elest.io/books/cicd-pipelines/page/pipelines-migration-move-pipelines-between-cicd-targets-safely) [#### Multi-factor authentication\ \ Security\ \ By default, Elestio uses Email-based MFA, each time you log in to Elestio we will send you an email with a one-time code to enter into our UI to be able to connect. This protection is in place to enforce security and avoid account hacking. We also have TOTP-b...](https://docs.elest.io/books/security/page/multi-factor-authentication) [#### Custom domains on CI/CD pipelines\ \ CI/CD Pipelines\ \ You can add any number of custom domain names on your CI/CD pipeline, Elestio will automatically configure the routing of the traffic and SSL termination / certificate creation and renewals. To add a custom domain on your pipeline click on "Domain Management"...](https://docs.elest.io/books/cicd-pipelines/page/custom-domains-on-cicd-pipelines) [#### Free trial\ \ Billing\ \ Elestio offers a 3-day free trial with $20 in credits, during which you can launch up to 2 services. In addition to the services in our catalog, you have access to load balancers, volumes, and CI/CD pipelines. Domain names are the only thing that cannot be ac...](https://docs.elest.io/books/billing/page/free-trial) [#### Newsletter\ \ Getting started\ \ You can get the most recent information about Elestio features, supported software, and tips by subscribing to the elestio newsletter. You can subscribe to the elestio newsletter during sign-up by checking the box (Sign up for our newsletter) and later ma...](https://docs.elest.io/books/getting-started/page/newsletter) [#### How to Deploy React App on Elestio\ \ CI/CD Pipelines\ \ So you made a React web application and want to deploy it to the cloud 🚀 You probably heard about Kubernetes (and all its complexity) or various options to deploy your apps like Heroku, Render Fly, or Railways. They all have something in common, those product...](https://docs.elest.io/books/cicd-pipelines/page/how-to-deploy-react-app-on-elestio) [#### How to Deploy NodeJs-express app with a static front-end in a pug on Elestio\ \ CI/CD Pipelines\ \ So you made a static full stack frontend pug with nodejs backend application and want to deploy it to the cloud 🚀 You probably heard about Kubernetes (and all its complexity) or various options to deploy your apps like Heroku, Render Fly, or Railways. They al...](https://docs.elest.io/books/cicd-pipelines/page/how-to-deploy-nodejs-express-app-with-a-static-front-end-in-a-pug-on-elestio) [#### Clone CI/CD pipeline\ \ CI/CD Pipelines\ \ When distributing your project pipeline across the Production, Staging, and Test environments, you might want to copy a deployed CI/CD pipeline from one target to another or the same target.When using Elestio, you can safely clone a pipeline between identical,...](https://docs.elest.io/books/cicd-pipelines/page/clone-cicd-pipeline) [#### Deploy examples & apps on Elestio using the "clone template" feature\ \ CI/CD Pipelines\ \ This tutorial will show you how to use our clone template feature in CI/CD. We're going to use a Simple Javascript web application, but you can use any template and deploy it in the same way. 🚀 The clone template feature was similar to forking our examples fr...](https://docs.elest.io/books/cicd-pipelines/page/deploy-examples-apps-on-elestio-using-the-clone-template-feature) [#### Deploy own docker-compose image using Elestio "Custom docker-compose"\ \ CI/CD Pipelines\ \ This tutorial will walk you through the process of deploying your own custom Docker image to the Elestio cloud. Use cases: Deploy one or multiple instances of stateful apps like Wordpress / Directus / MySQL / Redis / RabbitMQ / ... Deploy an internal serv...](https://docs.elest.io/books/cicd-pipelines/page/deploy-own-docker-compose-image-using-elestio-custom-docker-compose) [#### Create a new volume\ \ Volumes\ \ To create a new volume in an Elestio: Step 1: Open Elestio Dashboard and then click the volume tab in the left sidebar. Step 2: Select Service Cloud Provider Elestio has the top 5 cloud partners in 85 locations across 27 countries (AWS Lightsail, Di...](https://docs.elest.io/books/volumes/page/create-a-new-volume) [#### Deploy examples & apps on Elestio using the "Import Third-Party Git Repository" feature\ \ CI/CD Pipelines\ \ This tutorial will walk you through the process of deploying GitHub, GitLab, or Bitbucket public repositories in CI/CD using our Import Third-Party Git Repository feature. In our example, we'll use a Simple JavaScript web application public repository, but you...](https://docs.elest.io/books/cicd-pipelines/page/deploy-examples-apps-on-elestio-using-the-import-third-party-git-repository-feature) [#### Elestio Data Processing Agreement\ \ Legal & Compliance\ \ Last Modified: Feb 06, 2025 1. Background This Data Processing Agreement (‘’DPA’’) is attached to the General Terms (available at https://elest.io/terms and forms an inseparable part of the Agreement entered into by Elestio limited (hereinafter “Elestio”) an...](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement) [#### Documentation\ \ Elestio Terraform provider\ \ With Elestio’s Terraform provider, you can use an open-source infrastructure as code software tool to declare and manage your cloud services. See the Elestio Terraform provider documentation to learn about the services and resources, and visit the GitHub...](https://docs.elest.io/books/elestio-terraform-provider/page/documentation) Back to top --- # Books | docs.elest.io [Skip to main content](https://docs.elest.io/books?page=2#main-content) Info Content Books ===== Sort Name * [Name](https://docs.elest.io/books?page=2#) * [Created Date](https://docs.elest.io/books?page=2#) * [Updated Date](https://docs.elest.io/books?page=2#) [MySQL\ -----\ \ Created 8 months ago\ \ Updated 8 months ago](https://docs.elest.io/books/mysql) [PostgreSQL\ ----------\ \ Created 9 months ago\ \ Updated 9 months ago](https://docs.elest.io/books/postgresql) [Projects & Teams\ ----------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/projects-teams) [Redis\ -----\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/redis) [Security\ --------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/security) [Services Dashboard\ ------------------\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/services-dashboard) [Supported Softwares\ -------------------\ \ Our catalog is comprised of over 350+ open source software services. We plan to continue adding to our catalog each month, so k...\ \ Created 3 years ago\ \ Updated 1 year ago](https://docs.elest.io/books/supported-softwares) [TimescaleDB\ -----------\ \ Created 7 months ago\ \ Updated 7 months ago](https://docs.elest.io/books/timescaledb) [Valkey\ ------\ \ Created 5 months ago\ \ Updated 5 months ago](https://docs.elest.io/books/valkey) [Volumes\ -------\ \ Elestio has the top 6 cloud partners in 110 locations across 29 countries (AWS Lightsail, Digital Ocean, Scaleway, Vultr, Linod...\ \ Created 3 years ago\ \ Updated 2 years ago](https://docs.elest.io/books/volumes) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=9#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Get started\ \ Elestio Terraform provider\ \ Build your first Elestio Terraform project This exemple shows the setup for a Terraform project containing a single PostgreSQL service, and shows off some useful commands to stand up (and destroy) your Elestio infrastructure. You can check this repository ...](https://docs.elest.io/books/elestio-terraform-provider/page/get-started) [#### Providers, datacenters and server types\ \ Elestio Terraform provider\ \ This guide explain how to find available options for provider\_name, datacenter and server\_type variables when you want to manage a service resource with terraform : resource "elestio\_vault" "my\_vault" { ... provider\_name = "hetzner" datacente...](https://docs.elest.io/books/elestio-terraform-provider/page/providers-datacenters-and-server-types) [#### Import an existing resource\ \ Elestio Terraform provider\ \ You can use the terraform import command to import in the Elestio state an existing project or service already running. Project # Import a project by specifying the project ID. terraform import elestio\_project.myawesomeproject project\_id Declare the ...](https://docs.elest.io/books/elestio-terraform-provider/page/import-an-existing-resource) [#### Why am I receiving a low credit warning even though auto recharge is enabled?\ \ Frequently Asked Questions\ \ Users who have credits remaining for less than 7 days receive a low credit warning email once per day.To avoid this, increase your credit warning limit to a level corresponding to your cash burn rate to satisfy the 7-day credit requirement. You can change you...](https://docs.elest.io/books/frequently-asked-questions/page/why-am-i-receiving-a-low-credit-warning-even-though-auto-recharge-is-enabled) [#### Can I install more than one software on the same VM?\ \ Frequently Asked Questions\ \ Our dedicated services are running in complete isolation, so one service equals one VM. Using our CI/CD system, you can install multiple software's on a single VM.](https://docs.elest.io/books/frequently-asked-questions/page/can-i-install-more-than-one-software-on-the-same-vm)  [#### Can I migrate/clone my service to another cloud or region?\ \ Frequently Asked Questions\ \ Yes, you can migrate or clone a running service to any other target cloud or region by simply clicking the "clone" button on the service dashboard.](https://docs.elest.io/books/frequently-asked-questions/page/can-i-migrateclone-my-service-to-another-cloud-or-region)  [#### Is it possible to restrict access to my virtual machine (with a firewall)?\ \ Frequently Asked Questions\ \ Yes, every service has a pre-configured firewall that allows access to the internet through ports specific to certain applications. From the service dashboard, you can easily restrict access to a single or a range of IPs. Learn more about setting your firewal...](https://docs.elest.io/books/frequently-asked-questions/page/is-it-possible-to-restrict-access-to-my-virtual-machine-with-a-firewall) [#### What type of support does Elestio offer?\ \ Frequently Asked Questions\ \ Email and community support via our forum is available to everyone with our Test plan, with no SLA. Staging Support plans offers a guaranteed response within 2 business days and priority queueing for support tickets, and email support. Production Support pla...](https://docs.elest.io/books/frequently-asked-questions/page/what-type-of-support-does-elestio-offer) [#### Can my software services communicate between different cloud providers safely?\ \ Frequently Asked Questions\ \ Every Elestio project establishes a unique and secure encrypted virtual network, allowing services within the project to communicate through private IPv4 addresses. This communication occurs with nearly line-speed throughput, regardless of location or service...](https://docs.elest.io/books/frequently-asked-questions/page/can-my-software-services-communicate-between-different-cloud-providers-safely) [#### Can I deploy Elestio services on-premise or on my existing cloud infrastructure?\ \ Frequently Asked Questions\ \ Yes, you can connect any on-premises or cloud VM managed services dashboard with our "Bring Your Own VM" (BYOVM) feature. Any software we provide can be installed on your own infrastructure, and it will be handled just like any other virtual machine (VM) we ru...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-deploy-elestio-services-on-premise-or-on-my-existing-cloud-infrastructure) [#### AWS EC2 or (BYOAWS) Bring Your Own AWS Account\ \ Cloud Providers\ \ AWS is the largest cloud provider with one of the best networks available and a large number of regions and data centers. Supported Services Compute ✅ Private network ✅ Firewall ✅ Volumes ✅ Elastic IP ✅ Snapshots ✅ ...](https://docs.elest.io/books/cloud-providers/page/aws-ec2-or-byoaws-bring-your-own-aws-account) [#### Create a new service with Bring your own AWS Account (BYOAWS)\ \ Getting started\ \  To create a new service, first, open Elestio Dashboard, then go to services from the left sidebar and click the button to create a new service. The first step is to choose a template or service to deploy and then click Deploy to move on to the next step....](https://docs.elest.io/books/getting-started/page/create-a-new-service-with-bring-your-own-aws-account-byoaws) [#### Update AWS Account Access and Secret Credentials\ \ Projects & Teams Projects\ \ You can update your AWS Access and Secret Credentials at any time inside your project settings. To update AWS account credentials, go to the project settings in the left sidebar and then to the AWS Account tab. Enter your AWS Account Administration New acces...](https://docs.elest.io/books/projects-teams/page/update-aws-account-access-and-secret-credentials) [#### Increase AWS Main (Disk Or Volume) Size\ \ Services Dashboard Overview\ \ Your AWS provider instance disc size can be changed at any time between 10 GB and 10 TB. On AWS Disk, you can only increase the disc size, not decrease it. According to AWS policy, after upgrading a disc size, you must wait at least 6 hours before upgrading ...](https://docs.elest.io/books/services-dashboard/page/increase-aws-main-disk-or-volume-size) [#### How to Create AWS Access and Secret Key for BYOAWS\ \ Getting started\ \ To create your AWS Access and Secret Key, follow these steps. Step 1:- Use your AWS account ID or account alias, your IAM user name, and your password to sign in to the IAM console Step 2:- In the navigation bar on the upper right, choose your user name, a...](https://docs.elest.io/books/getting-started/page/how-to-create-aws-access-and-secret-key-for-byoaws) [#### I'm trying to add AWS keys to Elestio but getting an error "You are not authorized to perform this operation" in BYOAWS\ \ Frequently Asked Questions\ \ This error will appear when adding AWS Access and Secret Credentials keys if your keys do not have AmazonEC2FullAccess access permission on your AWS account. In order to use these keys, please try to grant permission on your AWS account. To find out more a...](https://docs.elest.io/books/frequently-asked-questions/page/im-trying-to-add-aws-keys-to-elestio-but-getting-an-error-you-are-not-authorized-to-perform-this-operation-in-byoaws) [#### Can I use OUTFILE in Managed MySQL?\ \ Frequently Asked Questions\ \ Yes it's possible on Elestio. Since we are running MySQL inside a docker container you will have to modify the stack to mount a new volume in the docker-compose. You can edit it with UPDATE CONFIG button from our dashboardYou will have to add a line like this ...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-use-outfile-in-managed-mysql) [#### How to Create AWS Access and Secret Key for External backups (S3)\ \ Backups\ \ To create your AWS Access and Secret Key, follow these steps. Step 1:- Use your AWS account ID or account alias, your IAM user name, and your password to sign in to the IAM console Step 2:- In the navigation bar on the upper right, choose your user name, a...](https://docs.elest.io/books/backups/page/how-to-create-aws-access-and-secret-key-for-external-backups-s3) [#### How to Create Bucket in AWS for External backups (S3)\ \ Backups\ \ To create your bucket for backups, follow these steps. Step 1:- Use your AWS account ID or account alias, your IAM user name, and your password to sign in to the IAM console Step 2:- Search for S3 in the Services section of the navigation menu on the top l...](https://docs.elest.io/books/backups/page/how-to-create-bucket-in-aws-for-external-backups-s3) [#### How can I automatically remove system log files in order to free up disk space?\ \ Frequently Asked Questions\ \ By default, new instances are automatically configured to delete log files on a daily basis. However, if your virtual machine (VM) does not have these files at /opt/maintenance-daily.sh or if you have deleted them, you can easily configure the deletion proces...](https://docs.elest.io/books/frequently-asked-questions/page/how-can-i-automatically-remove-system-log-files-in-order-to-free-up-disk-space) Back to top --- # Search for [book] {type:chapter} | docs.elest.io [Skip to main content](https://docs.elest.io/search?term=%5Bbook%5D+{type:chapter}#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 0 total results found No items available Back to top --- # Search for [book] {type:book} | docs.elest.io [Skip to main content](https://docs.elest.io/search?term=%5Bbook%5D+{type:book}#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 1 result found [#### DB Migrations\ \ Need help to migrate to Elestio? Follow the simple steps in the documentation here and get started.\ \ book\ \ migrations](https://docs.elest.io/books/db-migrations) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=10#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### How to Transfer your Domains from GoDaddy /others to elestio\ \ Domains\ \ If you desire to transfer your domain to Elestio, here is a comprehensive, step-by-step guide that will enable you to successfully migrate your domains to Elestio while effortlessly continuing to develop your online presence. Before initiating the domain tran...](https://docs.elest.io/books/domains/page/how-to-transfer-your-domains-from-godaddy-others-to-elestio) [#### Using Cloudflare\ \ Security\ \ Cloudflare DNS: If you wish to use Cloudflare for DNS ONLY, you can configure it just like any other DNS provider, and simply follow the steps for adding a custom domain as usual. WARNING: Your domain DNS entry must have a GRAY cloud, not an ORANGE (proxied)...](https://docs.elest.io/books/security/page/using-cloudflare) [#### Buying a Domain from Elest.io\ \ Domains\ \ Great brand names are like magnets that people gravitate towards. Try https://elest.io/domains domains to get your business's unique brand identity. In today's fast-paced digital world, establishing a strong online presence is crucial for businesses, indi...](https://docs.elest.io/books/domains/page/buying-a-domain-from-elestio) [#### How to resolve the Borg acquire lock in remote backups.\ \ Frequently Asked Questions\ \ If you see the following error when listing, restoring, or taking manual backups for your Borg remote backups. Failed to create/acquire the lock /root/.cache/borg/f80e5dfd25cb9/lock.exclusive (timeout). You may simply solve it by following the instructions b...](https://docs.elest.io/books/frequently-asked-questions/page/how-to-resolve-the-borg-acquire-lock-in-remote-backups) [#### How to resolve the Borg cache error in remote backups.\ \ Frequently Asked Questions\ \ If you see the following error related to the Borg cache when listing, restoring, or taking manual backups for your Borg remote backups. Local Exception Traceback (most recent call last): File "/usr/lib/python3/dist-packages/borg/archiver.py", line 5089, ...](https://docs.elest.io/books/frequently-asked-questions/page/how-to-resolve-the-borg-cache-error-in-remote-backups) [#### How to Renew a Domain on Elestio?\ \ Domains\ \ It is always best to renew a domain name before it expires so there is no interruption in service and there is no risk of losing ownership of the domain name. You can renew a domain for a minimum of 1 year and up to a maximum of 10 (you cannot exceed 10 yea...](https://docs.elest.io/books/domains/page/how-to-renew-a-domain-on-elestio) [#### How can I change the name server for elestio domains?\ \ Domains\ \ Nameservers are the first thing domain names look to when they need to know where the content of a site is located. Nameservers dictate the DNS, which means you have to set up the DNS records with your nameserver provider. If you use elestio nameservers, th...](https://docs.elest.io/books/domains/page/how-can-i-change-the-name-server-for-elestio-domains) [#### Locking/unlocking a domain\ \ Domains\ \ The domain lock is an added layer of security to guard against unauthorized domain transfers. You can lock or unlock your domain by following the instructions below: Step 1: Navigate to the Domains page from the left sidebar. Step 2: Select your domain f...](https://docs.elest.io/books/domains/page/lockingunlocking-a-domain) [#### I added fund to my elestio account, but my service is still not running\ \ Frequently Asked Questions\ \ If your service was suspended due to lack of credits and now it is still inactive even after adding the funds to your elestio account then please follow the below steps to active the inactive services. If termination protection is enabled on your servic...](https://docs.elest.io/books/frequently-asked-questions/page/i-added-fund-to-my-elestio-account-but-my-service-is-still-not-running) [#### Migrate to Elestio managed services\ \ DB Migrations\ \ This migration document focuses on the migration of the applications supported by Elestio. Find the software list here This document provides a step-by-step guide for migrating your existing system to Elestio. Elestio is designed to enhance performance, scala...](https://docs.elest.io/books/db-migrations/page/migrate-to-elestio-managed-services) [#### Elestio Domain shows SSL expired or Deceptive Site ahead\ \ Frequently Asked Questions\ \ Current Status: Resolved @ 2023-11-04, 07:11 Resolution: Google unflagged our domain in less than 24h in response to our appeal   Date of incident: 2023-11-03, 13:22 Dear Valued Customers, We want to inform you about an incident that has recently affected...](https://docs.elest.io/books/frequently-asked-questions/page/elestio-domain-shows-ssl-expired-or-deceptive-site-ahead) [#### Migrate your customized application to Elestio\ \ DB Migrations\ \ This migration document is only for services that are not being supported by Elestio as a fully managed option. If you are unaware of the software supported, take a look here. If Elestio is supporting the software then you can follow this migration document 1...](https://docs.elest.io/books/db-migrations/page/migrate-your-customized-application-to-elestio) [#### Migrate Wordpress to Elestio\ \ DB Migrations\ \ This migration document focuses on the migration of the applications supported by Elestio. Find the software list here This document provides a step-by-step guide for migrating your existing system to Elestio. Elestio is designed to enhance performance, scala...](https://docs.elest.io/books/db-migrations/page/migrate-wordpress-to-elestio) [#### Migrate MySQL Database to Elestio\ \ DB Migrations\ \ This migration document focuses on the migration of the applications supported by Elestio. Find the software list here NEW: Check our Data Migration Service for MySQL to migrate more easily This document provides a step-by-step guide for migrating your exist...](https://docs.elest.io/books/db-migrations/page/migrate-mysql-database-to-elestio) [#### Migrate Jenkins Pipeline to Elestio\ \ DB Migrations\ \ This migration document focuses on the migration of the applications supported by Elestio. Find the software list here This document provides a step-by-step guide for migrating your existing Jenkins pipelines to Elestio. Elestio is designed to enhance perform...](https://docs.elest.io/books/db-migrations/page/migrate-jenkins-pipeline-to-elestio) [#### Migrate Superset to Elestio\ \ DB Migrations\ \ This migration document focuses on the migration of the applications supported by Elestio. Find the software list here This document provides a step-by-step guide for migrating your existing Superset pipelines to Elestio. Elestio is designed to enhance perfor...](https://docs.elest.io/books/db-migrations/page/migrate-superset-to-elestio) [#### Migrate Mastodon server to Elestio\ \ DB Migrations\ \ This migration document focuses on the migration of the applications supported by Elestio. Find the software list here This document provides a step-by-step guide for migrating your existing Mastodon database system to Elestio. Elestio is designed to enhance ...](https://docs.elest.io/books/db-migrations/page/migrate-mastodon-server-to-elestio) [#### How are operating system(OS) upgrades managed?\ \ Frequently Asked Questions\ \ Automatic Minor OS Updates: Minor operating system updates are automatically performed every Sunday by default. (Note: This setting can be modified or disabled in the service settings.) Major OS Updates: For major updates, utilize our clone featur...](https://docs.elest.io/books/frequently-asked-questions/page/how-are-operating-systemos-upgrades-managed) [#### Why did the payment fail when I was attempting to add credits?\ \ Frequently Asked Questions\ \ Encountering difficulties with payment failures while attempting to add credits? Fear not, as we've outlined a comprehensive guide to help you address the issue: Resolving Payment Failures: A Step-by-Step Guide If you've been experiencing payment failures wh...](https://docs.elest.io/books/frequently-asked-questions/page/why-did-the-payment-fail-when-i-was-attempting-to-add-credits) [#### How can project ownership or service billing be transferred to another user's account?\ \ Frequently Asked Questions\ \ This guide explains how to transfer a project ownership from one Elestio account to another. Prerequisites Before starting the transfer: The new owner must have an active Elestio account The new owner must be added as a member in the project with Admin o...](https://docs.elest.io/books/frequently-asked-questions/page/how-can-project-ownership-or-service-billing-be-transferred-to-another-users-account) Back to top --- # Page Revisions for Netcup | docs.elest.io [Skip to main content](https://docs.elest.io/books/cloud-providers/page/netcup/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/cloud-providers/page/netcup/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 5 Netcup (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2025-12-10 10:44:19 UTC (1 week ago) [Changes](https://docs.elest.io/books/cloud-providers/page/netcup/revisions/2947/changes)  |  [_Current Version_](https://docs.elest.io/books/cloud-providers/page/netcup) # 4 Netcup (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2025-12-10 10:43:43 UTC (1 week ago) [Changes](https://docs.elest.io/books/cloud-providers/page/netcup/revisions/2945/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/netcup/revisions/2945) # 2 Netcup (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2025-12-10 10:43:31 UTC (1 week ago) [Changes](https://docs.elest.io/books/cloud-providers/page/netcup/revisions/2944/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/netcup/revisions/2944) # 1 Netcup (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2025-12-10 10:42:27 UTC (1 week ago) Initial publish [Preview](https://docs.elest.io/books/cloud-providers/page/netcup/revisions/2942) Back to top --- # Page Revisions for Upgrade support plan | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 4 Upgrade support plan (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-11-05 12:22:29 UTC (1 month ago) [Changes](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions/2939/changes)  |  [_Current Version_](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan) # 3 Upgrade support plan (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2022-09-29 09:29:41 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions/1548/changes)  |  [Preview](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions/1548) # 2 Upgrade support plan (**Editor Type:** WYSIWYG) ![Daniel](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/dm-headshot.jpg) Daniel 2022-01-30 18:44:12 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions/742/changes)  |  [Preview](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions/742) # 1 Upgrade support plan (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-11 17:35:32 UTC (3 years ago) Initial publish [Preview](https://docs.elest.io/books/services-dashboard/page/upgrade-support-plan/revisions/120) Back to top --- # Page Revisions for Introduction | docs.elest.io [Skip to main content](https://docs.elest.io/books/databases/page/introduction/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/databases/page/introduction/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 8 Introduction (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-11-05 12:17:07 UTC (1 month ago) [Changes](https://docs.elest.io/books/databases/page/introduction/revisions/2937/changes)  |  [_Current Version_](https://docs.elest.io/books/databases/page/introduction) # 7 Introduction (**Editor Type:** WYSIWYG) ![Joseph Amsellem](https://docs.elest.io/uploads/images/user/2025-01/thumbs-30-30/ztc5c5xkum-avatar.png) Joseph Amsellem 2025-01-28 12:45:32 UTC (10 months ago) [Changes](https://docs.elest.io/books/databases/page/introduction/revisions/2437/changes)  |  [Preview](https://docs.elest.io/books/databases/page/introduction/revisions/2437) # 6 Introduction (**Editor Type:** WYSIWYG) ![Joseph Amsellem](https://docs.elest.io/uploads/images/user/2025-01/thumbs-30-30/ztc5c5xkum-avatar.png) Joseph Amsellem 2025-01-28 08:20:12 UTC (10 months ago) [Changes](https://docs.elest.io/books/databases/page/introduction/revisions/2435/changes)  |  [Preview](https://docs.elest.io/books/databases/page/introduction/revisions/2435) # 5 Introduction (**Editor Type:** WYSIWYG) ![Joseph Amsellem](https://docs.elest.io/uploads/images/user/2025-01/thumbs-30-30/ztc5c5xkum-avatar.png) Joseph Amsellem 2025-01-28 07:23:15 UTC (10 months ago) [Changes](https://docs.elest.io/books/databases/page/introduction/revisions/2426/changes)  |  [Preview](https://docs.elest.io/books/databases/page/introduction/revisions/2426) # 4 Introduction (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-01-27 10:48:55 UTC (10 months ago) [Changes](https://docs.elest.io/books/databases/page/introduction/revisions/2388/changes)  |  [Preview](https://docs.elest.io/books/databases/page/introduction/revisions/2388) # 3 Introduction to clusters (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-01-27 10:47:46 UTC (10 months ago) [Changes](https://docs.elest.io/books/databases/page/introduction/revisions/2387/changes)  |  [Preview](https://docs.elest.io/books/databases/page/introduction/revisions/2387) # 2 Introduction to clusters (**Editor Type:** WYSIWYG) ![Joseph Amsellem](https://docs.elest.io/uploads/images/user/2025-01/thumbs-30-30/ztc5c5xkum-avatar.png) Joseph Amsellem 2025-01-27 10:08:46 UTC (10 months ago) [Changes](https://docs.elest.io/books/databases/page/introduction/revisions/2384/changes)  |  [Preview](https://docs.elest.io/books/databases/page/introduction/revisions/2384) # 1 Introduction to clusters (**Editor Type:** WYSIWYG) ![Joseph Amsellem](https://docs.elest.io/uploads/images/user/2025-01/thumbs-30-30/ztc5c5xkum-avatar.png) Joseph Amsellem 2025-01-27 09:23:04 UTC (10 months ago) Initial publish [Preview](https://docs.elest.io/books/databases/page/introduction/revisions/2381) Back to top --- # docs.elest.io [Skip to main content](https://docs.elest.io/books/db-migrations/references#main-content) References ========== Listed below is all the known content in the system that links to this item. [#### Migrate Superset to Elestio\ \ This migration document focuses on the migration of the applications supported by Elestio. Find t...](https://docs.elest.io/books/db-migrations/page/migrate-superset-to-elestio) Back to top --- # Page Revisions for BYOVM with AWS EC2 (Be... | docs.elest.io [Skip to main content](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 6 BYOVM with AWS EC2 (Beta AWS UI) (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-17 12:33:47 UTC (2 months ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/2935/changes)  |  [_Current Version_](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui) # 5 BYOVM with AWS EC2 (Beta AWS UI) (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-17 12:33:35 UTC (2 months ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/2934/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/2934) # 4 BYOVM with AWS EC2 (Beta AWS UI) (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-17 12:33:07 UTC (2 months ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/2933/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/2933) # 3 BYOVM with AWS EC2 (Beta AWS UI) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-03-30 10:40:13 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/1226/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/1226) # 2 BYOVM with AWS EC2 (Beta AWS UI) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-03-29 13:00:18 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/1217/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/1217) # 1 BYOVM with AWS EC2 (old UI) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-03-29 12:55:04 UTC (3 years ago) Initial publish [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-with-aws-ec2-beta-aws-ui/revisions/1214) Back to top --- # Page Revisions for Elestio Data Processin... | docs.elest.io [Skip to main content](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 14 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-11-20 13:38:02 UTC (1 month ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2940/changes)  |  [_Current Version_](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement) # 13 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-02-06 10:19:37 UTC (10 months ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2451/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2451) # 12 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-02-06 10:14:09 UTC (10 months ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2450/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2450) # 11 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-02-06 09:59:01 UTC (10 months ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2448/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2448) # 10 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-02-05 11:08:15 UTC (10 months ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2446/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2446) # 9 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-02-05 11:08:08 UTC (10 months ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2445/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2445) # 8 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-02-05 11:07:10 UTC (10 months ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2444/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2444) # 7 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-02-05 11:05:20 UTC (10 months ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2443/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2443) # 6 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2024-02-06 11:37:18 UTC (1 year ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2246/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/2246) # 5 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-12-21 06:37:14 UTC (3 years ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1769/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1769) # 4 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-12-21 06:36:58 UTC (3 years ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1768/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1768) # 3 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-12-01 13:10:24 UTC (3 years ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1762/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1762) # 2 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-11-30 18:49:52 UTC (3 years ago) [Changes](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1760/changes)  |  [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1760) # 1 Elestio Data Processing Agreement (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-11-30 08:26:27 UTC (3 years ago) Initial publish [Preview](https://docs.elest.io/books/legal-compliance/page/elestio-data-processing-agreement/revisions/1759) Back to top --- # Page Revisions for BYOVM (Bring Your Own VM) | docs.elest.io [Skip to main content](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 13 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-08 12:46:24 UTC (2 months ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/2921/changes)  |  [_Current Version_](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm) # 12 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-07 15:06:10 UTC (2 months ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/2916/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/2916) # 11 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2024-06-27 07:44:07 UTC (1 year ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/2289/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/2289) # 10 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-04-12 16:14:42 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/1263/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/1263) # 9 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-04-12 16:13:57 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/1261/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/1261) # 8 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-04-12 16:13:51 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/1260/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/1260) # 7 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Daniel](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/dm-headshot.jpg) Daniel 2022-02-12 19:31:09 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/922/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/922) # 6 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Daniel](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/dm-headshot.jpg) Daniel 2022-02-02 13:43:25 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/769/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/769) # 5 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-24 13:00:47 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/529/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/529) # 4 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-24 12:57:10 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/527/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/527) # 3 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-24 12:56:18 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/525/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/525) # 2 BYOVM (Bring Your Own VM) (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-09 13:24:29 UTC (3 years ago) [Changes](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/32/changes)  |  [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/32) # 1 Bring Your Own VM (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-09 13:24:13 UTC (3 years ago) Initial publish [Preview](https://docs.elest.io/books/cloud-providers/page/byovm-bring-your-own-vm/revisions/31) Back to top --- # Page Revisions for How Does Elestio’s Pri... | docs.elest.io [Skip to main content](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 4 How Does Elestio’s Pricing Work? (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-08 15:26:29 UTC (2 months ago) [Changes](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions/2928/changes)  |  [_Current Version_](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work) # 3 How Does Elestio’s Pricing Work? (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-08 15:26:16 UTC (2 months ago) [Changes](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions/2927/changes)  |  [Preview](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions/2927) # 2 How Does Elestio’s Pricing Work? (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-07 16:03:18 UTC (2 months ago) [Changes](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions/2919/changes)  |  [Preview](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions/2919) # 1 Understanding Elestio's Pricing Model (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2025-10-07 15:51:17 UTC (2 months ago) Initial publish [Preview](https://docs.elest.io/books/frequently-asked-questions/page/how-does-elestios-pricing-work/revisions/2917) Back to top --- # Page Revisions for Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/keycloak/page/overview-VG3/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/keycloak/page/overview-VG3/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 3 Overview (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-10-17 10:26:14 UTC (2 months ago) [Changes](https://docs.elest.io/books/keycloak/page/overview-VG3/revisions/2931/changes)  |  [_Current Version_](https://docs.elest.io/books/keycloak/page/overview-VG3) # 2 Overview (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2025-10-17 10:24:37 UTC (2 months ago) [Changes](https://docs.elest.io/books/keycloak/page/overview-VG3/revisions/2929/changes)  |  [Preview](https://docs.elest.io/books/keycloak/page/overview-VG3/revisions/2929) # 1 Overview (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-06-13 14:37:56 UTC (6 months ago) Initial publish [Preview](https://docs.elest.io/books/keycloak/page/overview-VG3/revisions/2778) Back to top --- # Page Revisions for How to secure your app... | docs.elest.io [Skip to main content](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 3 How to secure your application with Cloudflare Tunnel (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2025-10-08 14:27:10 UTC (2 months ago) [Changes](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel/revisions/2925/changes)  |  [_Current Version_](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel) # 2 Cloudflare Tunnel with Elestio (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2025-10-08 14:26:41 UTC (2 months ago) [Changes](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel/revisions/2924/changes)  |  [Preview](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel/revisions/2924) # 1 Cloudflare Tunnel with Elestio (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2025-10-08 14:25:16 UTC (2 months ago) Initial publish [Preview](https://docs.elest.io/books/security/page/how-to-secure-your-application-with-cloudflare-tunnel/revisions/2922) Back to top --- # How to Create AWS Acce... | docs.elest.io [Skip to main content](https://docs.elest.io/books/getting-started/page/how-to-create-aws-access-and-secret-key-for-byoaws#main-content) Info Content How to Create AWS Access and Secret Key for BYOAWS ================================================== ##### To create your AWS Access and Secret Key, follow these steps. * **Step 1**:- Use your AWS account ID or account alias, your IAM user name, and your password to sign in to the _[IAM console](https://console.aws.amazon.com/iam) _ * **Step 2**:- In the navigation bar on the upper right, choose your user name, and then choose **Security credentials**. [![Instances-EC2-Management-Console (1).png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/instances-ec2-management-console-1.png)](https://docs.elest.io/uploads/images/gallery/2023-02/instances-ec2-management-console-1.png) * **Step 3**:- If you want to create the AWS Access and Secret credentials with the root user, skip to **step 4**; otherwise, click _**Users**_ on the left side of access management and then _**Add users**_. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/jGZimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/jGZimage.png) Enter your AWS Account access user name and click Next, Next, Next and Create User to proceed. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/jkHimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/jkHimage.png) After clicking the Create User button, you will be taken to the user list. Choose your created user name from the user list and click on it. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/Llnimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/Llnimage.png) Navigate to **Security Credentials** under User Details. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/zSTimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/zSTimage.png) * **Step 4**:- Select **Create access key** from the **Access keys section**. If you already have two access keys, this button is disabled, and you must delete one before creating a new one. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/image.png)](https://docs.elest.io/uploads/images/gallery/2023-02/image.png) * * On the **Access key best practices & alternatives** page, choose your use case to learn about additional options which can help you avoid creating a long-term access key. If you determine that your use case still requires an access key, choose **Other** and then choose **Next**. * (Optional) Set a description tag value for the access key. This adds a tag key-value pair to your IAM user. This can help you identify and rotate access keys later. The tag key is set to the access key id. The tag value is set to the access key description that you specify. When you are finished, choose to **Create access key**. **For Non-Root Users:-**  Choose **Command Line Interface** as an alternative and check the box, then click Next and **Create Access Key.** [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/8Fhimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/8Fhimage.png)  **For Root User:-** Check the box and click **Create Access Key**. [![Screenshot 2023-02-20 122937.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/screenshot-2023-02-20-122937.png)](https://docs.elest.io/uploads/images/gallery/2023-02/screenshot-2023-02-20-122937.png) * **Step 5**:- On the **Retrieve access keys** page, choose either **Show** to reveal the value of your user's secret access key, or **Download .csv file**. This is your only opportunity to save your secret access key. After you've saved your secret access key in a secure location, choose **Done**. [![IAM-Management-Console.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/iam-management-console.png)](https://docs.elest.io/uploads/images/gallery/2023-02/iam-management-console.png) * **Step 6**:- Now grant **Administration** access to the newly created keys. > Elestio requires a _AmazonEC2FullAccess_ permission to manage your Ec2 services Navigate to permission in the user details to add the permission and select **Add Permission** [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/sLoimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/sLoimage.png) Select the **Attach policies directly** Tab to attach permission. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/NgQimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/NgQimage.png) Now Enter _AmazonEC2FullAccess_ into the search box and then select the _AmazonEC2FullAccess_ permission from the results. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/F8fimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/F8fimage.png) After Selecting both Click **Next** and then click **Add permission** to proceed. [![Screenshot 2023-02-20 204006.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/screenshot-2023-02-20-204006.png)](https://docs.elest.io/uploads/images/gallery/2023-02/screenshot-2023-02-20-204006.png) ##### Follow these steps if you already have an access key and want to activate it instead of creating a new one. * In the **Access keys** section, find the key to activate. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/z5Limage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/z5Limage.png) * To activate the key, go to **Actions** and select **Activate**. [![image.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/9pzimage.png)](https://docs.elest.io/uploads/images/gallery/2023-02/9pzimage.png) Before adding keys to elestio, you must grant Administration access to them. Enter section select mode [Previous\ \ Create a new service with Bring your own AWS ...](https://docs.elest.io/books/getting-started/page/create-a-new-service-with-bring-your-own-aws-account-byoaws) [Next\ \ How to Deploy or Integrate a Service with Tor...](https://docs.elest.io/books/getting-started/page/how-to-deploy-or-integrate-a-service-with-tor-onion-on-elestio) Back to top --- # Cloning a Service to A... | docs.elest.io [Skip to main content](https://docs.elest.io/books/valkey/page/cloning-a-service-to-another-provider-or-region#main-content) Info Content Cloning a Service to Another Provider or Region =============================================== Migrating or cloning services across cloud providers or geographic regions is a critical part of modern infrastructure management. Whether you’re optimizing for latency, preparing for disaster recovery, meeting regulatory requirements, or simply switching providers, a well-planned migration ensures continuity, performance, and data integrity. This guide outlines a structured methodology for service migration, applicable to most cloud-native environments. **Pre-Migration Preparation** ----------------------------- Before initiating a migration, thorough planning and preparation are essential. This helps avoid unplanned downtime, data loss, or misconfiguration during the move: * **Evaluate the Current Setup:** Begin by documenting the existing Valkey instance’s configuration. This includes runtime environments (Valkey version, memory policies), persistence settings (RDB, AOF, or both), custom configurations (valkey.conf), authentication credentials, and client connection settings. Make note of the current deployment region, storage volumes, instance sizing, and IP/firewall rules. * **Define the Migration Target:** Choose the new cloud provider or region you plan to migrate to. Confirm that Valkey is supported in the target environment with equivalent or better resources. Validate compatibility in terms of Valkey version, persistence format, and disk I/O performance. Ensure the target region meets your latency and compliance requirements, and verify that TLS, backup policies, and access controls can be replicated in the new environment. * **Provision the Target Environment:** Set up a new Valkey service in the desired target region or provider. This involves deploying a new instance with the same resource allocation, runtime version, and configuration as the original. If you’re using Elestio, simply create a new Valkey service and select the same software version. Configure access credentials, private/public networking, and any required firewall or IP rules at this stage. * **Backup the Current Service:** Always create a full backup of the current Valkey data before migration. For RDB-based persistence, this involves triggering a BGSAVE operation and extracting the dump.rdb file from the instance. If AOF is enabled, copy the appendonly.aof file to ensure complete recovery. Use tools like scp or rsync over SSH to securely transfer these files to the target environment. If the instance is containerized, use persistent volume snapshots or mounted volume copies to extract backup data. This backup serves as a rollback point and is essential for recovery in case of data corruption or migration failure. **Cloning Execution** --------------------- The cloning process begins with restoring the backed-up data into the new Valkey environment. Connect to the target instance and stop the Valkey process temporarily to allow safe file replacement. Move the dump.rdb or appendonly.aof file into the correct storage location, typically /var/lib/valkey/, ensuring that file permissions match the expected user and group settings. Once the data is in place, restart the Valkey service and monitor logs to confirm a successful startup and key load. After restoring data, verify the integrity and structure of the new instance. Use redis-cli or an equivalent client to query the dataset, confirm key counts, TTLs, and persistence settings. If your service uses custom modules, Lua scripts, or pub/sub channels, ensure they are functioning as expected. Review the configuration files (valkey.conf) to confirm replication, memory limits, eviction policies, and authentication are all consistent with the original service. For TLS-enabled instances, validate certificate paths, key permissions, and client connection behavior. Test the service in isolation to validate correctness. This includes read/write operations, key expiration, background tasks, or pub/sub behavior. Simulate application queries and ensure that memory allocation, CPU usage, and persistence behavior match your expectations. Use observability tools to monitor performance and identify discrepancies. This is also the stage to update client configurations or environment variables if the connection endpoint or credentials have changed. Once validation is complete, route live traffic to the new Valkey instance. This may involve updating DNS records to point to the new IP address, reconfiguring load balancers, or modifying firewall rules. If you’re using managed DNS with short TTLs, the switchover can be nearly instantaneous. For high-availability environments, consider running both instances in parallel temporarily and shifting client traffic gradually. Monitor logs, metrics, and connected clients throughout the transition to detect and resolve issues early. **Post-Migration Validation and Optimization** ---------------------------------------------- Once the new environment is live and receiving traffic, focus on optimizing and securing the setup: * **Validate Application Functionality:** Ensure that all applications relying on the Valkey instance function correctly. Check integration with authentication systems, session stores, queues, or caching logic. Review logs for connection failures, timeouts, or permission errors. Confirm that all services have been updated to use the new endpoint and that no application is attempting to write to the old instance. * **Monitor Performance:** Track memory usage, CPU load, disk I/O, and connection counts on the new instance. Valkey performance characteristics may vary across cloud providers or instance types, so tune your memory policy, eviction settings, and save intervals accordingly. Enable alerts for key metrics to proactively detect performance degradation. If autoscaling is supported in your environment, configure thresholds to manage traffic spikes. * **Secure the Environment:** Enforce access controls via IP allowlists, firewall settings, and encrypted transport. Rotate access credentials or ACL tokens post-migration to eliminate any risk associated with exposed keys. If TLS was not previously enabled, consider enabling it on the new instance to improve data-in-transit security. Review Valkey-specific security hardening such as disabling dangerous commands and isolating the instance from public access. * **Cleanup and Documentation:** Once the migration is stable, decommission the old Valkey instance and revoke any associated credentials. Ensure all monitoring, backups, and failover routines are redirected to the new service. Update internal documentation to reflect the new region, access endpoints, and runtime configuration. Log the migration steps and outcomes for future reference and audit trails. **Benefits of Cloning** ----------------------- Cloning a Valkey service enables safer testing, faster failover, and region-based redundancy. Teams can use cloned environments to stage changes, simulate workloads, or test application compatibility with newer Valkey versions without impacting production. Clones are also useful for development and QA workflows that require access to near-real datasets without write permission to production. In disaster recovery planning, a cloned instance in a separate region can act as a ready-to-promote failover node. If the primary region becomes unavailable, DNS can be redirected to the backup instance with minimal delay. Additionally, analytics or reporting workloads can run against a cloned read-only copy to isolate them from critical workloads, ensuring consistent performance for real-time applications. Additionally, rather than building a new environment from scratch, you can clone the database into another provider, validate it, and cut over with minimal disruption. This helps maintain operational continuity and reduces the effort needed for complex migrations. Enter section select mode [Previous\ \ Database Migration Service for Valkey](https://docs.elest.io/books/valkey/page/database-migration-service-for-valkey) [Next\ \ Manual Migration Using valkey-cli and Dump Files](https://docs.elest.io/books/valkey/page/manual-migration-using-valkey-cli-and-dump-files) Back to top --- # Cloning a Service to A... | docs.elest.io [Skip to main content](https://docs.elest.io/books/redis/page/cloning-a-service-to-another-provider-or-region#main-content) Info Content Cloning a Service to Another Provider or Region =============================================== Migrating or cloning services across cloud providers or geographic regions is a critical part of modern infrastructure management. Whether you’re optimizing for latency, preparing for disaster recovery, meeting regulatory requirements, or simply switching providers, a well-planned migration ensures continuity, performance, and data integrity. This guide outlines a structured methodology for service migration, applicable to most cloud-native environments. **Pre-Migration Preparation** ----------------------------- Before initiating a migration, thorough planning and preparation are essential. This helps avoid unplanned downtime, data loss, or misconfiguration during the move: * **Evaluate the Current Setup**: Begin by documenting the existing service’s configuration. This includes runtime environments (container images, platform versions), persistent data (databases, object storage), network rules (ports, firewalls), and application dependencies (APIs, credentials, linked services). * **Define the Migration Target**: Choose the new cloud provider or region you plan to migrate to. Confirm service compatibility, resource limits, and geographic latency requirements. If you’re replicating an existing environment, make sure the target region supports the same compute/storage features and versions. * **Provision the Target Environment**: Set up the target infrastructure where the service will be cloned. This could involve creating new Kubernetes clusters, VM groups, container registries, databases, or file storage volumes depending on your stack. * **Backup the Current Service**: Always create a full backup or snapshot of the current service and its associated data before proceeding. This acts as a rollback point in case of migration issues and ensures recovery in the event of failure. **Cloning Execution** --------------------- The first step in executing a clone is to replicate the configuration of the original service in the target environment. This involves deploying the same container image or service binary using the same runtime settings. If you’re using Kubernetes or container orchestrators, this can be done via Helm charts or declarative manifests. Pay close attention to environment variables, secrets, mounted paths, storage class definitions, and health check configurations to ensure a consistent runtime environment. Next, you’ll need to migrate any persistent data tied to the service. For file-based storage, tools like rsync or rclone are effective for copying volume contents over SSH or cloud storage backends. It’s crucial to verify compatibility across disk formats, database versions, and encoding standards to avoid corruption or mismatched behavior. After replicating the environment and data, it’s important to validate the new service in isolation. This means confirming that all application endpoints respond as expected, background tasks or cron jobs are functioning, and third-party integrations (e.g., payment gateways, S3 buckets) are accessible. You should test authentication flows, data read/write operations, and retry logic to ensure the new service is functionally identical. Use observability tools to monitor resource consumption and application logs during this stage. Once validation is complete, configure DNS and route traffic to the new environment. This might involve updating DNS A or CNAME records, changing cloud load balancer configurations, or applying new firewall rules. For high-availability setups, consider using health-based routing or weighted DNS to gradually transition traffic from the old instance to the new one. **Post-Migration Validation and Optimization** ---------------------------------------------- Once the new environment is live and receiving traffic, focus on optimizing and securing the setup: * **Validate Application Functionality**: Test all integrations, user workflows, and background jobs to confirm proper behavior. Review logs for silent errors or timeouts. Ensure all applications pointing to the service are updated with the new URL or connection string. * **Monitor Performance**: Analyze load, CPU, memory, and storage utilization. Scale resources as needed, or optimize runtime settings for the new provider/region. Enable autoscaling where applicable. * **Secure the Environment**: Implement firewall rules, IP restrictions, and access controls. Rotate secrets and validate that no hardcoded credentials or endpoints point to the old service. * **Cleanup and Documentation**: Once validated, decommission the old setup safely. Update internal documentation with new deployment details, endpoint addresses, and any configuration changes. **Benefits of Cloning** ----------------------- Cloning a database service, particularly for engines like Redis offers several operational and strategic advantages. It allows teams to test schema migrations, version upgrades, or major application features in an isolated environment without affecting production. By maintaining a cloned copy, developers and QA teams can work against realistic data without introducing risk. Cloning also simplifies cross-region redundancy setups. A replica in another region can be promoted quickly if the primary region experiences an outage. For compliance or analytics purposes, cloned databases allow for read-only access to production datasets, enabling safe reporting or data processing without interrupting live traffic. Additionally, rather than building a new environment from scratch, you can clone the database into another provider, validate it, and cut over with minimal disruption. This helps maintain operational continuity and reduces the effort needed for complex migrations. Enter section select mode [Previous\ \ Database Migration](https://docs.elest.io/books/redis/chapter/database-migration) [Next\ \ Database Migration Services for Redis](https://docs.elest.io/books/redis/page/database-migration-services-for-redis) Back to top --- # Database Migration | docs.elest.io [Skip to main content](https://docs.elest.io/books/timescaledb/chapter/database-migration#main-content) Info Content Database Migration ================== [#### Database Migration Service for TimescaleDB\ \ Elestio provides a structured approach for migrating TimescaleDB databases from various environme...](https://docs.elest.io/books/timescaledb/page/database-migration-service-for-timescaledb) [#### Cloning a Service to Another Provider or Region\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of ...](https://docs.elest.io/books/timescaledb/page/cloning-a-service-to-another-provider-or-region) [#### Manual Migration Using pg\_dump and pg\_restore\ \ Manual Migrations using TimescaleDB's built-in tools pg\_dump and pg\_restore are ideal for users w...](https://docs.elest.io/books/timescaledb/page/manual-migration-using-pg-dump-and-pg-restore) ### Search Results Clear Search [Previous\ \ Checking Database Size and Related Issues](https://docs.elest.io/books/timescaledb/page/checking-database-size-and-related-issues) [Next\ \ Database Migration Service for TimescaleDB](https://docs.elest.io/books/timescaledb/page/database-migration-service-for-timescaledb) Back to top --- # Restoring a Backup | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse/page/restoring-a-backup#main-content) Info Content Restoring a Backup ================== Restoring ClickHouse backups is essential for disaster recovery, staging environment duplication, or rolling back to a known state. Elestio supports backup restoration both through its web dashboard and manually through Docker Compose and command-line methods. This guide explains how to restore ClickHouse backups from SQL-based snapshots or file-based archives, covering both full and partial restore scenarios, and includes solutions for common restoration issues. **Restoring from a Backup via Terminal** ---------------------------------------- This method applies when you have a backup created using ClickHouse’s native BACKUP command or a direct copy of the data directory. To restore the backup, you must stop the running ClickHouse container, replace the data files, and restart the container to load the restored dataset. #### **Stop the ClickHouse Container** Shut down the ClickHouse container cleanly to avoid issues with open file handles or inconsistent state: docker-compose down #### **Replace the Backup Files** If your backup was created using the native ClickHouse BACKUP command and saved to /backups/backup\_2025\_06\_09, copy it into the appropriate path within the container or bind mount. Example: cp -r ./clickhouse_backup_2025_06_09 /opt/app/backups/backup_2025_06_09 Make sure this path corresponds to the volumes specified in your docker-compose.yml. For example: volumes: - ./backups:/backups - ./data:/var/lib/clickhouse If you’re restoring from a tarball archive, extract it into the correct volume mount: tar -xzf clickhouse_backup_2025_06_09.tar.gz -C /opt/app/data/ #### **Restart ClickHouse** Start the ClickHouse container again: docker-compose up -d ClickHouse will load the data either from the standard data directory or, if using the backup snapshot method, you can explicitly restore the database using SQL (next section). **Restoring via Docker Compose Terminal** ----------------------------------------- If you’re using backups made with the SQL BACKUP command, ClickHouse also provides a built-in method to restore via the RESTORE command. #### **Copy the Backup Directory into the Container** docker cp ./clickhouse_backup_2025_06_09 $(docker-compose ps -q clickhouse):/backups/backup_2025_06_09 #### **Restore with ClickHouse SQL** Enter the container terminal: docker-compose exec clickhouse bash Then run the restore command: clickhouse-client --query="RESTORE DATABASE default FROM Disk('/backups/backup_2025_06_09')" This will restore the default database and its contents from the previously created backup directory. **Partial Restores in ClickHouse** ---------------------------------- ClickHouse supports more granular restore operations using SQL syntax. You can restore individual tables or databases if the backup was created using the native BACKUP command. #### **Restore a Single Table** clickhouse-client --query="RESTORE TABLE default.events FROM Disk('/backups/backup_2025_06_09')" This restores just the events table from the default database without affecting other tables. #### **Restore Specific Schemas or Data** You can also export and import CSV or TSV snapshots for partial data management: clickhouse-client --query="SELECT * FROM default.events FORMAT CSV" > events.csv clickhouse-client --query="INSERT INTO default.events FORMAT CSV" < events.csv **Common Errors & How to Fix Them** ----------------------------------- Restoring ClickHouse data can occasionally fail due to permission issues, path mismatches, unsupported formats, or version conflicts. Here are some frequent issues and their solutions. #### **1\. ClickHouse Fails to Start After Restore** **Error:** DB::Exception: Corrupted data part ... **Cause:** The backup directory is incomplete or corrupted, or the file was not extracted properly. **Resolution:** * Re-verify that the backup files were copied completely. * Use tar -tzf to inspect archive contents before extracting. * Make sure you’re restoring on the same ClickHouse version that created the backup. #### **2\. RESTORE Command Fails with Permission Denied** **Error:** DB::Exception: Cannot read from backup: Permission denied **Cause:** The container cannot access the /backups/ directory due to permissions. **Resolution:** * Ensure the backup directory is readable by the ClickHouse process. * Use chmod -R 755 /opt/app/backups/ to adjust permissions if needed. #### **3\. Data Not Restored** **Cause:** The RESTORE command did not include the correct database/table name or no data existed in the backup path. **Resolution:** * Use `clickhouse-client --query="SHOW DATABASES"` to confirm no restore happened. * Run ls /backups/backup\_2025\_06\_09/ inside the container to verify backup contents. #### **4\. Permission Denied When Copying Files** **Error:** cp: cannot create regular file ‘/opt/app/data/’: Permission denied **Resolution:** Ensure your terminal session or script has write access to the target directory. Use sudo if needed: sudo cp -r ./clickhouse_backup_2025_06_09 /opt/app/data/ Enter section select mode [Previous\ \ Creating Manual Backups](https://docs.elest.io/books/clickhouse/page/creating-manual-backups) [Next\ \ Identifying Slow Queries](https://docs.elest.io/books/clickhouse/page/identifying-slow-queries) Back to top --- # Creating a Database | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse/page/creating-a-database#main-content) Info Content Creating a Database =================== ClickHouse is a high-performance columnar database designed for real-time analytical processing. It’s known for its blazing speed, horizontal scalability, and efficient use of disk I/O. Proper setup is essential for taking advantage of ClickHouse’s full capabilities, including fault tolerance, secure access, and high query performance. This guide walks through various ways to run and connect to ClickHouse: using the ClickHouse CLI (clickhouse-client), Docker containers, and command-line tools for scripting and automation. Best practices are highlighted throughout to ensure robust deployments. ### **Creating using clickhouse-client** The ClickHouse command-line interface (clickhouse-client) is a built-in tool used to connect to and manage ClickHouse servers. It supports both local and remote connections and allows for SQL-based interaction with the database engine. #### **Connect to ClickHouse:** If you’re running ClickHouse locally (via package manager or Docker), you can start the CLI with: clickhouse-client For remote connections, specify the hostname, port (default 9000), and user credentials: clickhouse-client -h --port -u --password Once connected, you can run SQL queries directly from the shell. ### **Running ClickHouse Using Docker** Docker provides a fast, reproducible way to run ClickHouse in isolated environments. This is ideal for local development or self-contained production setups. ##### **Access Elestio Terminal** If you’re using Elestio for ClickHouse hosting, log into the Elestio dashboard. Go to your ClickHouse service, then navigate to **Tools > Terminal** to open a pre-authenticated shell session. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/Cntimage.png)](https://docs.elest.io/uploads/images/gallery/2025-06/Cntimage.png) Now change the directory: cd /opt/app/ ##### **Access the ClickHouse Container Shell** Elestio-managed services run on Docker Compose. Use this to enter the ClickHouse container: docker-compose exec clickhouse bash ##### **Access ClickHouse CLI from Inside the Container** Once inside the container, the clickhouse-client tool is available. Run it like this (add \--password if needed): clickhouse-client -u --port --password You are now connected to the running ClickHouse instance inside the container. ##### **Test Connectivity** Try creating a database and querying data to verify functionality: CREATE DATABASE test_db; CREATE TABLE test_db.test_table (id UInt32, message String) ENGINE = MergeTree() ORDER BY id; INSERT INTO test_db.test_table VALUES (1, 'Hello ClickHouse'); SELECT * FROM test_db.test_table; **Expected Output:** 1 Hello ClickHouse This confirms read/write operations and query functionality. ### **Connecting Using clickhouse-client in Scripts** clickhouse-client can be used non-interactively for scripting, automation, and cron-based jobs. For example, to insert data from a shell script: echo "INSERT INTO test_db.test_table VALUES (2, 'Automated')" | \ clickhouse-client -h -u --password This is useful for automated ETL jobs, health checks, or backup pipelines. **Best Practices for Setting Up ClickHouse** -------------------------------------------- ##### **Use Clear Naming for Databases and Tables** Adopt consistent naming conventions for databases, tables, and columns. Use lowercase, underscore-separated names like: user_events_2024 product_sales_agg This improves clarity in multi-schema environments and helps with automation and maintenance scripts. ##### **Choose the Right Engine and Indexing Strategy** ClickHouse supports various table engines like MergeTree, ReplacingMergeTree, and SummingMergeTree. Pick the engine that best matches your use case and define ORDER BY keys carefully to optimize performance. Example: CREATE TABLE logs ( timestamp DateTime, service String, message String ) ENGINE = MergeTree() ORDER BY (timestamp, service); Inappropriate engine selection can lead to poor query performance or high disk usage. ##### **Enable Authentication and Secure Access** Always configure user-level authentication and restrict access in production. Add users and passwords in users.xml or via SQL: CREATE USER secure_user IDENTIFIED WITH plaintext_password BY 'strong_password'; GRANT ALL ON *.* TO secure_user; Use TLS for encrypted connections by enabling SSL in the config.xml file: 9440 /etc/clickhouse-server/certs/server.crt /etc/clickhouse-server/certs/server.key ##### **Configure Data Persistence and Storage Paths** ClickHouse stores data on disk by default, but ensure proper mounting, storage separation, and backup routines. In config.xml: /var/lib/clickhouse/ /var/lib/clickhouse/tmp/ /var/lib/clickhouse/user_files/ Use RAID, SSDs, or networked volumes depending on your availability and performance needs. ##### **Monitor and Tune Performance** Use built-in introspection tools like: SELECT * FROM system.metrics; SELECT * FROM system.query_log ORDER BY event_time DESC LIMIT 10; SELECT * FROM system.parts; For real-time observability, integrate with Grafana, Prometheus, or use [ClickHouse Keeper metrics](https://clickhouse.com/docs/en/operations/monitoring/metrics/) . Also review: * system.mutations for long-running mutation jobs * system.errors for crash/debug info * system.replication\_queue for sync issues in replicated tables **Common Issues and Their Solutions** ------------------------------------- | **Issue** | **Cause** | **Solution** | | --- | --- | --- | | Authentication failure | Wrong password or no user set | Double-check credentials; use \--password flag | | Cannot connect to localhost | Service not running or incorrect port | Ensure ClickHouse is running and check the port | | SSL/TLS handshake failed | Incorrect certificate paths or permissions | Verify file locations in config.xml and restart service | | Queries are slow | Poor ORDER BY design or unoptimized table engine | Reevaluate schema design and use indexes effectively | | Data lost after restart | Misconfigured data path or ephemeral container | Ensure proper disk volume mounts and storage persistence | Enter section select mode [Previous\ \ How-To Guides](https://docs.elest.io/books/clickhouse/chapter/how-to-guides) [Next\ \ Upgrading to Major Version](https://docs.elest.io/books/clickhouse/page/upgrading-to-major-version) Back to top --- # Delete a Cluster | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse/page/delete-a-cluster#main-content) Info Content Delete a Cluster ================ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete workload deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire clusters directly from the dashboard. This action permanently removes the associated services, data, and compute resources tied to the cluster. **When to Delete a Cluster** ---------------------------- Deleting a cluster is a final step often performed when decommissioning an environment. This could include shutting down a test setup, replacing infrastructure during migration, or retiring an unused production instance. In some cases, users also delete and recreate clusters as part of major version upgrades or architectural changes. It is essential to confirm that all data and services tied to the cluster are no longer required or have been backed up or migrated before proceeding. Since cluster deletion is irreversible, any services, volumes, and backups associated with the cluster will be permanently removed. **Delete a Cluster** -------------------- To delete a cluster, log in to the [Elestio dashboard](https://dash.elest.io/)  and navigate to the **Clusters** section. From the list of clusters, select the one you want to remove. Inside the selected cluster, you’ll find a **navigation bar** at the top of the page. One of the available options in this navigation bar is **“Delete Cluster.”**  [![Screenshot 2025-06-09 at 3.20.11 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/screenshot-2025-06-09-at-3-20-11-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-06/screenshot-2025-06-09-at-3-20-11-pm.jpg) Clicking this opens a confirmation dialog that outlines the impact of deletion. It will clearly state that deleting the cluster will **permanently remove** all associated services, storage, and configurations. By acknowledging a warning or typing in the cluster name, depending on the service type. Once confirmed, Elestio will initiate the deletion process, which includes tearing down all resources associated with the cluster. This typically completes within a few minutes, after which the cluster will no longer appear in your dashboard. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/ea9image.png)](https://docs.elest.io/uploads/images/gallery/2025-06/ea9image.png) **Considerations Before Deleting** ---------------------------------- Deleting a cluster also terminates any linked domains, volumes, monitoring configurations, and scheduled backups. These cannot be recovered once deletion is complete, so plan accordingly before confirming the action. If the cluster was used for production workloads, consider archiving data to external storage (e.g., S3) or exporting final snapshots for compliance and recovery purposes. Before deleting a cluster, verify that: * All required data has been backed up externally (e.g., downloaded dumps or exports). * Any active services or dependencies tied to the cluster have been reconfigured or shut down. * Access credentials, logs, or stored configuration settings have been retrieved if needed for auditing or migration. Enter section select mode [Previous\ \ Database Migration](https://docs.elest.io/books/clickhouse/page/database-migration) [Next\ \ Restricting Access by IP](https://docs.elest.io/books/clickhouse/page/restricting-access-by-ip) Back to top --- # Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse/page/overview#main-content) Info Content Overview ======== ClickHouse is an open-source columnar database management system designed for online analytical processing (OLAP). It enables fast processing of large volumes of data by storing data by columns instead of rows, making it highly efficient for analytical queries. ClickHouse excels at real-time analytics, complex aggregations, and high-throughput data ingestion, making it suitable for data warehousing and business intelligence applications. **Key Features of ClickHouse:** * **High Performance for OLAP:** Designed specifically for analytical workloads, ClickHouse delivers lightning-fast query performance on large datasets by utilizing vectorized query execution and data compression techniques. * **Columnar Storage:** Stores data by columns rather than rows, reducing I/O operations and improving the efficiency of aggregation and filtering operations common in analytics workloads. * **Scalability and Distributed Processing:** Supports horizontal scaling across multiple nodes with sharding and replication, enabling the system to handle petabytes of data while maintaining high availability and fault tolerance. * **Real-Time Data Ingestion and Querying:** Capable of ingesting millions of rows per second and running complex queries with low latency, making it ideal for real-time dashboards and monitoring systems. * **SQL Support:** Provides a rich SQL dialect with extensions for analytical use cases, including window functions, subqueries, joins, arrays, and nested data structures, allowing for expressive and powerful queries. * **Data Compression:** Implements advanced compression algorithms (LZ4, ZSTD, etc.), significantly reducing disk usage and improving query performance by minimizing disk reads. * **Fault Tolerance and Replication:** Ensures data reliability through built-in replication and automatic failover mechanisms. Data can be replicated across nodes to prevent loss and allow for uninterrupted service. * **Extensibility:** Allows users to extend functionality with user-defined functions, external dictionaries, and integrations with external systems (e.g., Kafka, S3, HDFS). * **Security and Access Control:** Includes role-based access control, user authentication, and TLS encryption to secure data access and communication. * **Cross-Platform Support:** ClickHouse runs on major operating systems, including Linux, macOS, and FreeBSD, offering flexibility for various infrastructure environments. These features make ClickHouse a preferred choice for organisations that require real-time analytics at scale, combining high performance, fault tolerance, and rich SQL support in a modern columnar database system. Enter section select mode [Next\ \ How to Connect](https://docs.elest.io/books/clickhouse/chapter/how-to-connect) Back to top --- # Cluster Management | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse/chapter/cluster-management#main-content) Info Content Cluster Management ================== [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/clickhouse/page/overview-Ys0) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide ...](https://docs.elest.io/books/clickhouse/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/clickhouse/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/clickhouse/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/clickhouse/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/clickhouse/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/clickhouse/page/backups-and-restores) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/clickhouse/page/cluster-resynchronization) [#### Database Migration\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/clickhouse/page/database-migration) [#### Delete a Cluster\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/clickhouse/page/delete-a-cluster) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/clickhouse/page/restricting-access-by-ip) ### Search Results Clear Search [Previous\ \ Manual ClickHouse Migration Using clickhouse-...](https://docs.elest.io/books/clickhouse/page/manual-clickhouse-migration-using-clickhouse-backup) [Next\ \ Overview](https://docs.elest.io/books/clickhouse/page/overview-Ys0) Back to top --- # Adding a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse/page/adding-a-node#main-content) Info Content Adding a Node ============= As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, improve availability, and distribute workloads more effectively.  **Need to Add a Node** ---------------------- There are several scenarios where adding a node becomes necessary. One of the most common cases is **resource saturation** when existing nodes are fully utilized in terms of CPU, memory, or disk. Adding another node helps distribute the workload and maintain performance under load. In clusters that run **stateful services** or require **high availability**, having additional nodes ensures that workloads can fail over without downtime. Even in development environments, nodes can be added to isolate environments or test services under production-like load conditions. Scaling out also gives you flexibility when deploying services with different resource profiles or placement requirements. **Add a Node to Cluster** ------------------------- To begin, log in to the [Elestio dashboard](https://dash.elest.io/)  and navigate to the **Clusters** section from the sidebar. Select the cluster you want to scale. Once inside the cluster view, switch to the **Nodes** tab. This section provides an overview of all current nodes along with their health status and real-time resource usage. [![Screenshot 2025-06-09 at 1.05.37 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/screenshot-2025-06-09-at-1-05-37-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-06/screenshot-2025-06-09-at-1-05-37-pm.jpg) To add a new node, click the **“Add Node”** button. This opens a configuration panel where you can define the specifications for the new node. You’ll be asked to specify the amount of **CPU**, **memory**, and **disk** you want to allocate. If you’re using a bring-your-own-cloud setup, you may also need to confirm or choose the cloud provider and deployment region.[![Screenshot 2025-06-09 at 1.05.37 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/azlscreenshot-2025-06-09-at-1-05-37-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-06/azlscreenshot-2025-06-09-at-1-05-37-pm.jpg) After configuring the node, review the settings to ensure they meet your performance and cost requirements. Click **“Create”** to initiate provisioning. Elestio will begin setting up the new node, and once it’s ready, it will automatically join your cluster.[![Screenshot 2025-06-09 at 1.20.18 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/screenshot-2025-06-09-at-1-20-18-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-06/screenshot-2025-06-09-at-1-20-18-pm.jpg) Once provisioned, the new node will appear in the node list with its own metrics and status indicators. You can monitor its activity, verify that workloads are being scheduled to it, and access its logs directly from the dashboard. From this point onward, the node behaves like any other in the cluster and can be managed using the same lifecycle actions such as rebooting or draining. **Post-Provisioning Considerations** ------------------------------------ After the node has been added, it becomes part of the active cluster and is available for scheduling workloads. Elestio’s orchestration layer will begin using it automatically, but you can further customize service placement through resource constraints or affinity rules if needed. For performance monitoring, the dashboard provides per-node metrics, including CPU load, memory usage, and disk I/O. This visibility helps you confirm that the new node is functioning correctly and contributing to workload distribution as expected. Maintenance actions such as draining or rebooting the node are also available from the same interface, making it easy to manage the node lifecycle after provisioning. Enter section select mode [Previous\ \ Node Management](https://docs.elest.io/books/clickhouse/page/node-management) [Next\ \ Promoting a Node](https://docs.elest.io/books/clickhouse/page/promoting-a-node) Back to top --- # Removing a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/clickhouse/page/removing-a-node#main-content) Info Content Removing a Node =============== Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structured process designed to avoid disruption. The dashboard provides an accessible interface for performing this task while preserving workload stability. **Why Remove a Node?** ---------------------- Node removal is typically part of resource optimization or cluster reconfiguration. You might remove a node when reducing costs in a staging environment, when redistributing workloads across fewer or more efficient machines, or when phasing out a node for maintenance or retirement. Another common scenario is infrastructure rebalancing, where workloads are shifted to newer nodes with better specs or different regions. Removing an idle or underutilized node can simplify management and reduce noise in your monitoring stack. It also improves scheduling efficiency by removing unneeded targets from the orchestration engine. In high-availability clusters, node removal may be preceded by data migration or role reassignment (such as promoting a replica). Proper planning helps maintain system health while reducing reliance on unnecessary compute resources. **Remove a Node** ----------------- To begin the removal process, open the [Elestio dashboard](https://dash.elest.io/)  and navigate to the **Clusters** section. Select the cluster that contains the node you want to remove. From within the cluster view, open the **Nodes** tab to access the list of active nodes and their statuses. Find the node you want to delete from the list. If the node is currently running services, ensure that those workloads can be safely rescheduled to other nodes or are no longer needed. Since Elestio does not have a built-in drain option, any workload redistribution needs to be handled manually, either by adjusting deployments or verifying that redundant nodes are available. Once the node is drained and idle, open the action menu for that node and select **“Delete Node”**. [![Screenshot 2025-06-09 at 1.24.05 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/screenshot-2025-06-09-at-1-24-05-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-06/screenshot-2025-06-09-at-1-24-05-pm.jpg) The dashboard may prompt you to confirm the operation. After confirmation, Elestio will begin the decommissioning process. This includes detaching the node from the cluster, cleaning up any residual state, and terminating the associated virtual machine. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/bDHimage.png)](https://docs.elest.io/uploads/images/gallery/2025-06/bDHimage.png) Once the operation completes, the node will no longer appear in the cluster’s node list, and its resources will be released. **Considerations for Safe Node Removal** ---------------------------------------- Before removing a node in Elestio, it’s important to review the services and workloads currently running on that node. Since Elestio does not automatically redistribute or migrate workloads during node removal, you should ensure that critical services are either no longer in use or can be manually rescheduled to other nodes in the cluster. This is particularly important in multi-node environments running stateful applications, databases, or services with specific affinity rules. You should also verify that your cluster will have sufficient capacity after the node is removed. If the deleted node was handling a significant portion of traffic or compute load, removing it without replacement may lead to performance degradation or service interruption. In high-availability clusters, ensure that quorum-based components or replicas are not depending on the node targeted for deletion. Additionally, confirm that the node is not playing a special role such as holding primary data or acting as a manually promoted leader before removal. If necessary, reconfigure or promote another node prior to deletion to maintain cluster integrity. Enter section select mode [Previous\ \ Promoting a Node](https://docs.elest.io/books/clickhouse/page/promoting-a-node) [Next\ \ Backups and Restores](https://docs.elest.io/books/clickhouse/page/backups-and-restores) Back to top --- # Create your own templa... | docs.elest.io [Skip to main content](https://docs.elest.io/books/cicd-pipelines/page/create-your-own-template-elestioyml#main-content) Info Content Create your own template (elestio.yml) ====================================== You can **create your own template to be deployed on Elestio** for yourself (private repo) or for anyone (public repo). We recommend that you fork one of our sample repositories as a base and modify it to meet your requirements:  [Samples repositories for the most popular stacks & frameworks (52 Apps & Frameworks)](https://github.com/orgs/elestio-examples/repositories) To streamline the deployment process the application stack must be defined in [elestio.yml](https://github.com/elestio-examples/reactjs/blob/master/elestio.yml) , this file contains all details about the runtime, build/run commands, env vars, ports & reverse proxy. Here is an example [elestio.yml](https://github.com/elestio-examples/docker-compose-redis) file about a docker-compose-based stack (must be placed at the root of your repository) config: runTime: "dockerCompose" version: "" framework: "" installCommand: "" buildCommand: "docker-compose build" buildDir: "/" runCommand: "docker-compose up -d" isMonoRepoPackageInRoot: true/false environments: - key: "SOFTWARE_VERSION_TAG" value: "latest" - key: "SOFTWARE_PASSWORD" value: "random_password" - key: "ADMIN_EMAIL" value: "[EMAIL]" - key: "ADMIN_PASSWORD" value: "random_password" ports: - protocol: "HTTPS" targetProtocol: "HTTP" listeningPort: "443" targetPort: "8001" targetIP: "172.17.0.1" public: true path: "/" isAuth: true login: "root" password: "random_password" - protocol: "TCP" targetProtocol: "TCP" listeningPort: "26379" targetIP: "172.17.0.1" targetPort: "6379" public: true lifeCycleConfig: preInstallCommand: "./scripts/preInstall.sh" postInstallCommand: "./scripts/postInstall.sh" preBackupCommand: "./scripts/preBackup.sh" postBackupCommand: "./scripts/postBackup.sh" preRestoreCommand: "./scripts/preRestore.sh" postRestoreCommand: "./scripts/postRestore.sh" preUpdateCommand: "./scripts/preUpdateCommand.sh" postUpdateCommand: "./scripts/postUpdateCommand.sh" preDeployCommand: "./scripts/preDeployCommand.sh" postDeployCommand: "./scripts/postDeployCommand.sh" webUI: - url: "https://[CI_CD_DOMAIN]" label: "Redis Insight Web UI" login: "[ADMIN_EMAIL]" password: "[ADMIN_PASSWORD]" monoRepoWorkSpaces: [] ##### ##### **"config" section** **Runtime:** define the base runtime image used to build your app, possible values are: **NodeJs, Java, PHP, Ruby, Python, .NET, GO, static, dockerCompose, docker** **Version:** define the version of the runtime image used to build your app, a list of available versions is provided in the dropdown in our dashboard, you can find the corresponding values in the docker hub. **Framework:** based on the selected framework, our UI will auto-populate build/run commands & output directory. This is optional. **installCommand:** command to be executed only for the first deployment. **buildCommand:** indicate the command to execute to build your code. **runCommand:** indicate the command to execute to run your code. **buildDir:** indicate the directory where the build output will be placed. **isMonoRepoPackageInRoot:**  Not necessary unless you want to deploy a yarn/npm mono repo workspace. (Boolean type true/false) ##### **"environments" section** If your app requires env vars for configuration, you can define them one by one in the section. For each env var, you need to indicate the key and the value. Here is an example to define an env var named "DB\_TYPE" and with value "postgres": - key: "DB_TYPE" value: "postgres" You can use those variables in the "value" field: **random\_password:** this will be replaced by a randomly generated password on deployment. **\[EMAIL\]:** this will be replaced by the email address of the user deploying the pipeline on deployment. **\[CI\_CD\_DOMAIN\]:** this will be replaced by the CNAME of the pipeline on deployment. ##### **"ports" section** For each port exposed by your application you need to define a few fields: **protocol:** host protocol (exposed to the internet), which can be HTTP, HTTPS, TCP, or UDP.  **targetProtocol:** container protocol, which can be HTTP, HTTPS, TCP, or UDP. **listeningPort:** host port (exposed to the internet), any port between 1 to 65535.  **targetPort:** container port, any port between 1 to 65535.  **targetIP:** container IP address used as a reverse proxy target. You should leave it to 172.17.0.1 except if you know what you are doing.  **public:** can be true or false, if true, the app is exposed on the public IPV4, if not it's exposed only on the private ip address. **path:** relative path to the service in the container. You should keep "/" except if you know what you are doing.  **public:** can be true or false, if true the app will be exposed to the internet. **isAuth:** can be true or false, if true the app will require a basic authentication (define in login/password below) **login:** login to be required to access the service **password:** password to be required to access the service (can be any string, or **random\_password** described above**)** Here is an example to define an inbound route with HTTPS on port 443 pointing to a container running on port 8001 on the docker host with default IP 172.17.0.1, we also want the service to be protected with basic auth with the login "root" and a new random password generated at deploy time: - protocol: "HTTPS" targetProtocol: "HTTP" listeningPort: "443" targetPort: "8001" targetIP: "172.17.0.1" public: true path: "/" isAuth: true login: "root" password: "random_password" ##### **"lifeCycleConfig" section** Define custom scripts to be executed before or after installation, backup, or restore operations lifeCycleConfig: preInstallCommand: "./scripts/preInstall.sh" postInstallCommand: "./scripts/postInstall.sh" preBackupCommand: "./scripts/preBackup.sh" postBackupCommand: "./scripts/postBackup.sh" preRestoreCommand: "./scripts/preRestore.sh" postRestoreCommand: "./scripts/postRestore.sh" preUpdateCommand: "./scripts/preUpdateCommand.sh" postUpdateCommand: "./scripts/postUpdateCommand.sh" preDeployCommand: "./scripts/preDeployCommand.sh" postDeployCommand: "./scripts/postDeployCommand.sh" This is optional, if you want to use it just add the section and define the relative path from the root of your repository to the script to be executed when the event occurs. ##### **"copyCommandConfig" section** Define shortcuts pointing to the web UI. They will appear in the Elestio dashboard. copyCommandConfig: - ./myLocalFile1 . - ./myLocalFile2 . **\[CI\_CD\_DOMAIN\]** will be replaced at runtime with the pipeline CNAME address **\[EMAIL\]** will be replaced at runtime with the email address of the user deploying the pipeline In login and password, you can indicate the env vars to be used instead ##### **"monoRepoWorkSpaces" section** It will be of array type. example: \["workspace-a", "workspace-b"\] Not necessary unless you want to deploy a yarn/npm mono repo workspace and you're passing _true_ for _isMonoRepoPackageInRoot_ in the config section. ##### **"webUI" section** Define shortcuts pointing to the web UI. They will appear in the Elestio dashboard. webUI: - url: "https://[CI_CD_DOMAIN]/" label: "Admin Web UI" login: "[ADMIN_EMAIL]" password: "[ADMIN_PASSWORD]" **\[CI\_CD\_DOMAIN\]** will be replaced at runtime with the pipeline CNAME address **\[EMAIL\]** will be replaced at runtime with the email address of the user deploying the pipeline In login and password, you can indicate the env vars to be used instead You can then add a Deploy on Elestio button to your site or readme file like this: Deploy on Elest.io It will be displayed like this:  [![Deploy on Elest.io](https://raw.githubusercontent.com/elestio-examples/docker-compose-redis/main/deploy-on-elestio.png)](https://dash.elest.io/deploy?source=cicd&social=Github&thirdParty=true&url=https://github.com/elestio-examples/docker-compose-redis) Enter section select mode [Previous\ \ Custom domains on CI/CD pipelines](https://docs.elest.io/books/cicd-pipelines/page/custom-domains-on-cicd-pipelines) [Next\ \ Clone CI/CD pipeline](https://docs.elest.io/books/cicd-pipelines/page/clone-cicd-pipeline) Back to top --- # Cluster Management | docs.elest.io [Skip to main content](https://docs.elest.io/books/keydb/chapter/cluster-management#main-content) Info Content Cluster Management ================== [#### Overview\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps us...](https://docs.elest.io/books/keydb/page/overview-QjM) [#### Deploying a New Cluster\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide is...](https://docs.elest.io/books/keydb/page/deploying-a-new-cluster) [#### Node Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elesti...](https://docs.elest.io/books/keydb/page/node-management) [#### Adding a Node\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster ...](https://docs.elest.io/books/keydb/page/adding-a-node) [#### Promoting a Node\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may t...](https://docs.elest.io/books/keydb/page/promoting-a-node) [#### Removing a Node\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommissio...](https://docs.elest.io/books/keydb/page/removing-a-node) [#### Backups and Restores\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio pr...](https://docs.elest.io/books/keydb/page/backups-and-restores) [#### Restricting Access by IP\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the mo...](https://docs.elest.io/books/keydb/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that...](https://docs.elest.io/books/keydb/page/cluster-resynchronization) [#### Database Migrations\ \ When managing production-grade services, the ability to perform reliable and repeatable database ...](https://docs.elest.io/books/keydb/page/database-migrations) [#### Deleting a Cluster\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete wo...](https://docs.elest.io/books/keydb/page/deleting-a-cluster) ### Search Results Clear Search [Previous\ \ Manual Migration Using keydb-cli and Dump Files](https://docs.elest.io/books/keydb/page/manual-migration-using-keydb-cli-and-dump-files) [Next\ \ Overview](https://docs.elest.io/books/keydb/page/overview-QjM) Back to top --- # Node Management | docs.elest.io [Skip to main content](https://docs.elest.io/books/redis/page/node-management#main-content) Info Content Node Management =============== Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining stability and performance.  **Understanding Nodes** ----------------------- In Elestio, a **node** is a virtual machine that contributes compute, memory, and storage resources to a cluster. Clusters can be composed of a single node or span multiple nodes, depending on workload demands and availability requirements. Each node runs essential services and containers as defined by your deployed applications or databases. Nodes in Elestio are provider-agnostic, meaning the same concepts apply whether you’re using Elestio-managed infrastructure or connecting your own cloud provider (AWS, Azure, GCP, etc.). Each node is isolated at the VM level but participates fully in the cluster’s orchestration and networking. This abstraction allows you to manage infrastructure without diving into the complexity of underlying platforms. **Node Operations** ------------------- The Elestio dashboard allows you to manage the lifecycle of nodes through clearly defined operations. These include: * **Creating a node**, which adds capacity to your cluster and helps with horizontal scaling of services. This is commonly used when load increases or when preparing a high-availability deployment. * **Deleting a node**, which removes underutilized or problematic nodes. Safe deletion includes draining workloads to ensure service continuity. * **Promoting a node**, which changes the role of a node within the cluster—typically used in clusters with redundancy, where certain nodes may need to take on primary or leader responsibilities. Each of these operations is designed to be safely executed through the dashboard and is validated against the current cluster state to avoid unintended service disruption. These actions are supported by Elestio’s backend orchestration, which handles tasks like container rescheduling and load balancing when topology changes. **Monitoring and Maintenance** ------------------------------ Monitoring is a key part of effective node management. Elestio provides per-node visibility through the dashboard, allowing you to inspect **CPU**, **memory**, and **disk utilization** in real time. Each node also exposes **logs**, **status indicators**, and **health checks** to help detect anomalies or degradation early. In addition to passive monitoring, the dashboard supports active maintenance tasks. You can **reboot a node** when applying system-level changes or troubleshooting, or **drain a node** to safely migrate workloads away from it before performing disruptive actions. Draining ensures that running containers are rescheduled on other nodes in the cluster, minimizing service impact. For production setups, combining resource monitoring with automation like scheduled reboots, log collection, and alerting can help catch issues before they affect users. While Elestio handles many aspects of orchestration automatically, having visibility at the node level helps teams make informed decisions about scaling, updates, and incident response. Cluster-wide resource graphs and node-level metrics are also useful for capacity planning. Identifying trends such as memory saturation or disk pressure allows you to preemptively scale or rebalance workloads, reducing the risk of downtime. Enter section select mode [Previous\ \ Deploying a New Cluster](https://docs.elest.io/books/redis/page/deploying-a-new-cluster) [Next\ \ Adding a Node](https://docs.elest.io/books/redis/page/adding-a-node) Back to top --- # Promoting a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/keydb/page/promoting-a-node#main-content) Info Content Promoting a Node ================ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. While not always needed in basic setups, node promotion becomes essential in distributed systems, replicated databases, or services requiring failover control. **When to Promote a Node?** --------------------------- Promoting a node is typically performed in clusters where role-based architecture is used. In high-availability setups, some nodes may act as leaders while others serve as followers or replicas. If a leader node becomes unavailable or needs to be replaced, you can promote another node to take over its responsibilities and maintain continuity of service. Node promotion is also useful when scaling out and rebalancing responsibilities across a larger cluster. For example, promoting a node to handle scheduling, state tracking, or replication leadership can reduce bottlenecks and improve responsiveness. In cases involving database clusters or consensus-driven systems, promotion ensures a clear and controlled transition of leadership without relying solely on automatic failover mechanisms. **Promote a Node in Elestio** ----------------------------- To promote a node, start by accessing the **Clusters** section in the [Elestio dashboard](https://dash.elest.io/) . Choose the cluster containing the node you want to promote. Inside the cluster view, navigate to the **Nodes** tab to see the full list of nodes, including their current roles, health status, and resource usage. Locate the node that you want to promote and open its action menu. From here, select the **“Promote Node”** option. [![Screenshot 2025-06-24 at 2.28.21 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/screenshot-2025-06-24-at-2-28-21-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-06/screenshot-2025-06-24-at-2-28-21-pm.jpg) You may be prompted to confirm the action, depending on the configuration and current role of the node. This confirmation helps prevent unintended role changes that could affect cluster behavior. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/btgimage.png)](https://docs.elest.io/uploads/images/gallery/2025-06/btgimage.png) Once confirmed, Elestio will initiate the promotion process. This involves reconfiguring the cluster’s internal coordination state to acknowledge the new role of the promoted node. Depending on the service architecture and the software running on the cluster, this may involve reassigning leadership, updating replication targets, or shifting service orchestration responsibilities. After promotion is complete, the node’s updated role will be reflected in the dashboard. At this point, it will begin operating with the responsibilities assigned to its new status. You can monitor its activity, inspect logs, and validate that workloads are being handled as expected. **Considerations for Promotion** -------------------------------- Before promoting a node, ensure that it meets the necessary resource requirements and is in a stable, healthy state. Promoting a node that is under high load or experiencing performance issues can lead to service degradation. It’s also important to consider replication and data synchronization, especially in clusters where stateful components like databases are in use. Promotion is a safe and reversible operation, but it should be done with awareness of your workload architecture. If your system relies on specific leader election mechanisms, promoting a node should follow the design patterns supported by those systems. Enter section select mode [Previous\ \ Adding a Node](https://docs.elest.io/books/keydb/page/adding-a-node) [Next\ \ Removing a Node](https://docs.elest.io/books/keydb/page/removing-a-node) Back to top --- # Backups and Restores | docs.elest.io [Skip to main content](https://docs.elest.io/books/keydb/page/backups-and-restores#main-content) Info Content Backups and Restores ==================== Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastructure failure. The platform includes an automated backup system with configurable retention policies and a straightforward restore process, all accessible from the dashboard. Whether you’re operating a production database or a test environment, understanding how backups and restores work in Elestio is critical for maintaining service reliability. **Cluster Backups** ------------------- Elestio provides multiple backup mechanisms designed to support various recovery and compliance needs. Backups are created automatically for most supported services, with consistent intervals and secure storage in managed infrastructure. These backups are performed in the background to ensure minimal performance impact and no downtime during the snapshot process. Each backup is timestamped, versioned, and stored securely with encryption. You can access your full backup history for any given service through the dashboard and select any version for restoration.  You can utilize different backup options depending on your preferences and operational requirements. Elestio supports **manual local backups** for on-demand recovery points, **automated snapshots** that capture the state of the service at fixed intervals, and **automated remote backups using Borg**, which securely stores backups on external storage volumes managed by Elestio. In addition, you can configure **automated external backups to S3-compatible storage**, allowing you to maintain full control over long-term retention and geographic storage preferences. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/iWzimage.png)](https://docs.elest.io/uploads/images/gallery/2025-06/iWzimage.png) **Restoring from a Backup** --------------------------- Restoring a backup in Elestio is a user-initiated operation, available directly from the service dashboard. Once you’re in the dashboard, select the service you’d like to restore. Navigate to the **Backups** section, where you’ll find a list of all available backups along with their creation timestamps. To initiate a restore, choose the desired backup version and click on the **“Restore”** option. You will be prompted to confirm the operation. Depending on the type of service, the restore can either overwrite the current state or recreate the service as a new instance from the selected backup. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-06/scaled-1680-/ZXiimage.png)](https://docs.elest.io/uploads/images/gallery/2025-06/ZXiimage.png) The restore process takes a few minutes, depending on the size of the backup and the service type. Once completed, the restored service is immediately accessible. In the case of databases, you can validate the restore by connecting to the database and inspecting the restored data. **Considerations for Backup & Restore** --------------------------------------- * Before restoring a backup, it’s important to understand the impact on your current data. Restores may **overwrite existing service state**, so if you need to preserve the current environment, consider creating a manual backup before initiating the restore. In critical environments, restoring to a new instance and validating the data before replacing the original is a safer approach. * Keep in mind that restore operations are not instantaneous and may temporarily affect service availability. It’s best to plan restores during maintenance windows or periods of low traffic, especially in production environments. * For services with high-frequency data changes, be aware of the backup schedule and retention policy. Elestio’s default intervals may not capture every change, so for high-volume databases, consider exporting incremental backups manually or using continuous replication where supported. **Monitoring Backup Health** ---------------------------- Elestio provides visibility into your backup history directly through the dashboard. You can monitor the **status**, **timestamps**, and **success/failure** of backup jobs. In case of errors or failed backups, the dashboard will display alerts, allowing you to take corrective actions or contact support if necessary. It’s good practice to periodically verify that backups are being generated and that restore points are recent and complete. This ensures you’re prepared for unexpected failures and that recovery options remain reliable. Enter section select mode [Previous\ \ Removing a Node](https://docs.elest.io/books/keydb/page/removing-a-node) [Next\ \ Restricting Access by IP](https://docs.elest.io/books/keydb/page/restricting-access-by-ip) Back to top --- # Database Migration Ser... | docs.elest.io [Skip to main content](https://docs.elest.io/books/postgresql/page/database-migration-service-for-postgresql#main-content) Info Content Database Migration Service for PostgreSQL ========================================= Elestio provides a structured approach for migrating PostgreSQL databases from various environments, such as on-premises systems or other cloud platforms, to its managed services. This process ensures data integrity and minimizes downtime, facilitating a smooth transition to a managed environment.​ **Key Steps in Migrating to Elestio** ------------------------------------- #### **Pre-Migration Preparation** Before initiating the migration process, it's essential to undertake thorough preparation to ensure a smooth transition: * **Create an Elestio Account:** Register on the Elestio platform to access their suite of managed services. This account will serve as the central hub for managing your PostgreSQL instance and related resources. * **Deploy the Target PostgreSQL Service:** Set up a new PostgreSQL instance on Elestio to serve as the destination for your data. It's crucial to match the software version of your current PostgreSQL database to avoid compatibility issues during data transfer. Detailed prerequisites and guidance can be found in Elestio's [migration documentation](https://docs.elest.io/books/databases/page/postgresql-database-migration-to-elestio) . #### **Initiating the Migration Process** With the preparatory steps completed, you can proceed to migrate your PostgreSQL database to Elestio: 1. **Access the Migration Tool:** Navigate to the overview of your PostgreSQL service on the Elestio dashboard. Click on the "Migrate Database" button to initiate the migration process. This tool is designed to facilitate a smooth transition by guiding you through each step. 2. **Configure Migration Settings:** A modal window will open, prompting you to ensure that your target service has sufficient disk space to accommodate your database. Adequate storage is vital to prevent interruptions during data transfer. Once confirmed, click on the "Get started" button to proceed. 3. **Validate Source Database Connection:** Provide the connection details for your existing PostgreSQL database, including: * **Hostname:** The address of your current database server. * **Port:** The port number on which your PostgreSQL service is running (default is 5432). * **Database Name:** The name of the database you intend to migrate. * **Username:** The username with access privileges to the database. * **Password:** The corresponding password for the user. After entering these details, click on "Run Check" to validate the connection. This step ensures that Elestio can securely and accurately access your existing data. You can find these details under Database admin section under your deployed PostgreSQL service. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-03/scaled-1680-/y44image.png)](https://docs.elest.io/uploads/images/gallery/2025-03/y44image.png) 4. **Execute the Migration:** If all checks pass without errors, initiate the migration by selecting "Start migration." Monitor the progress through the real-time migration logs displayed on the dashboard. This transparency allows for immediate detection and resolution of any issues, ensuring data integrity throughout the process. #### **Post-Migration Validation and Optimization** After completing the migration, it's crucial to perform validation and optimization tasks to ensure the integrity and performance of your database in the new environment: * **Verify Data Integrity:** Conduct thorough checks to ensure all data has been accurately transferred. This includes comparing row counts, checksums, and sample data between the source and target databases. Such verification maintains the reliability of your database and ensures that no data was lost or altered during migration. * **Test Application Functionality:** Ensure that applications interacting with the database function correctly in the new environment. Update connection strings and configurations as necessary to reflect the new database location. This step prevents potential disruptions and ensures seamless operation of dependent systems. * **Optimize Performance:** Utilize Elestio's managed service features to fine-tune database performance. Set up automated backups to safeguard your data, monitor resource utilization to identify and address bottlenecks, and configure scaling options to accommodate future growth. These actions contribute to improved application responsiveness and overall system efficiency. * **Implement Security Measures:** Review and configure security settings to protect your data within the Elestio environment. Set up firewalls to control access, manage user access controls to ensure only authorized personnel can interact with the database, and enable encryption where applicable to protect data at rest and in transit. Implementing these security measures safeguards your data against unauthorized access and potential threats. **Benefits of Using Elestio for PostgreSQL** -------------------------------------------- Migrating your PostgreSQL database to Elestio offers several advantages:​ * **Simplified Management:** Elestio automates database maintenance tasks, including software updates, backups, and system monitoring, reducing manual work. The platform provides a dashboard with real-time insights into database performance and resource usage. It allows for adjusting service plans, scaling CPU and RAM as needed. Users can modify environment variables and access software information to manage configurations. * **Security:** Elestio keeps PostgreSQL instances updated with security patches to protect against vulnerabilities. The platform automates backups to ensure data integrity and availability. It provides secure access mechanisms, including randomly generated passwords for database instances, which can be managed through the dashboard. * **Performance:** Elestio configures PostgreSQL instances for performance based on workload requirements. The platform supports the latest PostgreSQL versions, incorporating updates that improve database operations. Its infrastructure handles different workloads and maintains performance during high usage periods. * **Scalability:** Elestio's PostgreSQL service allows for scaling database resources to handle growth and changing workloads without major downtime. Users can upgrade or downgrade service plans, adjusting CPU and RAM as needed. The platform supports adding network volumes to increase storage capacity. Enter section select mode [Previous\ \ Database Migration](https://docs.elest.io/books/postgresql/chapter/database-migration) [Next\ \ Cloning a Service to Another Provider or Region](https://docs.elest.io/books/postgresql/page/cloning-a-service-to-another-provider-or-region) Back to top --- # Unknown Managed DB Overview Global Elestio offers comprehensive services, including various support plans, support for multiple database types, and robust backup retention policies.  Support Plans Elestio offers flexible support plans tailored to meet different user needs, ensuring smooth deployment and operation of services. Level 1 : This plan is included for free, and provides 7 days of remote backup retention, an email support channel, a 3-day response time, proactive monitoring, access to documentation & community forums, and direct console support access. However, this plan does not include service snapshots or an SLA (Service Level Agreement), making it most suitable for testing environments. Level 2 : Priced at $0.0685 per hour , offers 14 days of remote backup retention, 2 service snapshots, an email support channel, a 24-hour response time (business hours), and proactive monitoring. It also includes priority queuing, ensuring faster support response times compared to Level 1. This plan is recommended for staging environments where higher reliability is required. Level 3 : At $0.2740 per hour , is designed for enterprise and production environments, offering 30 days of remote backup retention, 4 service snapshots, access to email & phone support channels, and a 4-hour response time during business hours. Additionally, it includes proactive monitoring with email alerts, priority queuing, and a dedicated Customer Success Manager for personalized assistance. Database Types Elestio supports a comprehensive range of databases, each tailored to meet specific application requirements. Below is an overview of the supported databases, categorized for clarity: Relational Databases: MySQL : A widely adopted open-source relational database management system (RDBMS) renowned for its reliability, flexibility, and speed. It serves as a foundational component for many web applications and operates seamlessly across various platforms, including Linux, UNIX, and Windows. PostgreSQL : An advanced, enterprise-class open-source relational database known for its extensibility and standards compliance. It supports complex queries and offers robust performance, making it suitable for large-scale applications. MariaDB : A community-developed fork of MySQL, MariaDB offers enhanced features and improved performance. It ensures high compatibility with MySQL while providing additional storage engines and tools for better scalability. TimescaleDB : A time-series database built on PostgreSQL, optimized for complex queries and high ingest rates. It is designed to handle time-series data efficiently, making it ideal for applications involving monitoring, IoT, and real-time analytics. NoSQL Databases: Redis : An open-source, in-memory key-value data store used as a database, cache, and message broker. It supports various data structures and offers high performance for read and write operations, suitable for real-time applications. KeyDB : A high-performance fork of Redis, KeyDB introduces multi-threading capabilities, leading to improved efficiency and throughput. It maintains compatibility with Redis protocols while offering enhanced performance. Cassandra : An open-source NoSQL distributed database management system designed to handle large amounts of data across many commodity servers. It provides high availability with no single point of failure, making it suitable for mission-critical applications. ScyllaDB : A distributed NoSQL database designed for high performance and low latency. It is compatible with Apache Cassandra and Amazon DynamoDB, offering high throughput and minimal latency for data-intensive applications. Specialized Databases: ClickHouse : An open-source, columnar database management system optimized for online analytical processing (OLAP). It allows for real-time data analysis and is capable of processing large volumes of data quickly. Neo4j : A graph database management system optimized for connected data. It efficiently stores and queries data relationships, making it ideal for applications like social networks, recommendation engines, and fraud detection. Milvus : A vector database designed for embedding similarity search. It is widely used in AI applications to manage and search large-scale vector data, facilitating tasks like image retrieval, natural language processing, and recommendation systems. Weaviate : An open-source vector search engine that enables efficient semantic search and data exploration. It leverages machine learning models to provide context-aware search results, enhancing the user experience in information retrieval applications. Backup Retention Policy Elestio employs comprehensive backup strategies to ensure the safety and integrity of your data. Below is an expanded overview of each backup method, along with their respective retention policies, tailored to different support plans: Manual Local Backups : These are user-initiated backups stored directly on the local server. They are particularly useful for quickly safeguarding small datasets or before making significant changes to applications. While they offer immediate access and rapid restoration, it's important to note that they do not provide redundancy against hardware failures or catastrophic events affecting the local environment. Automated Remote Backups (Borg) : Utilizing the Borg backup system, these backups are automatically transmitted to a different datacenter located on the same continent as your service. This approach ensures data redundancy and protection against local failures. The use of Borg allows for efficient, deduplicated, and encrypted backups, optimizing storage usage and enhancing security. Automated External Backups (S3-Compatible Storage) : Elestio offers the capability to store backups in your own S3 bucket, compatible with AWS S3 and any S3-compatible provider. This method provides you with direct ownership and control over your backups, facilitating integration with existing cloud storage solutions and compliance with organizational policies. Retention Periods Based on Support Plans : Level 1 (Standard) : Backups are retained for 7 days , offering a basic level of data protection suitable for development or testing environments. Level 2 (Premium) : Backups are retained for 14 days , providing an extended safety net ideal for staging environments or applications with moderate data volatility. Level 3 (Enterprise) : Backups are retained for 30 days , ensuring long-term data availability and compliance, suitable for critical production environments requiring stringent data protection measures. For more detailed information on Elestio's backup strategies and retention policies, please refer to their official backup documentation. --- # Privacy policies | docs.elest.io [Skip to main content](https://docs.elest.io/books/legal-compliance/page/privacy-policies#main-content) Info Content Privacy policies ================ Elestio (“Elestio” / “We”) is aware that users of Elest.io and its related applications (“Users” / “You”) value their privacy. The purpose of this Privacy Statement is to provide You with relevant information regarding the use and disclosure of personal information of Users collected though the site. We provide this Privacy Statement to help You make informed decisions on whether to use or continue using Elest.io. This Privacy Statement is incorporated in the Elestio’s Terms of Use and is subject to them. Capitalized terms which are not defined herein shall have the meaning set forth in our Terms of Use. Your use of Elest.io, and all of the personal information You provide in connection with such use, remain subject to the terms of this Privacy Statement, as well as to Elestio’s Terms of Use. Please note that any image, video, or any other content posted by Users on websites or applications created using Elest.io become published content; hence these are not considered “personally identifiable information”, and therefore are not subject to this Privacy Statement. **1\. Information Collected by Elestio** Upon registration, purchase of Services, and at each time You visit Elest.io or You access Your account, We collect the following information: a) User Provided Information: Personally identifiable information (such as name and email address) that You provide to Elestio when registering to use Elestio services, or using different functionalities on the User Apps such as uploading images and captions, uploading videos, posting messages in forums, etc. b) Billing Information: Elestio will collect billing information if You sign up for a paid Service, which may include Your name, address, telephone number, credit card details, and other information that is necessary in order to process the transaction. Likewise, when purchasing Our Services, Elestio may collect additional details in order to process payments and comply with tax law, which may include Your social security number or EIN, Your address, and other information, as appropriate. Under no circumstance do we store any of Your sensitive billing details. We do not retain the details of Your credit card, as this information is discarded once Your transaction is processed. Since the subscription is auto-renewed, a recurring subscription will be created by Stripe, our third-party payment gateway. Stripe will store Your billing information on their secure payment gateway, for as long as necessary, to carry out the terms of Your subscription. Should You close Your Elestio account, Your billing information will be removed by Stripe. c) Cookies: When You visit Elest.io, We may send one or more cookies - a small text file containing a string of alphanumeric characters - to Your computer that uniquely identifies Your browser. We use, both, session cookies and persistent cookies. A persistent cookie remains on Your hard drive after You close Your browser. Persistent cookies may be used by Your browser on subsequent visits to the site. Persistent cookies can be removed by following Your web browser's help file directions. A session cookie is temporary, and disappears after You close Your browser. You can reset Your web browser to refuse all cookies or to indicate when a cookie is being sent. However, some functionalities of Elest.io may not work properly if the feature “accept cookies” is disabled. d) Log Files: Log file information is automatically reported by Your browser each time You view a webpage. When You view or register on Elest.io, Our servers automatically record certain information that Your web browser sends whenever You visit a website. These server logs may include information such as Your web request, Internet Protocol (IP) address, browser type, browser language, referring/exit pages and Universal Resource Locators (URL), platform type, number of clicks, domain names, landing pages, pages viewed and the order of those pages, the amount of time spent on particular pages, the date and time of Your request, and one or more cookies that may uniquely identify Your browser. **2\. Use of the Information** If You submit personally identifiable information to Us through Elest.io, We may use Your personal information to: a) Provide the Services to You. b) Provide customer support, respond and communicate with You about Your requests, questions, and comments. c) Diagnose or fix technical problems. d) Offer You Services that may be of interest to You. e) Operate, evaluate, and improve Our business (including developing new Services, managing Our communications, determining the effectiveness of Our sales, marketing, and advertising, analyzing and enhancing our Services, websites, and apps, and performing accounting, auditing, invoicing, reconciliation, and collection activities). f) Perform data analysis (including market and consumer search, trend analysis, financial analysis, and anonymization of personal information). g) Protect against, identify, and prevent fraud and other criminal activity, claims, and other liabilities. h) Comply with applicable legal requirements and our policies. Please be aware that any personal information or content that You voluntarily disclose online (on discussion boards, in messages areas, and blogs, within Your public profile page, etc.) becomes publicly available, and can be collected and used by others. Any images, captions, videos, or other content that You submit to the Elestio Apps may be redistributed through the Internet and other media channels, and may be viewed by the general public. **3\. Disclosure of Information** We do not sell, or otherwise share, personal information about You, except as described in this Privacy Statement. We may share personal information with third parties who perform services on Our behalf, based on Our instructions. These third parties are not authorized by us to use or disclose the information, except as necessary to perform services on Our behalf or comply with legal requirements. We may release personally identifiable information and/or non-personally identifiable information if required to do so by law, or in the good-faith belief that such action is necessary to comply with state laws or respond to a court order, subpoena, or search warrant. It may be necessary to share information in order to investigate, prevent, or take action regarding suspected or actual illegal activities, including, but not limited to, fraud, potential threats to public safety or the physical safety of any person, violations of Our Terms of Service, or as otherwise permitted by law. Elestio also reserves the right to disclose personally identifiable information and/or non-personally identifiable information that Elestio believes, in good-faith, is appropriate or necessary to enforce our Terms of Use, take precautions against liability, to investigate and defend Ourselves against any third-party claims or allegations, to assist government enforcement agencies, to protect the security or integrity of our websites, products, and services, and to exercise or protect the rights, property, or personal safety of Elestio, Our staff, our Users, or others. **4\. User Rights** The General Data Protection Regulation provides you with several rights under the legislation as a data subject. We will respond to your requests within one month of the receipt of your request, or inform you, in circumstances where an extension may be required. You are not obligated by law to provide Us with any information. You hereby acknowledge, warrant, and agree that any information You do provide Us is provided of Your own free will and consent, for the purposes and uses described herein. a) Right of Access We will provide You with certain details relating to Your information upon receipt of a request by email from You to support@Elest.io. In order to protect the security of Your information: b) Right to Rectification All information that Elestio stores related to Your account is accessible through Your user account. You may use this interface to correct, update or delete Your information at any time. We encourage You to keep this information up to date so Your customer service requests and billing processes operate efficiently. c) Right to Erasure To completely remove your personal informations from our system, send an email to support@Elest.io, and ask for an account deletion. We will require you to confirm certain security information in order to verify your identity, and process your request. c) Right to Data Portability You can request to receive your personal data, which you provided to us, in a structured, commonly used, and machine readable format, and have the right to transmit this data to another controller. d) Data Retention We will retain Your information for as long as Your account is active, or as needed to provide You Services. We will retain and use Your information as necessary to comply with Our legal obligations, resolve disputes, and enforce Our agreements. e) Right to Lodge a Complaint with Data Protection Commissioner You have the right to lodge a complaint with the Data Protection Commissioner by emailing info@dataprotection.ie, or by writing to the Data Protection Commissioner, Canal House, Station Road, Portarlington, R32 AP23 Co. Laois, Ireland. **4.1 Data Protection Officer (DPO)** We have appointed a Data Protection Officer (DPO) responsible for overseeing questions in relation to this privacy policy and our data protection practices. If you have any questions about this policy or how we handle your personal data, including any requests to exercise your legal rights, please contact our DPO (Steven Betito) at: steven@elest.io **5\. Data Security** We maintain administrative, technica,l and physical safeguards designed to protect the personal information that You provide against accidental, unlawful, or unauthorised destruction, loss, alteration, access, disclosure, or use. We cannot, however, ensure or warrant the security of any information You provide to Elestio, and You do so at Your own risk. Once We receive the information You submitted, Elestio makes commercially-reasonable efforts to ensure the security of Our systems. However, please note it is not guaranteed that such information may not be accessed, disclosed, altered, or destroyed by breach of any of our physical, technical, or managerial safeguards. To protect Your privacy and security, We take reasonable steps (such as requesting a unique password) to verify Your identity before granting You profile access or making corrections. You are responsible for maintaining the secrecy of Your unique password and account information at all times. If Elestio is aware of a security systems breach, then We may (i) notify You electronically so that You can take appropriate protective steps, or (ii) post a notice on Our Website. Given that the Internet is a global environment, using it to collect and process personal data involves the transmission of data on an international basis. This means, for instance, that data You pass to Us may be processed outside the European Economic Area, although the data will always be held securely and in accordance with applicable law. When processed as part of a hosted service, the information will be processed and stored on the servers of third-party providers hired to provide the hosting, and our agreements with such parties require that they not use, disclose, or share such information. **6\. Policy on Responding to External Requests for Customer Data** Elestio is committed to protecting the privacy, security, and confidentiality of our customers’ data. We will only consider external requests for customer data if one of the following conditions is met: The request is made pursuant to a valid and enforceable court order, warrant, or statutory obligation recognised under Irish or EU law. The request is routed through an applicable international legal assistance mechanism (e.g., MLAT). We have obtained the freely given, specific, informed, and unambiguous consent of the data subject. There is a legitimate legal obligation under Irish or EU law compelling disclosure.   We limit data collection and retention to the minimum necessary for operational purposes. We use robust security measures, including encryption, access controls, and data segregation, to protect customer data. As a result, certain data may be inaccessible even if a valid request is received. We aim to notify affected customers of any third-party data request involving their information, unless: We are legally prohibited from doing so, The request is clearly non-contentious and already disclosed under applicable terms (e.g., fraud detection), Immediate disclosure would compromise an investigation or endanger individuals. **7\. Other Sites** Our Website may contain links to other websites that are outside Our control and are not covered by this Privacy Statement. If You access other sites using the links provided, the operators of these sites may collect information from You that will be used by them in accordance with their Privacy Statement, which may differ from Ours. **8\. Changes and Updates to This Privacy Statement** This Privacy Statement may be revised periodically, and this will be reflected on the “last modification date” stated below. Please revisit this page to stay aware of any changes. In general, We only use Your personal information in the manner described in the Privacy Statement in effect at the time We received the personal information You provided. Your use of Our Website constitutes Your agreement to this Privacy Statement and any future revisions. **9\. Contact Information** You may contact Elestio in relation to this Privacy Statement by emailing support@elest.io. Last modification date: 2025-08-06 13:05:15 Enter section select mode [Previous\ \ Terms & Conditions](https://docs.elest.io/books/legal-compliance/page/terms-conditions) [Next\ \ Subcontractors](https://docs.elest.io/books/legal-compliance/page/subcontractors) Back to top --- # Custom domain and auto... | docs.elest.io [Skip to main content](https://docs.elest.io/books/security/page/custom-domain-and-automated-encryption-ssltls#main-content) Info Content Custom domain and automated encryption (SSL/TLS) ================================================ If you have activated the firewall on your service ensure port 80 is open or else certificate creation/renewal will fail Access the "Manage SSL Domains" option within the "Custom Domain Names" row located in the overview tab of the service dashboard. [![Screenshot 2022-09-29 163437.png](https://docs.elest.io/uploads/images/gallery/2022-09/screenshot-2022-09-29-163437.png)](https://docs.elest.io/uploads/images/gallery/2022-01/image-1643091885361.png) From there, you can manage allowed domains for SSL. If you want to add a new domain, type it and press enter to add it to the list of authorized domains. You will also need to create a DNS entry to point your domain to the IP address of your service. You can create an A or CNAME record to point to your service. CNAME is preferred as it won't change even if your IP changes (e.g., this can happen if you clone/migrate your service to another provider). Once added, you can verify if your DNS entry is propagated with a tool like [https://dnschecker.org/](https://dnschecker.org/) Once propagated, SSL should work instantly on your service. The certificate will be automatically generated and renewed. * * * ##### _**Important**_ For some software, you must also update an env var to indicate the domain to be used. To do that in the overview screen of your service click on the  UPDATE CONFIG button > Env tab > there update the domain env var with your domain * * * ##### **Cloudflare users** If you are using Cloudflare reverse proxy (orange cloud icon), please check detailed instructions about [Cloudflare & Elestio](https://docs.elest.io/books/security/page/using-cloudflare) here: [https://docs.elest.io/books/security/page/using-cloudflare](https://docs.elest.io/books/security/page/using-cloudflare) * * * ##### **Troubleshooting SSL not generated** You can display the nginx log with this command in a terminal: cd /opt/elestio/nginx; docker-compose logs -f; Press Ctrl+C to stop displaying the live logs * * * ##### **Reset SSL\_DATA folder** In some cases, the **/opt/elestio/nginx/ssl\_data** folder can become corrupt. If this happens, connect to a terminal and try this: cd /opt/elestio/nginx/; docker-compose down; mv ./ssl_data/ ./ssl_data_old/; mkdir ./ssl_data/; chmod 777 ./ssl_data/; docker-compose up -d Once executed, just open your custom website URL again, and your certificate should be generated and your site served over SSL/TLS. Enter section select mode [Previous\ \ Overview](https://docs.elest.io/books/security/page/overview) [Next\ \ Nginx advanced configuration](https://docs.elest.io/books/security/page/nginx-advanced-configuration) Back to top --- # Unknown \# Domains Domains # Buying a Domain from Elest.io > ##### Great brand names are like magnets that people gravitate towards. Try \[https://elest.io/domains\](https://t.co/A6jnS1w95h) domains to get your business's unique brand identity. In today's fast-paced digital world, establishing a strong online presence is crucial for businesses, individuals, and creative projects alike. One of the foundational steps in building this presence is securing a domain name that reflects your brand, vision, or purpose. In this guide, we'll walk you through the process of purchasing a domain from Elest.io, a trusted domain registration platform known for its user-friendly interface and reliable services. \### Why Choose Elest.io? ##### Elest.io stands out as a reputable domain registration platform for several reasons: 1\. \*\*Simplicity and User-Friendly Experience:\*\* Navigating through the domain purchasing process can be intimidating, especially for newcomers. Elest.io's intuitive interface makes the process easy, even for those with minimal technical experience. \*\*2. Wide Range of Domain Extensions:\*\* Elest.io offers a diverse selection of domain extensions, from the classic ".com" to more specialized options like ".io," ".tech," and ".app." This ensures you'll find a domain that aligns perfectly with your project's identity. \*\*3. Transparent Pricing:\*\* Transparent pricing is a hallmark of Elest.io's approach. You won't encounter hidden fees or surprises during the checkout process. What you see is what you pay. \### Step-by-Step Guide to Purchasing a Domain from Elest.io: \##### \*\*Step 1: Navigate to Elest.io\*\* Visit the \[\*\*Elest.io\*\*\](https://elest.io/ "Elest.io") website and navigate to domains inside the "\*\*\*Features\*\*"\* Tab https://elest.io/domains use the search bar to input your desired domain name. The platform will instantly display available domain options. \##### \*\*Step 2: Choose Your Domain\*\* Select the domain name that best suits your needs. Keep in mind that shorter, memorable names are often more effective. If your first choice isn't available, Elest.io might suggest alternatives that maintain the essence of your original idea. \[!\[Screenshot 2023-08-18 175401.png\](https://docs.elest.io/uploads/images/gallery/2023-08/scaled-1680-/screenshot-2023-08-18-175401.png)\](https://docs.elest.io/uploads/images/gallery/2023-08/screenshot-2023-08-18-175401.png) \##### \*\*Step 3: Check Availability and Pricing\*\* Elest.io will provide real-time information about the availability of your chosen domain name. \[!\[Screenshot 2023-08-18 175528.png\](https://docs.elest.io/uploads/images/gallery/2023-08/scaled-1680-/screenshot-2023-08-18-175528.png)\](https://docs.elest.io/uploads/images/gallery/2023-08/screenshot-2023-08-18-175528.png) \##### \*\*Step 4: Purchase\*\* When you're happy with your choice and it's available, click the "\*\*\*Purchase"\* \*\*button, which will take you to the Elestio dashboard where you may complete the rest of the process. \[!\[Screenshot 2023-08-18 175614.png\](https://docs.elest.io/uploads/images/gallery/2023-08/scaled-1680-/screenshot-2023-08-18-175614.png)\](https://docs.elest.io/uploads/images/gallery/2023-08/screenshot-2023-08-18-175614.png) \##### \*\*Step 5: Review and Proceed\*\* You can evaluate your domain pricing and alternative domain options here. Then, after reviewing, click the "\*\*\*Proceed"\*\*\* button to move on to the next stage. \[!\[Screenshot 2023-08-18 175659.png\](https://docs.elest.io/uploads/images/gallery/2023-08/scaled-1680-/screenshot-2023-08-18-175659.png)\](https://docs.elest.io/uploads/images/gallery/2023-08/screenshot-2023-08-18-175659.png) \##### \*\*Step 6: Personal Details and Year Selection.\*\* \*\*Elest.io takes data security seriously, so you can rest assured that your information is in safe hands.\*\* Review and update your personal information to make sure it is complete and accurate. Choose how many years you wish to register your domain for as well. Using the renewal domain option after acquiring a domain, you may easily change the registration year. \[!\[Screenshot 2023-08-18 175831.png\](https://docs.elest.io/uploads/images/gallery/2023-08/scaled-1680-/screenshot-2023-08-18-175831.png)\](https://docs.elest.io/uploads/images/gallery/2023-08/screenshot-2023-08-18-175831.png) After clicking the "\*\*\*Purchase\*\*\*" button, you will be asked to confirm your purchase by reviewing the domain name, price, and number of years. Click the "\*\*\*Confirm\*\*\*" button to confirm the purchase. \[!\[Screenshot 2023-08-18 175915.png\](https://docs.elest.io/uploads/images/gallery/2023-08/scaled-1680-/screenshot-2023-08-18-175915.png)\](https://docs.elest.io/uploads/images/gallery/2023-08/screenshot-2023-08-18-175915.png) It will just take a few seconds for your domain to be purchased and added to your project's Domains list🚀 \# How to Transfer your Domains from GoDaddy /others to elestio ##### If you desire to transfer your domain to Elestio, here is a comprehensive, step-by-step guide that will enable you to successfully migrate your domains to Elestio while effortlessly continuing to develop your online presence. ##### Before initiating the domain transfer process, ensure you have completed the following steps: - \*\*Verify domain eligibility:\*\* Confirm that your domain is eligible for transfer. The domain must be at least 60 days old as per ICANN policy, should not be in the process of expiration or redemption, and must not have a transfer lock enabled. \- \*\*Obtain the EPP/Auth Code:\*\* Request the EPP (Extensible Provisioning Protocol) or Auth Code from GoDaddy/others for the domain you wish to transfer. This code serves as an extra layer of security during the transfer process. - \*\*Backup your domain settings:\*\* Take note or screenshot your current DNS settings, email forwarding configurations, and any custom settings associated with the domain to replicate them on Elestio after the transfer. ##### \*\*Step 1. Unlock the domain in your GoDaddy account\*\* - Log in to GoDaddy, navigate to the domains menu, and then click “launch” for the domain you intend to transfer. If you’ve enabled privacy protection for the domain, you’ll need to turn it off before proceeding. \[!\[Screenshot 2023-07-25 174053.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/screenshot-2023-07-25-174053.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/screenshot-2023-07-25-174053.png) - After clicking “Launch,” you’ll be taken to a menu where you can manage settings for that specific domain. Click the “Manage” link in the “Lock” section, and a dialogue box will open. \[!\[2.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/2.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/2.png) - Switch the lock setting to “Off,” and then click “Save.” \[!\[31.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/31.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/31.png) ##### \*\*Step 2. Get an authorization code\*\* - After unlocking the domain you’ll return to the domain settings page. Scroll to the bottom, click the “Authorization code” link, and then click “Send” to have an authorization code sent to the email address associated with the domain. \[!\[4.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/4.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/4.png)\[!\[51.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/51.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/51.png) - You should receive an email containing the authorization code within a few minutes. \[!\[61.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/61.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/61.png) ##### \*\*Step 3. Use the elestio domain transfer page to initiate your transfer.\*\* - Go to the elestio dashboard and click on \*domains\* in the left sidebar. - Click on the text "Want to transfer your existing one ?" in the top right side. - Fill in the appropriate fields for the domain name and the authorization code (which you just received via email), and then click the “\*Create Transfer\*” button. ##### \*\*Step 4. Confirm the domain transfer at GoDaddy.com\*\* - Once you’ve approved the transfer, you’ll receive an email from GoDaddy (it may take a few hours). It’ll include a link to your GoDaddy account, where you can confirm the transfer. \[!\[16.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/16.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/16.png) - Clicking that link will take you to the transfers page in your GoDaddy account. Click on your pending transfers, follow the “Accept of decline transfer now” link, and accept the transfer. \[!\[18.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/18.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/18.png) \[!\[19.png\](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/19.png)\](https://docs.elest.io/uploads/images/gallery/2023-07/19.png) #### \*Celebrate! Your domain is now safe and sound in your elestio account 🚀\* Transferring your domains from GoDaddy to elestio can be a straightforward process when following the steps mentioned above. Remember to prepare in advance, backup essential domain settings, and ensure your domain is eligible for transfer. This guide is intended for GoDaddy users; however, it can also be applied to other service providers. You may begin the transfer process on your provider's account and subsequently proceed with step 3 to execute it on elestio. \# How to Renew a Domain on Elestio? ##### It is always best to renew a domain name before it expires so there is no interruption in service and there is no risk of losing ownership of the domain name. You can renew a domain for a minimum of 1 year and up to a maximum of 10 (you cannot exceed 10 years). \##### You can renew your domain by following these simple steps: \*\*Step 1:\*\* Navigate to the \*\*\*Domains\* \*\*page from the left sidebar. \[!\[Screenshot 2023-09-06 212600.png\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-212600.png)\](https://docs.elest.io/uploads/images/gallery/2023-08/screenshot-2023-08-18-175401.png) \*\*Step 2:\*\* Choose your domain from the list that you want to renew. \[!\[Screenshot 2023-09-06 204810.png\](https://docs.elest.io/uploads/images/gallery/2023-09/scaled-1680-/screenshot-2023-09-06-204810.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-204810.png) \*\*Step 3:\*\* In the Domain Renewals row, click the \*\*\*Show Setting\*\*\* button. \[!\[Screenshot 2023-09-06 204915.png\](https://docs.elest.io/uploads/images/gallery/2023-09/scaled-1680-/screenshot-2023-09-06-204915.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-204915.png) \*\*Step 4:\*\* Now you can review the domain's renewal pricing and select the number of years you want to renew before clicking the \*\*\*Renew domain\*\*\* button to proceed. \*\*Step 5:\*\* After selecting "Renew Domain," a confirmation window will now open where you can review the cost and number of years you choose. \[!\[image.png\](https://docs.elest.io/uploads/images/gallery/2023-09/scaled-1680-/image.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/image.png) \*\*Step 6:\*\* By clicking the \*\*\*Accept button\*,\*\* you can confirm the renewal. Your domain will be renewed in a few seconds after you accept the renewal. 🚀 # How can I change the name server for elestio domains? ##### Nameservers are the first thing domain names look to when they need to know where the content of a site is located. Nameservers dictate the DNS, which means you have to set up the DNS records with your nameserver provider. > If you use elestio nameservers, then elestio manages and hosts your DNS, and everything DNS-related needs to be set up in your elestio account. If you do not use elestio domain nameservers then we do NOT manage your DNS, and you will need to set up the DNS records with your nameserver provider. ##### In order to manage DNS records or use URL forwarding through elestio, you will need to use our default nameservers which are: \- ns1.name.com - ns2.name.com - ns3.name.com - ns4.name.com \##### You can add the default elestio nameservers or point others by following the instructions below: \*\*Step 1:\*\* Navigate to the \*\*\*Domains\*\*\* page from the left sidebar. \[!\[Screenshot 2023-09-06 212600.png\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-212600.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-204609.png) \*\*Step 2:\*\* Select your \*\*\*domain\*\*\* from the list to change the name server record. \[!\[Screenshot 2023-09-06 204810.png\](https://docs.elest.io/uploads/images/gallery/2023-09/scaled-1680-/screenshot-2023-09-06-204810.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-204810.png) \*\*Step 3:\*\* In the Domain overview, click the \*\*\*Security\*\*\* tab. \[!\[Screenshot 2023-09-06 211912.png\](https://docs.elest.io/uploads/images/gallery/2023-09/scaled-1680-/screenshot-2023-09-06-211912.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-211912.png) \*\*Step 4:\*\* Now, In the NameServers row, click the \*\*\*Edit NameServers\*\*\* button. \[!\[Screenshot 2023-09-06 212029.png\](https://docs.elest.io/uploads/images/gallery/2023-09/scaled-1680-/screenshot-2023-09-06-212029.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-212029.png) \*\*Step 5:\*\* You can add or update your name server record here. To save your changes, click the \*\*\*Update information\*\*\* button. # Locking/unlocking a domain ##### The domain lock is an added layer of security to guard against unauthorized domain transfers. You can lock or unlock your domain by following the instructions below: \*\*Step 1:\*\* Navigate to the \*\*\*Domains\*\*\* page from the left sidebar. \[!\[Screenshot 2023-09-06 212600.png\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-212600.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-204609.png) \*\*Step 2:\*\* Select your \*\*\*domain\*\*\* from the list to change the setting of the lock/unlock domain. \[!\[Screenshot 2023-09-06 204810.png\](https://docs.elest.io/uploads/images/gallery/2023-09/scaled-1680-/screenshot-2023-09-06-204810.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-204810.png) \*\*Step 3:\*\* In the Domain overview, click the \*\*\*Security\*\*\* tab. \[!\[Screenshot 2023-09-07 212642.png\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-07-212642.png)\](https://docs.elest.io/uploads/images/gallery/2023-09/screenshot-2023-09-06-211912.png) \*\*Step 4:\*\* Now, In the Domain Lock row, click the \*\*\*Toggle\*\*\* Switch to lock/unlock the domain. Once the switch to "lock/unlock" the domain has been flipped, a confirmation window will now open, allowing you to confirm the operation by clicking the "Lock" or "Unlock" button. As soon as you confirm the action, your domain's Lock/Unlock settings will change. This only affects transfers, so it is best to leave a domain name locked unless you are about to transfer it to another registrar. ##### \*\*Why won't my domain name unlock?\*\* \[\*\*ICANN\*\*\](https://www.icann.org/ "Learn more about ICANN restrictions"), the group that regulates the distribution of domain names, has a very strict rule that domain names cannot be transferred to another registrar within 60 days of the date they were registered or transferred to a new registrar. This is done to prevent fraud. Unfortunately, since this is an ICANN rule and not an elestio rule, there is no way we can remove the 60-day hold. The good news is that you can fully use your site while the domain name is locked. Your hosting provider or website builder will give you either name servers or DNS records to point to the domain name. --- # Is it possible to rest... | docs.elest.io [Skip to main content](https://docs.elest.io/books/frequently-asked-questions/page/is-it-possible-to-restrict-access-to-my-virtual-machine-with-a-firewall#main-content) Info Content Is it possible to restrict access to my virtual machine (with a firewall)? ========================================================================== Yes, every service has a pre-configured firewall that allows access to the internet through ports specific to certain applications. From the service dashboard, you can easily restrict access to a single or a range of IPs. [Learn more about setting your firewall](https://docs.elest.io/books/security/page/network-firewall "https://docs.elest.io/books/security/page/network-firewall") Enter section select mode [Previous\ \ Can I migrate/clone my service to another clo...](https://docs.elest.io/books/frequently-asked-questions/page/can-i-migrateclone-my-service-to-another-cloud-or-region) [Next\ \ What type of support does Elestio offer?](https://docs.elest.io/books/frequently-asked-questions/page/what-type-of-support-does-elestio-offer) Back to top --- # Connecting with keydb-cli | docs.elest.io [Skip to main content](https://docs.elest.io/books/valkey/page/connecting-with-keydb-cli#main-content) Info Content Connecting with keydb-cli ========================= This guide explains how to establish a connection between valkey-cli and a Valkey database instance. It walks through the necessary setup, configuration, and execution of a simple Valkey command from the terminal. **Variables** ------------- Certain parameters must be provided to establish a successful connection to a Valkey database. Below is a breakdown of each required variable, its purpose, and where to find it. Here’s what each variable represents: | **Variable** | **Description** | **Purpose** | | --- | --- | --- | | `HOST` | Valkey hostname, from the Elestio service overview page | The address of the server hosting your Valkey instance. | | `PORT` | Port for Valkey connection, from the Elestio service overview page | The network port used to connect to Valkey. The default port is 6379. | | `PASSWORD` | Valkey password, from the Elestio service overview page | The authentication key required to connect securely to Valkey. | These values can usually be found in the **Elestio service overview** details as shown in the image below. Make sure to take a copy of these details and use them in the command moving ahead. [![Screenshot 2025-07-04 at 4.12.37 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-07/scaled-1680-/GLuscreenshot-2025-07-04-at-4-12-37-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-07/GLuscreenshot-2025-07-04-at-4-12-37-pm.jpg) **Prerequisites** ----------------- #### **Install valkey****\-cli** Check if valkey\-cli is installed by running: valkey-cli --version If not installed, you can install it via: * **macOS**: brew install valkey * **Ubuntu/Debian**: sudo apt-get install valkey-tools * **Windows**: Use **Windows Subsystem for Linux (WSL)** or [download the CLI binaries from the Valkey](https://github.com/valkey-io/valkey/releases?utm_source=chatgpt.com) GitHub releases page. **Command** ----------- Once all prerequisites are set up, open the terminal or command prompt and run the following command: valkey-cli -h HOST -p PORT -a PASSWORD Replace HOST, PORT, and PASSWORD with the actual values from your Elestio Valkey service. If the connection is successful, the terminal will display a Valkey prompt like this: 127.0.0.1:6379> **Test the Connection** You can then run a simple command to test the connection: set testkey "Hello Valkey" get testkey **Expected output:** OK "Hello Valkey" If the connection is successful, the terminal will display output similar to the above. Enter section select mode [Previous\ \ Connecting with RedisInsight](https://docs.elest.io/books/valkey/page/connecting-with-redisinsight) [Next\ \ How-To Guides](https://docs.elest.io/books/valkey/chapter/how-to-guides) Back to top --- # Checking Database Size... | docs.elest.io [Skip to main content](https://docs.elest.io/books/timescaledb/page/checking-database-size-and-related-issues#main-content) Info Content Checking Database Size and Related Issues ========================================= As your TimescaleDB database grows over time, it’s important to monitor its size and identify what parts of the database consume the most space. Unmanaged growth can lead to performance issues, disk exhaustion, and backup delays. On Elestio, where TimescaleDB is hosted in a managed environment, you can use SQL and command-line tools to measure database usage, analyze large objects, and troubleshoot storage problems. This guide explains how to check database size, detect bloated tables and indexes, and optimize storage usage efficiently. **Checking Database and Table Sizes** ------------------------------------- TimescaleDB provides built-in functions to report the size of the current database, its individual schemas, tables, and indexes. These functions are useful for understanding where most of your storage is being used and planning cleanup or archiving strategies. To check the total size of the active database: SELECT pg_size_pretty(pg_database_size(current_database())); This returns a human-readable value like “2 GB”, indicating how much space the entire database consumes on disk. To list the largest tables in your schema: SELECT relname AS table, pg_size_pretty(pg_total_relation_size(relid)) AS total_size FROM pg_catalog.pg_statio_user_tables ORDER BY pg_total_relation_size(relid) DESC LIMIT 10; This helps you identify which tables take up the most space, including indexes and TOAST (large field) data. To break down table vs index size separately: SELECT relname AS object, pg_size_pretty(pg_relation_size(relid)) AS table_size, pg_size_pretty(pg_indexes_size(relid)) AS index_size FROM pg_catalog.pg_statio_user_tables ORDER BY pg_relation_size(relid) DESC LIMIT 10; This distinction allows you to assess whether most space is used by raw table data or indexes, which can inform optimization decisions. **Identifying Bloat and Inefficiencies** ---------------------------------------- Database bloat occurs when TimescaleDB retains outdated or deleted rows due to its MVCC model. This is common in high-write tables and can lead to wasted space and degraded performance. Bloated indexes and tables are often invisible unless explicitly checked. To estimate bloat at a table level, you can use a community query like this: SELECT schemaname, relname, round(100 * (pg_total_relation_size(relid) - pg_relation_size(relid)) / pg_total_relation_size(relid), 2) AS bloat_pct FROM pg_catalog.pg_statio_user_tables ORDER BY bloat_pct DESC LIMIT 10; This query calculates how much of a table’s total size is not accounted for by its base data—higher percentages suggest unused or dead space. You can also check dead tuples directly: SELECT relname, n_dead_tup FROM pg_stat_user_tables ORDER BY n_dead_tup DESC LIMIT 10; A high count of dead tuples suggests that autovacuum might not be keeping up and that a manual VACUUM could help. **Optimizing and Reducing Database Size** ----------------------------------------- Once you’ve identified large or bloated objects, the next step is to optimize them. TimescaleDB offers tools like VACUUM, REINDEX, and CLUSTER to reclaim space and improve storage efficiency. These commands must be run with care to avoid locking critical tables during active hours. To reclaim dead tuples and update statistics: VACUUM ANALYZE; This command removes dead rows and refreshes query planning statistics, which helps performance and frees up storage. To shrink large indexes that aren’t cleaned automatically, use: REINDEX TABLE ; This recreates the table’s indexes from scratch and can free up disk space if indexes are fragmented or bloated. If a table is heavily bloated and full table rewrites are acceptable during maintenance, use: CLUSTER ; This rewrites the entire table based on an index order and reclaims space similar to VACUUM FULL, but with more control. Additionally, removing or archiving old data from large time-based tables can reduce total size. Consider partitioning large tables to manage this process more efficiently. Enter section select mode [Previous\ \ Preventing Full Disk Issues](https://docs.elest.io/books/timescaledb/page/preventing-full-disk-issues) [Next\ \ Database Migration](https://docs.elest.io/books/timescaledb/chapter/database-migration) Back to top --- # Using Cloudflare | docs.elest.io [Skip to main content](https://docs.elest.io/books/security/page/using-cloudflare#main-content) Info Content Using Cloudflare ================ ##### **Cloudflare DNS:** If you wish to use Cloudflare for DNS ONLY, you can configure it just like any other DNS provider, and simply [follow the steps for adding a custom domain as usual.](https://docs.elest.io/books/security/page/custom-domain-and-automated-encryption-ssltls) WARNING: Your domain DNS entry **must have a GRAY cloud, not an ORANGE (proxied) cloud next to the entry.** [![image.png](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/image.png)**Using Cloudflare's proxy for your domain without additional configuration will cause all incoming connections to fail!**](https://docs.elest.io/uploads/images/gallery/2023-07/image.png) [![image.png](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/gMYimage.png) This is the correct image shown for DNS-only entries.](https://docs.elest.io/uploads/images/gallery/2023-07/gMYimage.png) ##### **Cloudflare Proxy** Even though Elest.io automatically provides SSL and has a firewall, there can be advantages to using Cloudflare for Proxying traffic, notably DDoS attacks and automatic filtering of scripted attacks. Note: [Cloudflare only proxies traffic on certain ports.](https://developers.cloudflare.com/fundamentals/get-started/reference/network-ports/) If you want to use this hostname for SSH, FTP, or other services whose ports are not listed in the above link, you must configure Cloudflare to provide DNS only or use [Cloudflare's Spectrum offer.](https://www.cloudflare.com/en-gb/products/cloudflare-spectrum/) Because Elest.io already creates an SSL certificate for your website trusted by a root CA, the recommended configuration is to set Cloudflare to use Strict SSL verification when connecting to your server. Before continuing, ensure you have already configured the domains [as per the instructions on the previous page.](https://docs.elest.io/books/security/page/custom-domain-and-automated-encryption-ssltls) ##### Option 1: To set up strict SSL verification for your **whole domain**: 1. Navigate to the `SSL/TLS` section of your domain's dashboard. 2. Select the `"Full (strict)"` option. 3. Your changes will be saved automatically. You're done! [![Screen Shot 2023-07-17 at 17.57.34.png](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/screen-shot-2023-07-17-at-17-57-34.png)](https://docs.elest.io/uploads/images/gallery/2023-07/screen-shot-2023-07-17-at-17-57-34.png) ##### Option 2: To set up strict SSL verification for a **specific subdomain:** 1. In your domain's dashboard, navigate to `Rules > Configuration Rules` and click `Create Rule` 2. Name your rule, and configure the incoming request filters.   [![Screen Shot 2023-07-17 at 18.07.16.png](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/screen-shot-2023-07-17-at-18-07-16.png)](https://docs.elest.io/uploads/images/gallery/2023-07/screen-shot-2023-07-17-at-18-07-16.png) 3\. Configure the SSL to `Strict` [![Screen Shot 2023-07-17 at 18.06.58.png](https://docs.elest.io/uploads/images/gallery/2023-07/scaled-1680-/screen-shot-2023-07-17-at-18-06-58.png)](https://docs.elest.io/uploads/images/gallery/2023-07/screen-shot-2023-07-17-at-18-06-58.png) 4\. Click `Save` ##### Option 3: Manual configuration (Advanced) If you need a custom implementation, you can disable the creation of an SSL certificate with the following steps. Create a CNAME record for your Cloudflare entry and point to the CNAME provided for that service in the Elestio dashboard. These changes can be overwritten in the future if you modify the list of domains via the Elest.io dashboard. 1) Connect to the VM with SSH and type this: **nano /opt/elestio/nginx/.env** there remove your domain from the first line and save with CTRL+X then type this command: **cd /opt/elestio/nginx;** **docker-compose down;** **docker-compose up -d;** After that, nginx won't try again to obtain an SSL certificate for your domain. Enter section select mode [Previous\ \ Nginx advanced configuration](https://docs.elest.io/books/security/page/nginx-advanced-configuration) [Next\ \ Network Firewall](https://docs.elest.io/books/security/page/network-firewall) Back to top --- # MariaDB Database Migra... | docs.elest.io [Skip to main content](https://docs.elest.io/books/databases/page/mariadb-database-migration-to-elestio-jV6#main-content) Info Content MariaDB Database Migration to Elestio ===================================== Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises MariaDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your MariaDB databases to Elestio, ensuring minimal downtime and disruption to your operations. This guide will walk you through the process of migrating your MariaDB database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress. ### Step 1 - Configure 1. Go to the overview of your MariaDB service on Elestio. [![Screenshot 2024-07-18 at 16.32.08.png](https://docs.elest.io/uploads/images/gallery/2024-07/scaled-1680-/screenshot-2024-07-18-at-16-32-08.png)](https://docs.elest.io/uploads/images/gallery/2024-07/screenshot-2024-07-18-at-16-32-08.png) 2. Click on the **Migrate Database** button. 3. A modal window will open, ensure that your target service has enough disk space to accommodate your database 4. Click on **Get started** button**.** [![Screenshot 2024-07-21 at 16.52.31.png](https://docs.elest.io/uploads/images/gallery/2024-07/scaled-1680-/screenshot-2024-07-21-at-16-52-31.png)](https://docs.elest.io/uploads/images/gallery/2024-07/screenshot-2024-07-21-at-16-52-31.png) ### Step 2 - Validation 1. You need to provide the connection details to establish a connection to your source database, enter the required details: * **Hostname** * **Port** * **Username** * **Password** 2. Click on **Run Check** to validate the connection. [![Screenshot 2024-07-18 at 16.32.37.png](https://docs.elest.io/uploads/images/gallery/2024-07/scaled-1680-/screenshot-2024-07-18-at-16-32-37.png)](https://docs.elest.io/uploads/images/gallery/2024-07/screenshot-2024-07-18-at-16-32-37.png) ### Step 3 - Migration 1. If all checks pass with no errors, you can trigger the migration by selecting **Start migration**. 2. Once the migration starts, you can monitor the progress through the migration logs displayed in real-time. [![Screenshot 2024-07-21 at 12.22.36.png](https://docs.elest.io/uploads/images/gallery/2024-07/scaled-1680-/screenshot-2024-07-21-at-12-22-36.png)](https://docs.elest.io/uploads/images/gallery/2024-07/screenshot-2024-07-21-at-12-22-36.png) Enter section select mode [Previous\ \ PostgreSQL Database Migration to Elestio](https://docs.elest.io/books/databases/page/postgresql-database-migration-to-elestio) [Next\ \ ColumnStore Database Migration to Elestio](https://docs.elest.io/books/databases/page/columnstore-database-migration-to-elestio-aZl) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=11#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### How to connect to an Elestio service with SSH keys\ \ Security\ \ Connecting to an Elestio service Using Existing SSH Keys from a Mac/Linux Machine Step 1: Check for Existing SSH Key Pair First, verify if you have an existing SSH key pair by checking the .ssh directory. Open a terminal and execute the following command: l...](https://docs.elest.io/books/security/page/how-to-connect-to-an-elestio-service-with-ssh-keys) [#### MySQL Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises MySQL database or from another cloud provider, Elestio's migration tool simplifies the process. By following a ...](https://docs.elest.io/books/databases/page/mysql-database-migration-to-elestio) [#### PostgreSQL Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises PostgreSQL database or from another cloud provider, Elestio's migration tool simplifies the process. By followi...](https://docs.elest.io/books/databases/page/postgresql-database-migration-to-elestio) [#### MariaDB Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises MariaDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following ...](https://docs.elest.io/books/databases/page/mariadb-database-migration-to-elestio-jV6) [#### ColumnStore Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises ColumnStore database or from another cloud provider, Elestio's migration tool simplifies the process. By follow...](https://docs.elest.io/books/databases/page/columnstore-database-migration-to-elestio-aZl) [#### Redis Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises Redis database or from another cloud provider, Elestio's migration tool simplifies the process. By following a ...](https://docs.elest.io/books/databases/page/redis-database-migration-to-elestio) [#### KeyDB Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises KeyDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following a ...](https://docs.elest.io/books/databases/page/keydb-database-migration-to-elestio) [#### Valkey Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises Valkey database or from another cloud provider, Elestio's migration tool simplifies the process. By following a...](https://docs.elest.io/books/databases/page/valkey-database-migration-to-elestio) [#### MongoDB Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises MongoDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following ...](https://docs.elest.io/books/databases/page/mongodb-database-migration-to-elestio) [#### TimescaleDB Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises TimescaleDB database or from another cloud provider, Elestio's migration tool simplifies the process. By follow...](https://docs.elest.io/books/databases/page/timescaledb-database-migration-to-elestio) [#### Hydra Database Migration to Elestio\ \ Databases DB Migration service\ \ Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises Hydra database or from another cloud provider, Elestio's migration tool simplifies the process. By following a ...](https://docs.elest.io/books/databases/page/hydra-database-migration-to-elestio) [#### How to Create a Pipeline for Git Submodule Repo\ \ CI/CD Pipelines\ \ Deploying code from a repository that includes Git submodules can be a bit more complex than a standard repository. This article will guide you through the process of deploying a submodule Git repository on the Elestio CI/CD pipeline.  Check out our example r...](https://docs.elest.io/books/cicd-pipelines/page/how-to-create-a-pipeline-for-git-submodule-repo) [#### How to Run a Nuxt App with preinstall script in Elestio\ \ CI/CD Pipelines\ \ When running a Nuxt.js application using runtime NodeJs, particularly with a preinstall script, you may encounter issues related to missing dependencies or commands not being found. In this guide, we'll walk you through how to set up a pipeline to run a Nuxt a...](https://docs.elest.io/books/cicd-pipelines/page/how-to-run-a-nuxt-app-with-preinstall-script-in-elestio) [#### How to Deploy or Integrate a Service with Tor Onion on Elestio\ \ Getting started\ \ To make your services accessible over Tor, you can configure a Tor service within your service Docker Compose setup. This will allow your service to function as an onion site, providing enhanced privacy and limiting access to Tor-compatible browsers. Here’s a ...](https://docs.elest.io/books/getting-started/page/how-to-deploy-or-integrate-a-service-with-tor-onion-on-elestio) [#### SEPA Direct Debit Payment Option on Elestio\ \ Billing\ \ At Elestio, we aim to make payment processing as convenient and accessible as possible for our customers. We’re pleased to offer SEPA Direct Debit as a payment option, available to our eligible European customers. This method ensures a secure, easy, and effici...](https://docs.elest.io/books/billing/page/sepa-direct-debit-payment-option-on-elestio) [#### How to Enable or Disable IPv6 on a Linux Virtual Machine\ \ Security\ \ IPv6 is the latest version of the Internet Protocol, designed to address the limitations of IPv4. In some scenarios, such as managing Docker Hub rate limits, disabling IPv6 may be necessary to ensure smooth operation. This guide provides step-by-step instructi...](https://docs.elest.io/books/security/page/how-to-enable-or-disable-ipv6-on-a-linux-virtual-machine) [#### Introduction\ \ Databases DB Clusters\ \ Clustered databases are essential for ensuring high availability, scalability, and fault tolerance in modern systems. By distributing data across multiple nodes, they can handle larger workloads, prevent single points of failure, and ensure that services rema...](https://docs.elest.io/books/databases/page/introduction) [#### Deploy a new cluster\ \ Databases DB Clusters\ \ How to deploy a new cluster 1) Go to the Elestio Clusters tab. 2) Click on Deploy My First Cluster. 3) Select your Software, for example, MySQL. 4) Choose your Provider and Service Plan, then click Next. 5) Choose a name for your cluster, for exampl...](https://docs.elest.io/books/databases/page/deploy-a-new-cluster) [#### Overview\ \ Databases DB Clusters\ \ Once your cluster is deployed, you can access it through the Clusters tab on the left. Here, you will see a new entry with the name of your cluster. In our example, it will appear as mysql-cluster. By clicking on the cluster name, you will access the Overvi...](https://docs.elest.io/books/databases/page/overview) [#### Nodes management\ \ Databases DB Clusters\ \ If you click on the Nodes tab, you will see a list of all your nodes with detailed information, such as: Node Role: Indicates whether the node is a Primary or a Replica. Status: Displays whether the node is running or not. Specifications: Includes detai...](https://docs.elest.io/books/databases/page/nodes-management) Back to top --- # Page Revisions for Cloning a Service to A... | docs.elest.io [Skip to main content](https://docs.elest.io/books/valkey/page/cloning-a-service-to-another-provider-or-region/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/valkey/page/cloning-a-service-to-another-provider-or-region/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 2 Cloning a Service to Another Provider or Region (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-07-02 06:41:21 UTC (5 months ago) [Changes](https://docs.elest.io/books/valkey/page/cloning-a-service-to-another-provider-or-region/revisions/2866/changes)  |  [_Current Version_](https://docs.elest.io/books/valkey/page/cloning-a-service-to-another-provider-or-region) # 1 Cloning a Service to Another Provider or Region (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-07-02 06:41:07 UTC (5 months ago) Initial publish [Preview](https://docs.elest.io/books/valkey/page/cloning-a-service-to-another-provider-or-region/revisions/2865) Back to top --- # Page Revisions for Admin UI | docs.elest.io [Skip to main content](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 7 Admin UI (**Editor Type:** WYSIWYG) ![Amit](https://docs.elest.io/uploads/images/user/2022-09/thumbs-30-30/70rvyvrpfb-avatar.png) Amit 2022-09-28 15:27:58 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/1530/changes)  |  [_Current Version_](https://docs.elest.io/books/services-dashboard/page/admin-ui) # 6 Admin UI (**Editor Type:** WYSIWYG) ![Daniel](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/dm-headshot.jpg) Daniel 2022-02-12 17:09:34 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/872/changes)  |  [Preview](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/872) # 5 Admin UI (**Editor Type:** WYSIWYG) ![Daniel](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/dm-headshot.jpg) Daniel 2022-01-30 17:53:46 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/732/changes)  |  [Preview](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/732) # 4 Admin UI (**Editor Type:** WYSIWYG) ![Daniel](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/dm-headshot.jpg) Daniel 2022-01-30 17:50:08 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/731/changes)  |  [Preview](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/731) # 3 Admin UI (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-11 17:18:05 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/113/changes)  |  [Preview](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/113) # 2 Admin UI (**Editor Type:** WYSIWYG) ![Joseph Benguira](https://docs.elest.io/uploads/images/user/2024-02/thumbs-30-30/moi.jpg) Joseph Benguira 2022-01-11 17:17:49 UTC (3 years ago) [Changes](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/112/changes)  |  [Preview](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/112) # 1 Admin UI (**Editor Type:** WYSIWYG) ![David Alimi](https://docs.elest.io/uploads/images/user/2022-01/thumbs-30-30/4-avatar.png) David Alimi 2022-01-09 12:00:45 UTC (3 years ago) Initial publish [Preview](https://docs.elest.io/books/services-dashboard/page/admin-ui/revisions/3) Back to top --- # Page Revisions for Cloning a Service to A... | docs.elest.io [Skip to main content](https://docs.elest.io/books/redis/page/cloning-a-service-to-another-provider-or-region/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/redis/page/cloning-a-service-to-another-provider-or-region/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Cloning a Service to Another Provider or Region (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-16 08:22:55 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/redis/page/cloning-a-service-to-another-provider-or-region) Back to top --- # docs.elest.io [Skip to main content](https://docs.elest.io/books/security/page/using-cloudflare/references#main-content) References ========== Listed below is all the known content in the system that links to this item. [#### Custom domain and automated encryption (SSL/TLS)\ \ If you have activated the firewall on your service ensure port 80 is open or else certificate cre...](https://docs.elest.io/books/security/page/custom-domain-and-automated-encryption-ssltls) Back to top --- # Update AWS Account Acc... | docs.elest.io [Skip to main content](https://docs.elest.io/books/projects-teams/page/update-aws-account-access-and-secret-credentials#main-content) Info Content Update AWS Account Access and Secret Credentials ================================================ ##### You can update your AWS Access and Secret Credentials at any time inside your project settings. To update AWS account credentials, go to the project settings in the left sidebar and then to the AWS Account tab. Enter your AWS Account Administration New access Access Key and Secret Key here, then click the _Update Credentials_ button to validate your new AWS access credentials.  [![Screenshot 2023-02-15 200603.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/screenshot-2023-02-15-200603.png)](https://docs.elest.io/uploads/images/gallery/2023-02/screenshot-2023-02-15-200603.png) When you click **_Update Credentials_**, a confirmation prompt will appear. If you want to update your credentials, click **_Update_**; otherwise, click **_Cancel_** to reject the update. [![Screenshot 2023-02-15 200816.png](https://docs.elest.io/uploads/images/gallery/2023-02/scaled-1680-/screenshot-2023-02-15-200816.png)](https://docs.elest.io/uploads/images/gallery/2023-02/screenshot-2023-02-15-200816.png) Enter section select mode [Previous\ \ Leave a project](https://docs.elest.io/books/projects-teams/page/leave-a-project) [Next\ \ Teams](https://docs.elest.io/books/projects-teams/chapter/teams) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=14#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Manual Migration Using pg\_dump and pg\_restore\ \ PostgreSQL Database Migration\ \ Manual Migrations using PostgreSQL’s built-in tools pg\_dump and pg\_restore are ideal for users who prefer full control over data export and import, particularly during provider transitions, database version upgrades, or when importing an existing self-managed ...](https://docs.elest.io/books/postgresql/page/manual-migration-using-pg-dump-and-pg-restore) [#### Overview\ \ MySQL\ \ MySQL is an open-source relational database management system. It supports SQL language and offers features like transactions, indexing, and replication. MySQL is widely used for web applications and enterprise solutions due to its performance, reliability, an...](https://docs.elest.io/books/mysql/page/overview) [#### Connecting with Node.js\ \ MySQL How to Connect\ \ This guide explains how to establish a connection between a Node.js application and a MySQL database using the mysql2 package. It walks through the necessary setup, configuration, and execution of a simple SQL query. Variables Certain parameters must be prov...](https://docs.elest.io/books/mysql/page/connecting-with-nodejs) [#### Connecting with Python\ \ MySQL How to Connect\ \ This guide explains how to establish a connection between a Python application and a MySQL database using the mysql-connector-python package. It walks through the necessary setup, configuration, and execution of a simple SQL query. Variables Certain paramete...](https://docs.elest.io/books/mysql/page/connecting-with-python) [#### Connecting with PHP\ \ MySQL How to Connect\ \ This guide explains how to establish a connection between a PHP application and a MySQL database using the mysqli extension. It walks through the necessary setup, configuration, and execution of a simple SQL query. Variables Certain parameters must be provid...](https://docs.elest.io/books/mysql/page/connecting-with-php) [#### Connecting with Go\ \ MySQL How to Connect\ \ This guide explains how to establish a connection between a Go application and a MySQL database using the go-sql-driver/mysql package. It walks through the necessary setup, configuration, and execution of a simple SQL query. Variables Certain parameters must...](https://docs.elest.io/books/mysql/page/connecting-with-go) [#### Connecting with Java\ \ MySQL How to Connect\ \ This guide explains how to establish a connection between a Java application and a MySQL database using the mysql-connector-j JDBC driver. It walks through the necessary setup, configuration, and execution of a simple SQL query. Variables Certain parameters ...](https://docs.elest.io/books/mysql/page/connecting-with-java) [#### Overview\ \ MySQL Cluster Management\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the sys...](https://docs.elest.io/books/mysql/page/overview-cMx) [#### Deploying a New Cluster\ \ MySQL Cluster Management\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide isolated environments where you can run containerized workloads, databases, and applications. Elestio’s web dashboard helps the process, allowing you to configure co...](https://docs.elest.io/books/mysql/page/deploying-a-new-cluster) [#### Node Management\ \ MySQL Cluster Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining st...](https://docs.elest.io/books/mysql/page/node-management) [#### Adding a Node\ \ MySQL Cluster Management\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, im...](https://docs.elest.io/books/mysql/page/adding-a-node) [#### Promoting a Node\ \ MySQL Cluster Management\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. ...](https://docs.elest.io/books/mysql/page/promoting-a-node) [#### Removing a Node\ \ MySQL Cluster Management\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structure...](https://docs.elest.io/books/mysql/page/removing-a-node) [#### Backups and Restores\ \ MySQL Cluster Management\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastruc...](https://docs.elest.io/books/mysql/page/backups-and-restores) [#### Cluster Resynchronization\ \ MySQL Cluster Management\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that services behave reliably and that data remains accurate across the cluster. Elestio provides built-in mechanisms to detect and resolve inconsistencies across node...](https://docs.elest.io/books/mysql/page/cluster-resynchronization) [#### Database Migrations\ \ MySQL Cluster Management\ \ When managing production-grade services, the ability to perform reliable and repeatable database migrations is critical. Whether you’re applying schema changes, updating seed data, or managing version-controlled transitions, Elestio provides a built-in mechani...](https://docs.elest.io/books/mysql/page/database-migrations) [#### Deleting a Cluster\ \ MySQL Cluster Management\ \ When a cluster is no longer needed—whether it was created for testing, staging, or an obsolete workload—deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire cluste...](https://docs.elest.io/books/mysql/page/deleting-a-cluster) [#### Cloning a Service to Another Provider or Region\ \ MySQL Database Migration\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of modern infrastructure management. Whether you’re optimizing for latency, preparing for disaster recovery, meeting regulatory requirements, or simply switching prov...](https://docs.elest.io/books/mysql/page/cloning-a-service-to-another-provider-or-region) [#### Database Migration Service for MySQL\ \ MySQL Database Migration\ \ Elestio provides a structured approach for migrating MySQL databases from various environments, such as on-premises systems or other cloud platforms, to its managed services. This process ensures data integrity and minimizes downtime, facilitating a smooth tra...](https://docs.elest.io/books/mysql/page/database-migration-service-for-mysql) [#### Restricting Access by IP\ \ MySQL Cluster Management\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the most effective ways to reduce unauthorized access is by restricting connectivity to a defined set of IP addresses. Elestio supports IP-based access control through i...](https://docs.elest.io/books/mysql/page/restricting-access-by-ip) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=16#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Database Migrations\ \ Hydra Cluster Management\ \ When managing production-grade services, the ability to perform reliable and repeatable database migrations is critical. Whether you’re applying schema changes, updating seed data, or managing version-controlled transitions, Elestio provides a built-in mechani...](https://docs.elest.io/books/hydra/page/database-migrations) [#### Deleting a Cluster\ \ Hydra Cluster Management\ \ When a cluster is no longer needed—whether it was created for testing, staging, or an obsolete workload—deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire cluste...](https://docs.elest.io/books/hydra/page/deleting-a-cluster) [#### Restricting Access by IP\ \ Hydra Cluster Management\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the most effective ways to reduce unauthorized access is by restricting connectivity to a defined set of IP addresses. Elestio supports IP-based access control through i...](https://docs.elest.io/books/hydra/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ Hydra Cluster Management\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that services behave reliably and that data remains accurate across the cluster. Elestio provides built-in mechanisms to detect and resolve inconsistencies across node...](https://docs.elest.io/books/hydra/page/cluster-resynchronization) [#### Connecting with Node.js\ \ Hydra How to Connect\ \ This guide walks you through the process of connecting a Node.js application to a Hydra database using the pg package. You’ll learn how to set up the environment, configure the connection, and run a simple SQL query. Variables To connect to a Hydra database,...](https://docs.elest.io/books/hydra/page/connecting-with-nodejs) [#### Connecting with Python\ \ Hydra How to Connect\ \ This guide explains how to connect a Python application to a Hydra database using the psycopg2-binary package. It covers environment setup, configuration, and execution of a simple query to test connectivity. Variables To connect to a Hydra database, you onl...](https://docs.elest.io/books/hydra/page/connecting-with-python) [#### Connecting with PHP\ \ Hydra How to Connect\ \ This guide explains how to connect a PHP application to a Hydra database using the PDO extension. It covers setting up prerequisites, configuring the connection URI, and running a test SQL query. Variables To connect to a Hydra database, you only need one en...](https://docs.elest.io/books/hydra/page/connecting-with-php) [#### Connecting with Go\ \ Hydra How to Connect\ \ This guide walks you through setting up a Go application to connect to a Hydra database, using the PostgreSQL-compatible lib/pq driver, and running a basic query to verify the connection. Variables To connect to a Hydra database, you only need one environmen...](https://docs.elest.io/books/hydra/page/connecting-with-go) [#### Connecting with Java\ \ Hydra How to Connect\ \ This guide shows how to connect your Java app to a Hydra database using the PostgreSQL JDBC driver, parse command-line arguments, and run a basic query. Variables To connect to a Hydra database, the following parameters are required. You can find these detai...](https://docs.elest.io/books/hydra/page/connecting-with-java) [#### Connecting with psql\ \ Hydra How to Connect\ \ This guide explains how to connect to a Hydra database using the psql command-line tool. It walks through the necessary setup, connection process, and execution of a simple SQL query. Variables To connect to a Hydra database, you only need one environment va...](https://docs.elest.io/books/hydra/page/connecting-with-psql) [#### Connecting with pgAdmin\ \ Hydra How to Connect\ \ pgAdmin is a widely used graphical interface for Hydra that allows you to manage, connect to, and run queries on your databases with ease. Variables To connect using pgAdmin, you'll need the following connection parameters. When you deploy a Hydra service on...](https://docs.elest.io/books/hydra/page/connecting-with-pgadmin) [#### Database Migration Service for Hydra\ \ Hydra Database Migration\ \ Elestio provides a structured approach for migrating Hydra databases from various environments, such as on-premises systems or other cloud platforms, to its managed services. This process ensures data integrity and minimizes downtime, facilitating a smooth tra...](https://docs.elest.io/books/hydra/page/database-migration-service-for-hydra) [#### Cloning a Service to Another Provider or Region\ \ Hydra Database Migration\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of modern infrastructure management. Whether you’re optimizing for latency, preparing for disaster recovery, meeting regulatory requirements, or simply switching prov...](https://docs.elest.io/books/hydra/page/cloning-a-service-to-another-provider-or-region) [#### Manual Migration Using pg\_dump and pg\_restore\ \ Hydra Database Migration\ \ Manual Migrations using Hydra’s built-in tools pg\_dump and pg\_restore are ideal for users who prefer full control over data export and import, particularly during provider transitions, database version upgrades, or when importing an existing self-managed Hydra...](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore) [#### Creating a Database\ \ Hydra How-To Guides\ \ Hydra allows you to create databases using different methods, including the PostgreSQL interactive shell (psql), Docker (assuming Hydra is running inside a container), and the command-line interface (createdb). This guide explains each method step-by-step, cov...](https://docs.elest.io/books/hydra/page/creating-a-database) [#### Upgrading to a Major Version\ \ Hydra How-To Guides\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing a full manual migration. Elestio provides a built-in option to change the database version directly from the dashboard. This is useful for cases where the upgrade...](https://docs.elest.io/books/hydra/page/upgrading-to-a-major-version) [#### Installing or Updating an Extension\ \ Hydra How-To Guides\ \ Hydra supports a growing range of PostgreSQL-compatible extensions that add extra functionality to the core database system. Extensions like pg\_trgm (for text search) and some UUID utilities are used to extend native capabilities. However, not all PostgreSQL e...](https://docs.elest.io/books/hydra/page/installing-or-updating-an-extension) [#### Creating Manual Backups\ \ Hydra How-To Guides\ \ Regular backups are a key part of managing a Hydra deployment. While Elestio provides automated backups by default, you may want to perform manual backups for specific reasons, such as preparing for a major change, keeping a local copy, or testing backup autom...](https://docs.elest.io/books/hydra/page/creating-manual-backups) [#### Restoring a Backup\ \ Hydra How-To Guides\ \ Restoring backups is essential for recovery, environment duplication, or rollback scenarios. Elestio supports restoring backups both through its built-in dashboard and via command-line tools like pg\_restore psql. You can also restore from inside Docker Compose...](https://docs.elest.io/books/hydra/page/restoring-a-backup) [#### Detect and terminate long-running queries\ \ Hydra How-To Guides\ \ Long-running queries can significantly impact database performance by consuming CPU, memory, and I/O resources over extended periods. In production environments like Elestio, it’s important to monitor for these queries and take timely action to terminate them ...](https://docs.elest.io/books/hydra/page/detect-and-terminate-long-running-queries) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=18#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Connecting with PHP\ \ TimescaleDB How to Connect\ \ This guide explains how to connect a PHP application to a TimescaleDB database using the PDO extension. It covers setting up prerequisites, configuring the connection URI, and running a test SQL query. Variables To connect to a TimescaleDB database, you only...](https://docs.elest.io/books/timescaledb/page/connecting-with-php) [#### Connecting with Go\ \ TimescaleDB How to Connect\ \ This guide walks you through setting up a Go application to connect to a TimescaleDB database, using the PostgreSQL-compatible lib/pq driver, and running a basic query to verify the connection. Variables To connect to a TimescaleDB database, you only need on...](https://docs.elest.io/books/timescaledb/page/connecting-with-go) [#### Connecting with Java\ \ TimescaleDB How to Connect\ \ This guide shows how to connect your Java app to a TimescaleDB database using the PostgreSQL JDBC driver, parse command-line arguments, and run a basic query. Variables To connect to a TimescaleDB database, the following parameters are required. You can find...](https://docs.elest.io/books/timescaledb/page/connecting-with-java) [#### Connecting with psql\ \ TimescaleDB How to Connect\ \ This guide explains how to connect to a TimescaleDB database using the psql command-line tool. It walks through the necessary setup, connection process, and execution of a simple SQL query. Variables To connect to a TimescaleDB database, you only need one en...](https://docs.elest.io/books/timescaledb/page/connecting-with-psql) [#### Connecting with pgAdmin\ \ TimescaleDB How to Connect\ \ pgAdmin is a widely used graphical interface for TimescaleDB that allows you to manage, connect to, and run queries on your databases with ease. Variables To connect using pgAdmin, you'll need the following connection parameters. When you deploy a TimescaleD...](https://docs.elest.io/books/timescaledb/page/connecting-with-pgadmin) [#### Creating a Database\ \ TimescaleDB How-To Guides\ \ TimescaleDB allows you to create databases using different methods, including the PostgreSQL interactive shell (psql), Docker (assuming TimescaleDB is running inside a container), and the command-line interface (createdb). This guide explains each method step-...](https://docs.elest.io/books/timescaledb/page/creating-a-database) [#### Upgrading to a Major Version\ \ TimescaleDB How-To Guides\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing a full manual migration. Elestio provides a built-in option to change the database version directly from the dashboard. This is useful for cases where the upgrade...](https://docs.elest.io/books/timescaledb/page/upgrading-to-a-major-version) [#### Installing or Updating an Extension\ \ TimescaleDB How-To Guides\ \ TimescaleDB supports a growing range of PostgreSQL-compatible extensions that add extra functionality to the core database system. Extensions like pg\_trgm (for text search) and some UUID utilities are used to extend native capabilities. However, not all Postgr...](https://docs.elest.io/books/timescaledb/page/installing-or-updating-an-extension) [#### Creating Manual Backups\ \ TimescaleDB How-To Guides\ \ Regular backups are a key part of managing a TimescaleDB deployment. While Elestio provides automated backups by default, you may want to perform manual backups for specific reasons, such as preparing for a major change, keeping a local copy, or testing backup...](https://docs.elest.io/books/timescaledb/page/creating-manual-backups) [#### Restoring a Backup\ \ TimescaleDB How-To Guides\ \ Restoring backups is essential for recovery, environment duplication, or rollback scenarios. Elestio supports restoring backups both through its built-in dashboard and via command-line tools like pg\_restore psql. You can also restore from inside Docker Compose...](https://docs.elest.io/books/timescaledb/page/restoring-a-backup) [#### Identifying Slow Queries\ \ TimescaleDB How-To Guides\ \ Slow queries can significantly affect application performance and user experience. TimescaleDB offers built-in tools to analyze and identify these slow operations. On Elestio, whether you’re connected via terminal, inside a Docker Compose container, or using T...](https://docs.elest.io/books/timescaledb/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ TimescaleDB How-To Guides\ \ Long-running queries can significantly impact database performance by consuming CPU, memory, and I/O resources over extended periods. In production environments like Elestio, it’s important to monitor for these queries and take timely action to terminate them ...](https://docs.elest.io/books/timescaledb/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ TimescaleDB How-To Guides\ \ Running out of disk space in a database environment can lead to failed writes, service downtime, and even data corruption. TimescaleDB systems require available space not only for storing data but also for managing temporary files, WAL logs, indexes, and routi...](https://docs.elest.io/books/timescaledb/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ TimescaleDB How-To Guides\ \ As your TimescaleDB database grows over time, it’s important to monitor its size and identify what parts of the database consume the most space. Unmanaged growth can lead to performance issues, disk exhaustion, and backup delays. On Elestio, where TimescaleDB ...](https://docs.elest.io/books/timescaledb/page/checking-database-size-and-related-issues) [#### How to configure NGINX to Listen on IPv6\ \ Security\ \ IPv6 is quickly becoming standard. If your VM already supports it, you just need to tell NGINX to listen on an IPv6 socket. (If IPv6 is disabled on the VM itself, start with the “Enable IPv6 on your VM” article and come back here.) 1. Open the dashboard ...](https://docs.elest.io/books/security/page/how-to-configure-nginx-to-listen-on-ipv6) [#### Overview\ \ Redis\ \ Redis is an open-source, in-memory key-value data store widely used as a database, cache, and message broker. Known for its high performance, Redis offers microsecond response times, making it ideal for real-time applications and high-throughput environments. ...](https://docs.elest.io/books/redis/page/overview) [#### Overview\ \ Redis Cluster Management\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the sys...](https://docs.elest.io/books/redis/page/overview-Yo0) [#### Deploying a New Cluster\ \ Redis Cluster Management\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide isolated environments where you can run containerized workloads, databases, and applications. Elestio’s web dashboard helps the process, allowing you to configure co...](https://docs.elest.io/books/redis/page/deploying-a-new-cluster) [#### Node Management\ \ Redis Cluster Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining st...](https://docs.elest.io/books/redis/page/node-management) [#### Adding a Node\ \ Redis Cluster Management\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, im...](https://docs.elest.io/books/redis/page/adding-a-node) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=19#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Promoting a Node\ \ Redis Cluster Management\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. ...](https://docs.elest.io/books/redis/page/promoting-a-node) [#### Removing a Node\ \ Redis Cluster Management\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structure...](https://docs.elest.io/books/redis/page/removing-a-node) [#### Backups and Restores\ \ Redis Cluster Management\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastruc...](https://docs.elest.io/books/redis/page/backups-and-restores) [#### Cluster Resynchronization\ \ Redis Cluster Management\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that services behave reliably and that data remains accurate across the cluster. Elestio provides built-in mechanisms to detect and resolve inconsistencies across node...](https://docs.elest.io/books/redis/page/cluster-resynchronization) [#### Database Migrations\ \ Redis Cluster Management\ \ When managing production-grade services, the ability to perform reliable and repeatable database migrations is critical. Whether you’re applying schema changes, updating seed data, or managing version-controlled transitions, Elestio provides a built-in mechani...](https://docs.elest.io/books/redis/page/database-migrations) [#### Delete a Cluster\ \ Redis Cluster Management\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete workload—deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire cluste...](https://docs.elest.io/books/redis/page/delete-a-cluster) [#### Restricting Access by IP\ \ Redis Cluster Management\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the most effective ways to reduce unauthorized access is by restricting connectivity to a defined set of IP addresses. Elestio supports IP-based access control through i...](https://docs.elest.io/books/redis/page/restricting-access-by-ip) [#### Cloning a Service to Another Provider or Region\ \ Redis Database Migration\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of modern infrastructure management. Whether you’re optimizing for latency, preparing for disaster recovery, meeting regulatory requirements, or simply switching prov...](https://docs.elest.io/books/redis/page/cloning-a-service-to-another-provider-or-region) [#### Database Migration Services for Redis\ \ Redis Database Migration\ \ Elestio provides a streamlined and reliable approach for migrating Redis instances from various environments such as on-premises servers, self-managed cloud deployments, or other managed services into its fully managed Redis platform. This migration process is...](https://docs.elest.io/books/redis/page/database-migration-services-for-redis) [#### Manual Redis Migration Using redis-cli and RDB Files\ \ Redis Database Migration\ \ Manual migrations using Redis’s built-in tools, such as redis-cli and RDB (Redis Database) files, are ideal for users who require full control over data export and import particularly during transitions between providers, Redis version upgrades, or importing e...](https://docs.elest.io/books/redis/page/manual-redis-migration-using-redis-cli-and-rdb-files) [#### Connecting with Node.js\ \ Redis How to Connect\ \ This guide explains how to establish a connection between a Node.js application and a Redis database using the redis package. It walks through the necessary setup, configuration, and execution of a simple Redis command. Variables To successfully connect to a...](https://docs.elest.io/books/redis/page/connecting-with-nodejs) [#### Connecting with Python\ \ Redis How to Connect\ \ This guide explains how to connect a Python application to a Redis database using the redis library. It walks through the required setup, configuration, and execution of a simple Redis command. Variables To connect to Redis, the following parameters are need...](https://docs.elest.io/books/redis/page/connecting-with-python) [#### Connecting with PHP\ \ Redis How to Connect\ \ This guide explains how to establish a connection between a PHP application and a Redis database using the phpredis extension. It walks through the necessary setup, configuration, and execution of a simple Redis command. Variables Certain parameters must be ...](https://docs.elest.io/books/redis/page/connecting-with-php) [#### Connecting with Go\ \ Redis How to Connect\ \ This guide explains how to establish a connection between a Go application and a Redis database using the go-redis package. It walks through the necessary setup, configuration, and execution of a simple Redis command. Variables Certain parameters must be pro...](https://docs.elest.io/books/redis/page/connecting-with-go) [#### Connecting with Java\ \ Redis How to Connect\ \ This guide explains how to establish a connection between a Java application and a Redis database using the Jedis library. It walks through the necessary setup, configuration, and execution of a simple Redis command. Variables Certain parameters must be prov...](https://docs.elest.io/books/redis/page/connecting-with-java) [#### Connecting with RedisInsight\ \ Redis How to Connect\ \ This guide explains how to establish a connection between RedisInsight and a Redis database instance. It walks through the necessary setup, configuration, and connection steps using the official Redis GUI. Variables Certain parameters must be provided to est...](https://docs.elest.io/books/redis/page/connecting-with-redisinsight) [#### Connecting with redis-cli\ \ Redis How to Connect\ \ This guide explains how to establish a connection between redis-cli and a Redis database instance. It walks through the necessary setup, configuration, and execution of a simple Redis command from the terminal. Variables Certain parameters must be provided t...](https://docs.elest.io/books/redis/page/connecting-with-redis-cli) [#### Creating a Database\ \ Redis How-To Guides\ \ Redis is a popular in-memory key-value data store known for its speed, flexibility, and support for a wide range of data structures. Setting up Redis properly is essential to ensure high availability, data persistence, and performance in modern applications. T...](https://docs.elest.io/books/redis/page/creating-a-database) [#### Upgrading to Major Version\ \ Redis How-To Guides\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing a full manual migration. Elestio provides a built-in option to change the database version directly from the dashboard. This is useful for cases where the upgrade...](https://docs.elest.io/books/redis/page/upgrading-to-major-version) [#### Installing and Updating an Extension\ \ Redis How-To Guides\ \ Redis supports modules to extend core functionality with new data types, commands, or algorithms. These modules behave like plugins in other systems and are loaded at server startup. Examples include RedisBloom, RedisTimeSeries, RedisJSON, and RedisSearch. In...](https://docs.elest.io/books/redis/page/installing-and-updating-an-extension) Back to top --- # Detect and terminate l... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/detect-and-terminate-long-running-queries#main-content) Info Content Detect and terminate long-running queries ========================================= Long-running queries can significantly impact database performance by consuming CPU, memory, and I/O resources over extended periods. In production environments like Elestio, it’s important to monitor for these queries and take timely action to terminate them when necessary. Hydra provides built-in monitoring tools and system views to help detect problematic queries and respond accordingly. This guide covers how to identify and cancel long-running queries using Hydra's terminal tools, Docker Compose environments, and logging features, along with preventive practices. **Identifying Long-Running Queries via Terminal** ------------------------------------------------- When connected to your Hydra service through the terminal using psql, you can check which queries are running and how long they have been active. This can help identify queries that are stuck, inefficient, or blocked.  To list all active queries sorted by duration, you can use: SELECT pid, now() - query_start AS duration, state, query FROM pg_stat_activity WHERE state = 'active' ORDER BY duration DESC; This query reveals which operations have been running the longest and their current state. If you want to isolate queries that have exceeded a specific duration (e.g., 1 minute), add a time filter: SELECT pid, now() - query_start AS runtime, query FROM pg_stat_activity WHERE state = 'active' AND now() - query_start > interval '1 minute'; These queries help you locate potential performance bottlenecks in real time. **Terminating Long-Running Queries Safely** ------------------------------------------- Once a problematic query is identified, Hydra allows you to cancel it using the pid (process ID). If you want to cancel the query without affecting the client session, use: SELECT pg_cancel_backend(); This tells Hydra to stop the running query, but keep the session connected. If the query is unresponsive or the client is idle for too long, you can fully terminate the session using: SELECT pg_terminate_backend(); This forcibly closes the session and stops the query. Termination should be used cautiously, especially in shared application environments. **Working Within Docker Compose Environments** ---------------------------------------------- If Hydra is deployed using Docker Compose on Elestio, you can detect and manage queries from inside the container. Start by entering the container: docker-compose exec hydra bash Inside the container, connect to the database with: psql -U $HYDRA_USER -d $HYDRA_DB From here, you can use the same commands as above to monitor and cancel long-running queries. The logic remains the same; you’re simply operating inside the container’s shell environment. **Using Logs and Monitoring Tools** ----------------------------------- Hydra supports logging queries that exceed a certain duration threshold, which is useful for long-term monitoring and post-incident review. To enable this, modify your hydra.conf file and set: log_min_duration_statement = 500 This setting logs every query that takes longer than 500 milliseconds. The logs are written to Hydra's log files, which you can access through the Elestio dashboard (if supported) or inside the container under the Hydra data directory. For cumulative insights, enable the pg\_stat\_statements extension to track long-running queries over time: CREATE EXTENSION IF NOT EXISTS pg_stat_statements; Then query the collected data: SELECT query, total_time, mean_time, calls FROM pg_stat_statements ORDER BY total_time DESC LIMIT 10; This shows which queries are consistently expensive, not just slow once. **Best Practices to Prevent Long-Running Queries** -------------------------------------------------- Preventing long-running queries is more effective than terminating them after the fact. Start by indexing columns used in WHERE, JOIN, and ORDER BY clauses. Use query analysis tools like EXPLAIN ANALYZE to find out how queries are executed and where performance issues may occur. Also, consider setting timeouts for queries. At the session level, you can use: SET statement_timeout = '2s'; This automatically cancels any query that runs longer than 2 seconds. For applications, set timeout configurations in the client or ORM layer to ensure they don’t wait indefinitely on slow queries. Monitoring tools and alerts can help you detect abnormal query behavior early. If you’re managing your own monitoring stack, connect it to Hydra logs or pg\_stat\_activity to trigger alerts for long-running operations. Enter section select mode [Previous\ \ Identifying Slow Queries](https://docs.elest.io/books/hydra/page/identifying-slow-queries) [Next\ \ Preventing Full Disk Issues](https://docs.elest.io/books/hydra/page/preventing-full-disk-issues) Back to top --- # Database Migrations | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/database-migrations#main-content) Info Content Database Migrations =================== When managing production-grade services, the ability to perform reliable and repeatable database migrations is critical. Whether you’re applying schema changes, updating seed data, or managing version-controlled transitions, Elestio provides a built-in mechanism to execute migrations safely from the dashboard. This functionality is especially relevant when running containerized database services like PostgreSQL, MySQL, or similar within a managed cluster. **Need for Migrations** ----------------------- Database migrations are commonly required when updating your application’s data model or deploying new features. Schema updates such as adding columns, modifying data types, creating indexes, or introducing new tables need to be synchronized with the deployment lifecycle of your application code. Migrations may also be needed during version upgrades to introduce structural or configuration changes required by newer database engine versions. In some cases, teams use migrations to apply baseline datasets, adjust permissions, or clean up legacy objects. Running these changes through a controlled migration system ensures consistency across environments and helps avoid untracked manual changes. **Running Database Migration** ------------------------------ To run a database migration in Elestio, start by logging into the [Elestio dashboard](https://dash.elest.io/)  and navigating to the **Clusters** section. Select the cluster that contains the target database service. From the **Cluster Overview** page, scroll down until you find the **“Migration”** option. [![Screenshot 2025-05-05 at 1.13.26 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-1-13-26-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-1-13-26-pm.jpg) Clicking this option will open the migration workflow, which follows a **three-step process**: **Configure**, **Validation**, and **Migration**. In the **Configure** step, Elestio provides a migration configuration guide specific to the database type, such as MySQL. At this point, you must ensure that your target service has sufficient **disk space** to complete the migration. If there is not enough storage available, the migration may fail midway, so it’s strongly recommended to review storage utilization beforehand. [![Screenshot 2025-05-05 at 1.14.02 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-1-14-02-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-1-14-02-pm.jpg) Once configuration prerequisites are met, you can proceed to the **Validation** step. Elestio will check the secondary database details you have provided for the migration. [![Screenshot 2025-05-05 at 1.14.12 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/J0Fscreenshot-2025-05-05-at-1-14-12-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/J0Fscreenshot-2025-05-05-at-1-14-12-pm.jpg) If the validation passes, the final **Migration** step will become active. You can then initiate the migration process. Elestio will handle the actual data transfer, schema replication, and state synchronization internally. The progress is tracked, and once completed, the migrated database will be fully operational on the target service. **Considerations Before Running Migrations** -------------------------------------------- * Before running any migration, it’s important to validate the script or changes in a staging environment. Since migrations may involve irreversible changes—such as dropping columns, altering constraints, or modifying data—careful review and version control are essential. * In production environments, plan migrations during maintenance windows or low-traffic periods to minimize the impact of any schema locks or temporary unavailability. If you’re using replication or high-availability setups, confirm that the migration is compatible with your architecture and will not disrupt synchronization between primary and secondary nodes. * You should also ensure that proper backups are in place before applying structural changes. In Elestio, the backup feature can be used to create a restore point that allows rollback in case the migration introduces issues. Enter section select mode [Previous\ \ Cluster Resynchronization](https://docs.elest.io/books/hydra/page/cluster-resynchronization) [Next\ \ Deleting a Cluster](https://docs.elest.io/books/hydra/page/deleting-a-cluster) Back to top --- # Restricting Access by IP | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/restricting-access-by-ip#main-content) Info Content Restricting Access by IP ======================== Securing access to services is a fundamental part of managing cloud infrastructure. One of the most effective ways to reduce unauthorized access is by restricting connectivity to a defined set of IP addresses. Elestio supports IP-based access control through its dashboard, allowing you to explicitly define which IPs or IP ranges are allowed to interact with your services. This is particularly useful when exposing databases, APIs, or web services over public endpoints. **Need to Restrict Access by IP** --------------------------------- Restricting access by IP provides a first layer of network-level protection. Instead of relying solely on application-layer authentication, you can control who is allowed to even initiate a connection to your service. This approach reduces the surface area for attacks such as brute-force login attempts, automated scanning, or unauthorized probing. Common use cases include: * Limiting access to production databases from known office networks or VPNs. * Allowing only CI/CD pipelines or monitoring tools with static IPs to connect. * Restricting admin dashboards or internal tools to internal teams. By defining access rules at the infrastructure level, you gain more control over who can reach your services, regardless of their authentication or API access status. **Restrict Access by IP** ------------------------- To restrict access by IP in Elestio, start by logging into the [Elestio dashboard](https://dash.elest.io/)  and navigating to the **Clusters** section. Select the cluster that hosts the service you want to protect. Once inside the **Cluster Overview** page, locate the **Security** section. [![Screenshot 2025-05-05 at 1.20.01 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-1-20-01-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-1-20-01-pm.jpg) Within this section, you’ll find a setting labeled **“Limit access per IP”**. This is where you can define which IP addresses or CIDR ranges are permitted to access the services running in the cluster. You can add a specific IPv4 or IPv6 address (e.g., 203.0.113.5) or a subnet in CIDR notation (e.g., 203.0.113.0/24) to allow access from a range of IPs. [![Screenshot 2025-05-05 at 1.20.40 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/Edoscreenshot-2025-05-05-at-1-20-40-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/Edoscreenshot-2025-05-05-at-1-20-40-pm.jpg) After entering the necessary IP addresses, save the configuration. The changes will apply to all services running inside the cluster, and only the defined IPs will be allowed to establish network connections. All other incoming requests from unlisted IPs will be blocked at the infrastructure level. **Considerations When Using IP Restrictions** --------------------------------------------- * When applying IP restrictions, it’s important to avoid locking yourself out. Always double-check that your own IP address is included in the allowlist before applying rules, especially when working on remote infrastructure. * For users on dynamic IPs (e.g., home broadband connections), consider using a VPN or a static jump host that you can reliably allowlist. Similarly, if your services are accessed through cloud-based tools, make sure to verify their IP ranges and update your rules accordingly when those IPs change. * In multi-team environments, document and review IP access policies regularly to avoid stale rules or overly permissive configurations. Combine IP restrictions with secure authentication and encrypted connections (such as HTTPS or SSL for databases) for layered security. Enter section select mode [Previous\ \ Backups and Restores](https://docs.elest.io/books/hydra/page/backups-and-restores) [Next\ \ Cluster Resynchronization](https://docs.elest.io/books/hydra/page/cluster-resynchronization) Back to top --- # Installing or Updating... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/installing-or-updating-an-extension#main-content) Info Content Installing or Updating an Extension =================================== Hydra supports a growing range of PostgreSQL-compatible extensions that add extra functionality to the core database system. Extensions like `pg_trgm` (for text search) and some UUID utilities are used to extend native capabilities. However, **not all PostgreSQL extensions are supported**, especially those requiring compiled C code like `uuid-ossp` or `postgis`, unless Hydra has explicitly implemented or emulated them. If you’re running Hydra on Elestio, many supported extensions can be enabled directly within your database. This guide explains how to enable, manage, and troubleshoot extensions in an Elestio-hosted Hydra environment, with attention to compatibility concerns. ### **Installing and Enabling Extensions** Hydra extensions can be installed in each database individually. Most common extensions are included in the Hydra installation on Elestio. To enable an extension, you need to connect to your database using a tool like psql. Start by connecting to your Hydra database. You can follow the detailed documentation as provided [here](https://docs.elest.io/books/postgresql/page/connecting-with-psql) . Once connected, you can enable an extension using the CREATE EXTENSION command. For example, to enable the uuid-ossp extension: CREATE EXTENSION IF NOT EXISTS "uuid-ossp"; To check which extensions are already installed in your current database, use the \`\\dx\` command within psql. If you want to see all available extensions on the server, use: SELECT * FROM pg_available_extensions ORDER BY name; If the extension you need is not listed in the available extensions, it may not be installed on the server. ### **Checking Extension Compatibility** Each Hydra extension is built for a specific Hydra version. Not all extensions are compatible across major versions. Before upgrading Hydra or deploying an extension, it is important to check whether the extension is compatible with the version you are using. To check the installed version of an extension and the default version provided by the system, run: SELECT name, default_version, installed_version FROM pg_available_extensions WHERE name = 'pg_trgm'; If you are planning to upgrade your Hydra version, it is recommended to deploy a new instance with the target version and run the above query to see if the extension is available and compatible. Some extensions may require specific builds for each version of Hydra. After upgrading your database, you may also need to update your extensions using: ALTER EXTENSION UPDATE; This ensures the extension objects in the database match the new database version. ### **Troubleshooting Common Extension Issues** There are some common issues users may encounter when working with extensions. These usually relate to missing files, permission problems, or version mismatches. If you see an error like could not open extension control file, it means the extension is not installed on the server. This usually happens when the extension is not included in the Hydra installation. If the error message says that the extension already exists, it means it has already been installed in the database. You can confirm this with the \\dx command or the query: SELECT * FROM pg_extension; If you need to reinstall it, you can drop and recreate it. Be careful, as dropping an extension with CASCADE may remove objects that depend on it: DROP EXTENSION IF EXISTS CASCADE; CREATE EXTENSION ; Another common issue appears after upgrading Hydra, where some functions related to the extension stop working. This is often due to the extension not being updated. Running the following command will usually fix this. ALTER EXTENSION UPDATE; In some cases, you may get a permission denied error when trying to create an extension. This means your database role does not have the required privileges. You will need to connect using a superuser account like postgres, or request that Elestio enable the extension for you. Enter section select mode [Previous\ \ Upgrading to a Major Version](https://docs.elest.io/books/hydra/page/upgrading-to-a-major-version) [Next\ \ Creating Manual Backups](https://docs.elest.io/books/hydra/page/creating-manual-backups) Back to top --- # Creating a Database | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/creating-a-database#main-content) Info Content Creating a Database =================== Hydra allows you to create databases using different methods, including the PostgreSQL interactive shell (`psql`), Docker (assuming Hydra is running inside a container), and the command-line interface (`createdb`). This guide explains each method step-by-step, covering required permissions, best practices, and troubleshooting common issues. **Creating Using psql CLI** --------------------------- Hydra is a database system that stores and manages structured data efficiently. The `psql` tool is an interactive command-line interface (CLI) that allows users to execute SQL commands directly on a Hydra database. Follow these steps to create a database: #### **Connect to Hydra** Open terminal on your local system, and if Hydra is installed locally, connect using the following command. If not installed, install from [official website](https://www.postgresql.org/download/) : psql -U postgres For a remote database, use: psql -h HOST -U USER -d DATABASE Replace `HOST` with the database server address, `USER` with the Hydra username, and `DATABASE` with an existing database name. #### **Create a New Database** Inside the `psql` shell, run: CREATE DATABASE mydatabase; The default settings will apply unless specified otherwise. To customize the encoding and collation, use: CREATE DATABASE mydatabase ENCODING 'UTF8' LC_COLLATE 'en_US.UTF-8' LC_CTYPE 'en_US.UTF-8' TEMPLATE template0; **Creating Database in Docker** ------------------------------- Docker is a tool that helps run applications in isolated environments called containers. A Hydra container provides a self-contained database instance that can be quickly deployed and managed. If you are running Hydra inside a Docker container, follow these steps: #### **Access Elestio Terminal** Head over to your deployed Hydra service dashboard and head over to **Tools > Terminal**. Use the credentials provided there to log in to your terminal. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/N3bimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/N3bimage.png) Once you are in your terminal, run the following command to head over to the correct directory to perform the next steps cd /opt/app/ #### **Access the Hydra Container Shell** Instead of pulling an image or running the container manually, use Docker Compose to interact with your running container. As you are using Elestio, it will already be a Docker compose: docker-compose exec postgres bash This opens a shell session inside the running Hydra container. #### **Use Environment Variables to Connect via** **psql** Once inside the container shell, if environment variables like `POSTGRES_USER` and `POSTGRES_DB` are already set in the stack, you can use them directly: psql -U "$HYDRA_USER" -d "$HYDRA_DB" Or use the default one: psql -U postgres #### **Create Database** Now, to create a database, use the following command. This command tells Hydra to create a new logical database called `mydatabase`. By default, it inherits settings like encoding and collation from the template database (template1), unless specified otherwise. CREATE DATABASE mydatabase; You can quickly list the database you just created using the following command /l **Creating Using createdb CLI**  -------------------------------- The `createdb` command simplifies database creation from the terminal without using `psql`. #### **Ensure Hydra is Running** Check the Hydra service status, this ensures that the Hydra instance is running on your local instance: sudo systemctl status hydra If not running, start it: sudo systemctl start hydra #### **Create a Database** Now, you can create a simple database using the following command: createdb -U postgres mydatabase To specify encoding and collation: createdb -U postgres --encoding=UTF8 --lc-collate=en_US.UTF-8 --lc-ctype=en_US.UTF-8 mydatabase #### **Verify Database Creation** List all databases using the following commands, as it will list all the databases available under your Hydra: psql -U postgres -l #### **Connect to the New Database** Next, you can easily connect with the database using the psql command and start working on it. psql -U postgres -d mydatabase **Required Permissions for Database Creation** ---------------------------------------------- Creating a database requires the `CREATEDB` privilege. By default, the `postgres` user has this privilege. To grant it to another user: ALTER USER username CREATEDB; For restricted access, assign specific permissions: CREATE ROLE newuser WITH LOGIN PASSWORD 'securepassword'; GRANT CONNECT ON DATABASE mydatabase TO newuser; GRANT USAGE ON SCHEMA public TO newuser; GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO newuser; **Best Practices for Creating Databases** ----------------------------------------- * **Use Meaningful Names:** Choosing clear and descriptive names for databases helps in organization and maintenance. Avoid generic names like `testdb` or `database1`, as they do not indicate the database’s purpose. Instead, use names that reflect the type of data stored, such as `customer_data` or `sales_records`. Meaningful names make it easier for developers and administrators to understand the database’s function without extra documentation. * **Follow Naming Conventions:** A standardized naming convention ensures consistency across projects and simplifies database management. Hydra is case-sensitive, so using lowercase letters and underscores (e.g., `order_details`) is recommended to avoid unnecessary complexities. Avoid spaces and special characters in names, as they require additional quoting in SQL queries. * **Restrict User Permissions:** Granting only the necessary permissions improves database security and reduces risks. By default, users should have the least privilege required for their tasks, such as read-only access for reporting tools. Superuser or administrative privileges should be limited to trusted users to prevent accidental or malicious changes. Using roles and groups simplifies permission management and ensures consistent access control. * **Enable Backups:** Regular backups ensure data recovery in case of accidental deletions, hardware failures, or security breaches. Hydra provides built-in tools like `pg_dump` for single-database backups and `pg_basebackup` for full-instance backups. Automating backups using cron jobs or scheduling them through a database management tool reduces the risk of data loss. * **Monitor Performance:** Monitoring database performance helps identify bottlenecks, optimize queries, and ensure efficient resource utilization. Hydra provides system views like `pg_stat_activity` and `pg_stat_database` to track query execution and database usage. Analyzing slow queries using `EXPLAIN ANALYZE` helps in indexing and optimization.  SELECT datname, numbackends, xact_commit, blks_read FROM pg_stat_database; **Common Issues and Troubleshooting** ------------------------------------- | **Issue** | **Possible Cause** | **Solution** | | --- | --- | --- | | `ERROR: permission denied to create database` | User lacks `CREATEDB` privileges | Grant permission using `ALTER USER username CREATEDB;` | | `ERROR: database "mydatabase" already exists` | Database name already taken | Use a different name or drop the existing one with `DROP DATABASE mydatabase;` | | `FATAL: database "mydatabase" does not exist` | Attempting to connect to a non-existent database | Verify creation using `\l` | | `psql: could not connect to server` | Hydra is not running | Start Hydra with `sudo systemctl start hydra` | | `ERROR: role "username" does not exist` | The specified user does not exist | Create the user with `CREATE ROLE username WITH LOGIN PASSWORD 'password';` | Enter section select mode [Previous\ \ How-To Guides](https://docs.elest.io/books/hydra/chapter/how-to-guides) [Next\ \ Upgrading to a Major Version](https://docs.elest.io/books/hydra/page/upgrading-to-a-major-version) Back to top --- # Connecting with pgAdmin | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-pgadmin#main-content) Info Content Connecting with pgAdmin ======================= **pgAdmin** is a widely used graphical interface for Hydra that allows you to manage, connect to, and run queries on your databases with ease. ### **Variables** To connect using `pgAdmin`, you'll need the following connection parameters. When you deploy a Hydra service on Elestio, you also get a pgAdmin dashboard configured for you to use with these variables. These details are available in the **Elestio service overview page**: | Variable | Description | Purpose | | --- | --- | --- | | `**USER**` | pgAdmin username | Identifies the pgAdmin user with access permission. | | `**PASSWORD**` | pgAdmin password | Authentication key for the `USER`. | You can find these values in your Elestio project dashboard under **Admin** section.  [![Screenshot 2025-05-07 at 10.08.35 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-07-at-10-08-35-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-07-at-10-08-35-pm.jpg) ### **Prerequisites** Make sure the **Hydra** service is correctly deployed on Elestio and you are able to access the Admin section like the one in the image above. ### **Setting Up the Connection** 1. Launch **pgAdmin** from the Admin UI URL and log in with the credentials acquired in the steps before. ![Screenshot 2025-04-01 at 3.51.28 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-04/scaled-1680-/screenshot-2025-04-01-at-3-51-28-pm.jpg) 2. Click on **"Create"** and select **"Server…"** from the dropdown, or find **Add New Server** from the quick links![Screenshot 2025-04-01 at 3.55.59 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-04/scaled-1680-/screenshot-2025-04-01-at-3-55-59-pm.jpg) 3. In the **General** tab: * Enter a name for your connection (e.g., `Trial pgAdmin Connection`).![image.png](https://docs.elest.io/uploads/images/gallery/2025-04/scaled-1680-/image.png) 4. Go to the **Connection** tab and enter the following details: * **Host name/address**: `HOSTNAME` * **Port**: `PORT` * **Maintenance database**: `DATABASE` * **Username**: `USERNAME` * **Password**: `PASSWORD` ![image.png](https://docs.elest.io/uploads/images/gallery/2025-04/scaled-1680-/6v6image.png) Enter section select mode [Previous\ \ Connecting with psql](https://docs.elest.io/books/hydra/page/connecting-with-psql) [Next\ \ How-To Guides](https://docs.elest.io/books/hydra/chapter/how-to-guides) Back to top --- # Connecting with PHP | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-php#main-content) Info Content Connecting with PHP =================== This guide explains how to connect a PHP application to a Hydra database using the **PDO extension**. It covers setting up prerequisites, configuring the connection URI, and running a test SQL query. ### **Variables** To connect to a Hydra database, you only need **one environment variable** — the connection URI. | **Variable** | **Description** | **Purpose** | | --- | --- | --- | | `HYDRA_URI` | Full Hydra connection string from Elestio | Encodes all connection info in one URI | A typical URI looks like this: postgresql://:@:/ You can find the details needed in the URI from the **Elestio service overview** details. Copy and replace the variables carefully in the URI example provided above. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/eTcimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/eTcimage.png) ### **Prerequisites** **Install PHP** Check if PHP is installed: php -v If not, download and install PHP from: [https://www.php.net/downloads.php](https://www.php.net/downloads.php) ### **Code** Once all prerequisites are set up, create a new file named `hydra.php` and add the following code and replace the `HYDRA_URI` with actual link or in environment setup as you wish: query("SELECT VERSION()")->fetchColumn(); echo "Connected to Hydra: " . $version . PHP_EOL; } catch (PDOException $e) { echo "Connection failed: " . $e->getMessage() . PHP_EOL; } To execute the script, open the terminal or command prompt and navigate to the directory where `hydra.php`. Once in the correct directory, run the script with the command export HYDRA_URI=postgresql://user:password@host:port/database Navigate to the directory containing `hydra.php` and run: php hydra.php If successful, you’ll see output like: Connected to Hydra: PostgreSQL 14.13 (Debian 14.13-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit Enter section select mode [Previous\ \ Connecting with Python](https://docs.elest.io/books/hydra/page/connecting-with-python) [Next\ \ Connecting with Go](https://docs.elest.io/books/hydra/page/connecting-with-go) Back to top --- # Deleting a Cluster | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/deleting-a-cluster#main-content) Info Content Deleting a Cluster ================== When a cluster is no longer needed—whether it was created for testing, staging, or an obsolete workload—deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire clusters directly from the dashboard. This action permanently removes the associated services, data, and compute resources tied to the cluster. **When to Delete a Cluster** ---------------------------- Deleting a cluster is a final step often performed when decommissioning an environment. This could include shutting down a test setup, replacing infrastructure during migration, or retiring an unused production instance. In some cases, users also delete and recreate clusters as part of major version upgrades or architectural changes. It is essential to confirm that all data and services tied to the cluster are no longer required or have been backed up or migrated before proceeding. Since cluster deletion is irreversible, any services, volumes, and backups associated with the cluster will be permanently removed. **Delete a Cluster** -------------------- To delete a cluster, log in to the [Elestio dashboard](https://dash.elest.io/)  and navigate to the **Clusters** section. From the list of clusters, select the one you want to remove. Inside the selected cluster, you’ll find a **navigation bar** at the top of the page. One of the available options in this navigation bar is **“Delete Cluster.”**  [![Screenshot 2025-05-05 at 1.17.55 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-1-17-55-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-1-17-55-pm.jpg) Clicking this opens a confirmation dialog that outlines the impact of deletion. It will clearly state that deleting the cluster will **permanently remove** all associated services, storage, and configurations. By acknowledging a warning or typing in the cluster name, depending on the service type. Once confirmed, Elestio will initiate the deletion process, which includes tearing down all resources associated with the cluster. This typically completes within a few minutes, after which the cluster will no longer appear in your dashboard. [![Screenshot 2025-05-05 at 1.18.15 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-1-18-15-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-1-18-15-pm.jpg) **Considerations Before Deleting** ---------------------------------- Deleting a cluster also terminates any linked domains, volumes, monitoring configurations, and scheduled backups. These cannot be recovered once deletion is complete, so plan accordingly before confirming the action. If the cluster was used for production workloads, consider archiving data to external storage (e.g., S3) or exporting final snapshots for compliance and recovery purposes. Before deleting a cluster, verify that: * All required data has been backed up externally (e.g., downloaded dumps or exports). * Any active services or dependencies tied to the cluster have been reconfigured or shut down. * Access credentials, logs, or stored configuration settings have been retrieved if needed for auditing or migration. Enter section select mode [Previous\ \ Database Migrations](https://docs.elest.io/books/hydra/page/database-migrations) Back to top --- # Connecting with Node.js | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-nodejs#main-content) Info Content Connecting with Node.js ======================= This guide walks you through the process of connecting a Node.js application to a Hydra database using the `pg` package. You’ll learn how to set up the environment, configure the connection, and run a simple SQL query. ### **Variables** To connect to a Hydra database, the following parameters are required. You can find these details in the **Elestio service overview page** of your Hydra service. | **Variable** | **Description** | **Purpose** | | --- | --- | --- | | `**USER**` | Hydra (PostgreSQL) username | Identifies the database user with access privileges | | `**PASSWORD**` | Hydra password | Authenticates the user against the Hydra database | | `**HOST**` | Hostname of the Hydra instance | Specifies the server address of the database | | `**PORT**` | Port for Hydra (usually 5432) | Specifies the network port for connections | | `**DATABASE**` | Name of the Hydra database | Specifies which database to access | These values can usually be found in the Elestio service overview details as shown in the image below, make sure to take a copy of these details and add it to the code moving ahead. [![Screenshot 2025-05-07 at 2.09.07 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-07-at-2-09-07-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-07-at-2-09-07-pm.jpg) ### **Prerequisites** * **Install Node.js and NPM** * Check if Node.js is installed: node -v npm -v * * If not, download and install it from [https://nodejs.org](https://nodejs.org/) . * **Install the pg Package** * Hydra is PostgreSQL-compatible, so use the pg package: npm install pg --save ### **Code** Once all prerequisites are set up, create a new file named `hydra.js` and add the following code. const { Client } = require("pg"); // Database connection configuration const config = { host: "HOST", user: "USER", password: "PASSWORD", database: "DATABASE", port: PORT, ssl: { rejectUnauthorized: false, // Only if Hydra requires SSL (check Elestio settings) }, }; // Create a new client instance const client = new Client(config); // Connect to the Hydra database client.connect((err) => { if (err) { console.error("Connection failed:", err.stack); return; } console.log("Connected to Hydra"); // Run a test query client.query("SELECT version()", (err, res) => { if (err) { console.error("Query failed:", err.stack); } else { console.log("Hydra/PostgreSQL Version:", res.rows[0].version); } // Close the connection client.end((err) => { if (err) console.error("Error closing connection:", err.stack); }); }); }); To execute the script, open the terminal or command prompt and navigate to the directory where `hydra.js`. Once in the correct directory, run the script with the command node hydra.js If successful, you’ll see: Connected to Hydra Hydra/PostgreSQL Version: PostgreSQL 14.13 (Debian 14.13-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit Enter section select mode [Previous\ \ How to Connect](https://docs.elest.io/books/hydra/chapter/how-to-connect) [Next\ \ Connecting with Python](https://docs.elest.io/books/hydra/page/connecting-with-python) Back to top --- # Restoring a Backup | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/restoring-a-backup#main-content) Info Content Restoring a Backup ================== Restoring backups is essential for recovery, environment duplication, or rollback scenarios. Elestio supports restoring backups both through its built-in dashboard and via command-line tools like `pg_restore` psql. You can also restore from inside Docker Compose environments. This guide provides detailed steps for full and partial restores using each method and explains how to address common errors that occur during restoration. **Restoring from a Backup via Terminal**  ----------------------------------------- This method is used when you’ve created a `.dump` file using `pg_dump` in custom format. You can restore it using `pg_restore`, which gives you fine-grained control over what gets restored. This is useful for restoring backups to new environments, during version upgrades, or testing data locally. ##### **Create the target database if it does not exist** If the database you’re restoring into doesn’t already exist, you must create it first. PGPASSWORD='' createdb \ -U \ -h \ -p \ ##### **Run pg\_restore to import the backup** This command restores the full contents of the .dump file into the specified database. PGPASSWORD='' pg_restore \ -U \ -h \ -p \ -d \ -v .dump You can add `--clean` to drop existing objects before restoring. **Restoring via Docker Compose** -------------------------------- If your Hydra service is deployed using Docker Compose, you can restore the database inside the container environment. This is useful when Hydra runs in an isolated Docker setup, and you want to handle all backup and restore processes inside that environment. ##### **Copy the backup into the container** Use docker cp to move the `.dump` file from your host machine to the Hydra container. docker cp ./manual_backup.dump $(docker-compose ps -q hydra):/tmp/manual_backup.dump ##### **Run the restore inside the container** Use pg\_restore from within the container to restore the file to the database. docker-compose exec hydra \ bash -c "PGPASSWORD='\$HYDRA_PASSWORD' pg_restore -U \$HYDRA_USER -d \$HYDRA_DB -Fc -v /tmp/manual_backup.dump" Make sure your environment variables in the Docker Compose file match the values used here. **Partial Restores** -------------------- Hydra supports partial restores, allowing you to restore only selected tables, schemas, or schema definitions. This can be useful when recovering a specific part of the database or testing part of the data. #### **Restore a specific table** Use the \-t flag to restore only one table from the `.dump` file. PGPASSWORD='' pg_restore \ -U \ -h \ -p \ -d \ -t \ -v .dump #### **Restore schema only (no data)** This command will restore only the table structures, types, functions, and other schema definitions without inserting any data. pg_restore \ -U \ -h \ -p \ -d \ --schema-only \ -v .dump Partial restores work best with custom-format .dump files generated by `pg_dump` `-Fc`. **Common Errors & How to Fix Them** ----------------------------------- Errors during restore are often caused by permission issues, incorrect formats, or missing objects. Understanding the error messages and their causes will help you recover faster and avoid data loss. **1\. Could not connect to database** pg_restore: [archiver] could not connect to database This usually happens if the database doesn’t exist or the credentials are incorrect. Make sure the database has been created and the connection details are correct. **2\. Permission denied for schema** ERROR: permission denied for schema public This error indicates that the user account used for restore lacks the privileges needed to write into the schema. Use a superuser account or adjust the schema permissions before restoring. **3\. Input file appears to be a text format dump** pg_restore: error: input file appears to be a text format dump This means you are trying to use `pg_restore` a plain SQL file. In this case, you should use psql instead: psql -U -h -p -d -f backup.sql **4\. Duplicate key value violates unique constraint** This occurs when the restore process tries to insert rows that already exist in the target database. You can either drop the target database before restoring or use `--clean` it in `pg_restore` to drop existing objects automatically. Enter section select mode [Previous\ \ Creating Manual Backups](https://docs.elest.io/books/hydra/page/creating-manual-backups) [Next\ \ Identifying Slow Queries](https://docs.elest.io/books/hydra/page/identifying-slow-queries) Back to top --- # Upgrading to a Major V... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/upgrading-to-a-major-version#main-content) Info Content Upgrading to a Major Version ============================ Upgrading a database service on Elestio can be done without creating a new instance or performing a full manual migration. Elestio provides a built-in option to change the database version directly from the dashboard. This is useful for cases where the upgrade does not involve breaking changes or when minimal manual involvement is preferred. The version upgrade process is handled by Elestio internally, including restarting the database service if required. This method reduces the number of steps involved and provides a way to keep services up to date with minimal configuration changes. ### **Log In and Locate Your Service** To begin the upgrade process, log in to your Elestio dashboard and navigate to the specific database service you want to upgrade. It is important to verify that the correct instance is selected, especially in environments where multiple databases are used for different purposes such as staging, testing, or production. The dashboard interface provides detailed information for each service, including version details, usage metrics, and current configuration. Ensure that you have access rights to perform upgrades on the selected service. Identifying the right instance helps avoid accidental changes to unrelated environments. ### **Back Up Your Data** Before starting the upgrade, create a backup of your database. A backup stores the current state of your data, schema, indexes, and configuration, which can be restored if something goes wrong during the upgrade. In Elestio, this can be done through the **Backups** tab by selecting **Back up now** under Manual local backups and **Download** the backup file. Scheduled backups may also be used, but it is recommended to create a manual one just before the upgrade. Keeping a recent backup allows quick recovery in case of errors or rollback needs. This is especially important in production environments where data consistency is critical. [![Screenshot 2025-05-08 at 12.49.21 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-08-at-12-49-21-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-08-at-12-49-21-pm.jpg) ### **Select the New Version** Once your backup is secure, proceed to the **Overview** and then **Software > Update config** tab within your database service page. [![Screenshot 2025-05-08 at 12.50.19 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-08-at-12-50-19-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-08-at-12-50-19-pm.jpg) Here, you'll find an option labeled **ENV**. In the **ENV** menu, change the desired database version to `SOFTWARE_VERSION`. After confirming the version, Elestio will begin the upgrade process automatically. During this time, the platform takes care of the version change and restarts the database if needed. No manual commands are required, and the system handles most of the operational aspects in the background. [![Screenshot 2025-05-08 at 12.51.13 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-08-at-12-51-13-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-08-at-12-51-13-pm.jpg) ### **Monitor the Upgrade Process** The upgrade process may include a short downtime while the database restarts. Once it is completed, it is important to verify that the upgrade was successful and the service is operating as expected. Start by checking the logs available in the Elestio dashboard for any warnings or errors during the process. Then, review performance metrics to ensure the database is running normally and responding to queries. Finally, test the connection from your client applications to confirm that they can interact with the upgraded database without issues. Enter section select mode [Previous\ \ Creating a Database](https://docs.elest.io/books/hydra/page/creating-a-database) [Next\ \ Installing or Updating an Extension](https://docs.elest.io/books/hydra/page/installing-or-updating-an-extension) Back to top --- # Connecting with Java | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-java#main-content) Info Content Connecting with Java ==================== This guide shows how to connect your Java app to a **Hydra database** using the [PostgreSQL JDBC driver](https://jdbc.postgresql.org/) , parse command-line arguments, and run a basic query. ### **Variables** To connect to a Hydra database, the following parameters are required. You can find these details in the **Elestio service overview page** of your Hydra service. | **Variable** | **Description** | **Purpose** | | --- | --- | --- | | `**USER**` | Hydra (PostgreSQL) username | Identifies the database user with access privileges | | `**PASSWORD**` | Hydra password | Authenticates the user against the Hydra database | | `**HOST**` | Hostname of the Hydra instance | Specifies the server address of the database | | `**PORT**` | Port for Hydra (usually 5432) | Specifies the network port for connections | | `**DATABASE**` | Name of the Hydra database | Specifies which database to access | These values can usually be found in the Elestio service overview details as shown in the image below, make sure to take a copy of these details and add it to the code moving ahead. [![Screenshot 2025-05-07 at 2.09.07 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-07-at-2-09-07-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-07-at-2-09-07-pm.jpg) ### **Prerequisites** ##### **Install Java & JDBC driver** Check if Java is installed by running: java -version If not installed, install it first and then download and install **JDBC** driver from [https://jdbc.postgresql.org/download/](https://jdbc.postgresql.org/download/) or if you have Maven installed, run the following command with updated version of the driver: mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get \ -Dartifact=org.postgresql:postgresql:42.7.5:jar \ -Ddest=postgresql-42.7.5.jar **Code** -------- Once all prerequisites are set up, create a new file named `HydraPg.java` and add the following code: import java.sql.Connection; import java.sql.DriverManager; import java.sql.ResultSet; import java.sql.SQLException; import java.sql.Statement; import java.util.HashMap; import java.util.Map; public class HydraPg { static class Config { String host, port, database, username, password; Config(String host, String port, String database, String username, String password) { this.host = host; this.port = port; this.database = database; this.username = username; this.password = password; } String getJdbcUrl() { return String.format("jdbc:postgresql://%s:%s/%s?sslmode=require", host, port, database); } boolean isComplete() { return host != null && port != null && database != null && username != null && password != null; } } static Map parseArgs(String[] args) { Map map = new HashMap<>(); for (int i = 0; i < args.length - 1; i += 2) { map.put(args[i], args[i + 1]); } return map; } public static void main(String[] args) { try { Class.forName("org.postgresql.Driver"); Map argMap = parseArgs(args); Config cfg = new Config( argMap.get("-host"), argMap.get("-port"), argMap.get("-database"), argMap.get("-username"), argMap.get("-password") ); if (!cfg.isComplete()) { System.err.println("Missing required arguments. Example usage:"); System.err.println("java -cp postgresql-42.7.5.jar:. HydraPg -host -port -database -username -password "); return; } try (Connection conn = DriverManager.getConnection(cfg.getJdbcUrl(), cfg.username, cfg.password)) { System.out.println("Connected to Hydra database successfully."); Statement stmt = conn.createStatement(); ResultSet rs = stmt.executeQuery("SELECT current_database(), current_user, version()"); while (rs.next()) { System.out.println("Database: " + rs.getString(1)); System.out.println("User: " + rs.getString(2)); System.out.println("Version: " + rs.getString(3)); } rs.close(); stmt.close(); } } catch (ClassNotFoundException e) { System.err.println("PostgreSQL JDBC driver not found."); e.printStackTrace(); } catch (SQLException e) { System.err.println("Connection or query error:"); e.printStackTrace(); } } } To execute the script, open the terminal or command prompt and navigate to the directory where `HydraPg.java`. Once in the correct directory, run the script with the command (Update the variables with actual values acquired from previous steps). javac HydraPg.java java -cp postgresql-42.7.5.jar:. HydraPg -host HOST -port PORT -database DATABASE -username USERNAME -password PASSWORD If the connection is successful, the terminal will display output similar to: Connected to Hydra database successfully. Database: elestio User: postgres Version: PostgreSQL 14.13 (Debian 14.13-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit Enter section select mode [Previous\ \ Connecting with Go](https://docs.elest.io/books/hydra/page/connecting-with-go) [Next\ \ Connecting with psql](https://docs.elest.io/books/hydra/page/connecting-with-psql) Back to top --- # Cluster Resynchronization | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/cluster-resynchronization#main-content) Info Content Cluster Resynchronization ========================= In distributed systems, consistency and synchronization between nodes are critical to ensure that services behave reliably and that data remains accurate across the cluster. Elestio provides built-in mechanisms to detect and resolve inconsistencies across nodes using a feature called **Cluster Resynchronization**. This functionality ensures that node-level configurations, data replication, and service states are properly aligned, especially after issues like node recovery, temporary network splits, or service restarts. **Need for Cluster Resynchronization** -------------------------------------- Resynchronization is typically required when secondary nodes in a cluster are no longer consistent with the primary node. This can happen due to temporary network failures, node restarts, replication lag, or partial service interruptions. In such cases, secondary nodes may fall behind or store incomplete datasets, which could lead to incorrect behavior if a failover occurs or if read operations are directed to those nodes. Unresolved inconsistencies can result in data divergence, serving outdated content, or failing health checks in load-balanced environments. Performing a resynchronization ensures that all secondary nodes are forcibly aligned with the current state of the primary node, restoring a clean and unified cluster state. It may also be necessary to perform a resync after restoring a service from backup, during infrastructure migrations, or after recovering a previously offline node. In each of these cases, resynchronization acts as a corrective mechanism to ensure that every node is operating with the same configuration and dataset, reducing the risk of drift and maintaining data integrity across the cluster. **Cluster Resynchronization** ----------------------------- To perform a resynchronization, start by accessing the [Elestio dashboard](https://dash.elest.io/)  and navigating to the **Clusters** section. Select the cluster where synchronization is needed. On the **Cluster Overview** page, scroll down slightly until you find the **“Resync Cluster”** option. This option is visible as part of the cluster controls and is available only in clusters with multiple nodes and a defined primary node. [![Screenshot 2025-05-05 at 7.35.44 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-7-35-44-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-7-35-44-pm.jpg) Clicking the **Resync** button opens a confirmation dialog. The message clearly explains that this action will initiate a request to resynchronize **all secondary nodes**. During the resync process, **existing data on all secondary nodes will be erased and replaced with a copy of the data from the primary node**. This operation ensures full consistency across the cluster but should be executed with caution, especially if recent changes exist on any of the secondaries that haven’t yet been replicated. [![Screenshot 2025-05-05 at 7.35.59 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-7-35-59-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-7-35-59-pm.jpg) You will receive an email notification once the resynchronization is complete. During this process, Elestio manages the replication safely, but depending on the size of the data, the operation may take a few minutes. It’s advised to avoid making further changes to the cluster while the resync is in progress. **Considerations Before Resynchronizing** ----------------------------------------- * Before triggering a resync, it’s important to verify that the primary node holds the desired state and that the secondary nodes do not contain any critical unsynced data. Since the resync **overwrites** the secondary nodes completely, any local changes on those nodes will be lost. * This action is best used when you’re confident that the primary node is healthy, current, and stable. Avoid initiating a resync if the primary has recently experienced errors or data issues. Additionally, consider performing this operation during a low-traffic period, as synchronization may temporarily impact performance depending on the data volume. * If your application requires high consistency guarantees, it’s recommended to monitor your cluster closely during and after the resync to confirm that services are functioning correctly and that the replication process completed successfully. Enter section select mode [Previous\ \ Restricting Access by IP](https://docs.elest.io/books/hydra/page/restricting-access-by-ip) [Next\ \ Database Migrations](https://docs.elest.io/books/hydra/page/database-migrations) Back to top --- # Connecting with Python | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-python#main-content) Info Content Connecting with Python ====================== This guide explains how to connect a Python application to a Hydra database using the `psycopg2-binary` package. It covers environment setup, configuration, and execution of a simple query to test connectivity. ### **Variables** To connect to a Hydra database, you only need **one environment variable** — the connection URI. | **Variable** | **Description** | **Purpose** | | --- | --- | --- | | `HYDRA_URI` | Full Hydra (PostgreSQL-compatible) connection string from the Elestio service overview | Provides all credentials and connection details in a single URI | A typical URI format looks like: postgresql://:@:/ You can find the details needed in the URI from the **Elestio service overview** details. Copy and replace the variables carefully in the URI example provided above. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/kHqimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/kHqimage.png) ### **Prerequisites** **Install Python** Check if Python is installed: python --version If not installed, download it from [https://python.org](https://python.org/) . **Install** `**psycopg2-binary**` Install the PostgreSQL driver for Python: pip install psycopg2-binary ### **Code** Once all prerequisites are set up, create a new file named `hydra.py` and add the following code and replace the `HYDRA_URI` with actual link or in environment setup as you wish: import psycopg2 import os def get_db_version(): try: # Use the Hydra URI from environment variable connection_uri = os.getenv('HYDRA_URI', 'POSTGRESQL_URI') db_connection = psycopg2.connect(connection_uri) db_cursor = db_connection.cursor() db_cursor.execute('SELECT VERSION()') db_version = db_cursor.fetchone()[0] return db_version except Exception as e: print(f"Database connection error: {e}") return None finally: if 'db_cursor' in locals(): db_cursor.close() if 'db_connection' in locals(): db_connection.close() def display_version(): version = get_db_version() if version: print(f"Connected to Hydra: {version}") if __name__ == "__main__": display_version() > 🔐 **Tip:** Save your URI in an .env file or set it in your terminal session like this: export HYDRA_URI=postgresql://user:password@host:port/database To execute the script, open the terminal or command prompt and navigate to the directory where `hydra.py`. Once in the correct directory, run the script with the command python hydra.py If the connection is successful, you’ll see: Connected to Hydra: PostgreSQL 14.13 (Debian 14.13-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit Enter section select mode [Previous\ \ Connecting with Node.js](https://docs.elest.io/books/hydra/page/connecting-with-nodejs) [Next\ \ Connecting with PHP](https://docs.elest.io/books/hydra/page/connecting-with-php) Back to top --- # Connecting with psql | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-psql#main-content) Info Content Connecting with psql ==================== This guide explains how to connect to a **Hydra** database using the **`psql`** command-line tool. It walks through the necessary setup, connection process, and execution of a simple SQL query. ### **Variables** To connect to a Hydra database, you only need **one environment variable** — the connection URI. | **Variable** | **Description** | **Purpose** | | --- | --- | --- | | `HYDRA_URI` | Full Hydra connection string from Elestio | Encodes all connection info in one URI | A typical URI looks like this: postgresql://:@:/ You can find the details needed in the URI from the **Elestio service overview** details. Copy and replace the variables carefully in the URI example provided above. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/eTcimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/eTcimage.png) ### **Prerequisites** While following this tutorial, you will need to have **`psql`** already installed; if not head over to [https://www.postgresql.org/download/](https://www.postgresql.org/download/)  and download it first. ### **Connecting to Hydra** Open your terminal and run the following command to connect to your Hydra database using the full connection URI: psql HYDRA_URI If the connection is successful, you’ll see output similar to this. Here it will show you the database you tried to connect to, which in this case is Elestio: psql (17.4, server 14.13 (Debian 14.13-1.pgdg120+1)) SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off, ALPN: none) Type "help" for help. elestio=# To ensure you're connected correctly, run this command inside the `psql` prompt: SELECT version(); You should receive output like the following: version --------------------------------------------------------------------------------------------------------------------- PostgreSQL 16.8 (Debian 16.8-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit (1 row) Enter section select mode [Previous\ \ Connecting with Java](https://docs.elest.io/books/hydra/page/connecting-with-java) [Next\ \ Connecting with pgAdmin](https://docs.elest.io/books/hydra/page/connecting-with-pgadmin) Back to top --- # Connecting with Go | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-go#main-content) Info Content Connecting with Go ================== This guide walks you through setting up a Go application to connect to a Hydra database, using the PostgreSQL-compatible `lib/pq` driver, and running a basic query to verify the connection. ### **Variables** To connect to a Hydra database, you only need **one environment variable** — the connection URI. This URI contains all the necessary information like username, password, host, port, and database name. | **Variable** | **Description** | **Purpose** | | --- | --- | --- | | `HYDRA_URI` | Full Hydra (PostgreSQL-compatible) connection string from the Elestio service overview | Provides all credentials and connection details in a single URI | A typical URI format looks like: postgresql://:@:/ You can find the details needed in the URI from the **Elestio service overview** details. Copy and replace the variables carefully in the URI example provided above. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/kHqimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/kHqimage.png) ### **Prerequisites** * **Install Go** * Check if Go is installed: go version * * If not, download and install Go: [https://go.dev/dl/](https://go.dev/dl/) * **Install pq Driver** go get github.com/lib/pq ### **Code** Once all prerequisites are set up, create a new file named `main.go` and add the following code, and replace the `HYDRA_URI` with actual link or in environment setup as you wish: package main import ( "database/sql" "fmt" "log" "os" _ "github.com/lib/pq" ) func getDBConnection(connStr string) (*sql.DB, error) { db, err := sql.Open("postgres", connStr) if err != nil { return nil, fmt.Errorf("failed to open database connection: %v", err) } if err := db.Ping(); err != nil { return nil, fmt.Errorf("failed to ping database: %v", err) } return db, nil } func main() { // Get the Hydra connection string from environment variable connStr := os.Getenv("HYDRA_URI") if connStr == "" { log.Fatal("HYDRA_URI environment variable not set") } db, err := getDBConnection(connStr) if err != nil { log.Fatal(err) } defer db.Close() query := "SELECT current_database(), current_user, version()" row := db.QueryRow(query) var dbName, user, version string if err := row.Scan(&dbName, &user, &version); err != nil { log.Fatal("Failed to scan row:", err) } fmt.Printf("Connected to Hydra\nDatabase: %s\nUser: %s\nVersion: %s\n", dbName, user, version) } Set your Hydra URI as an environment variable: export HYDRA_URI=postgresql://user:password@host:port/database To execute the script, open the terminal or command prompt and navigate to the directory where `main.go`. Once in the correct directory, run the script with the command go run main.go If successful, you’ll see output like: Connected to Hydra Database: elestio User: postgres Version: PostgreSQL 14.13 (Debian 14.13-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit Enter section select mode [Previous\ \ Connecting with PHP](https://docs.elest.io/books/hydra/page/connecting-with-php) [Next\ \ Connecting with Java](https://docs.elest.io/books/hydra/page/connecting-with-java) Back to top --- # Cloning a Service to A... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/cloning-a-service-to-another-provider-or-region#main-content) Info Content Cloning a Service to Another Provider or Region =============================================== Migrating or cloning services across cloud providers or geographic regions is a critical part of modern infrastructure management. Whether you’re optimizing for latency, preparing for disaster recovery, meeting regulatory requirements, or simply switching providers, a well-planned migration ensures continuity, performance, and data integrity. This guide outlines a structured methodology for service migration, applicable to most cloud-native environments. **Pre-Migration Preparation** ----------------------------- Before initiating a migration, thorough planning and preparation are essential. This helps avoid unplanned downtime, data loss, or misconfiguration during the move: * **Evaluate the Current Setup**: Begin by documenting the existing service’s configuration. This includes runtime environments (container images, platform versions), persistent data (databases, object storage), network rules (ports, firewalls), and application dependencies (APIs, credentials, linked services). * **Define the Migration Target**: Choose the new cloud provider or region you plan to migrate to. Confirm service compatibility, resource limits, and geographic latency requirements. If you’re replicating an existing environment, make sure the target region supports the same compute/storage features and versions. * **Provision the Target Environment**: Set up the target infrastructure where the service will be cloned. This could involve creating new Kubernetes clusters, VM groups, container registries, databases, or file storage volumes—depending on your stack. * **Backup the Current Service**: Always create a full backup or snapshot of the current service and its associated data before proceeding. This acts as a rollback point in case of migration issues and ensures recovery in the event of failure. **Cloning Execution** --------------------- The first step in executing a clone is to replicate the configuration of the original service in the target environment. This involves deploying the same container image or service binary using the same runtime settings. If you’re using Kubernetes or container orchestrators, this can be done via Helm charts or declarative manifests. Pay close attention to environment variables, secrets, mounted paths, storage class definitions, and health check configurations to ensure a consistent runtime environment. Next, you’ll need to migrate any persistent data tied to the service. For Hydra databases, this might involve using `pg_dump` to export the schema and data, followed by psql or pg\_restore to import it into the new instance. In more complex cases, tools like `pgBackRest`, `wal-g`, or logical replication can be used to minimize downtime during the switchover. For file-based storage, tools like rsync or rclone are effective for copying volume contents over SSH or cloud storage backends. It’s crucial to verify compatibility across disk formats, database versions, and encoding standards to avoid corruption or mismatched behavior. After replicating the environment and data, it’s important to validate the new service in isolation. This means confirming that all application endpoints respond as expected, background tasks or cron jobs are functioning, and third-party integrations (e.g., payment gateways, S3 buckets) are accessible. You should test authentication flows, data read/write operations, and retry logic to ensure the new service is functionally identical. Use observability tools to monitor resource consumption and application logs during this stage. Once validation is complete, configure DNS and route traffic to the new environment. This might involve updating DNS A or CNAME records, changing cloud load balancer configurations, or applying new firewall rules. For high-availability setups, consider using health-based routing or weighted DNS to gradually transition traffic from the old instance to the new one. **Post-Migration Validation and Optimization** ---------------------------------------------- Once the new environment is live and receiving traffic, focus on optimizing and securing the setup: * **Validate Application Functionality**: Test all integrations, user workflows, and background jobs to confirm proper behavior. Review logs for silent errors or timeouts. Ensure all applications pointing to the service are updated with the new URL or connection string. * **Monitor Performance**: Analyze load, CPU, memory, and storage utilization. Scale resources as needed, or optimize runtime settings for the new provider/region. Enable autoscaling where applicable. * **Secure the Environment**: Implement firewall rules, IP restrictions, and access controls. Rotate secrets and validate that no hardcoded credentials or endpoints point to the old service. * **Cleanup and Documentation**: Once validated, decommission the old setup safely. Update internal documentation with new deployment details, endpoint addresses, and any configuration changes. **Benefits of Cloning** ----------------------- Cloning a database service, particularly for engines like Hydra offers several operational and strategic advantages. It allows teams to test schema migrations, version upgrades, or major application features in an isolated environment without affecting production. By maintaining a cloned copy, developers and QA teams can work against realistic data without introducing risk. Cloning also simplifies cross-region redundancy setups. A replica in another region can be promoted quickly if the primary region experiences an outage. For compliance or analytics purposes, cloned databases allow for read-only access to production datasets, enabling safe reporting or data processing without interrupting live traffic. Additionally, rather than building a new environment from scratch, you can clone the database into another provider, validate it, and cut over with minimal disruption. This helps maintain operational continuity and reduces the effort needed for complex migrations. Enter section select mode [Previous\ \ Database Migration Service for Hydra](https://docs.elest.io/books/hydra/page/database-migration-service-for-hydra) [Next\ \ Manual Migration Using pg\_dump and pg\_restore](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore) Back to top --- # Creating Manual Backups | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/creating-manual-backups#main-content) Info Content Creating Manual Backups ======================= Regular backups are a key part of managing a Hydra deployment. While Elestio provides automated backups by default, you may want to perform manual backups for specific reasons, such as preparing for a major change, keeping a local copy, or testing backup automation. This guide walks through how to create Hydra backups on Elestio using multiple approaches. It covers manual backups through the Elestio dashboard, using Hydra CLI tools, and Docker Compose-based setups. It also includes advice for backup storage, retention policies, and automation using scheduled jobs. **Manual Service Backups on Elestio** ------------------------------------- If you’re using Elestio’s managed Hydra service, the easiest way to create a manual backup is through the dashboard. This built-in method creates a full snapshot of your current database state and stores it within Elestio’s infrastructure. These backups are tied to your service and can be restored through the same interface. This option is recommended when you need a quick, consistent backup without using any terminal commands. To trigger a manual backup from the Elestio dashboard: 1. Log in to the Elestio dashboard and navigate to your Hydra service/cluster. 2. Click the **Backups** tab in the service menu. 3. Select **Back up now** to generate a snapshot. [![Screenshot 2025-05-08 at 12.49.21 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/daZscreenshot-2025-05-08-at-12-49-21-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/daZscreenshot-2025-05-08-at-12-49-21-pm.jpg) **Manual Backups Using CLI** ---------------------------- Hydra/PostgreSQL provides a set of command-line tools that are useful when you want to create backups from your terminal. These include `pg_dump` exporting the database, psql for basic connectivity and queries, and `pg_restore` restoring backups. This approach is useful when you need to store backups locally or use them with custom automation workflows. The CLI method gives you full control over the backup format and destination. #### **Collect Database Connection Info** To use the CLI tools, you’ll need the database host, port, name, username, and password. These details can be found in the **Overview** section of your Hydra service in the Elestio dashboard. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/Ii6image.png)](https://docs.elest.io/uploads/images/gallery/2025-05/Ii6image.png) #### **Back Up with** **pg\_dump** Use `pg_dump` to export the database in a custom format. This format is flexible and preferred for restore operations using `pg_restore`. Replace the values with actual values that you copied from the Elestio overview page. PGPASSWORD='' pg_dump \ -U \ -h \ -p \ -Fc -v \ -f .dump \ This command connects to the Elestio database and creates a `.dump` file containing your data. You can use the `-v` flag for verbose output and confirm that the backup completed successfully. **Manual Backups Using Docker Compose** --------------------------------------- If your Hydra database is deployed through a Docker Compose setup on Elestio, you can run the `pg_dump` command from within the running container. This is useful when the tools are installed inside the container environment and you want to keep everything self-contained. The backup can be created inside the container and then copied to your host system for long-term storage or transfer. #### **Access Elestio Terminal** Head over to your deployed Hydra service dashboard and head over to **Tools > Terminal**. Use the credentials provided there to log in to your terminal. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/SGwimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/SGwimage.png) Once you are in your terminal, run the following command to head over to the correct directory to perform the next steps cd /opt/app/ #### **Run `pg_dump`** **Inside the Container** This command runs `pg_dump` from inside the container and saves the backup to a file in `/tmp`. Make sure you have the following things in command in your env, else replace them with actual values and not the env variables. docker-compose exec hydra \ bash -c "PGPASSWORD='\$HYDRA_PASSWORD' pg_dump -U \$HYDRA_USER -Fc -v \$HYDRA_DB > /tmp/manual_backup.dump" This assumes that environment variables like `HYDRA_USER`, `HYDRA_PASSWORD`, and `HYDRA_DB` are defined in your Compose setup. #### **Copy Backup to Host** After creating the backup inside the container, use `docker cp` to copy the file to your host machine. docker cp $(docker-compose ps -q hydra):/tmp/manual_backup.dump ./manual_backup.dump This creates a local copy of the backup file, which you can then upload to external storage or keep for versioned snapshots. **Backup Storage & Retention Best Practices** --------------------------------------------- Once backups are created, they should be stored securely and managed with a clear retention policy. Proper naming, encryption, and rotation reduce the risk of data loss and help during recovery. Use timestamped filenames to identify when the backup was created. External storage services such as AWS S3, Backblaze B2, or an encrypted server volume are recommended for long-term storage. Here are some guidelines to follow: * Name your backups clearly: `mydb_backup_2024_04_02.dump`. * Store in secure, off-site storage if possible. * Retain 7 daily backups, 4 weekly backups, and 3–6 monthly backups. * Remove old backups automatically to save space. By combining storage hygiene with regular scheduling, you can maintain a reliable backup history and reduce manual effort. **Automating Manual Backups (****cron****)** -------------------------------------------- Manual backup commands can be scheduled using tools like cron on Linux-based systems. This allows you to regularly back up your database without needing to run commands manually. Automating the process also reduces the risk of forgetting backups and ensures more consistent retention. #### **Example: Daily Backup at 2 AM** Open your crontab file for editing: crontab -e Then add a job like the following: 0 2 * * * PGPASSWORD='mypassword' pg_dump -U elestio -h db-xyz.elestio.app -p 5432 -Fc -f /backups/backup_$(date +\%F).dump mydatabase Make sure the `/backups/` directory exists and is writable by the user running the job. You can also compress the backup and upload it to a remote destination as part of the same script. Enter section select mode [Previous\ \ Installing or Updating an Extension](https://docs.elest.io/books/hydra/page/installing-or-updating-an-extension) [Next\ \ Restoring a Backup](https://docs.elest.io/books/hydra/page/restoring-a-backup) Back to top --- # Manual Migration Using... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore#main-content) Info Content Manual Migration Using pg\_dump and pg\_restore =============================================== Manual Migrations using Hydra’s built-in tools `pg_dump` and `pg_restore` are ideal for users who prefer full control over data export and import, particularly during provider transitions, database version upgrades, or when importing an existing self-managed Hydra dataset into Elestio’s managed environment. This guide walks through the process of performing a manual migration to and from Elestio Hydra services using command-line tools, ensuring that your data remains portable, auditable, and consistent. **When to Use Manual Migration** -------------------------------- Manual migration using `pg_dump` and `pg_restore` is well-suited for scenarios where full control over the data export and import process is required. This method is particularly useful when migrating from an existing Hydra setup, whether self-hosted, on-premises, or on another cloud provider, into Elestio’s managed Hydra service. It allows for one-time imports without requiring continuous connectivity between source and target systems. This approach is also ideal when dealing with version upgrades, as Hydra's logical backups can be restored into newer versions without compatibility issues. In situations where Elestio’s built-in snapshot or replication tools aren’t applicable such as migrations from isolated environments or selective schema transfers, manual migration becomes the most practical option. Additionally, this method enables users to retain portable, versioned backups outside of Elestio’s infrastructure, which can be archived, validated offline, or re-imported into future instances. **Performing the Migration** ---------------------------- #### **Prepare the Environments** Before initiating a migration, verify that Hydra is properly installed and configured on both the source system and your Elestio service. On the source, you need an active Hydra instance with a user account that has sufficient privileges to read schemas, tables, sequences, and any installed extensions. The user must also be allowed to connect over TCP if the server is remote. On the Elestio side, provision a Hydra service from the dashboard. Once deployed, retrieve the connection information from the Database admin tab. This includes the hostname, port, database name, username, and password. You’ll use these credentials to connect during the restore step. Ensure that your IP is allowed to connect under the Cluster Overview > Security > Limit access per IP section; otherwise, the Hydra port will be unreachable during the migration. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/EWNimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/EWNimage.png) #### **Create a Dump Using** **pg\_dump** In this step, you generate a logical backup of the source database using `pg_dump`. This utility connects to the Hydra server and extracts the structure and contents of the specified database. It serializes tables, indexes, constraints, triggers, views, and functions into a consistent snapshot. The custom format (\-Fc) is used because it produces a compressed binary dump that can be restored selectively using `pg_restore`. pg_dump -U -h -p -Fc > backup.dump This command connects to the source server (\-h), authenticates with the user (\-U), targets the database (source\_database), and exports the entire schema and data into `backup.dump`. The resulting file is portable and version-aware. You can also add `--no-owner` and `--no-acl` If you’re migrating between environments that use different database roles or access models. This prevents restore-time errors related to ownership mismatches. #### **Transfer the Dump File to the Target** If your source and target environments are on different hosts, the dump file must be transferred securely. This step ensures the logical backup is available on the system from which you’ll perform the restore. You can use secure copy (scp), rsync, or any remote file transfer method. scp backup.dump your_user@your_workstation:/path/to/local/ If restoring from your local machine to Elestio, ensure the dump file is stored in a location readable by your current shell user. Elestio does not require the file to be uploaded to its servers; the restore is performed by connecting over the network using standard Hydra protocols. At this point, your backup is isolated from the source environment and ready for import. #### **Create the Target Database** By default, Elestio provisions a single database instance. However, if you wish to restore into a separate database name or if your dump references a different name, you must create the new database manually. Use the psql client to connect to your Elestio service using the credentials from the dashboard. psql -U -h -p -d postgres Within the psql session, create the database: CREATE DATABASE target_database WITH ENCODING='UTF8' LC_COLLATE='en_US.UTF-8' LC_CTYPE='en_US.UTF-8' TEMPLATE=template0; This ensures that the new database has consistent encoding and locale settings, which are critical for text comparison, sorting, and indexing. Using template0 avoids inheriting default extensions or templates that might conflict with your dump file. At this stage, you can also create any roles, schemas, or extensions that were used in the original database if they are not included in the dump. #### **Restore Using** **pg\_restore** With the target database created and the dump file in place, initiate the restoration using `pg_restore`. This tool reads the custom-format archive and reconstructs all schema and data objects in the new environment. pg_restore -U elestio_user -h elestio_host -p 5432 -d target_database -Fc /path/to/backup.dump --verbose This command establishes a network connection to the Elestio Hydra service and begins issuing `CREATE`, `INSERT`, and `ALTER` statements to rebuild the database. The `--verbose` flag provides real-time feedback about the objects being restored. You can also use `--jobs=N` to run the restore in parallel, improving performance for large datasets, provided the dump was created with `pg_dump --jobs=N`. It’s important to ensure that all referenced extensions, collations, and roles exist on the target instance to avoid partial restores. If errors occur, the logs will point to the missing components or permission issues that need to be resolved. #### **Validate the Migration** Once the restore completes, you must validate the accuracy and completeness of the migration. Connect to the Elestio database using psql or a Hydra GUI (such as pgAdmin or TablePlus), and run checks across critical tables. Begin by inspecting the table existence and row counts: \dt SELECT COUNT(*) FROM your_important_table;s Validate views, functions, and indexes, especially if they were used in reporting or application queries. Run application-specific health checks, reinitialize ORM migrations if applicable, and confirm that the application can read and write to the new database without errors. If you made any changes to connection strings or credentials, update your environment variables or secret managers accordingly. Elestio also supports automated backups, which you should enable post-migration to protect the restored dataset. **Benefits of Manual Migration** -------------------------------- Manual Hydra migration using `pg_dump` and `pg_restore` on Elestio provides several key advantages: * **Compatibility and Portability**: Logical dumps allow you to migrate from any Hydra/PostgreSQL-compatible source into Elestio, including on-premises systems, Docker containers, or other clouds. * **Version-Safe Upgrades**: The tools support migrating across Hydra versions, which is ideal during controlled upgrades. * **Offline Archiving**: Manual dumps serve as portable archives for cold storage, disaster recovery, or historical snapshots. * **Platform Independence**: You retain full access to Hydra native tools without being locked into Elestio-specific formats or interfaces. This method complements Elestio’s automated backup and migration features by enabling custom workflows and one-off imports with full visibility into each stage. Enter section select mode [Previous\ \ Cloning a Service to Another Provider or Region](https://docs.elest.io/books/hydra/page/cloning-a-service-to-another-provider-or-region) [Next\ \ Cluster Management](https://docs.elest.io/books/hydra/chapter/cluster-management) Back to top --- # Database Migration Ser... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/database-migration-service-for-hydra#main-content) Info Content Database Migration Service for Hydra ==================================== Elestio provides a structured approach for migrating Hydra databases from various environments, such as on-premises systems or other cloud platforms, to its managed services. This process ensures data integrity and minimizes downtime, facilitating a smooth transition to a managed environment.​ **Key Steps in Migrating to Elestio** ------------------------------------- #### **Pre-Migration Preparation** Before initiating the migration process, it's essential to undertake thorough preparation to ensure a smooth transition: * **Create an Elestio Account:** Register on the Elestio platform to access their suite of managed services. This account will serve as the central hub for managing your Hydra instance and related resources. * **Deploy the Target Hydra Service:** Set up a new Hydra instance on Elestio to serve as the destination for your data. It's crucial to match the software version of your current Hydra database to avoid compatibility issues during data transfer. Detailed prerequisites and guidance can be found in Elestio's [migration documentation](https://docs.elest.io/books/databases/page/postgresql-database-migration-to-elestio) . #### **Initiating the Migration Process** With the preparatory steps completed, you can proceed to migrate your Hydra database to Elestio: 1. **Access the Migration Tool:** Navigate to the overview of your Hydra service on the Elestio dashboard. Click on the "Migrate Database" button to initiate the migration process. This tool is designed to facilitate a smooth transition by guiding you through each step. 2. **Configure Migration Settings:** A modal window will open, prompting you to ensure that your target service has sufficient disk space to accommodate your database. Adequate storage is vital to prevent interruptions during data transfer. Once confirmed, click on the "Get started" button to proceed. 3. **Validate Source Database Connection:** Provide the connection details for your existing Hydra database, including: * **Hostname:** The address of your current database server. * **Port:** The port number on which your Hydra service is running (default is 5432). * **Database Name:** The name of the database you intend to migrate. * **Username:** The username with access privileges to the database. * **Password:** The corresponding password for the user. After entering these details, click on "Run Check" to validate the connection. This step ensures that Elestio can securely and accurately access your existing data. You can find these details under Database admin section under your deployed Hydra service. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/hy6image.png)](https://docs.elest.io/uploads/images/gallery/2025-05/hy6image.png) 4. **Execute the Migration:** If all checks pass without errors, initiate the migration by selecting "Start migration." Monitor the progress through the real-time migration logs displayed on the dashboard. This transparency allows for immediate detection and resolution of any issues, ensuring data integrity throughout the process. #### **Post-Migration Validation and Optimization** After completing the migration, it's crucial to perform validation and optimization tasks to ensure the integrity and performance of your database in the new environment: * **Verify Data Integrity:** Conduct thorough checks to ensure all data has been accurately transferred. This includes comparing row counts, checksums, and sample data between the source and target databases. Such verification maintains the reliability of your database and ensures that no data was lost or altered during migration. * **Test Application Functionality:** Ensure that applications interacting with the database function correctly in the new environment. Update connection strings and configurations as necessary to reflect the new database location. This step prevents potential disruptions and ensures seamless operation of dependent systems. * **Optimize Performance:** Utilize Elestio's managed service features to fine-tune database performance. Set up automated backups to safeguard your data, monitor resource utilization to identify and address bottlenecks, and configure scaling options to accommodate future growth. These actions contribute to improved application responsiveness and overall system efficiency. * **Implement Security Measures:** Review and configure security settings to protect your data within the Elestio environment. Set up firewalls to control access, manage user access controls to ensure only authorized personnel can interact with the database, and enable encryption where applicable to protect data at rest and in transit. Implementing these security measures safeguards your data against unauthorized access and potential threats. **Benefits of Using Elestio for Hydra** --------------------------------------- Migrating your Hydra database to Elestio offers several advantages:​ * **Simplified Management:** Elestio automates database maintenance tasks, including software updates, backups, and system monitoring, reducing manual work. The platform provides a dashboard with real-time insights into database performance and resource usage. It allows for adjusting service plans, scaling CPU and RAM as needed. Users can modify environment variables and access software information to manage configurations. * **Security:** Elestio keeps Hydra instances updated with security patches to protect against vulnerabilities. The platform automates backups to ensure data integrity and availability. It provides secure access mechanisms, including randomly generated passwords for database instances, which can be managed through the dashboard. * **Performance:** Elestio configures Hydra instances for performance based on workload requirements. The platform supports the latest Hydra versions, incorporating updates that improve database operations. Its infrastructure handles different workloads and maintains performance during high usage periods. * **Scalability:** Elestio's Hydra service allows for scaling database resources to handle growth and changing workloads without major downtime. Users can upgrade or downgrade service plans, adjusting CPU and RAM as needed. The platform supports adding network volumes to increase storage capacity. Enter section select mode [Previous\ \ Database Migration](https://docs.elest.io/books/hydra/chapter/database-migration) [Next\ \ Cloning a Service to Another Provider or Region](https://docs.elest.io/books/hydra/page/cloning-a-service-to-another-provider-or-region) Back to top --- # Page Revisions for Database Migrations | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/database-migrations/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/database-migrations/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Database Migrations (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:46:59 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/database-migrations) Back to top --- # Page Revisions for Deleting a Cluster | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/deleting-a-cluster/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/deleting-a-cluster/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Deleting a Cluster (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:49:12 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/deleting-a-cluster) Back to top --- # Page Revisions for Restricting Access by IP | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/restricting-access-by-ip/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/restricting-access-by-ip/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Restricting Access by IP (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:51:54 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/restricting-access-by-ip) Back to top --- # Page Revisions for Connecting with Node.js | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-nodejs/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/connecting-with-nodejs/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 3 Connecting with Node.js (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:21:41 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-nodejs/revisions/2606/changes)  |  [_Current Version_](https://docs.elest.io/books/hydra/page/connecting-with-nodejs) # 2 Connecting with Node.js (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 14:05:19 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-nodejs/revisions/2600/changes)  |  [Preview](https://docs.elest.io/books/hydra/page/connecting-with-nodejs/revisions/2600) # 1 Connecting with Node.js (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 08:40:42 UTC (7 months ago) Initial publish [Preview](https://docs.elest.io/books/hydra/page/connecting-with-nodejs/revisions/2591) Back to top --- # Page Revisions for Cluster Resynchronization | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/cluster-resynchronization/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/cluster-resynchronization/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Cluster Resynchronization (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 14:08:03 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/cluster-resynchronization) Back to top --- # Page Revisions for Connecting with PHP | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 4 Connecting with PHP (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:22:15 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions/2609/changes)  |  [_Current Version_](https://docs.elest.io/books/hydra/page/connecting-with-php) # 3 Connecting with PHP (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:20:04 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions/2603/changes)  |  [Preview](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions/2603) # 2 Connecting with PHP (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 10:25:45 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions/2596/changes)  |  [Preview](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions/2596) # 1 Connecting with PHP (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 10:25:18 UTC (7 months ago) Initial publish [Preview](https://docs.elest.io/books/hydra/page/connecting-with-php/revisions/2595) Back to top --- # Page Revisions for Connecting with Java | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-java/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/connecting-with-java/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Connecting with Java (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:38:35 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/connecting-with-java) Back to top --- # Page Revisions for Connecting with Go | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-go/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/connecting-with-go/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 2 Connecting with Go (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:22:32 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-go/revisions/2610/changes)  |  [_Current Version_](https://docs.elest.io/books/hydra/page/connecting-with-go) # 1 Connecting with Go (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:19:09 UTC (7 months ago) Initial publish [Preview](https://docs.elest.io/books/hydra/page/connecting-with-go/revisions/2601) Back to top --- # Page Revisions for Connecting with psql | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-psql/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/connecting-with-psql/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Connecting with psql (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 16:35:15 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/connecting-with-psql) Back to top --- # Page Revisions for Connecting with Python | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 5 Connecting with Python (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:21:59 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2608/changes)  |  [_Current Version_](https://docs.elest.io/books/hydra/page/connecting-with-python) # 4 Connecting with Python (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 15:20:56 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2605/changes)  |  [Preview](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2605) # 3 Connecting with Python (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 14:04:59 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2599/changes)  |  [Preview](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2599) # 2 Connecting with Python (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 10:01:17 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2594/changes)  |  [Preview](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2594) # 1 Connecting with Python (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 09:59:26 UTC (7 months ago) Initial publish [Preview](https://docs.elest.io/books/hydra/page/connecting-with-python/revisions/2592) Back to top --- # Page Revisions for Database Migration Ser... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/database-migration-service-for-hydra/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/database-migration-service-for-hydra/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Database Migration Service for Hydra (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 05:07:39 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/database-migration-service-for-hydra) Back to top --- # Page Revisions for Detect and terminate l... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/detect-and-terminate-long-running-queries/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/detect-and-terminate-long-running-queries/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Detect and terminate long-running queries (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 10:32:48 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/detect-and-terminate-long-running-queries) Back to top --- # Page Revisions for Installing or Updating... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/installing-or-updating-an-extension/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/installing-or-updating-an-extension/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Installing or Updating an Extension (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 08:10:52 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/installing-or-updating-an-extension) Back to top --- # Page Revisions for Creating a Database | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/creating-a-database/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/creating-a-database/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Creating a Database (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 07:10:44 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/creating-a-database) Back to top --- # Page Revisions for Connecting with pgAdmin | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/connecting-with-pgadmin/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/connecting-with-pgadmin/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Connecting with pgAdmin (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-07 16:40:51 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/connecting-with-pgadmin) Back to top --- # Page Revisions for Restoring a Backup | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/restoring-a-backup/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/restoring-a-backup/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Restoring a Backup (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 09:13:55 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/restoring-a-backup) Back to top --- # Page Revisions for Upgrading to a Major V... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/upgrading-to-a-major-version/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/upgrading-to-a-major-version/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Upgrading to a Major Version (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 07:22:58 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/upgrading-to-a-major-version) Back to top --- # Page Revisions for Cloning a Service to A... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/cloning-a-service-to-another-provider-or-region/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/cloning-a-service-to-another-provider-or-region/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Cloning a Service to Another Provider or Region (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 05:12:43 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/cloning-a-service-to-another-provider-or-region) Back to top --- # Page Revisions for Creating Manual Backups | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/creating-manual-backups/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/creating-manual-backups/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 3 Creating Manual Backups (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 09:09:07 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/creating-manual-backups/revisions/2625/changes)  |  [_Current Version_](https://docs.elest.io/books/hydra/page/creating-manual-backups) # 2 Creating Manual Backups (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 09:07:48 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/creating-manual-backups/revisions/2623/changes)  |  [Preview](https://docs.elest.io/books/hydra/page/creating-manual-backups/revisions/2623) # 1 Creating Manual Backups (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 09:06:47 UTC (7 months ago) Initial publish [Preview](https://docs.elest.io/books/hydra/page/creating-manual-backups/revisions/2621) Back to top --- # Page Revisions for Manual Migration Using... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 2 Manual Migration Using pg\_dump and pg\_restore (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-12 10:54:47 UTC (7 months ago) [Changes](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore/revisions/2657/changes)  |  [_Current Version_](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore) # 1 Manual Migration Using pg\_dump and pg\_restore (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 05:34:46 UTC (7 months ago) Initial publish [Preview](https://docs.elest.io/books/hydra/page/manual-migration-using-pg-dump-and-pg-restore/revisions/2617) Back to top --- # Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/overview#main-content) Info Content Overview ======== **Hydra** is an open-source OAuth2 and OpenID Connect (OIDC) server and identity provider written in Go. Developed by Ory, Hydra acts as a secure, scalable authentication and authorization layer for modern applications. It does not manage user identities directly but integrates with any login system to handle secure token issuance and authorization flows. Hydra is designed to comply with industry standards like OAuth2 and OIDC, making it suitable for microservices, APIs, and large-scale enterprise systems. **Key Features of Hydra:** * **OAuth2 & OpenID Connect Compliance**: Fully supports OAuth2.1 and OIDC standards, including flows like Authorization Code, Implicit, Client Credentials, and Device Code, ensuring compatibility with third-party applications and identity layers. * **Separation of Concerns**: Delegates authentication to your login system (via Login & Consent endpoints), enabling seamless integration with any identity provider or SSO platform without locking you into a specific user store. * **Security by Design**: Enforces strong security practices including TLS-by-default, token hashing, PKCE (Proof Key for Code Exchange), and proper consent handling, making it compliant with modern security requirements. * **Scalability and Performance**: Built in Go with minimal memory footprint and high concurrency capabilities, Hydra scales easily in cloud-native environments using containers or Kubernetes. * **Extensibility and Integration**: Works with any OAuth2-compatible clients and supports extensive customizations via HTTP hooks for login, consent, and error handling—giving developers full control over user flows. * **Stateless Architecture**: Does not store sessions on the server, relying instead on JWTs and external session systems. This design ensures horizontal scalability and simplifies distributed deployments. * **Consent and Login UI Integration**: Hydra allows external web UIs to handle login and consent, offering developers freedom to build fully customized, branded experiences for users. * **Database Agnostic**: Supports PostgreSQL and MySQL as backend stores, with schema migrations managed via SQL scripts, ensuring compatibility across most relational database environments. * **Multi-Tenant and Multi-Client Support**: Handles multiple OAuth2 clients and tenant apps securely, making it ideal for SaaS platforms, API gateways, and B2B/B2C authentication needs. * **Container-Ready and Cloud Native**: Designed for use in DevOps pipelines and cloud deployments, Hydra runs smoothly in Docker, Kubernetes, and serverless environments with minimal setup. These features make **Hydra** a preferred choice for organizations seeking a secure, standards-compliant authorization server that integrates cleanly with their existing identity infrastructure and scales with their application architecture. Enter section select mode [Next\ \ How to Connect](https://docs.elest.io/books/hydra/chapter/how-to-connect) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=22#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Restricting Access by IP\ \ Keycloak Cluster Management\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the most effective ways to reduce unauthorized access is by restricting connectivity to a defined set of IP addresses. Elestio supports IP-based access control through i...](https://docs.elest.io/books/keycloak/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ Keycloak Cluster Management\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that services behave reliably and that data remains accurate across the cluster. Elestio provides built-in mechanisms to detect and resolve inconsistencies across node...](https://docs.elest.io/books/keycloak/page/cluster-resynchronization) [#### Deleting a Cluster\ \ Keycloak Cluster Management\ \ When a cluster is no longer needed—whether it was created for testing, staging, or an obsolete workload—deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire cluste...](https://docs.elest.io/books/keycloak/page/deleting-a-cluster) [#### Exporting and Importing Realms\ \ Keycloak Realm & Configuration Migration\ \ Elestio enables seamless migration of Keycloak realms by supporting realm exports and imports. This capability is vital for backing up configurations, replicating environments, or transitioning between staging and production systems. The process ensures consis...](https://docs.elest.io/books/keycloak/page/exporting-and-importing-realms) [#### Migrating from Another IAM Provider to Keycloak\ \ Keycloak Realm & Configuration Migration\ \ Migrating to Keycloak from other IAM platforms such as Auth0, Okta, Firebase Auth, or custom-built identity solutions requires careful preparation, structured data transformation, and secure reconfiguration of users, applications, and federation protocols. Thi...](https://docs.elest.io/books/keycloak/page/migrating-from-another-iam-provider-to-keycloak) [#### Cloning a Realm to a New Cluster or Region\ \ Keycloak Realm & Configuration Migration\ \ In scenarios where high availability, regional redundancy, or environment separation (e.g., staging to production) is required, cloning an entire Keycloak realm to a new cluster or region becomes essential. This process involves exporting the realm’s configura...](https://docs.elest.io/books/keycloak/page/cloning-a-realm-to-a-new-cluster-or-region) [#### Connecting with Node.js\ \ Keycloak How to Connect\ \ This guide explains how to establish a secure connection between a Node.js application and a Keycloak identity provider using the keycloak-connect middleware. It walks through the necessary setup, configuration, and usage of a protected route that requires aut...](https://docs.elest.io/books/keycloak/page/connecting-with-nodejs) [#### Connecting with Python\ \ Keycloak How to Connect\ \ This guide explains how to establish a connection between a Python Flask application and a Keycloak identity provider using Flask-OIDC. It walks through the necessary setup, configuration, and usage of a protected route that requires authentication. Variables...](https://docs.elest.io/books/keycloak/page/connecting-with-python) [#### Connecting with PHP\ \ Keycloak How to Connect\ \ This guide explains how to establish a connection between a PHP application and a Keycloak identity provider using the jumbojett/openid-connect-php library. It walks through the necessary setup, configuration, and execution of a protected login route using Ope...](https://docs.elest.io/books/keycloak/page/connecting-with-php) [#### Connecting with Go\ \ Keycloak How to Connect\ \ This guide explains how to establish a connection between a Go application and a Keycloak identity provider using the OIDC (OpenID Connect) protocol. It walks through the necessary setup, configuration, and execution of a basic login flow to authenticate users...](https://docs.elest.io/books/keycloak/page/connecting-with-go) [#### Connecting with Java\ \ Keycloak How to Connect\ \ This guide explains how to establish a connection between a Java Spring Boot application and a Keycloak identity provider using the OAuth2 resource server configuration. It walks through the necessary setup, configuration, and creation of a protected endpoint ...](https://docs.elest.io/books/keycloak/page/connecting-with-java) [#### Connecting with Frontend Applications\ \ Keycloak How to Connect\ \ This guide explains how to establish a connection between a frontend single-page application (SPA) — such as those built with React, Vue, or Angular and a Keycloak identity provider using the official Keycloak JavaScript adapter. It walks through the necessary...](https://docs.elest.io/books/keycloak/page/connecting-with-frontend-applications) [#### Connecting with Keycloak Admin Rest API\ \ Keycloak How to Connect\ \ This guide explains how to authenticate with and use the Keycloak Admin REST API from a backend application. It walks through the necessary setup, authentication flow, and execution of a sample API request to list users in a realm. Variables Certain paramete...](https://docs.elest.io/books/keycloak/page/connecting-with-keycloak-admin-rest-api) [#### Connecting External Identity Providers\ \ Keycloak How to Connect\ \ This guide explains how to integrate external identity providers (IdPs) like Google, GitHub, Facebook, or LDAP/Active Directory into a Keycloak realm. It walks through the necessary setup, configuration, and execution of a login flow that delegates authenticat...](https://docs.elest.io/books/keycloak/page/connecting-external-identity-providers) [#### Creating a Realm in Keycloak\ \ Keycloak How-To Guides\ \ A realm in Keycloak is the top-level container for managing users, roles, groups, identity providers, and applications. It provides complete logical isolation, making it ideal for multi-tenant systems or staging/production splits. This guide explains different...](https://docs.elest.io/books/keycloak/page/creating-a-realm-in-keycloak) [#### Adding and Managing Users in Keycloak\ \ Keycloak How-To Guides\ \ Users in Keycloak represent the individuals or system accounts that authenticate and interact with your applications. This guide explains multiple methods to create and manage users via the Admin Console, REST API, and Docker CLI while covering required roles,...](https://docs.elest.io/books/keycloak/page/adding-and-managing-users-in-keycloak) [#### Creating and Configuring Clients in Keycloak\ \ Keycloak How-To Guides\ \ A client in Keycloak represents an application or service that uses Keycloak to authenticate users. Clients can be web apps, REST APIs, mobile apps, or even CLI tools. This guide explains how to create and configure clients through the Admin Console, REST API,...](https://docs.elest.io/books/keycloak/page/creating-and-configuring-clients-in-keycloak) [#### Setting Up Roles and Permissions in Keycloak\ \ Keycloak How-To Guides\ \ Roles and permissions in Keycloak define what users and applications are allowed to do. Roles can be assigned to users, groups, or clients, and are embedded into access tokens to enforce authorization. This guide explains how to define and manage roles via the...](https://docs.elest.io/books/keycloak/page/setting-up-roles-and-permissions-in-keycloak) [#### Enabling Identity Federation in Keycloak\ \ Keycloak How-To Guides\ \ Identity federation allows you to delegate authentication to external identity providers (IdPs) like Google, GitHub, Facebook, or enterprise systems such as LDAP and Active Directory. This guide explains how to integrate identity providers using the Keycloak A...](https://docs.elest.io/books/keycloak/page/enabling-identity-federation-in-keycloak) [#### Enabling Two-Factor Authentication (2FA) in Keycloak\ \ Keycloak How-To Guides\ \ Two-Factor Authentication (2FA) adds an extra layer of security to user logins by requiring something the user knows (password) and something they have (typically an OTP via a mobile app). This guide explains how to enable and enforce OTP-based 2FA for all or ...](https://docs.elest.io/books/keycloak/page/enabling-two-factor-authentication-2fa-in-keycloak) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=20#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Creating Manual Backups\ \ Redis How-To Guides\ \ Regular backups are essential when running a Redis deployment especially if you’re using it for persistent data. While Elestio handles automated backups by default, you may want to create manual backups before configuration changes, retain a local archive, or ...](https://docs.elest.io/books/redis/page/creating-manual-backups) [#### Restoring a Backup\ \ Redis How-To Guides\ \ Restoring Redis backups is essential for disaster recovery, staging environment duplication, or rolling back to a known state. Elestio supports backup restoration both through its web dashboard and manually through Docker Compose and command-line methods. This...](https://docs.elest.io/books/redis/page/restoring-a-backup) [#### Identifying Slow Queries\ \ Redis How-To Guides\ \ Slow commands can impact Redis performance, especially under high load or when poorly optimized operations are used. Whether you’re using Redis on Elestio through the dashboard, accessing it inside a Docker Compose container, or connecting via CLI tools, Redis...](https://docs.elest.io/books/redis/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ Redis How-To Guides\ \ Long-running commands in Redis can block the single-threaded event loop, causing delayed responses or complete unresponsiveness in production environments like Elestio. Monitoring and handling these commands is critical for maintaining performance and reliabil...](https://docs.elest.io/books/redis/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ Redis How-To Guides\ \ Running out of disk space in a Redis environment can lead to failed writes, snapshot errors, and service unavailability. Redis relies on disk storage for persistence (RDB and AOF files), temporary dumps, and logs especially when persistence is enabled. On plat...](https://docs.elest.io/books/redis/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ Redis How-To Guides\ \ As your Redis data grows especially when using persistence modes like RDB or AOF it’s important to track how storage is being used. Unchecked growth can lead to full disks, failed writes, longer startup times, and backup complications. While Elestio handles th...](https://docs.elest.io/books/redis/page/checking-database-size-and-related-issues) [#### Bandwidth Billing\ \ Billing\ \ At Elestio, we're committed to transparency and simplicity when it comes to billing. One area where we often receive questions is bandwidth usage, especially what happens after your allocated free bandwidth is exceeded. This post will walk you through how band...](https://docs.elest.io/books/billing/page/bandwidth-billing) [#### Overview\ \ ClickHouse\ \ ClickHouse is an open-source columnar database management system designed for online analytical processing (OLAP). It enables fast processing of large volumes of data by storing data by columns instead of rows, making it highly efficient for analytical queries...](https://docs.elest.io/books/clickhouse/page/overview) [#### Overview\ \ ClickHouse Cluster Management\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the sys...](https://docs.elest.io/books/clickhouse/page/overview-Ys0) [#### Deploying a New Cluster\ \ ClickHouse Cluster Management\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide isolated environments where you can run containerized workloads, databases, and applications. Elestio’s web dashboard helps the process, allowing you to configure ...](https://docs.elest.io/books/clickhouse/page/deploying-a-new-cluster) [#### Node Management\ \ ClickHouse Cluster Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining st...](https://docs.elest.io/books/clickhouse/page/node-management) [#### Adding a Node\ \ ClickHouse Cluster Management\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, im...](https://docs.elest.io/books/clickhouse/page/adding-a-node) [#### Promoting a Node\ \ ClickHouse Cluster Management\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. ...](https://docs.elest.io/books/clickhouse/page/promoting-a-node) [#### Removing a Node\ \ ClickHouse Cluster Management\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structure...](https://docs.elest.io/books/clickhouse/page/removing-a-node) [#### Backups and Restores\ \ ClickHouse Cluster Management\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastruc...](https://docs.elest.io/books/clickhouse/page/backups-and-restores) [#### Cluster Resynchronization\ \ ClickHouse Cluster Management\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that services behave reliably and that data remains accurate across the cluster. Elestio provides built-in mechanisms to detect and resolve inconsistencies across node...](https://docs.elest.io/books/clickhouse/page/cluster-resynchronization) [#### Database Migration\ \ ClickHouse Cluster Management\ \ When managing production-grade services, the ability to perform reliable and repeatable database migrations is critical. Whether you’re applying schema changes, updating seed data, or managing version-controlled transitions, Elestio provides a built-in mechani...](https://docs.elest.io/books/clickhouse/page/database-migration) [#### Delete a Cluster\ \ ClickHouse Cluster Management\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete workload deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire cluste...](https://docs.elest.io/books/clickhouse/page/delete-a-cluster) [#### Restricting Access by IP\ \ ClickHouse Cluster Management\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the most effective ways to reduce unauthorized access is by restricting connectivity to a defined set of IP addresses. Elestio supports IP-based access control through i...](https://docs.elest.io/books/clickhouse/page/restricting-access-by-ip) [#### Cloning a Service to Another Provider or Region\ \ ClickHouse Database Migration\ \ Migrating or cloning ClickHouse across cloud providers or geographic regions is essential for optimizing performance, meeting compliance requirements, or ensuring high availability. ClickHouse, being a distributed columnar OLAP database, introduces some unique...](https://docs.elest.io/books/clickhouse/page/cloning-a-service-to-another-provider-or-region) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=21#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Database Migration Services for ClickHouse\ \ ClickHouse Database Migration\ \ Elestio provides a easy and reliable approach for migrating ClickHouse instances from various environments such as on-premises servers, self-managed cloud deployments, or other managed services into its fully managed ClickHouse platform. This migration process...](https://docs.elest.io/books/clickhouse/page/database-migration-services-for-clickhouse) [#### Manual ClickHouse Migration Using clickhouse-backup\ \ ClickHouse Database Migration\ \ Manual migrations using ClickHouse’s native tools, such as clickhouse-client, clickhouse-backup, and SQL dump files, are ideal for users who require full control over data export and import, particularly during transitions between providers, ClickHouse version...](https://docs.elest.io/books/clickhouse/page/manual-clickhouse-migration-using-clickhouse-backup) [#### Creating a Database\ \ ClickHouse How-To Guides\ \ ClickHouse is a high-performance columnar database designed for real-time analytical processing. It’s known for its blazing speed, horizontal scalability, and efficient use of disk I/O. Proper setup is essential for taking advantage of ClickHouse’s full capabi...](https://docs.elest.io/books/clickhouse/page/creating-a-database) [#### Upgrading to Major Version\ \ ClickHouse How-To Guides\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing a full manual migration. Elestio provides a built-in option to change the database version directly from the dashboard. This is useful for cases where the upgrade...](https://docs.elest.io/books/clickhouse/page/upgrading-to-major-version) [#### Installing and Updating an Extension\ \ ClickHouse How-To Guides\ \ ClickHouse supports custom extensions via \[User Defined Functions (UDFs)\], external dictionaries, and shared libraries that extend its core capabilities with custom logic, formats, or integrations. These behave similarly to modules or plugins in other systems ...](https://docs.elest.io/books/clickhouse/page/installing-and-updating-an-extension) [#### Creating Manual Backups\ \ ClickHouse How-To Guides\ \ Regular backups are essential when running a ClickHouse deployment, especially if you’re using it for persistent analytics or time-series data. While Elestio handles automated backups by default, you may want to create manual backups before configuration chang...](https://docs.elest.io/books/clickhouse/page/creating-manual-backups) [#### Restoring a Backup\ \ ClickHouse How-To Guides\ \ Restoring ClickHouse backups is essential for disaster recovery, staging environment duplication, or rolling back to a known state. Elestio supports backup restoration both through its web dashboard and manually through Docker Compose and command-line methods....](https://docs.elest.io/books/clickhouse/page/restoring-a-backup) [#### Identifying Slow Queries\ \ ClickHouse How-To Guides\ \ Slow queries can impact ClickHouse performance, especially under high load or with inefficient queries or schema design. Whether you’re using ClickHouse on Elestio via the dashboard, accessing it inside a Docker Compose container, or running CLI queries, Click...](https://docs.elest.io/books/clickhouse/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ ClickHouse How-To Guides\ \ ClickHouse is a high-performance, column-oriented OLAP database, but poorly optimized or long-running queries can still impact performance especially in resource-constrained environments like Elestio. Because ClickHouse executes large queries across multiple t...](https://docs.elest.io/books/clickhouse/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk Issues\ \ ClickHouse How-To Guides\ \ Running out of disk space in a ClickHouse environment can cause query failures, part merge errors, and even full service downtime. ClickHouse is highly dependent on disk for storing columnar data, part files, metadata, temporary sort buffers, and backups. On p...](https://docs.elest.io/books/clickhouse/page/preventing-full-disk-issues) [#### Checking Database Size and Related Issues\ \ ClickHouse How-To Guides\ \ As your ClickHouse data grows especially with large analytical workloads or high-ingestion pipelines it’s important to track how storage is being used. Unchecked growth can lead to full disks, failed inserts, increased merge times, and slower queries. While El...](https://docs.elest.io/books/clickhouse/page/checking-database-size-and-related-issues) [#### Connecting with ClickHouse GUI\ \ ClickHouse How to Connect\ \ Tabix is a lightweight browser-based GUI for ClickHouse that lets you browse tables, write queries, and manage your ClickHouse instance using a preconfigured admin dashboard provided by Elestio. Variables To connect using Tabix, you’ll need the following log...](https://docs.elest.io/books/clickhouse/page/connecting-with-clickhouse-gui) [#### Overview\ \ Keycloak\ \ Keycloak is an open-source identity and access management (IAM) solution aimed at modern applications and services. It provides features such as single sign-on (SSO), user federation, identity brokering, and social login. Designed for flexibility and scalabili...](https://docs.elest.io/books/keycloak/page/overview) [#### Overview\ \ Keycloak Cluster Management\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the sys...](https://docs.elest.io/books/keycloak/page/overview-VG3) [#### Deploying a New Cluster\ \ Keycloak Cluster Management\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide isolated environments where you can run containerized workloads, databases, and applications. Elestio’s web dashboard helps the process, allowing you to configure co...](https://docs.elest.io/books/keycloak/page/deploying-a-new-cluster) [#### Node Management\ \ Keycloak Cluster Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining st...](https://docs.elest.io/books/keycloak/page/node-management) [#### Adding a Node\ \ Keycloak Cluster Management\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, im...](https://docs.elest.io/books/keycloak/page/adding-a-node) [#### Promoting a Node\ \ Keycloak Cluster Management\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. ...](https://docs.elest.io/books/keycloak/page/promoting-a-node) [#### Removing a Node\ \ Keycloak Cluster Management\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structure...](https://docs.elest.io/books/keycloak/page/removing-a-node) [#### Backups and Restores\ \ Keycloak Cluster Management\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastruc...](https://docs.elest.io/books/keycloak/page/backups-and-restores) Back to top --- # Identifying Slow Queries | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/identifying-slow-queries#main-content) Info Content Identifying Slow Queries ======================== Slow queries can significantly affect application performance and user experience. Hydra offers built-in tools to analyze and identify these slow operations. On Elestio, whether you’re connected via terminal, inside a Docker Compose container, or using Hydra CLI tools, you can use several methods to pinpoint and fix performance issues. This guide walks through various techniques to identify slow queries, interpret execution plans, and apply optimizations. **Analyzing Slow Queries Using Terminal** ----------------------------------------- When connected to your Hydra service via terminal, you can use built-in tools like psql and SQL functions to observe how queries behave. This method is useful for immediate, ad hoc diagnostics in production or staging environments. You can use simple commands to view currently running queries, analyze individual query plans, and measure runtime performance. These steps help determine which queries are taking the most time and why. Use psql to connect directly to your Hydra instance. This provides access to administrative and diagnostic SQL commands. psql -U -h -d Now use the following command to show the query plan the database will use. It highlights whether Hydra will perform a sequential scan, index scan, or other operation. EXPLAIN SELECT * FROM orders WHERE customer_id = 42; Another type of command that executes the query and returns actual runtime and row counts. Comparing planned and actual rows helps determine if the planner is misestimating costs. EXPLAIN ANALYZE SELECT * FROM orders WHERE customer_id = 42; Lastly, monitor queries in real time using the following command. This view lists all active queries, sorted by duration. It helps you identify queries that are taking too long and might need optimization. SELECT pid, now() - query_start AS duration, query FROM pg_stat_activity WHERE state = 'active' ORDER BY duration DESC; **Analyzing Slow Queries in Docker Compose Environments** --------------------------------------------------------- If your Hydra is deployed using Docker Compose on Elestio, you can inspect and troubleshoot slow queries from within the container. This method is useful when the Hydra instance is isolated inside a container and not accessible directly from the host. Logs and query data can be collected from inside the service container using Hydra tools or by checking configuration files. docker-compose exec hydra bash This command opens a shell inside the running Hydra container. From here, you can run commands like psql or view logs. Use the same psql interface from inside the container to interact with the database and execute analysis commands. psql -U $HYDRA_USER -d $HYDRA_DB Next, edit hydra.conf inside the container to enable slow query logging: log_min_duration_statement = 500 log_statement = 'none' This setting logs all queries that take longer than 500 milliseconds. You may need to restart the container for these settings to take effect. **Using CLI Tools to Analyze Query Performance** ------------------------------------------------ PostgreSQL offers CLI-based tools and extensions like pg\_stat\_statements for long-term query performance analysis. These tools provide aggregated metrics over time, helping you spot frequently executed but inefficient queries. This section shows how to use Hydra extensions and views to collect detailed statistics. CREATE EXTENSION IF NOT EXISTS pg_stat_statements; This extension logs each executed query along with performance metrics such as execution time and row count. The next command shows the queries that have consumed the most total execution time. These are strong candidates for indexing or rewriting. SELECT query, calls, total_time, mean_time, rows FROM pg_stat_statements ORDER BY total_time DESC LIMIT 10; **Understanding Execution Plans and Metrics** --------------------------------------------- Hydra/ PostgreSQL’s query planner produces execution plans that describe how a query will be executed. Reading these plans can help identify operations that slow down performance, such as full table scans or repeated joins. Comparing estimated and actual rows processed can also reveal outdated statistics or inefficient filters. Understanding these elements is key to choosing the right optimization strategy. #### **Key elements to understand:** * **Seq Scan**: A full table scan; slow on large tables unless indexed. * **Index Scan**: Uses an index for fast lookup; typically faster than a sequential scan. * **Cost**: Estimated cost of the query, used by the planner to decide the best execution path. * **Rows**: Estimated vs. actual rows; large mismatches indicate bad planning or outdated stats. * **Execution Time**: Total time it took to run the query; from `EXPLAIN ANALYZE`. Use these metrics to compare how the query was expected to run versus how it actually performed. **Optimizing Queries for Better Performance** --------------------------------------------- Once you’ve identified slow queries, the next step is to optimize them. Optimizations may involve adding indexes, rewriting SQL statements, or updating statistics. The goal is to reduce scan times, avoid redundant operations, and guide the planner to more efficient execution paths. Performance tuning is iterative—test after each change. #### **Common optimization steps:** * **Add indexes** to columns used in WHERE, JOIN, and ORDER BY clauses. * **Use EXPLAIN ANALYZE** before and after changes to measure impact. * **Avoid SELECT \*** to reduce data transfer and memory use. * **Use LIMIT** to restrict row output when only a subset is needed. * **Run ANALYZE** to update Hydra's internal statistics and improve planner accuracy: ANALYZE; By focusing on frequent and long-running queries, you can make improvements that significantly reduce overall load on the database. Enter section select mode [Previous\ \ Restoring a Backup](https://docs.elest.io/books/hydra/page/restoring-a-backup) [Next\ \ Detect and terminate long-running queries](https://docs.elest.io/books/hydra/page/detect-and-terminate-long-running-queries) Back to top --- # Preventing Full Disk I... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/preventing-full-disk-issues#main-content) Info Content Preventing Full Disk Issues =========================== Running out of disk space in a database environment can lead to failed writes, service downtime, and even data corruption. Hydra systems require available space not only for storing data but also for managing temporary files, WAL logs, indexes, and routine background tasks. On Elestio, while infrastructure is managed, you are still responsible for monitoring growth and preventing overuse. This guide outlines how to monitor disk usage, configure alerts, automate cleanup, and follow best practices to avoid full disk conditions in Hydra. **Monitoring Disk Usage** ------------------------- Proactively monitoring disk usage helps you detect unusual growth in time to act. Whether you’re accessing your database directly via the terminal or through a Docker Compose environment, several built-in tools can provide usage stats and trends. Combining filesystem-level monitoring with Hydra-specific checks gives a complete view of space utilization To check the overall disk usage of the system from a terminal or container: df -h This command shows available space for each mounted volume. Focus on the mount point where your Hydra data directory is stored, usually `/var/lib/postgresql`. For detailed Hydra-specific usage, connect to your database and run: SELECT pg_size_pretty(pg_database_size(current_database())); This shows the total size used by the active database. You can also analyze individual tables and indexes using: SELECT relname AS object, pg_size_pretty(pg_total_relation_size(relid)) AS size FROM pg_catalog.pg_statio_user_tables ORDER BY pg_total_relation_size(relid) DESC LIMIT 10; This query highlights the largest tables by size, helping you identify which parts of your schema consume the most space. **Configuring Alerts and Cleanup** ---------------------------------- Even with monitoring in place, automatic alerts and cleanup scripts ensure you act before hitting disk limits. You can set up external monitoring agents or run container-level scripts to track disk usage and notify you. If you’re using Docker Compose, you can monitor container-level storage stats using: docker system df This command provides an overview of Docker volumes, images, and container usage. To monitor and clean unused volumes and logs manually: docker volume ls docker volume rm Make sure you’re not deleting active database volumes. Always verify that backups exist and are up-to-date before running cleanup commands. To configure Hydra-specific cleanup, enable auto-vacuum and monitor its effectiveness. Hydra removes dead tuples and reclaims space using this process. Check the vacuum activity with: SELECT relname, n_dead_tup, last_vacuum, last_autovacuum FROM pg_stat_user_tables ORDER BY n_dead_tup DESC; If dead tuples accumulate, increase autovacuum frequency or run a manual vacuum: VACUUM ANALYZE; Autovacuum settings can also be tuned in hydra.conf to trigger more aggressively based on table activity. **Best Practices for Disk Space Management** -------------------------------------------- * Beyond immediate cleanup, long-term strategies help keep disk usage under control. These include data retention policies, partitioning, compression, and regular maintenance. It’s also important to have a growth plan based on usage trends. * Avoid storing large binary objects like images or PDFs directly in the database. Use object storage for large files and reference them by URL. If historical data is no longer needed for queries, archive it into a separate cold-storage database or export to files. * Partition large tables by time or ID ranges to manage growth and make pruning easier. Use tools like `pg_partman` native Hydra table partitioning to automatically offload older data * Regularly rotate and clean up Hydra logs and WAL files. If using archive mode, ensure archived WALs are uploaded and removed from disk after successful backup. * To keep your setup safe, also monitor backup file sizes and locations. Backups stored on the same volume as the database may consume critical space. If possible, push backups to remote object storage or another disk volume. Enter section select mode [Previous\ \ Detect and terminate long-running queries](https://docs.elest.io/books/hydra/page/detect-and-terminate-long-running-queries) [Next\ \ Checking Database Size and Related Issues](https://docs.elest.io/books/hydra/page/checking-database-size-and-related-issues) Back to top --- # Checking Database Size... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/checking-database-size-and-related-issues#main-content) Info Content Checking Database Size and Related Issues ========================================= As your Hydra database grows over time, it’s important to monitor its size and identify what parts of the database consume the most space. Unmanaged growth can lead to performance issues, disk exhaustion, and backup delays. On Elestio, where Hydra is hosted in a managed environment, you can use SQL and command-line tools to measure database usage, analyze large objects, and troubleshoot storage problems. This guide explains how to check database size, detect bloated tables and indexes, and optimize storage usage efficiently. **Checking Database and Table Sizes** ------------------------------------- Hydra provides built-in functions to report the size of the current database, its individual schemas, tables, and indexes. These functions are useful for understanding where most of your storage is being used and planning cleanup or archiving strategies. To check the total size of the active database: SELECT pg_size_pretty(pg_database_size(current_database())); This returns a human-readable value like “2 GB”, indicating how much space the entire database consumes on disk. To list the largest tables in your schema: SELECT relname AS table, pg_size_pretty(pg_total_relation_size(relid)) AS total_size FROM pg_catalog.pg_statio_user_tables ORDER BY pg_total_relation_size(relid) DESC LIMIT 10; This helps you identify which tables take up the most space, including indexes and TOAST (large field) data. To break down table vs index size separately: SELECT relname AS object, pg_size_pretty(pg_relation_size(relid)) AS table_size, pg_size_pretty(pg_indexes_size(relid)) AS index_size FROM pg_catalog.pg_statio_user_tables ORDER BY pg_relation_size(relid) DESC LIMIT 10; This distinction allows you to assess whether most space is used by raw table data or indexes, which can inform optimization decisions. **Identifying Bloat and Inefficiencies** ---------------------------------------- Database bloat occurs when Hydra retains outdated or deleted rows due to its MVCC model. This is common in high-write tables and can lead to wasted space and degraded performance. Bloated indexes and tables are often invisible unless explicitly checked. To estimate bloat at a table level, you can use a community query like this: SELECT schemaname, relname, round(100 * (pg_total_relation_size(relid) - pg_relation_size(relid)) / pg_total_relation_size(relid), 2) AS bloat_pct FROM pg_catalog.pg_statio_user_tables ORDER BY bloat_pct DESC LIMIT 10; This query calculates how much of a table’s total size is not accounted for by its base data—higher percentages suggest unused or dead space. You can also check dead tuples directly: SELECT relname, n_dead_tup FROM pg_stat_user_tables ORDER BY n_dead_tup DESC LIMIT 10; A high count of dead tuples suggests that autovacuum might not be keeping up and that a manual VACUUM could help. **Optimizing and Reducing Database Size** ----------------------------------------- Once you’ve identified large or bloated objects, the next step is to optimize them. Hydra offers tools like VACUUM, REINDEX, and CLUSTER to reclaim space and improve storage efficiency. These commands must be run with care to avoid locking critical tables during active hours. To reclaim dead tuples and update statistics: VACUUM ANALYZE; This command removes dead rows and refreshes query planning statistics, which helps performance and frees up storage. To shrink large indexes that aren’t cleaned automatically, use: REINDEX TABLE ; This recreates the table’s indexes from scratch and can free up disk space if indexes are fragmented or bloated. If a table is heavily bloated and full table rewrites are acceptable during maintenance, use: CLUSTER ; This rewrites the entire table based on an index order and reclaims space similar to VACUUM FULL, but with more control. Additionally, removing or archiving old data from large time-based tables can reduce total size. Consider partitioning large tables to manage this process more efficiently. Enter section select mode [Previous\ \ Preventing Full Disk Issues](https://docs.elest.io/books/hydra/page/preventing-full-disk-issues) [Next\ \ Database Migration](https://docs.elest.io/books/hydra/chapter/database-migration) Back to top --- # Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/overview-NsK#main-content) Info Content Overview ======== Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the system fails. Elestio supports different cluster setups to handle various technical needs like load balancing, failover, and data replication. #### **Supported Software for Clustering:** Elestio supports clustering for a wide range of open-source software. Each is designed to support different use cases like databases, caching, and analytics: * **MySQL**: Supports Single Node, Primary/Replica, and Multi-Master cluster types. These allow users to create simple setups or more advanced ones where reads and writes are distributed across nodes. In a Primary/Replica setup, replicas are updated continuously through replication. These configurations are useful for high-traffic applications that need fast and reliable access to data. * **PostgreSQL**: PostgreSQL clusters can be configured for read scalability and failover protection. Replication ensures that data written to the primary node is copied to replicas. Clustering PostgreSQL also improves query throughput by offloading read queries to replicas. Elestio handles replication setup and node failover automatically. * **Redis/KeyDB/Valkey**: These in-memory data stores support clustering to improve speed and fault tolerance. Clustering divides data across multiple nodes (sharding), allowing horizontal scaling. These tools are commonly used for caching and real-time applications, so fast failover and data availability are critical. * **Hydra and TimescaleDB**: These support distributed and time-series workloads, respectively. Clustering helps manage large datasets spread across many nodes. TimescaleDB, built on PostgreSQL, benefits from clustering by distributing time-based data for fast querying. Hydra uses clustering to process identity and access management workloads more efficiently in high-load environments. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/image.png)](https://docs.elest.io/uploads/images/gallery/2025-05/image.png) **Note**: Elestio is frequently adding support for more clustered software like OpenSearch, Kafka, and ClickHouse. Always check the Elestio catalogue for the latest supported services. #### **Cluster Configurations:** Elestio offers several clustering modes, each designed for a different balance between simplicity, speed, and reliability: * **Single Node**: This setup has only one node and is easy to manage. It acts as a standalone Primary node. It’s good for testing, development, or low-traffic applications. Later, you can scale to more nodes without rebuilding the entire setup. Elestio lets you expand this node into a full cluster with just a few clicks. * **Primary/Replica**: One node (Primary) handles all write operations, and one or more Replicas handle read queries. Replication is usually asynchronous and ensures data is copied to all replicas. This improves read performance and provides redundancy if the primary node fails. Elestio manages automatic data syncing and failover setup. #### **Cluster Management Features:** Elestio’s cluster dashboard includes tools for managing, monitoring, and securing your clusters. These help ensure stability and ease of use: * **Node Management**: You can scale your cluster by adding or removing nodes as your app grows. Adding a node increases capacity; removing one helps reduce costs. Elestio handles provisioning and configuring nodes automatically, including replication setup. This makes it easier to scale horizontally without downtime. * **Backups and Restores**: Elestio provides scheduled and on-demand backups for all nodes. Backups are stored securely and can be restored if something goes wrong. You can also create a snapshot before major changes to your system. This helps protect against data loss due to failures, bugs, or human error. * **Access Control**: You can limit access to your cluster using IP allowlists, ensuring only trusted sources can connect. Role-based access control (RBAC) can be applied for managing different user permissions. SSH and database passwords are generated securely and can be rotated easily from the dashboard. These access tools help reduce the risk of unauthorized access. * **Monitoring and Alerts**: Real-time metrics like CPU, memory, disk usage, and network traffic are available through the dashboard. You can also check logs for troubleshooting and set alerts for high resource usage or failure events. Elestio uses built-in observability tools to monitor the health of your cluster and notify you if something needs attention. This allows you to catch problems early and take action. Enter section select mode [Previous\ \ Cluster Management](https://docs.elest.io/books/hydra/chapter/cluster-management) [Next\ \ Deploying a New Cluster](https://docs.elest.io/books/hydra/page/deploying-a-new-cluster) Back to top --- # Adding a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/adding-a-node#main-content) Info Content Adding a Node ============= As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, improve availability, and distribute workloads more effectively.  **Need to Add a Node** ---------------------- There are several scenarios where adding a node becomes necessary. One of the most common cases is **resource saturation** when existing nodes are fully utilized in terms of CPU, memory, or disk. Adding another node helps distribute the workload and maintain performance under load. In clusters that run **stateful services** or require **high availability**, having additional nodes ensures that workloads can fail over without downtime. Even in development environments, nodes can be added to isolate environments or test services under production-like load conditions. Scaling out also gives you flexibility when deploying services with different resource profiles or placement requirements. **Add a Node to Cluster** ------------------------- To begin, log in to the [Elestio dashboard](https://dash.elest.io/)  and navigate to the **Clusters** section from the sidebar. Select the cluster you want to scale. Once inside the cluster view, switch to the **Nodes** tab. This section provides an overview of all current nodes along with their health status and real-time resource usage. [![Screenshot 2025-05-05 at 12.42.41 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-42-41-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-42-41-pm.jpg) To add a new node, click the **“Add Node”** button. This opens a configuration panel where you can define the specifications for the new node. You’ll be asked to specify the amount of **CPU**, **memory**, and **disk** you want to allocate. If you’re using a bring-your-own-cloud setup, you may also need to confirm or choose the cloud provider and deployment region. [![Screenshot 2025-05-05 at 12.42.41 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/wnRscreenshot-2025-05-05-at-12-42-41-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/wnRscreenshot-2025-05-05-at-12-42-41-pm.jpg) After configuring the node, review the settings to ensure they meet your performance and cost requirements. Click **“Create”** to initiate provisioning. Elestio will begin setting up the new node, and once it’s ready, it will automatically join your cluster. [![Screenshot 2025-05-05 at 12.44.35 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-44-35-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-44-35-pm.jpg) Once provisioned, the new node will appear in the node list with its own metrics and status indicators. You can monitor its activity, verify that workloads are being scheduled to it, and access its logs directly from the dashboard. From this point onward, the node behaves like any other in the cluster and can be managed using the same lifecycle actions such as rebooting or draining. **Post-Provisioning Considerations** ------------------------------------ After the node has been added, it becomes part of the active cluster and is available for scheduling workloads. Elestio’s orchestration layer will begin using it automatically, but you can further customize service placement through resource constraints or affinity rules if needed. For performance monitoring, the dashboard provides per-node metrics, including CPU load, memory usage, and disk I/O. This visibility helps you confirm that the new node is functioning correctly and contributing to workload distribution as expected. Maintenance actions such as draining or rebooting the node are also available from the same interface, making it easy to manage the node lifecycle after provisioning. Enter section select mode [Previous\ \ Node Management](https://docs.elest.io/books/hydra/page/node-management) [Next\ \ Promoting a Node](https://docs.elest.io/books/hydra/page/promoting-a-node) Back to top --- # Deploying a New Cluster | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/deploying-a-new-cluster#main-content) Info Content Deploying a New Cluster ======================= Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide isolated environments where you can run containerized workloads, databases, and applications. Elestio’s web dashboard helps the process, allowing you to configure compute resources, choose cloud providers, and define deployment regions without writing infrastructure code. This guide walks through the steps required to create a new cluster using the Elestio dashboard. **Prerequisites** ----------------- To get started, you’ll need an active Elestio account. If you’re planning to use your own infrastructure, make sure you have valid credentials for your preferred cloud provider (like AWS, GCP, Azure, etc.). Alternatively, you can choose to deploy clusters using Elestio-managed infrastructure, which requires no external configuration. **Creating a Cluster** ---------------------- Once you’re logged into the Elestio dashboard, navigate to the **Clusters** section from the sidebar. You’ll see an option to **Create a new cluster**—clicking this will start the configuration process. The cluster creation flow is flexible but simple for defining essential details like provider, region, and resources in one place. [![Screenshot 2025-04-23 at 2.09.00 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-04/scaled-1680-/screenshot-2025-04-23-at-2-09-00-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-04/screenshot-2025-04-23-at-2-09-00-pm.jpg) Now, select the database service of your choice that you need to create in a cluster environment. Click on **Select** button as you choose one. [![Screenshot 2025-05-05 at 12.21.45 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-21-45-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-21-45-pm.jpg) During setup, you’ll be asked to choose a hosting provider. Elestio supports both managed and BYOC (Bring Your Own Cloud) deployments, including AWS, DigitalOcean, Hetzner, and custom configurations. You can then select a region based on latency or compliance needs, and specify the number of nodes along with CPU, RAM, and disk sizes per node. [![Screenshot 2025-05-05 at 12.22.24 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-22-24-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-22-24-pm.jpg) If you’re setting up a high-availability cluster, the dashboard also allows you to configure cluster-related details under **Cluster configuration,** where you get to select things like replication modes, number of replicas, etc. After you’ve configured the cluster, review the summary to ensure all settings are correct. Click the **Create Cluster** button to begin provisioning. [![Screenshot 2025-05-05 at 12.23.05 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-23-05-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-23-05-pm.jpg) Elestio will start the deployment process, and within a few minutes, the cluster will appear in your dashboard. Once your cluster is live, it can be used to deploy new nodes and additional configurations. Each cluster supports real-time monitoring, log access, and scaling operations through the dashboard. You can also set up automated backups and access control through built-in features available in the cluster settings. Enter section select mode [Previous\ \ Overview](https://docs.elest.io/books/hydra/page/overview-NsK) [Next\ \ Node Management](https://docs.elest.io/books/hydra/page/node-management) Back to top --- # Node Management | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/node-management#main-content) Info Content Node Management =============== Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining stability and performance.  **Understanding Nodes** ----------------------- In Elestio, a **node** is a virtual machine that contributes compute, memory, and storage resources to a cluster. Clusters can be composed of a single node or span multiple nodes, depending on workload demands and availability requirements. Each node runs essential services and containers as defined by your deployed applications or databases. Nodes in Elestio are provider-agnostic, meaning the same concepts apply whether you’re using Elestio-managed infrastructure or connecting your own cloud provider (AWS, Azure, GCP, etc.). Each node is isolated at the VM level but participates fully in the cluster’s orchestration and networking. This abstraction allows you to manage infrastructure without diving into the complexity of underlying platforms. **Node Operations** ------------------- The Elestio dashboard allows you to manage the lifecycle of nodes through clearly defined operations. These include: * **Creating a node**, which adds capacity to your cluster and helps with horizontal scaling of services. This is commonly used when load increases or when preparing a high-availability deployment. * **Deleting a node**, which removes underutilized or problematic nodes. Safe deletion includes draining workloads to ensure service continuity. * **Promoting a node**, which changes the role of a node within the cluster—typically used in clusters with redundancy, where certain nodes may need to take on primary or leader responsibilities. Each of these operations is designed to be safely executed through the dashboard and is validated against the current cluster state to avoid unintended service disruption. These actions are supported by Elestio’s backend orchestration, which handles tasks like container rescheduling and load balancing when topology changes. **Monitoring and Maintenance** ------------------------------ Monitoring is a key part of effective node management. Elestio provides per-node visibility through the dashboard, allowing you to inspect **CPU**, **memory**, and **disk utilization** in real time. Each node also exposes **logs**, **status indicators**, and **health checks** to help detect anomalies or degradation early. In addition to passive monitoring, the dashboard supports active maintenance tasks. You can **reboot a node** when applying system-level changes or troubleshooting, or **drain a node** to safely migrate workloads away from it before performing disruptive actions. Draining ensures that running containers are rescheduled on other nodes in the cluster, minimizing service impact. For production setups, combining resource monitoring with automation like scheduled reboots, log collection, and alerting can help catch issues before they affect users. While Elestio handles many aspects of orchestration automatically, having visibility at the node level helps teams make informed decisions about scaling, updates, and incident response. Cluster-wide resource graphs and node-level metrics are also useful for capacity planning. Identifying trends such as memory saturation or disk pressure allows you to preemptively scale or rebalance workloads, reducing the risk of downtime. Enter section select mode [Previous\ \ Deploying a New Cluster](https://docs.elest.io/books/hydra/page/deploying-a-new-cluster) [Next\ \ Adding a Node](https://docs.elest.io/books/hydra/page/adding-a-node) Back to top --- # Promoting a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/promoting-a-node#main-content) Info Content Promoting a Node ================ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. While not always needed in basic setups, node promotion becomes essential in distributed systems, replicated databases, or services requiring failover control. **When to Promote a Node?** --------------------------- Promoting a node is typically performed in clusters where role-based architecture is used. In high-availability setups, some nodes may act as leaders while others serve as followers or replicas. If a leader node becomes unavailable or needs to be replaced, you can promote another node to take over its responsibilities and maintain continuity of service. Node promotion is also useful when scaling out and rebalancing responsibilities across a larger cluster. For example, promoting a node to handle scheduling, state tracking, or replication leadership can reduce bottlenecks and improve responsiveness. In cases involving database clusters or consensus-driven systems, promotion ensures a clear and controlled transition of leadership without relying solely on automatic failover mechanisms. **Promote a Node in Elestio** ----------------------------- To promote a node, start by accessing the **Clusters** section in the [Elestio dashboard](https://dash.elest.io/) . Choose the cluster containing the node you want to promote. Inside the cluster view, navigate to the **Nodes** tab to see the full list of nodes, including their current roles, health status, and resource usage. Locate the node that you want to promote and open its action menu. From here, select the **“Promote Node”** option. [![Screenshot 2025-05-05 at 12.48.55 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-48-55-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-48-55-pm.jpg) You may be prompted to confirm the action, depending on the configuration and current role of the node. This confirmation helps prevent unintended role changes that could affect cluster behavior. [![Screenshot 2025-05-05 at 12.49.17 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-49-17-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-49-17-pm.jpg) Once confirmed, Elestio will initiate the promotion process. This involves reconfiguring the cluster’s internal coordination state to acknowledge the new role of the promoted node. Depending on the service architecture and the software running on the cluster, this may involve reassigning leadership, updating replication targets, or shifting service orchestration responsibilities. After promotion is complete, the node’s updated role will be reflected in the dashboard. At this point, it will begin operating with the responsibilities assigned to its new status. You can monitor its activity, inspect logs, and validate that workloads are being handled as expected. **Considerations for Promotion** -------------------------------- Before promoting a node, ensure that it meets the necessary resource requirements and is in a stable, healthy state. Promoting a node that is under high load or experiencing performance issues can lead to service degradation. It’s also important to consider replication and data synchronization, especially in clusters where stateful components like databases are in use. Promotion is a safe and reversible operation, but it should be done with awareness of your workload architecture. If your system relies on specific leader election mechanisms, promoting a node should follow the design patterns supported by those systems. Enter section select mode [Previous\ \ Adding a Node](https://docs.elest.io/books/hydra/page/adding-a-node) [Next\ \ Removing a Node](https://docs.elest.io/books/hydra/page/removing-a-node) Back to top --- # Removing a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/removing-a-node#main-content) Info Content Removing a Node =============== Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structured process designed to avoid disruption. The dashboard provides an accessible interface for performing this task while preserving workload stability. **Why Remove a Node?** ---------------------- Node removal is typically part of resource optimization or cluster reconfiguration. You might remove a node when reducing costs in a staging environment, when redistributing workloads across fewer or more efficient machines, or when phasing out a node for maintenance or retirement. Another common scenario is infrastructure rebalancing, where workloads are shifted to newer nodes with better specs or different regions. Removing an idle or underutilized node can simplify management and reduce noise in your monitoring stack. It also improves scheduling efficiency by removing unneeded targets from the orchestration engine. In high-availability clusters, node removal may be preceded by data migration or role reassignment (such as promoting a replica). Proper planning helps maintain system health while reducing reliance on unnecessary compute resources. **Remove a Node** ----------------- To begin the removal process, open the [Elestio dashboard](https://dash.elest.io/)  and navigate to the **Clusters** section. Select the cluster that contains the node you want to remove. From within the cluster view, open the **Nodes** tab to access the list of active nodes and their statuses. Find the node you want to delete from the list. If the node is currently running services, ensure that those workloads can be safely rescheduled to other nodes or are no longer needed. Since Elestio does not have a built-in drain option, any workload redistribution needs to be handled manually, either by adjusting deployments or verifying that redundant nodes are available. Once the node is drained and idle, open the action menu for that node and select **“Delete Node”**. [![Screenshot 2025-05-05 at 12.53.00 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-53-00-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-53-00-pm.jpg) The dashboard may prompt you to confirm the operation. After confirmation, Elestio will begin the decommissioning process. This includes detaching the node from the cluster, cleaning up any residual state, and terminating the associated virtual machine. [![Screenshot 2025-05-05 at 12.53.24 PM.jpg](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/screenshot-2025-05-05-at-12-53-24-pm.jpg)](https://docs.elest.io/uploads/images/gallery/2025-05/screenshot-2025-05-05-at-12-53-24-pm.jpg) Once the operation completes, the node will no longer appear in the cluster’s node list, and its resources will be released. **Considerations for Safe Node Removal** ---------------------------------------- Before removing a node in Elestio, it’s important to review the services and workloads currently running on that node. Since Elestio does not automatically redistribute or migrate workloads during node removal, you should ensure that critical services are either no longer in use or can be manually rescheduled to other nodes in the cluster. This is particularly important in multi-node environments running stateful applications, databases, or services with specific affinity rules. You should also verify that your cluster will have sufficient capacity after the node is removed. If the deleted node was handling a significant portion of traffic or compute load, removing it without replacement may lead to performance degradation or service interruption. In high-availability clusters, ensure that quorum-based components or replicas are not depending on the node targeted for deletion. Additionally, confirm that the node is not playing a special role such as holding primary data or acting as a manually promoted leader before removal. If necessary, reconfigure or promote another node prior to deletion to maintain cluster integrity. Enter section select mode [Previous\ \ Promoting a Node](https://docs.elest.io/books/hydra/page/promoting-a-node) [Next\ \ Backups and Restores](https://docs.elest.io/books/hydra/page/backups-and-restores) Back to top --- # Backups and Restores | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/backups-and-restores#main-content) Info Content Backups and Restores ==================== Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastructure failure. The platform includes an automated backup system with configurable retention policies and a straightforward restore process, all accessible from the dashboard. Whether you’re operating a production database or a test environment, understanding how backups and restores work in Elestio is critical for maintaining service reliability. **Cluster Backups** ------------------- Elestio provides multiple backup mechanisms designed to support various recovery and compliance needs. Backups are created automatically for most supported services, with consistent intervals and secure storage in managed infrastructure. These backups are performed in the background to ensure minimal performance impact and no downtime during the snapshot process. Each backup is timestamped, versioned, and stored securely with encryption. You can access your full backup history for any given service through the dashboard and select any version for restoration.  You can utilize different backup options depending on your preferences and operational requirements. Elestio supports **manual local backups** for on-demand recovery points, **automated snapshots** that capture the state of the service at fixed intervals, and **automated remote backups using Borg**, which securely stores backups on external storage volumes managed by Elestio. In addition, you can configure **automated external backups to S3-compatible storage**, allowing you to maintain full control over long-term retention and geographic storage preferences. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/PgBimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/PgBimage.png) **Restoring from a Backup** --------------------------- Restoring a backup in Elestio is a user-initiated operation, available directly from the service dashboard. Once you’re in the dashboard, select the service you’d like to restore. Navigate to the **Backups** section, where you’ll find a list of all available backups along with their creation timestamps. To initiate a restore, choose the desired backup version and click on the **“Restore”** option. You will be prompted to confirm the operation. Depending on the type of service, the restore can either overwrite the current state or recreate the service as a new instance from the selected backup. [![image.png](https://docs.elest.io/uploads/images/gallery/2025-05/scaled-1680-/pItimage.png)](https://docs.elest.io/uploads/images/gallery/2025-05/pItimage.png) The restore process takes a few minutes, depending on the size of the backup and the service type. Once completed, the restored service is immediately accessible. In the case of databases, you can validate the restore by connecting to the database and inspecting the restored data. **Considerations for Backup & Restore** --------------------------------------- * Before restoring a backup, it’s important to understand the impact on your current data. Restores may **overwrite existing service state**, so if you need to preserve the current environment, consider creating a manual backup before initiating the restore. In critical environments, restoring to a new instance and validating the data before replacing the original is a safer approach. * Keep in mind that restore operations are not instantaneous and may temporarily affect service availability. It’s best to plan restores during maintenance windows or periods of low traffic, especially in production environments. * For services with high-frequency data changes, be aware of the backup schedule and retention policy. Elestio’s default intervals may not capture every change, so for high-volume databases, consider exporting incremental backups manually or using continuous replication where supported. **Monitoring Backup Health** ---------------------------- Elestio provides visibility into your backup history directly through the dashboard. You can monitor the **status**, **timestamps**, and **success/failure** of backup jobs. In case of errors or failed backups, the dashboard will display alerts, allowing you to take corrective actions or contact support if necessary. It’s good practice to periodically verify that backups are being generated and that restore points are recent and complete. This ensures you’re prepared for unexpected failures and that recovery options remain reliable. Enter section select mode [Previous\ \ Removing a Node](https://docs.elest.io/books/hydra/page/removing-a-node) [Next\ \ Restricting Access by IP](https://docs.elest.io/books/hydra/page/restricting-access-by-ip) Back to top --- # Page Revisions for Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/overview/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/overview/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Overview (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-03 06:56:40 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/overview) Back to top --- # Page Revisions for Identifying Slow Queries | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/identifying-slow-queries/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/identifying-slow-queries/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Identifying Slow Queries (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 11:20:38 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/identifying-slow-queries) Back to top --- # Page Revisions for Preventing Full Disk I... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/preventing-full-disk-issues/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/preventing-full-disk-issues/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Preventing Full Disk Issues (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 11:02:37 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/preventing-full-disk-issues) Back to top --- # Page Revisions for Overview | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/overview-NsK/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/overview-NsK/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Overview (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 06:48:19 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/overview-NsK) Back to top --- # Page Revisions for Checking Database Size... | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/checking-database-size-and-related-issues/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/checking-database-size-and-related-issues/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Checking Database Size and Related Issues (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-08 11:17:27 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/checking-database-size-and-related-issues) Back to top --- # Page Revisions for Adding a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/adding-a-node/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/adding-a-node/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Adding a Node (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:16:10 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/adding-a-node) Back to top --- # Page Revisions for Deploying a New Cluster | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/deploying-a-new-cluster/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/deploying-a-new-cluster/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Deploying a New Cluster (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:09:32 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/deploying-a-new-cluster) Back to top --- # Page Revisions for Node Management | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/node-management/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/node-management/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Node Management (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:10:39 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/node-management) Back to top --- # Page Revisions for Removing a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/removing-a-node/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/removing-a-node/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Removing a Node (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:24:25 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/removing-a-node) Back to top --- # Page Revisions for Promoting a Node | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/promoting-a-node/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/promoting-a-node/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Promoting a Node (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:21:54 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/promoting-a-node) Back to top --- # Page Revisions for Backups and Restores | docs.elest.io [Skip to main content](https://docs.elest.io/books/hydra/page/backups-and-restores/revisions#main-content) Page Revisions ============== Listed below are all the past revisions of this page. You can look back upon, compare, and restore old page versions if permissions allow. The full history of the page may not be fully reflected here since, depending on system configuration, old revisions could be auto-deleted. Sort Revision Number * [Revision Number](https://docs.elest.io/books/hydra/page/backups-and-restores/revisions#) # Page Name / Editor Type Created By / Revision Date Changelog Actions # 1 Backups and Restores (**Editor Type:** WYSIWYG) ![kaiwalya](https://docs.elest.io/uploads/images/user/2023-10/thumbs-30-30/4rrapxebzv-avatar.png) kaiwalya 2025-05-05 07:30:48 UTC (7 months ago) Initial publish [_Current Version_](https://docs.elest.io/books/hydra/page/backups-and-restores) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=24#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Restoring a Backup\ \ KeyDB How-To Guides\ \ Restoring KeyDB backups is critical for disaster recovery, staging environment replication, or rolling back to a known good state. Elestio supports restoration via its web dashboard and manual methods using Docker Compose and command-line tools. This guide cov...](https://docs.elest.io/books/keydb/page/restoring-a-backup) [#### Identifying Slow Queries\ \ KeyDB How-To Guides\ \ Slow commands can impact KeyDB performance, especially under high concurrency or when inefficient data access patterns are used. Whether you’re running KeyDB on Elestio via the dashboard, inside a Docker Compose setup, or accessing it through the CLI, KeyDB in...](https://docs.elest.io/books/keydb/page/identifying-slow-queries) [#### Detect and terminate long-running queries\ \ KeyDB How-To Guides\ \ Optimizing memory usage in KeyDB is essential for maintaining performance, especially in production environments like Elestio. Without proper memory control, large datasets, long-lived keys, or inefficient operations can lead to high memory pressure, slowdowns...](https://docs.elest.io/books/keydb/page/detect-and-terminate-long-running-queries) [#### Preventing Full Disk\ \ KeyDB How-To Guides\ \ Running out of disk space in a KeyDB environment can result in failed writes, background save errors, and degraded availability. KeyDB, like Redis, uses disk storage for persistence (RDB and AOF), temporary files, and logs especially when persistence is enable...](https://docs.elest.io/books/keydb/page/preventing-full-disk) [#### Checking Database Size and Related Issues\ \ KeyDB How-To Guides\ \ As your KeyDB data grows especially when using persistence modes like RDB or AOF—it’s essential to monitor how disk and memory resources are consumed. Uncontrolled growth can result in full disks, write failures, longer restarts, and issues with snapshot backu...](https://docs.elest.io/books/keydb/page/checking-database-size-and-related-issues) [#### Connecting with Node.js\ \ KeyDB How to Connect\ \ This guide explains how to establish a connection between a Node.js application and a KeyDB database using the redis package. It walks through the necessary setup, configuration, and execution of a simple KeyDB command. Variables To successfully connect to a...](https://docs.elest.io/books/keydb/page/connecting-with-nodejs) [#### Connecting with Python\ \ KeyDB How to Connect\ \ This guide explains how to connect a Python application to a KeyDB database using the redis library. It walks through the required setup, configuration, and execution of a simple KeyDB command. Variables To connect to KeyDB, the following parameters are need...](https://docs.elest.io/books/keydb/page/connecting-with-python) [#### Connecting with PHP\ \ KeyDB How to Connect\ \ This guide explains how to establish a connection between a PHP application and a KeyDB database using the phpredis extension. It walks through the necessary setup, configuration, and execution of a simple KeyDB command. Variables Certain parameters must be ...](https://docs.elest.io/books/keydb/page/connecting-with-php) [#### Connecting with Go\ \ KeyDB How to Connect\ \ This guide explains how to establish a connection between a Go application and a KeyDB database using the go-redis package. It walks through the necessary setup, configuration, and execution of a simple KeyDB command. Variables Certain parameters must be pro...](https://docs.elest.io/books/keydb/page/connecting-with-go) [#### Connecting with Java\ \ KeyDB How to Connect\ \ This guide explains how to establish a connection between a Java application and a KeyDB database using the Jedis library. It walks through the necessary setup, configuration, and execution of a simple KeyDB command. Variables Certain parameters must be prov...](https://docs.elest.io/books/keydb/page/connecting-with-java) [#### Connecting with RedisInsight\ \ KeyDB How to Connect\ \ This guide explains how to establish a connection between RedisInsight and a KeyDB database instance. It walks through the necessary setup, configuration, and connection steps using the official Redis GUI. Variables Certain parameters must be provided to est...](https://docs.elest.io/books/keydb/page/connecting-with-redisinsight) [#### Connecting with keydb-cli\ \ KeyDB How to Connect\ \ This guide explains how to establish a connection between keydb-cli and a KeyDB database instance. It walks through the necessary setup, configuration, and execution of a simple KeyDB command from the terminal. Variables Certain parameters must be provided t...](https://docs.elest.io/books/keydb/page/connecting-with-keydb-cli) [#### Overview\ \ Valkey\ \ Valkey is an open-source, high-performance in-memory data store designed for building real-time, scalable applications. Fully compatible with Redis, Valkey continues the legacy of Redis OSS under a community-governed fork, ensuring long-term open development a...](https://docs.elest.io/books/valkey/page/overview) [#### Overview\ \ Valkey Cluster Management\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the sys...](https://docs.elest.io/books/valkey/page/overview-QYk) [#### Deploying a New Cluster\ \ Valkey Cluster Management\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide isolated environments where you can run containerized workloads, databases, and applications. Elestio’s web dashboard helps the process, allowing you to configure co...](https://docs.elest.io/books/valkey/page/deploying-a-new-cluster) [#### Node Management\ \ Valkey Cluster Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining st...](https://docs.elest.io/books/valkey/page/node-management) [#### Adding a Node\ \ Valkey Cluster Management\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, im...](https://docs.elest.io/books/valkey/page/adding-a-node) [#### Promoting a Node\ \ Valkey Cluster Management\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. ...](https://docs.elest.io/books/valkey/page/promoting-a-node) [#### Removing a Node\ \ Valkey Cluster Management\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structure...](https://docs.elest.io/books/valkey/page/removing-a-node) [#### Backups and Restores\ \ Valkey Cluster Management\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastruc...](https://docs.elest.io/books/valkey/page/backups-and-restores) Back to top --- # Search for | docs.elest.io [Skip to main content](https://docs.elest.io/search?page=23#main-content) ##### Advanced Search ###### Search Terms ###### Content Type Page Chapter Book Shelf ###### Exact Matches Add ###### Tag Searches Add ###### Date Options | | | | --- | --- | | Updated after | | | Set Date | | | | | | --- | --- | | Updated before | | | Set Date | | | | | | --- | --- | | Created after | | | Set Date | | | | | | --- | --- | | Created before | | | Set Date | | Update Search Search Results ============== ###### 507 total results found [#### Resetting User Passwords in KeycloakNew Page\ \ Keycloak How-To Guides\ \ Password resets are a critical part of account lifecycle management. Keycloak provides multiple secure methods for resetting a user’s password manually through the Admin Console, programmatically via REST API, or via user self-service workflows using email lin...](https://docs.elest.io/books/keycloak/page/resetting-user-passwords-in-keycloaknew-page) [#### Overview\ \ KeyDB\ \ KeyDB is an open-source, high-performance in-memory database solution designed for real-time applications. Fully compatible with Redis, it offers advanced features such as multithreading, active-active replication, and forkless background saving. Engineered fo...](https://docs.elest.io/books/keydb/page/overview) [#### Overview\ \ KeyDB Cluster Management\ \ Elestio provides a complete solution for setting up and managing software clusters. This helps users deploy, scale, and maintain applications more reliably. Clustering improves performance and ensures that services remain available, even if one part of the sys...](https://docs.elest.io/books/keydb/page/overview-QjM) [#### Deploying a New Cluster\ \ KeyDB Cluster Management\ \ Creating a cluster is a foundational step when deploying services in Elestio. Clusters provide isolated environments where you can run containerized workloads, databases, and applications. Elestio’s web dashboard helps the process, allowing you to configure co...](https://docs.elest.io/books/keydb/page/deploying-a-new-cluster) [#### Node Management\ \ KeyDB Cluster Management\ \ Node management plays a critical role in operating reliable and scalable infrastructure on Elestio. Whether you’re deploying stateless applications or stateful services like databases, managing the underlying compute units nodes is essential for maintaining st...](https://docs.elest.io/books/keydb/page/node-management) [#### Adding a Node\ \ KeyDB Cluster Management\ \ As your application usage grows or your infrastructure requirements change, scaling your cluster becomes essential. In Elestio, you can scale horizontally by adding new nodes to an existing cluster. This operation allows you to expand your compute capacity, im...](https://docs.elest.io/books/keydb/page/adding-a-node) [#### Promoting a Node\ \ KeyDB Cluster Management\ \ Clusters can be designed for high availability or role-based workloads, where certain nodes may take on leadership or coordination responsibilities. In these scenarios, promoting a node is a key administrative task. It allows you to change the role of a node. ...](https://docs.elest.io/books/keydb/page/promoting-a-node) [#### Removing a Node\ \ KeyDB Cluster Management\ \ Over time, infrastructure needs change. You may scale down a cluster after peak load, decommission outdated resources, or remove a node that is no longer needed for cost, isolation, or maintenance reasons. Removing a node from a cluster is a safe and structure...](https://docs.elest.io/books/keydb/page/removing-a-node) [#### Backups and Restores\ \ KeyDB Cluster Management\ \ Reliable backups are essential for data resilience, recovery, and business continuity. Elestio provides built-in support for managing backups across all supported services, ensuring that your data is protected against accidental loss, corruption, or infrastruc...](https://docs.elest.io/books/keydb/page/backups-and-restores) [#### Restricting Access by IP\ \ KeyDB Cluster Management\ \ Securing access to services is a fundamental part of managing cloud infrastructure. One of the most effective ways to reduce unauthorized access is by restricting connectivity to a defined set of IP addresses. Elestio supports IP-based access control through i...](https://docs.elest.io/books/keydb/page/restricting-access-by-ip) [#### Cluster Resynchronization\ \ KeyDB Cluster Management\ \ In distributed systems, consistency and synchronization between nodes are critical to ensure that services behave reliably and that data remains accurate across the cluster. Elestio provides built-in mechanisms to detect and resolve inconsistencies across node...](https://docs.elest.io/books/keydb/page/cluster-resynchronization) [#### Database Migrations\ \ KeyDB Cluster Management\ \ When managing production-grade services, the ability to perform reliable and repeatable database migrations is critical. Whether you’re applying schema changes, updating seed data, or managing version-controlled transitions, Elestio provides a built-in mechani...](https://docs.elest.io/books/keydb/page/database-migrations) [#### Deleting a Cluster\ \ KeyDB Cluster Management\ \ When a cluster is no longer needed whether it was created for testing, staging, or an obsolete workload deleting it helps free up resources and maintain a clean infrastructure footprint. Elestio provides a straightforward and secure way to delete entire cluste...](https://docs.elest.io/books/keydb/page/deleting-a-cluster) [#### Database Migration Service for KeyDB\ \ KeyDB Database Migration\ \ Elestio provides a structured approach for migrating KeyDB databases from various environments, such as self-hosted servers, on-premises infrastructure, or other cloud platforms, to its managed services. This process ensures data integrity and minimizes downti...](https://docs.elest.io/books/keydb/page/database-migration-service-for-keydb) [#### Cloning a Service to Another Provider or Region\ \ KeyDB Database Migration\ \ Migrating or cloning services across cloud providers or geographic regions is a critical part of modern infrastructure management. Whether you’re optimizing for latency, preparing for disaster recovery, meeting regulatory requirements, or simply switching prov...](https://docs.elest.io/books/keydb/page/cloning-a-service-to-another-provider-or-region) [#### Manual Migration Using keydb-cli and Dump Files\ \ KeyDB Database Migration\ \ Manual migrations using KeyDB’s native tools are ideal for users who prefer full control over data export and import, particularly during provider transitions, environment duplication, or when importing an existing self-managed KeyDB dataset into Elestio’s man...](https://docs.elest.io/books/keydb/page/manual-migration-using-keydb-cli-and-dump-files) [#### Creating a Database\ \ KeyDB How-To Guides\ \ KeyDB is a high-performance fork of Redis that offers multithreading, active-active replication, and enhanced memory management. Setting up KeyDB correctly is essential for achieving low-latency performance and ensuring durability in modern applications. This ...](https://docs.elest.io/books/keydb/page/creating-a-database) [#### Upgrading to Major Version\ \ KeyDB How-To Guides\ \ Upgrading a database service on Elestio can be done without creating a new instance or performing a full manual migration. Elestio provides a built-in option to change the database version directly from the dashboard. This is useful for cases where the upgrade...](https://docs.elest.io/books/keydb/page/upgrading-to-major-version) [#### Installing and Updating an Extension\ \ KeyDB How-To Guides\ \ KeyDB supports Redis-compatible modules to extend core database functionality with custom data types, specialized algorithms, and advanced operations. These modules are compiled as shared object (.so) files and must be loaded at server startup. Examples includ...](https://docs.elest.io/books/keydb/page/installing-and-updating-an-extension) [#### Creating Manual Backups\ \ KeyDB How-To Guides\ \ Regular backups are essential when running a KeyDB deployment, especially if you’re using it for persistent workloads. While Elestio provides automated backups for managed services by default, you may still want to create manual backups before major configurat...](https://docs.elest.io/books/keydb/page/creating-manual-backups) Back to top ---