Deploy a Serverless maintenance webpage in 1 second

Setup a Serverless Maintenance Webpage in seconds

One of the most damaging things that can damage your website’s applications is for the users to see is the “This site can’t be reached” message. It’s very important to keep your users informed.

Your website might be down because it’s undergoing maintenance, a DDoS attack or simply because there are issues in your application stack.

Steps

1. Create an s3 bucket with the same name as the record you are trying to redirect to.
2. Allow public access.
3. Static website enable
4. Setup the policy
5. Upload your files and make them read public
6. run nslookup resolves to current dns record
7. See the webpage it resolves to
8. Route53: edit existing www palo record
9. Run nslookup to the same record that you just modified
10. Test using a different browser

Use cases:

1. Scheduled Maintenance window.
2. Someone made a change and your application is down
3. DDoS attacks.
4. You can also use the static website feature to host your static website content.

Requirements

1. Ability to build s3 bucket
2. Have a registered domain
3. Have Route53 DNS records

Advantages

1. You reputations is not damaged. The users will see a maintenance page whenever your site is down,.
2. You keep your customers update with the website status.

Try Status pages

Atlassian status pages is an option you can use to keep your users informed.

Statuspage | Atlassian

Find more great tutorials at

Smart Cloud Computing | CyberSecurity: Network, Cloud and SecDevOps