Starting an AWS account from scratch…
July 19, 2019
July 19, 2019
I’ve been thinking lately about all the times I’ve setup or have been working in AWS. Mostly, I was thinking about how many times I had made a mistake or thought “if I could just do it over, I would…” There is a lot of that. I always preface every thing I do with 100% uncertainty by saying “we like it until we don’t like it.” There really are no right answers to problems, only an answer at a specific time, in a specific day that is a result of several events. So you go with what you got.
My first problem when working with existing accounts or after a some time in an old one is that I wish there were things that were already set up. These are things that would just make putting things out there a lot easier. They are a combination of ‘rules’ and things. Because “we like until we don’t like it!”, the list currently is:
- Use CloudFormation for everything possible.
- Build a development VPC
- Establish a good S3 bucket pattern
- Build out local development environment for lambda
- Build out CodePipeline tempaltes for Lambda’s WITH a deployment.
Once these things are setup, I think I would be good to go to start ‘building’ things out.
Over the course of the next few weeks, I’m going to be reviewing this by creating a new AWS account and using it to test ideas and patterns to better define a solid foundation. Starting from the ground up, I’ll see what things we need to have ready before we say “Ok, let’s build something.” I’m going to try to document and automate as much as possible. because the goal is to to get to “build” as fast as possible.
The list above is a little high level, but we will dig into them as we go along.
Advanced Data Engineering Platform for Cleansing, Preprocessing and Analytics