I feel like a dope coming here to ask a basic question like this, but here I am. I don't know if it's an AWS question or a WebWork question, but here goes:
Last year I had a perfectly good instance of WebWork up and running on AWS. I followed the instructions for getting it set up and it worked like a charm.
Last week I noted we were up to version 2.18, so I terminated my original instance and went to install 2.18 from scratch. for more practice. The instructions have not changed since the last version I installed and I went through the same process - from the US East Ohio region, I found and copied the WebWork 2.18 AMI, picked t3.small, set the default security group, selected a key pair, and installed the image successfully ... or so it seemed.
Now that the instance is "running" per the AWS control panel, I cannot connect to it using either the EC2 Connect feature within AWS, or by trying to use SSH via MobaXTerm on my machine to sign on as firstname.lastname@example.org (using the new address in place there). The EC2 Connect feature will tell me I can't connect to the instance, but does not provide a specific reason why. On a local use of SSH, I get timed out.
Has anyone encountered this before? I feel like I followed the directions, and I got it to work last year. Any ideas as to the cause? What dumb thing is this newbie doing?