We have previously seen how to set up a GitHub to Jenkins pipeline with webhooks, this time we are going to continue on that lesson and learn how to configure Jenkins to build and push Docker images to DockerHub. We’ll also see how to create images for both arm64 as well as amd64 architectures machines. Keep on reading.

Today I'll go through how get and configure a HTTPS certificate from Let's Encrypt for all the subdomain. I have already posted about how we can automate installation of Jenkins & Nginx with Ansible. I have also done a post where I talk about how to enable HTTPS on a non-wildcard basis i.e. only for the root domain and not on subdomain.

I don't claim to be a DevOps expert. I just know some basic ssh and scp, that's all. I have done whatever server configuration till date by ssh'ing into instances and then configuring them by hand. But now-a-days I feel like spinning up and destroying a server has increased in my life style.

In 2014, Google hinted that they are running tests taking into account whether sites use secure, encrypted connections as a signal in our search ranking algorithms. This means it will affect SEO in some way. Today in the age of HTTP2, https is defualt. Default in the sense that many server software will only allow HTTP2 when https is configured.

Docker makes it easy to develop and deploy application, reducing friction between the processes. And ElasticBeanstak is a great platform build upon EC2 infrastructure which provides provisioning capability without much effort.