Amazon Web Services SAA-C03 Exam With Confidence Using Practice Dumps

To serve a static website hosted in Amazon S3 over HTTPS, you must use Amazon CloudFront because S3 does not natively support HTTPS for static website endpoints.

Steps to meet HTTPS requirement:

B. Create a CloudFront distribution and configure the S3 bucket as the origin. This enables global edge caching and performance optimization.

D. Attach an SSL/TLS certificate (typically from AWS Certificate Manager) to the CloudFront distribution to handle HTTPS connections.

S3 buckets used as static website hosts only support HTTP directly. While S3 supports HTTPS for REST API access, it does not support HTTPS on static website endpoints.

This setup aligns with security best practices and supports the Secure and Operational Excellence pillars of the AWS Well-Architected Framework.

???? References:

Hosting a static website using Amazon S3 and CloudFront

CloudFront + HTTPS with ACM

The correct answer isCbecause the company needs asecure cross-account accesssolution that usestemporary credentials, followsleast privilege, and avoidslong-term access keys. The best practice for this design is to allow anIAM role in Account Ato access theAmazon S3 bucket in Account Bthrough aresource-based bucket policy. Analysts or applications in Account A can assume the IAM role and receive temporary credentials through AWS Security Token Service (AWS STS), which satisfies the requirement to avoid permanent access keys.

This approach is secure because permissions can be scoped precisely to the required bucket and prefixes, supporting least-privilege access. It also avoids creating separate IAM users in Account B and eliminates the operational and security risks of sharing static credentials across accounts. Cross-account access through IAM roles and S3 bucket policies is the standard AWS pattern for securely granting one account access to resources in another account.

Option A is incorrect because creating IAM users and sharing access keys introduces long-term credentials, which the company explicitly wants to avoid. Option B is incorrect because making the S3 bucket public violates security requirements and does not enforce least privilege. Option D is incorrect because using a bastion host adds unnecessary infrastructure and operational overhead and is not the recommended approach for S3 access.

AWS security best practices favorrole-based access with temporary credentialsandresource policiesfor cross-account resource sharing. Therefore, configuring the S3 bucket policy in Account B to allow access from an IAM role in Account A is the most secure and appropriate solution.

The Lambda function already has an execution role, so the correct fix is toadd CloudWatch Logs permissions to that same role. AWS documentation lists the required permissions for a Lambda function to write logs: logs:CreateLogGroup, logs:CreateLogStream, and logs:PutLogEvents. A separate role for the S3 bucket would not help because Lambda uses its own execution role when it runs. An S3 bucket policy is unrelated to CloudWatch Logs logging. The logs:GetLogEvents permission is for reading logs, not writing them. Updating the existing execution role is the least-complex and correct solution.

============