If you have a DIY Server license and wish to install Sitebulb Server on an Amazon AWS EC2 instance, please check out our video guide below.
It is only 10 minutes long for the complete end-to-end process, but does assume that you have already set up an AWS account and added billing details.
Aside: In the long run, this is much more expensive than our managed cloud servers, but can work as a convenient way to test out Sitebulb Server.
It is reasonably common for users to stop an AWS instance when they aren't using it, and then start it up again at some point in the future - in order to avoid spiraling costs.
If you do this, the IP address of the instance will change!
So you will need to make sure you update the IP address in your server list, otherwise you will not be able to connect to the server.
Your server will start like this, everything great:
Then if you go into AWS and 'Stop' the instance:
Sitebulb will now show 'Server Error', which makes sense, since the instance is no longer available so Sitebulb can't connect to it.
A week or two may pass before you then go to start the instance back up again in AWS:
Now this is the tricky bit, once you have started the instance again, if you scroll across to the right, lo and behold, the IP address will have changed!
And Sitebulb will continue to show a server error until you update it to this new IP address (the secret key remains the same, so it's just the IP address that needs updating):