Which solution will meet these requirements?
Create a public SSL/TLS certificate in AWS Certificate Manager (ACM). Associate the certificate with Amazon S3. Configure default encryption for each S3 bucket to use server-side encryption with AWS KMS keys (SSE-KMS). Assign the compliance team to manage the KMS keys.
Use the aws:SecureTransport condition on S3 bucket policies to allow only encrypted connections over HTTPS (TLS). Configure default encryption for each S3 bucket to use server-side encryption with S3 managed encryption keys (SSE-S3). Assign the compliance team to manage the SSE-S3 keys.
Use the aws:SecureTransport condition on S3 bucket policies to allow only encrypted connections over HTTPS (TLS). Configure default encryption for each S3 bucket to use server-side encryption with AWS KMS keys (SSE-KMS). Assign the compliance team to manage the KMS keys.
Use the aws:SecureTransport condition on S3 bucket policies to allow only encrypted connections over HTTPS (TLS). Use Amazon Macie to protect the sensitive data that is stored in Amazon S3. Assign the compliance team to manage Macie.
Explanations:
While this option mentions using an SSL/TLS certificate for secure transmission and server-side encryption with AWS KMS (SSE-KMS) for data at rest, the use of a public SSL/TLS certificate with S3 is not applicable as S3 does not directly support this. Instead, HTTPS is automatically used for encrypted transmission. The solution correctly includes KMS key management, but the incorrect SSL/TLS setup makes this option invalid.
This option allows encrypted connections using the awscondition, but it configures S3 to use SSE-S3, which does not allow the compliance team to manage the encryption keys. SSE-S3 uses AWS-managed keys, which do not meet the requirement for key management by the compliance team. Therefore, this option is not suitable for the requirements.
This option correctly implements the awscondition to ensure encrypted connections over HTTPS and uses server-side encryption with AWS KMS keys (SSE-KMS) for data at rest. This allows the compliance team to manage the KMS keys, meeting both requirements of encryption in transit and at rest with appropriate key management.
This option correctly includes the awscondition to allow only encrypted connections over HTTPS. However, it relies on Amazon Macie for data protection, which is primarily used for data classification and does not provide encryption capabilities. Additionally, Macie does not address the requirement for managing encryption keys for data at rest. Thus, this option fails to meet the specified requirements.
I estimate that the answer is:
Use the aws:SecureTransport condition on S3 bucket policies to allow only encrypted connections over HTTPS (TLS). Configure default encryption for each S3 bucket to use server-side encryption with AWS KMS keys (SSE-KMS). Assign the compliance team to manage the KMS keys.
I systematize that the answer is:
Use the aws:SecureTransport condition on S3 bucket policies to allow only encrypted connections over HTTPS (TLS). Configure default encryption for each S3 bucket to use server-side encryption with AWS KMS keys (SSE-KMS). Assign the compliance team to manage the KMS keys.