Walt.id announced an integration letting governments and businesses operate AWS Key Management Service with the walt.id stack.
What happened
- Keys for digital identity wallets created via walt.id wallet SDKs and APIs are created and stored in AWS KMS.
- Signatures for credential issuance and presentation are created inside AWS KMS when AWS is used as external KMS.
- The integration has been open-sourced via the Community Stack.
Why it matters to Signicat
- The integration targets a key-custody gap for wallet and issuance deployments that run on AWS KMS, relevant to Signicat's Wallet Hub and EUDI wallet work.
- Open-sourcing the integration lowers switching cost for developers already on walt.id, a competitive pressure on developer adoption.
Evidence from the source (5 quotes)
- “Keys powering the digital identity wallets created via the walt.id wallet SDKs and APIs are now created and stored in the highly secure AWS KMS environment.” source ↗
- “Signatures for issuance and presentation of digital credentials are also created in the AWS environment.” source ↗
- “Since we’ve decided to open-source it (via the Community Stack), everyone will get access” source ↗
- “This will enable a faster launch of highly secure digital identity products without headaches.” source ↗
- “Since we’ve decided to open-source it (via the Community Stack), everyone will get access and will enjoy complete flexibility and extensibility.” source ↗
Reusable identity VCDeveloper experienceData sovereignty privacyFeature updateProduct launchGlobal
4 of 4 facts verified against the source · confidence high · claude-haiku-5-5