|
|
The other way is using a AWS virtual server with Bitnami and Amazon Lightsail:
|
|
AWS Lightsail rents private virtual server space:
Link to your lightsail Node.JS instance
Here is an introduction to lightsail
|
|
Lightsail uses Bitnami. Bitnami provides pre-packaged application images, so you can choose Node.JS, or whatever programming package you want and they implement it. You chose Node.js. You can then just open a SSH connection ("Secure Shell (SSH) is a cryptographic network protocol for operating network services securely over an unsecured network.[1] Typical applications include remote command-line, login, and remote command execution, but any network service can be secured with SSH."
Wikipedia link
) to the command line of the server and you are able to create files and manage the server from that command line.
Here is a link to the various 'images' of operating systems Bitnami provides (wordpress, Node.js, Ruby, etc)
|
|
You have set up a static public IP address (currently http://52.204.34.43/) for your private virtual lightsail server so that your domain can point to it.
This is the link to the page that manages the static domain
|
|
Your domain can be pointed to wherever you website is being served from. If you log into AWS Route53 and go to 'Hosted Zone' in the dashboard under DNS management you will find the Records that show where the site is being pointed.
Records can be different types. A = routes traffic to an IPv4 address (the classic xxx.xx.xx.xxx number system) and some AWS resources, CNAME = Routes traffic to another domain name and to some AWS resources, NS = name server ("Amazon Route 53 automatically creates a name server (NS) record that has the same name as your hosted zone. It lists the four name servers that are the authoritative name servers for your hosted zone. Except in rare circumstances, we recommend that you don't add, change, or delete name servers in this record."), SOA = start of authority (The start of authority (SOA) record identifies the base DNS information about the domain, so the name server that created the record, the email address of the administrator, etc.. read more about NS and SOA here.).
Here is a 'how-to' document from AWS explaining it all
|
|
|
|
|
|
|
|