Unable to Connect Amazon AWS Resource Handler
Sometimes users run into the situation where they're unable to connect their CloudBolt instance to AWS.
This could be related to a proxy issue, which is addressed by entering the appropriate proxy info in ADMIN > MISCELLANEOUS SETTINGS.
The other frequent issue we see causing this is related to the time on the CloudBolt server. If the time on the server is off by a minute or more, the CB server will be unable to connect to AWS due to time differences in the signed API request coming from CloudBolt.
To fix the date on the CloudBolt appliance, either manually set your time with:
$ date -s "2 OCT 2006 18:00:00"
$ ntpdate -s time.nist.gov
To fetch the latest date/time from a public ntp server.