Skip to main content

AWS AosEdge Health check strategies

EKS Kubernetes health check​

All Aos Edge microservices had being configured to use health checks and readiness checks, we are using cloud native k8s approach to get those and restart if somehow those are failing.

The kubelet uses readiness probes to know when a container is ready to start accepting traffic. A Pod is considered ready when all of its containers are ready. One use of this signal is to control which Pods are used as backends for Services. When a Pod is not ready, it is removed from Service load balancers.

More information about readiness and livenness in k8s docs.

AWS Cloud Watch and route53 health check​

Amazon Route 53 health checks monitor the health and performance of your web applications, web servers, and other resources. Each health check that you create can monitor one of the following:

  • The health of a specified resource, such as a web server.
  • The status of other health checks.
  • The status of an Amazon CloudWatch alarm -> In aos Edge this will trigger an alarm and send to configured administrator emails.

More information in route53 health check docs.

AosEdge AWS Smoke Test​

Disclaimer: There is no smoke test for the AosEdge yet, but testing full E2E.

  • Check that the frontend it is reachable I.E. https://<myown.fqdn>/en/
  • Check that port 10000 and 9000 are listening.

curl -kI https://<myown.fqdn>:9000
curl: (35) OpenSSL//1.1.1k: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure curl -kI https://<myown.fqdn>:10000

HTTP/2 200
server: -

End to end testing​

It is highly recommended to start following the cookbooks to generate aos keys and vm's for testing.