This repository was archived by the owner on Dec 5, 2024. It is now read-only.
This repository was archived by the owner on Dec 5, 2024. It is now read-only.
AWS improvements #204
Description
This "issue" will serve as a place holder to summarize the current teams thoughts on next steps for AWS.
Description
There are some things that could be improved for AWS deployments.
- Trigger a frontend deploy after the backend deploys
- set up more advanced health triggers to stop failed deployments
- set up more advanced health triggers to redeploy latest working version upon failure (5xx's)
- set up notifications for health triggers so that the team/sponsors will be aware of issues
- Figure out why the deployed application fails every 10-14 days (500's, no unexpected data in logs/metrics)
-
- Atleast maybe set up a cloudwatch trigger for re deploys every friday night as a work around?
- Clear autodock and openbabel s3 buckets automatically
-
- done either through the code (deleting after succesful docking) or maybe a cloudwatch event?
- DIscuss with sponsors to change to multiple ec2 instances
-
- would use elastic load balancer
-
- would create/remove instances based on metrics of use
-
- cost be cost effective but a more complex architecture and planning.