Self-Hosted Solution: Redash t2.small AMI failing status checks once a week

Issue Summary

Thank you cyber gurus in advance for your help! I have an on-prem redash solution hosted on AWS’s EC2. I am using the redash AMI suggested on the docs, size t2.small. I am having an issue that about once a week the status checks start failing, but once I reboot the ec2 instance redash comes back up. This doesn’t look to be a resource constraint on our side (checking cloudwatch), so I’m a little bit at a loss. That being said, network packets in/out surge before the system goes down. I do have queries scheduled to update once every 30 minutes. CPU credit usage also goes up to 1.56 before the failed status checks come up. Any help? ʕ•ᴥ•ʔ

Technical details:

  • Redash Version: AMI on the docs t2.small, 8.0.0
  • Browser/OS: chrome
  • How did you install Redash: through the docs instructions