Skip to content

Commit 41702fe

Browse files
fix 177
AWS Secrets Manager is not a valid S3 encryption option Secrets Manager is designed for storing and rotating secrets like database passwords and API keys, not for S3 server-side encryption The question is asking about S3 SSE methods, and Secrets Manager doesn't provide this AWS KMS managed keys would be the best option
1 parent cdced04 commit 41702fe

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2154,8 +2154,8 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
21542154
### A Developer decides to store highly secure data in Amazon S3 and wants to implement server-side encryption (SSE) with granular control of who can access the master key. Company policy requires that the master key be created, rotated, and disabled easily when needed, all for security reasons. Which solution should be used to meet these requirements?
21552155

21562156
- [ ] SSE with Amazon S3 managed keys (SSE-S3).
2157-
- [ ] SSE with AWS KMS managed keys (SSE-KMS).
2158-
- [x] SSE with AWS Secrets Manager.
2157+
- [x] SSE with AWS KMS managed keys (SSE-KMS).
2158+
- [ ] SSE with AWS Secrets Manager.
21592159
- [ ] SSE with customer-provided encryption keys.
21602160

21612161
**[⬆ Back to Top](#table-of-contents)**

0 commit comments

Comments
 (0)