I have a t3.micro instance that has been running stably for a while. However, the environment health suddenly shows “No Data” and says it’s not retrieving any information from the instance. When I check, the instance is running, and all health checks pass. It takes hours for the environment health to return to “OK.” Afterward, I start receiving CORS errors when trying to call my APIs.

I’m not sure how to identify the root cause or where I should investigate. Any guidance would be greatly appreciated.

Thank you in advance!

Comments (2)2

2 Comments

Sep 15, 2024

please mention what is your stack and how you are accessing the apis?

eg:

1)are you using ELB, api gateway, cloudfront, Route 53?

2)how is the client calling APIs? mobile app / Postman / Webapp / S3 website / third-party / external hosted site?

3)have you enabled CORS if you are using api gateway or ALB?

4)are you using on-demand or Spot instances

5)are you able to connect your instance from cli/console

6)how long this has been happening?

In general, basic thing you can do is it check cloudwatch logs for monitoring, which by default are updated once in 5 minutes.

If you have some budget, you can enable detailed monitoring for your instances

You can check with AWS Support if you have a Business Support plan

Select your cookie preferences

Site Terms, Privacy, and more.

Environment Health - No Data Problem

Cutting off my environment and cannot access APIs.

2 Comments