I haven't written in awhile and that one is on me. I meant to keep this up regularly, but I've been slacking with it to say the least. Who knew that having a family, a full time job and responsibilities would take up so much of my time! I'm going to do my best to update regularly going forward.
Now that I've got that out of the way, the real reason for my post...
I meant to get to finishing this up shortly after my last post, but life comes at you fast sometimes. No excuses though, as I've been continuing with my course and should be finished within the next day or two. In the meantime, I still have a bunch of content to write, so let's get to it.
This will be a continuation in the Database series covering the AWS offerings as part of the AWS Solutions Architect: Associate exam. I covered RDS in part 1 and will continue with Aurora in this part.
I finished the database section of the AWS Solutions Architect Associate course a few days ago, and it was by far the most challenging to wrap my head around.
Just to point it out for the record — I am by no means a database guy. I know what they are at a cursory level, but I have no real hands-on experience to speak of with any type of databases.
This will be my attempt to make sense of all the database offerings from AWS.
I'll start by saying I have a very general understanding of DNS. I know it's often dubbed the “internet phone book” and that it translates IP addresses into URLs. I know some of the various DNS record types off the top of my head — A, AAAA, CNAME, MX, TXT — along with how each of them are used, but mostly at a high level.
As a baseline...
I just finished the Virtual Private Cloud (VPC) section of the AWS Certified Solutions Architect course and I wanted to write it out in order to gain some clarity around it.
For some reason, this has been the hardest topic of the course so far. There were certain things that were easier than I thought they'd be (subnetting), while others were much more difficult (NAT Instance vs NAT Gateway).
I have to preface this by saying that I am not a developer. I can read snippets of code and muddle my way through certain things, but coding is not my strong suit.
Having said that, I need to break down API Gateway as much as I can in order to better understand it.
Serverless architecture is the current topic I'm learning in the AWS Certified Solutions Architect: Associate course from Linux Academy. It's a bit of a challenge for me because I don't have any real experience with it, but I understand the concepts at a 30,000 ft level.
I'll start with what I know and then get into some theory I've compiled.
As I mentioned in my first post, I'm working my way through the AWS Certified Solutions Architect certification training course. I finished the EC2 Fundamentals course last night and just wanted to write some of my thoughts on it as I move onto the Intermediate coursework.
Since I'm currently going through the AWS Certified Solutions Architect course offered by Linux Academy, I'm going to need to write things out so that they make a bit more sense to me. Today, it's going to be the differences between Instance Stores and Elastic Block Stores.