Thunderbolt brings incredible performance but also some new security concerns. Delve into the new concerns so you don’t get fooled again.

In the last post, we discussed the concepts behind the valet key pattern. In this post, I will walk through how to perform this operation on AWS.

This is a continuation from a previous article and gets a lot more technical. It is not a part 2, but a branch. Think of it has a hub and spoke style collection of articles. This is the Amazon Web Services (AWS) spoke. I will be focusing on how to automate the user management on a jump host within the AWS cloud.

So far in this series, we’ve covered a lot of the technical aspects of object storage and have explored how they are implemented in both cloud providers. For this post, I’d like to examine a cloud architecture pattern called the valet key pattern, and discuss how to implement this in both Azure and AWS. In this post, lets talk about what the valet key pattern is.

It’s no secret that I believe privacy is going to be a major issue of discussion and chatter this year. As part of our first monthly newsletter, Keep Secure focused on user privacy and how to stay safe online. We’ve also chatted a bit about it in our security tasks for 2019 post.

Monitoring of object storage services in the public cloud is tightly integrated with the general monitoring services (read AWS CloudWatch, Azure Monitor) of those cloud providers. The goal for this post is to discuss how monitoring is conducted.