Restricting Access to Call Lambda Functions to a VPC Endpoint in a Service Control Policy

ACM.314 An SCP policy with multiple conditions evaluated as NOT OR or NOR

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

⚙️ Check out my series on Automating Cybersecurity Metrics | Code.

🔒 Related Stories: Lambda | Container Security | Application Security

💻 Free Content on Jobs in Cybersecurity | ✉️ Sign up for the Email List

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In the last post, I was attempting to use IP addresses to restrict access to using the AWS IP restrictions in a Service Control Policy. It worked for public IPs but not private IP addresses.

AWS IP Conditions in an SCP Not Working With Private IP Ranges and Lambda VPC Endpoint

I felt like I was forgetting something (it happens) and sure enough while reading around I ran across this post:

Restrict access to AWS resources based on Region, IP, or VPC

Create an identity-based…