Simplifying An AWS Network Design

Today I was working on my container for my Lambda function to use as a trigger for AWS CodeCommit to push to an S3 bucket. I started by revamping my base container based on findings from prior posts so I can use a single container with all the base files required for my bash custom runtime. More on that in the next post. But first, networking has really been a drag on my productivity. <h2>The problems with my current approach and lack of automation</h2> As I work through developing and testing my Lambda function, I realize that my networking can be simplified, or maybe in some ways more complex in the short term but reduce cost and complexity in the long run. At the same time, I want to reduce the number of endpoints I need to deploy because apparently they are going to break the bank more than I expected. Along the way, I keep realizing I was missing some VPC Endpoints. Or one service doesn’t work so I have to tear down that endpoint and deploy a different one. <a href="https://medium.com/cloud-security/simplifying-our-network-design-af4fc8916d22">Read More</a>