From Chaos to Order: Implementing a Robust S3 Strategy

In Rippling, initially there was no process or conventions for storing static assets in s3. Various teams were dumping the test and production assets in the same s3 bucket. As we were expanding our business to multiple regions, It started becoming more clumsier and I wanted to fix this.

I put forth a strategy for managing static assets for multiregion setup, it involved categorizing the static assets based on the end users and who uploads it. I implemented a solution for each category, helped team to migrate from old s3 bucket and CDN to new setup. And the hard part here was understanding the current requirements of various teams and also design a solution which is flexible for future expansions as well. For which I had to collaborate with various teams in the organization, convince them and help to migrate to the new setup without any downtime

Tt made a great impact at the organization level. Now each team has their own buckets for every region, but use single CDN for each category. It also improved the security posture of the assets which was uploaded by the customers.