Update docs for HTTPS monitoring

[dmasters19]

This is just a suggestion - in the docs there is a section called Set up custom HTTPS monitoring that advises to create a custom lambda function and cloudwatch metric to monitor an endpoint.

However, Route 53 now has this capability and it works with Cloudwatch as well. You can even include metrics for latency, and then import the metric from cloudwatch to your status page without having to further configure any functions.

[ks888]

Thank you for your suggestion. I see, that route53 feature may also work, but I wonder some users do not have the Route53 setting.

@wmnnd what do you think?

[wmnnd]

It’s an interesting idea!
I see mainly two arguments to be made for sticking with lambda-watchtower:

1. Route 53 is much more expensive: measuring latency for a single external HTTPS endpoint would cost USD 4.75/month while lambda-watchtower costs hardly anything
2. lambda-watchtower is more easily extendable and configurable. It already supports non-HTTP(S) port checks and SMTP, for example.