technology.8.27.24

I began the Deploy in Public challenge today. To be honest, I’m not so much interested in the “in public” part, which seems to mean posting on LinkedIn for most people — writing on Substack will be my workaround.

I don’t really understand what we’re doing yet. Like, conceptually, I don’t grasp what we’re going to achieve by the end of the course. I know what the course outline says, but most of the jargon goes beyond me and, therefore, leaves me in a stupor.

I think, however, that the course will include networking stuff and other DevOps’y things. Well, I know this. It’s my hope to learn only a bird’s eye view of the content because I’m not super interested in DevOps. I don’t want to be afraid to get my hands dirty, but I don’t really want to approach the course like DevOps is going to become my career.

——

We started by creating an AWS account, which actually required a little finagling because of the other AWS accounts I have. I had to create a new email and start fresh.

Once into the AWS Console, we enabled the IAM Identity Center. There’s always a billion micro-decisions you have to make whenever you do anything on AWS. It’s terrifying. You feel like any wrong one will break everything. But I enabled the Identity Center just fine

Then we created a new VPC (virtual private cloud). We poked around the default VPC that AWS provides, as well as its subnets, route tables, and its internet gateway. Then we initiated our own VPC, created two subnets within it, one private (not connecting to the igw) and one public, and created a route table for the public subnet.

Each subnet has 128 ip addresses.

Lastly, we made it possible to ssh into the public subnet, which we then did from our terminals. After this, we tried ssh’ing into the private subnet — and couldn’t (which is what we wanted, nothing in nothing out).

Maybe tomorrow I’ll research a bit more about what we’re actually trying to achieve.

IAM

IAM Identity Center

VPC (virtual private cloud)