CachingMostRecentProvider - What is the need for MetaStore DynamoDB Table?

Question

We have a encrypted dynamodb table and recently noticed latency on ddb calls, looking further it was actually kms calls that was taking time. So we looked into caching solutions and found that CachingMostRecentProvider as the general suggestion. But would like to know why does CachingMostRecentProvider/MetaStore need a DDB table? Why cannot it store the required data in memory and on expiry can it not fetch using DirectKMS?

Answer

> We have a encrypted dynamodb table

Firstly, its important that you are referring to Client Side Encryption, and not server side encryption offered by DynamoDB natively.

For Client Side Encryption, `CachingMostRecentProvider` does not necessarily mean you must use DynamoDB, you are free to store the keys CMP where you like. DynamoDB as a metastore is just a built in solution for the encryption client which enables you to quickly implement caching.

CachingMostRecentProvider - What is the need for MetaStore DynamoDB Table?

Conteúdo relevante