Cloud

Busy Holidays? You’ll find below my preferred papers from this summer, 2024 🏖️ Cloud Security Holding Cloud Vendors to a Higher Security Bar An AWS IAM Security Tooling Reference [2024] AWS Organizations Viewer Are my AWS Resources Encrypted or Unencrypted by Default? Strategies for performing security migrations Infrastructure Continuous reinvention: A brief history of block storage at AWS DNS best practices for Amazon Route 53 Introducing Parameter Store cross-account sharing Engineering The Over-Engineering Trap Anyone can Access Deleted and Private Repository Data on GitHub That’s all, folks! 👋🏼 ...

Background I started my career in the glass industry as a SysAdmin, specifically in a glass factory crafting fragrance bottles and bottles for pharmaceutical industries in the north of France. Since then, I’ve focused on IT security and cloud computing. After many full-time positions for Microsoft, French Logistic Railroad, and IT Consulting parties, I decided to run my AWS consulting boutique by myself 5 years ago. Just at the beginning of the pandemic, what a visionary… ...

Purpose Recently, I was working on a centralized explicit proxy service for one of my customers using a well-known Squid Internet proxy. The infrastructure is built on top of a shared AWS account hosting all standard infrastructure services, such as Internet Proxy, SOCKS5 Proxy, DNS Resolvers, ADDC, Centralized logging, and much more. Consumers are using the Internet Proxy service from multiple child AWS accounts and regions within the client AWS Organization thanks to AWS PrivateLink. ...

Following a post from my friend Julien Delange (Tech Ramblings) on software over-engineering, I want to share my thoughts about over-architecting in my preferred field of Public Cloud Architecture. Background I have been doing Cloud Architecture for more than ten years and have seen many different scenarios and use cases, from startups to GAFAM and multiple company verticals, from TV audience measurement to Gambling and Energy Producers. I also frequently challenge my fellow architects’ decisions. ...

This post was updated in July 2020. It was originally my first post on this blog in December 2016. 👴 I’m often asked by many colleagues, friends, or Twitter followers where to start with Amazon Web Services (AWS). In this post, I will try to explain where you should start in 2020. I’ll try to write this post as I wish I had in 2016 when I came into this technology. Basically, with the number of AWS Services today (197 top-level services (April 2020)), you will need to find your path and specialty, you will not become “an” AWS expert. It’s not possible, or you will be a generalist expert… ...