How Danggeun Built a Large-Scale Signing Key Management System with AWS CloudHSM – Part 1: The Importance of Signing Key Security and Service Selection
Key point
Danggeun introduced a hybrid system combining AWS CloudHSM and KMS to securely process an average of 65 million JWT signings per day.
Details
South Korea's local community platform Danggeun has over 21 million MAU and processes an average of more than 65 million JWT (JSON Web Token) signings every day.
The existing structure stored the Private Key used for signing in an extractable form, which posed a security vulnerability. Since the token signing key is the Root of Trust for the entire authentication system, a new system was needed that could protect it more securely while also handling large-scale traffic.
To solve this problem, Danggeun chose a hybrid signing key management system combining AWS CloudHSM and AWS KMS. Through this series, they share their technical experience, from the risks of security incidents to architecture design and the process of zero-downtime key migration.
The reasons signing key security matters are as follows.
- Hardcoded keys: Risk of full infrastructure privilege takeover if keys are leaked from source code
- Supply chain attacks: Distribution of malicious updates through stolen signing keys
- Authentication forgery: Compromise of sensitive systems by forging tokens with leaked keys
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.