As Public Sector development teams transition to cloud-based architectures and adopt more agile processes, the tools they need to support their development cycles will change. In this session, we'll take you through the transition that Amazon made to a service-oriented architecture over a decade ago. We will share the lessons we learned, the processes we adopted, and the tools we built to increase both our agility and reliability. We will also introduce you to the AWS Code family services which were born out of Amazon's internal DevOps experience and are utilised by many Public Sector customers globally.
Mario Vlachakis, Solutions Architect, AWS
https://secure.flickr.com/photos/mgifford/4525333972
Today we are all here to discuss DevOps
I will start with "What is DevOps and why?”
Followed by a bit of history about Amazon's own DevOps transformation, and the changes that we made to become more agile with our product delivery
And finally introduce the AWS Code Services services that’ can assist customer with their DevOps transformation.
You should walk away with a high level understanding of the different parts involved with a DevOps transformation, and an idea of how you could use our AWS Code services in your own DevOps processes
Software creation and distribution is much easier and faster than ever:
Startups can now take on giants with little to no funding ahead of time
Getting your software into the hands of millions is just a download away
Your ability to move fast is paramount to your ability to fight off disruption
Amazon created a shared internal deployment service called Apollo. Apollo’s job was to reliably deploy a specified set of software across a target fleet of hosts. Developers could define their software setup process for a single host, and Apollo would coordinate that update across an entire fleet of hosts.
https://www.flickr.com/photos/stevendepolo/5749192025/
- after we tell customers the story of our DevOps transformation, they typically ask us how they can do the same
- I'm not going to over-simplify this, because it is a very complex answer
- this can involve organizational changes, cultural changes, and process changes
- plus there's no one right answer for these
- every company is going to tweak their approach to optimize for their own environment
- but there is one standard thing that every DevOps transformation needs, and that's an efficient and reliable continuous delivery pipeline
- that's the focus for the rest of this talk
CodeCommit gave us a single version-controlled source of truth
CodeBuild used HashiCorp Packer to build and image an EC2 instance, enabling faster deployments
CodePipeline hooked them all together to give us a visualation