Skip to main content

FAQs

Can I access my database from outside the SleakOps cluster?​

Not directly. By design, all databases in SleakOps are private. This means they are only accessible from within the Kubernetes cluster or through the configured VPN for that environment.

If you need to connect an external server (e.g., a BI tool or a server in another cloud), the technical solution is VPC Peering.

  • Manual Configuration: Currently, SleakOps does not automate peering creation through the dashboard. If required, you must contact the support team to set up the network configuration securely.

Why not just make the database public? Exposing a database to the internet is a high-risk practice that we avoid for several reasons:

  1. Brute Force Attacks: If public, any bot on the internet can constantly attempt to guess your credentials.
  2. Engine Vulnerabilities: If the database engine (PostgreSQL/MySQL) has an unpatched security flaw, an attacker could exploit it directly.
  3. Data Exfiltration: A simple misconfiguration in security groups could leave your sensitive data exposed to the entire world.

What does choosing "No Production" or "Production" mean when creating a dependency?​

It's simply a default configuration template. Selecting one or the other pre-fills recommended settings for that type of environment — for example, "Production" suggests larger instances, automatic backups, Multi AZ, etc. It does not lock the dependency to a specific environment.

So if I create a PostgreSQL dependency with "No Production", can I later switch it to a Production-like config?​

Yes. Just edit the dependency after creation and adjust the settings (instance size, backups, Multi AZ, etc.) to match your production needs. No need to create a new one or migrate data manually.