Sanderknape.com Website Review

blocking account-wide creation of public s3 buckets through a cloudformation custom resource. yesterday, aws announced the release of an important and much-wanted new feature for s3: blocking the creation of public s3 buckets on an account-wide. enough has been written already about open s3 buckets on the internet. given that it is very simple to create a public s3 bucket, we regularly learn about new (big) companies that have exposed privacy-sensitive data to the world through such buckets. the confusion is mainly around opening up your bucket to “everyone”. local development environment is kept as close as possible to production using technology such as docker or aws sam when working with aws lambda. however, when working with aws resources through identity and access management (iam) policies, local iam permissions are typically different from the permissions the application will have in aws. it’s been close to two years since i started working with aws cloudformation, the infrastructure as code solution by and for aws. with cloudformation you can describe and provision your entire aws infrastructure in code. the entire aws environment i work with is provisioned through cloudformation - we only have read-only access to our aws accounts. we now work with a number of different vpcs and many serverless is a relatively new term. it’s a software development paradigm where the entire concept of a “server” is abstracted away from the development process. you essentially only use managed services that handle scaling, and you pay only for what you use. you no longer need to think about operating systems, security patches, scaling configuration and more. all this is handled for you behind the scenes. the most well-known example is aws lambda, though as we will see in this blog post, serverless is much more than that. aws secrets manager is a service recently released designed to make the management of secrets easier. it provides built-in support for