How do you handle network egress filtering when an agent legitimately needs to install dependencies or pull docs versus preventing arbitrary outbound traffic during autonomous execution?
Rules can be per Security Group, too, for fine-grained access control. I would also strongly recommend that installation of dependencies is a build-time task, not a run-time task, and if those two stages are separated, it makes egress filtering a whole lot more effective since the build-time allowlists are often multi-tenant CDNs where a threat actor can host their own data capturing or malicious payload delivering service.