They are very done in Gaia and Blockstack;
Follow the document https://docs.blockstack.org/storage/amazon-s3-deploy.html
There are some issues to be aware of ：
6. | 7.
when choise an instance Type; Please choose t2.small ;
Because t2.micro , The memory is too small too run the blockstack Gaia;
1 - confirm the port is open
nmap -Pn 18.104.22.168 -p 22,80,443
[** @ zhous-MBP-2:*]~/Documents/Password$ nmap -Pn 22.214.171.124 -p 22,80,443
Starting Nmap 7.80 ( https://nmap.org ) at 2019-08-16 03:03 CST
Nmap scan report for ec2-3-112-127-199.ap-northeast-1.compute.amazonaws.com(126.96.36.199)
Host is up (0.11s latency).
PORT STATE SERVICE
22/tcp open ssh
80/tcp closed http
443/tcp closed https
Nmap done: 1 IP address (1 host up) scanned in 0.17 seconds
It is not correct the the Port 80/tcp and 443/tcp closed
run the command to slove the problem
sudo systemctl start reset-ssl-certs.service
sudo sed -ie '39d' /gaia/docker/nginx/conf.d/nginx-ssl.conf
It will take sometime to be available;
2 - Login the EC2
[ @ zhous-MBP-2: ] ~/Documents/Password $ ssh -t -i filehub.pem [email protected]
The authenticity of host ‘188.8.131.52 (184.108.40.206)’ can’t be established.
ECDSA key fingerprint is SHA256:mttwvRS7xfLqKFuRa84oNYXP/D4W8NFf877qI3Sfpuo.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘220.127.116.11’ (ECDSA) to the list of known hosts.
Last login: Mon Feb 18 20:19:06 UTC 2019 from 18.104.22.168 on pts/0
Container Linux by CoreOS stable (1967.6.0)
Update Strategy: No Reboots
3 - localhost test
4 - ip test
5 - domain test
The domain is the same as in the 【6. Advanced Details】 setting
Follow the instructions and Create a New BlockstackID； Choose use different provider ；
Use the url ： https://filehub.fun — the same as in the 【6. Advanced Details】 setting
When the url is correct is wrong ; it will be an information that unavailable
You can also refer to [About AWS - Blockstack Gaia — cannot access hub_info]
Yes， Did it ，Congratulations