Day 1 of re:Invent has come and gone and it was an epic start to the week. I’ve often heard it said that re:Invent is a marathon and not a sprint and that’s a very true statement. If you are reading this and are at the conference, pace yourself. And if you are at home watching virtually, do the same, but perhaps more mental pacing than physical.
Let’s dig into Day 1 of AWS re:Invent 2023.
Here goes the beginning of a nightly blog post recapping my experience at AWS re:Invent 2023 in Las Vegas. AWS re:Invent officially kicks off on Monday 11/27/2023 but for those of us who arrived early, the week started a bit early. Let’s recap Day 0.
For this series, I’m going to do a nightly recap of the things that I experienced at re:Invent. I plan to share my highlights from people I meet, exciting news drops or sessions I found to be fantastic.
I’ve had a few people ask me about my writing process and how I produced the articles and code that I do here on my blog. At first, I thought, no way anyone cares what it takes for me to produce the articles that I do. But as I stepped back and thought about it, looking back on my 1 year of solid writing I have developed a method to my creating. Hopefully, this proves useful and whether you are a veteran writer or just getting started, there could be something in here for you. Let’s dive in and take a look at writing a technical blog article.
I’ve been working recently with some data that doesn’t naturally fit into my AWS HealthLake datastore. I have some additional information captured in a DynamoDB table that would be useful to blend with HealthLake but on its own is not an FHIR resource. I pondered on this for a while and came up with the idea of piping DynamoDB stream changes to S3 so that I could then pick up with AWS Glue. In this article, I want to show you an approach to building a partitioned S3 bucket from DynamoDB. Refining that further with Glue jobs, tables and crawlers will come later.
I’ve been trying to learn Rust for the better part of this year. My curiosity peaked a few years back when I learned the AWS-led Firecracker was developed with the language. And I’ve continued to want to learn it ever since. Fast-forward and I’m jumping both feet in. That’s usually how I work. I must admit that right now, I’m the most noob of noobs, but that’s not going to keep me from sharing what I’m up to and what I’m learning. For me, this blog is as much about sharing as it is about learning and communicating to those reading that it’s OK to be where you are in your journey. There are no straight lines. Only periods of growth and plateaus. In this article, I’ll walk you through consuming an SQS Event with Lambda and Rust.
