Store model inputs, outputs, and customization data in S3.
Meet an organization's key-management and audit requirements.
Which design is appropriate?
Use managed key policies, access control, rotation, and audit for encryption keys; do not embed keys or grant universal access.
Detailed explanation
Encryption must include control over who can use and administer the key.
Encryption must include control over who can use and administer the key.
A source leak exposes the key and prevents safe rotation.
A source leak exposes the key and prevents safe rotation.
Universal access defeats confidentiality.
Universal access defeats confidentiality.
Data in transit also needs protection according to requirements.
Data in transit also needs protection according to requirements.
Try it yourself
An example you can run in a temporary verification environment.
AWS KMS Developer GuideとAmazon S3の暗号化公式ドキュメントを確認する。Expected result
暗号化とキー管理を別の責任として、アクセス・監査・ローテーションを説明できる。Key points
- KMS
- Key policy
- Audit
Notes
- Environment: AWS公式AIF-C01試験ガイドとAWS公式ドキュメントの確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.