feat(monitoring): add memory monitoring to EC2 instances #620
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
EC2 memory monitoring was previously relying on an unofficial 3rd party solution, which at one point was working intermittently.
The problem has become more pressing since PR #555 was merged, which reported a 19 MB increase in memory usage for a single bulk download of 10,000 submissions.
Solution
Upgrade to use an official solution provided by AWS here, which provides both memory and disk monitoring. The only change made was to the cron expression, which has been updated to report every minute instead of every 5 minutes.
The requisite permissions have been granted to our Elastic Beanstalk instance profiles.