Building a Container for AWS Batch vs. AWS Lambda
ACM.332 Also trying to figure out which IP ranges are required for trusted downloads
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
⚙️ Check out my series on Automating Cybersecurity Metrics | Code.
🔒 Related Stories: Lambda | Secure Code | Container Security | Batch
💻 Free Content on Jobs in Cybersecurity | ✉️ Sign up for the Email List
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In the last post I explored what changes I would need to make to move my container from Lambda to Batch because it’s not working in Lambda and I’m curious about using Batch long term anyway.
In this post I’m going to make some changes to my container so it works with AWS Batch. Now you may recall that I added some network restrictions to my EC2 network where I’m running docker to build my container. I did that after I built most of my initial Lambda function. That means my Dockerfile is now running from a private network with additional network restrictions that did not exist before. Let’s see what happens. And by the way I’ll address this further in a future…
