Run CE near an AWS database

Run WhoDB where it can reach your AWS-hosted database. Opening the web interface and reaching the database are separate network paths, so verify each before troubleshooting credentials.

Plan the source connection#

Record the database engine, endpoint, port, database name, authentication requirements, and TLS settings. Choose the matching CE source type.

Place the CE container or binary on infrastructure with the required network route. Check security groups, routing, DNS, and any database access rules for that path. A private endpoint reachable from one VPC location may not be reachable from your laptop or another container host.

Use AWS's VPC documentation for infrastructure-specific configuration. This guide assumes the infrastructure exists; it does not provision resources.

Configure the instance#

Follow Installation for the image or binary. Persist the data directory and encryption key when sessions need to survive replacement. Supply real credentials through the deployment's secret handling rather than committing them in a Compose file.

Provide the intended browser access path, use HTTPS for remote access, and set WHODB_SECURE=true for that HTTPS deployment. If you add configured profiles, remember that everyone who can reach the CE instance can use them.

Verify the two paths#

First open WhoDB from the intended user network. Then connect to the database using its endpoint and required TLS configuration. Inspect a known object and run a small query with the planned database account.

If the page loads but the database connection times out, investigate the server-to-database route. If the database rejects authentication, check credentials and its accepted authentication method.

Discover endpoints from the CLI#

Opt-in cloud discovery is available through the local CLI. It helps find supported managed resources but does not add cloud-resource management to the CE web app. See Cloud providers for setup and limits.