Jenkins with Docker on HTTPS on AWS and inside a Corporate Firewall
With an understanding of the architecture from Chapter 1, Jenkins Infrastructure with TLS/SSL and Reverse Proxy, we are ready to run Jenkins. We'll learn two ways of running Jenkins – one on AWS and another inside a corporate firewall. We'll see that they're generally similar, but the reverse proxy and the port opening for inbound agent configuration are different. Don't worry – we'll configure not only a Jenkins controller but also the reverse proxy, HTTPS, agents, and even Docker Cloud together. By the end of the chapter, we will have a fully functioning Jenkins instance that's ready to take on a production workload.
In this chapter, we're going to cover the following main topics:
- Running a Jenkins controller with Docker on HTTPS
- Reverse proxy and TLS/SSL termination options
- Installing plugins and configuring Jenkins
- Attaching SSH and inbound agents
- Creating a secure Docker Cloud