Skip to main content
Analytics access is a normal Postgres connection: host, port, database name, username, and password. That is enough for Power BI, DBeaver, DataGrip, Azure Data Studio, or any other Postgres client.

​
Create credentials

1

Open Analytics settings

In your organization, go to Settings → Analytics. You can also open the Analytics page from the workspace sidebar.
2

Create a credential

Under Connection, create a credential. Lambda shows the password once — copy it immediately.
3

Store the password

Save it in your team’s secret store or Power BI connection settings. If you lose it, rotate the credential and update every client that used the old password.
You can create more than one credential, rotate an active one, or revoke access when someone leaves.
The password is shown only once on create or rotate. Copy connection details before you close the dialog.

​
Connection facts

Use the host, database, username, and password exactly as Lambda shows them. Prefer the replica-oriented username when Lambda provides one. Do not point reporting tools at other Lambda database endpoints.

​
Connect with a database client

1

New Postgres connection

Create a connection in your client and paste host, port 5432, database, username, and password.
2

Require TLS

Enable SSL / TLS. Connections without encryption are rejected.
3

Open reporting

Connect, then open schema reporting. Start with shipments for everyday questions.

​
Connect with Power BI

Use the PostgreSQL connector with the same host, database, username, and password. Require encryption, then load schema reporting. Full model guidance — storage modes, relationships, and publish ownership — is in Power BI.

​
What stays live

As long as the credential exists and has not been rotated or revoked:
  • the connection keeps working
  • new long-term data keeps landing in reporting
  • you do not reconnect just because the dataset updated
When you rotate or revoke a credential, update or remove that login in Power BI and every other client.

​
Common mistakes

  • Looking for an Analytics API instead of Postgres — day-to-day reporting uses the database login
  • Querying without choosing schema reporting
  • Sharing one password across many unmanaged tools — prefer one credential per team or integration, and revoke what you no longer need
  • Opening unbounded queries against cargowise_xml_observations — always filter by date (and usually by field path or label)