Which version of the application are you using?:
Latest Version: 8.6.12117-2 on Ubuntu 16.04
Please choose how you got the application: Installer (Windows, Linux, macOS), cloud image (AWS, GCE, Azure, ...) or VM (VMDK, VBOX):
Have you installed any plugin or modified any configuration file?:
No it is a brand new install on a brand new AWS account created specifically for this.
Describe here your question/suggestion/issue (expected and actual results):
Full disclaimer, I am new to AWS (but am an professional C++ developer) so its entirely possible that there is something I have to do that I didn't know to do to enable connections to the instance.
I created the AWS account, then created an Instance using the "Subscribe" workflow on this page: https://aws.amazon.com/marketplace/pp/B00NPHKB3G and selecting the t2.micro instance type (which I believe is required for Free service?) I didn't set any special security settings on my account or anything like that - only created a normal ssh key for the installer since my account didn't have one.
I waited a few minutes - then the server shows that it is running with DNS at blahblah.compute-1.amazonaws.com
I tried connecting to this via http and https in both Chrome and Edge but both timed out. I tried conncting via the IP4 address with the same result.
Then I tried connecting via SSH, using the key I created during the install process. using both "ubuntu" and "bitnami" as usernames
ssh -vvv -i ./Firstkeypair-ResrouceSpace.pem email@example.com
OpenSSH_7.7p1, OpenSSL 1.0.2o 27 Mar 2018
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: resolving "blahblahblah.compute-1.amazonaws.com" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to blahblahblah.compute-1.amazonaws.com [IP4 ADDRESS HERE] port 22.
debug1: connect to address IP4 ADDRESS HERE port 22: Connection timed out
ssh: connect to host blahblah.compute-1.amazonaws.com port 22: Connection timed out
Steps to reproduce the issue (if relevant):
I tried making another one in this same AWS account with the same result, I can't connect to it at all :-/ As mentioned this may totally be something wrong with my AWS skills but I have no idea what to even search for - not being able to connect via ssh or http on a fresh install on a fresh account seems to not be a thing anyone else has experienced as far as my searches go.
Copy the apache log (if relevant):
Would love to but AFAIK I can't get to this without SSH access to the server unless there is some interface in the AWS panel to read this out of the VM?