Closed jumbatm closed 5 years ago
Due to student tier AWS being overly-strict on ElastiCache for Redis creation, we will resort to using Azure Cache for Redis (tested, deployment successful). Notes: Azure-for-students accounts has 100AUD credit. Using standard cache size (250MB) costs about 2.2cents/hr (see pricing here)
Here is the tutorial to connect Azure Cache for Redis to Node.js app.
Set up is pretty easily. Add it as a normal resource, and then you can access the Access Key to put data on. Cheapest tier is pretty solid, seems that it's interacted with through get and set async methods.
We decided not to close this until we confirm exactly what format to put into scene information in.
Information must goes into the scene information cache:
How to deal with individual RUs failing?
We can get instance status information: see https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/EC2.html#describeInstanceStatus-property
Example of aws-cli returning instance states under specified (my) account:
aws ec2 describe-instances --filters Name=instance-state-name,Values=running --query Reservations[].Instances[].State.Name
Returns the following:
[
"running"
]
Similarly, we can check by instance ID:
aws ec2 describe-instances --instance-ids i-06fd9f6bf6343fd46 --query Reservations[].Instances[].State.Name
This is now completed. Comments related to Phase 3 will be moved to ther respective issues.