About the series
Bill Vass: VP, Object Streaming and Storage, Amazon Web Services
Title: DevOps at Amazon: A Look at Our Tools and Processes
Abstract:
As Amazon has transitioned to the cloud, it moved from a monolithic architecture and waterfall based development model to a service oriented architecture based on an agile and devops methodology. We will discuss Amazon’s move to the cloud, the development and growth of Amazon Web Services (AWS), and how the devops model is implemented within AWS. Amazon’s customer focused methodology combined with devops and a flexible scaling infrastructure has allowed Amazon and AWS to significantly accelerate innovation and the delivery of new products and features.
Bio:
Bill Vass is Vice President of Engineering at Amazon Web Services, where he oversees the team working on Amazon S3 Object Storage Service, Amazon Glacier, Simple Queuing Service, Simple Work Flow, Auto Scaling, Messaging, Transactional Systems, and Kinesis Streaming Services. With these projects, the Storage Services team runs the largest software defined storage system in the world, which is used by web-based companies, consumer companies, enterprises, and the growing world of Internet of Things stream, to store and retrieve information quickly and efficiently. The services help to on-ramp data into the AWS ecosystem so that companies can scale quickly and utilize data by taking advantage the AWS compute and analytic services.
Most recently, Mr. Vass was the President and Chief Executive Officer of Liquid Robotics, Inc., a pioneering Data as a Service, cloud-based solutions company that designs and builds autonomous robots that serve a wide range of customers in the energy, shipping, defense, communications, scientific, intelligence, and environmental markets.
Previously, Mr. Vass was the President and Chief Operating Officer of Sun Microsystems Federal, an independent subsidiary with its own board of directors, where he was responsible for growing over $1.4B of revenue. His responsibilities spanned Product Development, Sales and Business Development, Marketing, Partner Management, and Service Delivery.
Before leading Sun Microsystems Federal, Mr. Vass served as Chief Information Officer and Chief Information Security Officer at Sun, where he defined and delivered the technology vision, architecture, and managed global deployments in support of Sun’s 50K business users. During his time as CIO, Mr. Vass significantly improved security, availability, and application delivery while reducing the overall operations cost of IT from $880M to $360M.
Mr. Vass had a lengthy public service career. Working for the Secretary of Defense in the Office of the CIO, he was responsible for a $35.5B budget, as well as system and software acquisition, research, development, and integration standards for over 6,800 IT systems. His organization managed networks, servers and applications across the Pentagon’s defense networks.
Prior to joining the Office of the CIO, Mr. Vass was CTO and technical lead for the U.S. Army’s personnel systems worldwide. Before his work at the DoD, Mr. Vass developed large-scale commercial Information Technology engineering and business systems solutions for defense system integrators, as well as the oil and gas and ocean engineering industries.
Mr. Vass lives on Bainbridge Island, WA with his family.
To Join the Webinar:
Please register at:
https://nsf.webex.com/nsf/j.php?RGID=r1cca5e51dcff710b4848ca957263de0e
by 11:59pm EST on Monday, June 20, 2016.
After your registration is accepted, you will receive an email with a URL to join the meeting. Please be sure to join a few minutes before the start of the webinar. This system does not establish a voice connection on your computer; instead, your acceptance message will have a toll-free phone number that you will be prompted to call after joining. If you are international, please email kgeary@nsf.gov to obtain the appropriate dial in number. Please note that this registration is a manual process; therefore, do not expect an immediate acceptance. In the event the number of requests exceeds the capacity, some requests may have to be denied.
