Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

CachingMostRecentProvider - What is the need for MetaStore DynamoDB Table?

0

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?

Topics
Security, Identity, & ComplianceDatabase
Tags
AWS Key Management ServiceDatabaseAmazon DynamoDB
Language
English
asked 3 years ago458 views
1 Answer
1

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.

AWS
EXPERT
answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content