SAA-C03 Exam Dumps : AWS Certified Solutions Architect - Associate (SAA-C03)

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 key requirements are asynchronous processing, high availability, burst handling, and strict message ordering. Amazon SQS FIFO queues are specifically designed to guarantee exactly-once processing and ordered message delivery, making them ideal for transactional workflows like ecommerce order processing.

Option B meets all requirements. SQS FIFO preserves the order of messages within a message group and scales automatically to absorb traffic spikes. Integrating SQS FIFO with AWS Lambda enables serverless, event-driven processing with automatic scaling and no infrastructure management. Lambda processes messages as they arrive while maintaining order guarantees.

Option A (SNS) does not guarantee ordering and is designed for fan-out messaging. Option C (SQS standard) scales well but does not preserve order. Option D introduces unnecessary batch infrastructure and increased latency.

Therefore, B is the best solution because it combines ordered delivery, resilience, elasticity, and serverless compute, ensuring reliable and scalable order processing.

The job runs for about 1 hour and must not be interrupted, so Lambda is not suitable because AWS Lambda has a maximum execution time of 15 minutes. Fargate Spot is also not appropriate because the workload explicitly cannot tolerate interruption. The most cost-effective remaining design is to run the Python script on an EC2 On-Demand instance only during the nightly processing window and automate instance start/stop around the schedule. That avoids paying for compute all day while preserving uninterrupted execution during the job. The Step Functions Express option is not the natural fit for a single long-running Python job of this type. Therefore, an EC2 instance scheduled to run only when needed is the most economical answer among the choices.

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