AWS batch documentation change
Summary
Clarified security group behavior for multi-node parallel jobs, explicitly stating they don't use launch template security groups
Security assessment
Documents security group configuration behavior which could prevent misconfiguration risks, but no evidence of a specific security issue being fixed.
Diff
diff --git a/batch/latest/userguide/mnp-ce.md b/batch/latest/userguide/mnp-ce.md index baa266f41..a21d992de 100644 --- a//batch/latest/userguide/mnp-ce.md +++ b//batch/latest/userguide/mnp-ce.md @@ -19 +19 @@ There are several things to consider when configuring compute environments to ru - * Your compute environment might have no more than five security groups associated with it. The elastic network interfaces that are created and attached to an MNP task will use the security groups specified in your compute environment, If you don't specify a security group, the default security group for the VPC is used. + * Your compute environment might have no more than five security groups associated with it. The elastic network interfaces that are created and attached to an MNP task will use the security groups specified in your compute environment, If you don't specify a security group, the default security group for the VPC is used. Unlike regular AWS Batch jobs, multi-node parallel jobs do not use security groups specified in launch templates.