This is supremely complicated, compared to the usual advice of just using bcrypt, and there's a lot of complexity left unmentioned, mainly IAM. You need to ensu

This is supremely complicated, compared to the usual advice of just using bcrypt, and there's a lot of complexity left unmentioned, mainly IAM. You need to ensure: 1. DynamoDB IAM permissions are correct. 2. EC2 IAM is correct. 3. The nitroenclave attestation is securely written, so as to avoid proxy-attestations from the main VM (and other attacks) 4. KMS IAM permissions are correctly written, to avoid direct decryption. The additional complexity of writing this beast, managing it, making sure that your setup remains maintainable and scalable might be worth it, but you need to compare it to the ROI: >The salt for any hash cannot be accessed by the attacker to perform a brute-force attack. Using bcrypt with a high cost factor pretty much guarantees the same. I'd be more interested in seeing a SGX-like solution using NitroEnclaves. Perhaps something that solves the Signal Contact Discovery problem[0]? [0]: https://signal.org/blog/private-contact-discovery/ https://signal.org/blog/private-contact-discovery/