Testing environments have lots of advantages, like the ability to run any new version of your code without impacting real users; they also have inherent costs - especially when there are many of them at different scales, such as at the service level and the integration level.
You don't want to budget for thousands of hours of CPU time per day for quality assurance; therefore, you can use the cloud for what it's good for, and only pay for what you use. At the same time, you want to keep set-up times short and to be able to keep around resources used for testing for ease of debugging.
This session presents a practical way to build a fleet of EC2 instances to help test your services; all while minimising the operating costs incurred through an efficient shutdown and reboot procedure, free from race conditions and flaky builds.
Giorgio is a software engineer in test. He searches for the harmony between form and context, which is a fancy way of saying he builds software to fit in the world he's in and all the forces around it.
His areas of expertise are testing, architecture and distributed computing.