EC2 image”). Make sure SSH is open from your build server’s IP address in the default security group
on Amazon EC2. If you don’t do this, Jenkins will time out when it tries to start up a new slave node.
Once you have prepared your image, you will be able to use it for your EC2 configuration.
Figure 11.20. Creating a new Amazon EC2 image
Now Jenkins will automatically create a new EC2 instance using this image when it needs to, and delete
(or “terminate,” in Amazon terms) the instance once it is no longer needed. Alternatively, you can
bring a new EC2 slave online manually from the Nodes screen using the Provision via EC2 button (see
Figure 11.21, “Bringing an Amazon EC2 slave online manually”). This is a useful way to test your
configuration.
Figure 11.21. Bringing an Amazon EC2 slave online manually
11.7. Using the CloudBees DEV@cloud Service
Another option you might consider is running your Jenkins instance using a dedicated cloud-based
Jenkins architecture, such as the DEV@cloud service offered by CloudBees. CloudBees provides
Jenkins as a service as well as various development services (like Sonar) around Jenkins. Using a
dedicated Jenkins-specific service, there is no need to install (or manage) Jenkins masters or slaves on
your machines. A master instance is automatically configured for you, and when you give a job to be
built, CloudBees provisions a slave for you and takes it back when the job is done.