AWS re:Post을(를) 사용하면 다음에 동의하게 됩니다. AWS re:Post 이용 약관
AWS re:Postre: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?

주제
보안, 신원 및 규정 준수데이터베이스
태그
AWS 키 관리 서비스데이터베이스아마존 DynamoDB
언어
English
Prasannaa Santhanam
질문됨 일 년 전288회 조회
1개 답변
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.

profile pictureAWS
전문가
Leeroy Hannigan
답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠