Unlike Mike Rowe's "Road To Coober Pedy," my trip to Seattle, Washington for my Summer Internship with Amazon, will hopefully not be filled with death, injury, or road kill. This post will help serve as my record of the progress that I have made, and the events that have taken place, leading up to my First Day as a Software Development Engineering Intern.
After submitting my acceptance letter, I received a "Team Preference" survey from my point of contact at Amazon in early February. Based on my start and end dates, and the areas of interest I marked on my survey, I was presented with three options, as well as a brief description of what the team does and where they are located. One of the options, and the one that I ended up marking as my first preference (and receiving) was working with Amazon Web Services' (AWS) CloudFormation team in Seattle.
AWS CloudFormation gives developers and systems administrators an easy way to create and manage a collection of related AWS resources, provisioning and updating them in an orderly and predictable fashion. - AWS CloudFormation
I have had some experience working with AWS and its various services (namely Lightsail for WebHosting, and Glacier for Backups). From that, I know that AWS' many services, each of which are extremely powerful by themselves, only become more powerful when combined. However, doing this becomes increasingly difficult to do repeatedly and consistently, as the size of your infrastructure grows; and that is why CloudFormation is so cool!
The real fun starts once I cross the T-60 day mark, which will happen in Mid-March. At that point, my team placement, start/end dates are set in stone, and the on-boarding process begins (Relocation, Background Check, etc.) I will be updating this post until my first day in Mid-May.
I have no doubts that this is going to be very exciting summer!