Bug #9063
closedBraille AWS server appears to be gone
0%
Description
I was doing some testing with our Braille setup #4859, and found that requests to the AWS box were failing. I tried logging into AWS using the Commons credentials that Matt previously provided to me, but got a "This AWS account is not accessible." error message.
Matt, do you have insight into what might've happened here? Did the account lapse?
Updated by Matt Gold over 6 years ago
Hi Boone,
Argh!!! We recently deactivated an AWS account because I didn't think we were using it and I had no memory of your using one for the CAC. I'm very sorry.
What would be the best path forward. Should I try to reactivate it so that you can perhaps (hopefully?) reinstate the service as it was? If that probably won't be possible, I will help you get set up on one of our other accounts. Sorry about this.
Updated by Boone Gorges over 6 years ago
Oh shoot - I wonder if I had something to do with this. I seem to remember you asking whether it seemed OK to shut it down. (Maybe I'm misremembering.)
If it's possible to reactivate this very box, that'd be ideal. But, from what I recall, it's not an enormous amount of work to spin up another LibLouis box. Maybe you could try reactivating and see what happens?
Updated by Boone Gorges over 6 years ago
- Target version set to Not tracked
Bump - If you have a chance to look into the AWS situation, it'd be appreciated.
Updated by Matt Gold over 6 years ago
Dear Boone, I'm sorry about this, but I think we may have to create the installation anew. We can add it to an AWS account I already have, or you can create a new one and I can add the credit card to it. Please let me know what you prefer.
Updated by Boone Gorges about 6 years ago
OK, thanks. As long as there are no financial/bureaucratic reasons not to do so, it's probably easiest to attach to your existing account. If you can set me up with an account, that'd be great. (I think it's https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users.html but I don't know much about AWS.)
Updated by Boone Gorges almost 6 years ago
- Status changed from New to Resolved
I've set up the new instance and fixed the endpoint on the production site and in the repo https://github.com/cuny-academic-commons/cac/commit/64a6ba1a4f00f8446fc76739173574f4ecbbe3f5. This should now be resolved.
Updated by Boone Gorges almost 6 years ago
- Target version changed from Not tracked to 1.13