AWS, Azure & HashiCorp Secret Managers

Secret managers & the credential vaultA report project should be safe to e-mail or commit to Git. ATX AnalyticsTable makes that possible by never putting a password in a project file: credentials live in an encrypted vault on the machine, or in the enterprise secret manager you already run.

What you can do

Local vault encrypted with AES-256-GCM, its master key held by Windows Credential Manager, macOS Keychain or libsecret
Enterprise secret managers as vault back-ends: AWS Secrets Manager, Azure Key Vault, Google Secret Manager and HashiCorp Vault
Connection definitions export as metadata-only bundles (safe to share) or with secrets encrypted under a passphrase
Test Connection checks reachability and credentials before a definition is saved

How to connect Secret managers & the credential vault

Out of the box, secrets go into the local vault protected by the OS keychain.
To use AWS Secrets Manager, Azure Key Vault, Google Secret Manager or HashiCorp Vault, configure it as the vault back-end.
Share connection definitions as a metadata-only bundle; each machine supplies its own credentials once.

Security and governance

Each record is encrypted with a fresh nonce and an authentication tag, so tampering is detectable
A copied vault file is inert on any other machine, because the master key stays in that machine's keychain
There is no endpoint that returns a stored secret — it can be replaced, never read back

Availability

The OS keychain vault is on every plan; enterprise secret managers are included from Corporate Advanced upwards, and on Free and Individual.

More integrations

ATX Institute on LinkedIn

This site needs JavaScript for the full experience. Every page above is reachable without it.