1. Install certbot:
sudo apt install certbot
2. Shudown OpenVPN server command:
sudo systemctl stop openvpnas
3. Install Let’s Encrypt certs multi-line command:
sudo certbot certonly \
--email EMAIL_ADDRESS \
--domains DOMAIN_NAME \
--pre-hook 'sudo service openvpnas stop' \
--post-hook 'sudo service openvpnas start'
4. Link Let’s Encrypt certs to OpenVPN web certs commands:
sudo ln -s -f /etc/letsencrypt/live/DOMAIN_NAME/cert.pem /usr/local/openvpn_as/etc/web-ssl/server.crt
sudo ln -s -f /etc/letsencrypt/live/DOMAIN_NAME/privkey.pem /usr/local/openvpn_as/etc/web-ssl/server.key
5. Restart OpenVPN service:
sudo systemctl start openvpnas
A Practical Example of Moving Web Servers into the Cloud
In this article I’ll detail my experiences virtualizing servers into Amazon Web Services ecosystem.
A client who runs a niche web hosting company contacted me about improving his infrastructure. Costs were going up and it was getting difficult managing resources as the business expanded. He had several physical servers spread over three different providers and combined data center and provider fees were approaching $1000.00 per month. That might be a rounding error for big companies, but for a small business it’s real money. The servers included sole-tenant nodes, which are essentially physical servers with only one virtual instance, and co-located boxes. If I’ve ever seen a scenario perfect for virtualization this was it.
There were about 200 WordPress installations that needed to be consolidated. So we put together a plan to migrate them all to AWS in stages.