An application deployed on AWS Elastic Beanstalk uses Amazon Aurora and is fronted by a CloudFront distribution that uses the Elastic Beanstalk domain as its origin. CloudFront is configured with an alternate domain name that users access. Each week the application is taken offline for maintenance; during that time the company wants visitors to see an informational page (not a CloudFront error). The first step — creating an S3 bucket — is already done. Which three actions should the solutions architect take next to implement this behavior?

The first correct action is to upload the static informational content to the S3 bucket. This content will be displayed to users during maintenance. The second correct action is to configure the existing CloudFront distribution to add the S3 bucket as a second origin and use an Origin Access Identity (OAI). This allows CloudFront to securely access the S3 bucket. The third correct action is to edit the existing distribution’s default cache behavior during maintenance to point to the S3 origin, then revert the change. This redirects all traffic to the S3 informational page. Creating a brand-new CloudFront distribution is unnecessary and adds complexity. Configuring Elastic Beanstalk to serve traffic from S3 is not the intended solution; CloudFront should handle the redirection. Adding a cache behavior for the S3 origin on a new distribution is incorrect because we are modifying the existing distribution.