Serverless, DevOps, k8s, AWS, cloud, fishing, cycling.
You’ve probably heard of AWS Lambda and serverless by now. But what is Lambda
all about? The short definition of AWS Lambda is a “Functions as a Service”
(FaaS) technology. The longer and more complicated answer is that Lambda is a
lightweight runtime that requires no infrastructure to be defined by the
developer.
Networking can sometimes be quite complicated. Despite the oft repeated joke that “It’s always DNS”, sometimes your problem is even more difficult to diagnose than DNS.
According to Wikipedia, Classless Inter-Domain Routing (or CIDR) “is the method for allocating IP addresses and for IP routing” on the internet and on private networks. If there are conflicts in two networks’ CIDR ranges, it can cause headaches that make DNS problems look like childs play.
Over the last few years I’ve provided information on how to approach a job search to friends and coworkers. I typically send an email with this information, but I think it’s useful to a broader audience, so I’ll provide it here in a blog post.
This is certainly not meant to be an exhaustive discussion of every aspect of job searching. There are many other resources out there on the internet that have great recommendations.
This will be the first in a series of posts describing Tweets I’ve sent with the hashtag #awswishlist. Tweets to this #awswishlist hashtag come from anyone who uses AWS and is frustrated with the AWS user experience in some way. These Tweets are often responded to by AWS Support staff on Twitter, indicating they’ll be passing the feedback on to the team responsible for the AWS service. But in my tenure using AWS, I’ve only personally seen one wishlist item get resolved within a reasonable time frame.
Recently I moved my personal blog from GitHub Pages to AWS Amplify. While it was fairly easy to setup the Amplify project and CI/CD pieces, the DNS configuration for Custom Domains was less straightforward. The following observations are what I found to be less than ideal while using Amplify for the first time.
AWS Amplify DNS instructions One problem that I found with AWS Amplify, which was surprising for someone who is familiar with Route53 and DNS, is that the suggested instructions on the Amplify Domain Management page are somewhat cryptic.
Discourse is used for a number of purposes, but their forum software is quite
popular. I’ve been looking at how to us the Discourse
API to automate creating posts. This blog post
describes how to setup a local Discourse instance and perform API calls against
it.
