SigilbaseAWS Secrets Manager and KMS records, sealed as they change.
Sigilbase will collect configuration snapshots from AWS Secrets Manager and KMS into a chained, signed ledger: every change dated, every gap declared, and evidence your auditor verifies offline without an account.
AWS Secrets Manager and KMS records will arrive with the AWS connector (first wave); nothing extra is set up for AWS Secrets Manager and KMS. Until then, anything that can send JSON reaches Sigilbase through the events API today.
- Status. With the AWS connector.
- Collected by. The AWS connector.
- Category. Password managers and secrets.
What can be ingested from AWS Secrets Manager and KMS
Each stream below becomes its own sequence in the ledger, with the record kept exactly as AWS Secrets Manager and KMS gives it and a hash of those bytes beside it. Snapshots are read on a cadence and the differences between them dated.
-
Snapshot
Rotation configuration.
How it will be collected
The AWS connector will collect these records with its own; nothing extra is set up for AWS Secrets Manager and KMS.
Stream and credential names follow the vendor's documentation as read in October 2026; the connector's build confirms them.
The evidence model
What every connector and receiver ships with, whatever the source:
- A receipt per collection: what was asked for, what arrived, the cursor before and after
- A declared gap for any interval nothing covers, never a blank
- A daily settlement once late records can no longer arrive
- The raw record, byte for byte, with its hash
- An evidence bundle anyone can verify offline
What you get
-
Sealed as it arrives
Every record is hashed and chained to the one before; every few minutes the chain is sealed into a signed checkpoint. A changed, deleted or reordered record fails verification at that exact point.
-
Continuity you can show
The receipts chain too, so an auditor sees not only the records but that nothing between them went uncollected, and where a gap was, that it was declared.
-
Verified without us
An export carries the open-source verifier. It runs offline, checks the chain, the receipts and the gaps, and needs no Sigilbase account. How the service is run.
Questions about AWS Secrets Manager and KMS
-
Does Sigilbase support AWS Secrets Manager and KMS?
AWS Secrets Manager and KMS records will arrive with the AWS connector (first wave); nothing extra is set up for AWS Secrets Manager and KMS. Until then, anything that can send JSON reaches Sigilbase through the events API today. Whatever arrives is written to a chained, signed ledger whose evidence anyone can verify offline with the open-source verifier, without a Sigilbase account.
-
What AWS Secrets Manager and KMS data can Sigilbase ingest?
Snapshot: Rotation configuration.
-
How will AWS Secrets Manager and KMS evidence be collected and verified?
The AWS connector will collect these records with its own; nothing extra is set up for AWS Secrets Manager and KMS. Every collection will be receipted in the connection's own stream: what was asked for, what arrived, and the cursor before and after. An interval nothing covers will be declared as a gap, never left blank. Exports carry the standalone verifier, which checks the chain, the receipts and the gaps offline.
Start recording provable history
Chained, sealed, independently verifiable audit logs, from the first event. Free while Sigilbase is in beta.
Questions first? Write to hello@sigilbase.io.