AWS managedservices documentation change
Summary
Updated security group creation change type descriptions from 'review required' to 'manual' and corrected terminology.
Security assessment
The change clarifies process terminology (manual vs automated) for security group creation but does not introduce new security features or address vulnerabilities. Security groups are a security feature, but this update is procedural.
Diff
diff --git a/managedservices/latest/ctref/deployment-advanced-security-group-create-review-required.md b/managedservices/latest/ctref/deployment-advanced-security-group-create-review-required.md index bf738c627..c78e2a4ee 100644 --- a//managedservices/latest/ctref/deployment-advanced-security-group-create-review-required.md +++ b//managedservices/latest/ctref/deployment-advanced-security-group-create-review-required.md @@ -128 +128 @@ You receive the ID of the new RFC in the response and can use it to submit and m -There is an automated change type for creating a security group, Deployment | Advanced stack components | Security group | Create (no review required) (ct-3pc215bnwb6p7) that provides options for TCP and ICMP ingress and egress rules. If those rules are adequate, the Create (auto) change type will execute more quickly than this change type. For details, see [ Security Group | Create](https://docs.aws.amazon.com/managedservices/latest/ctref/deployment-advanced-security-group-create.html). +There is an automated change type for creating a security group, Deployment | Advanced stack components | Security group | Create (no managed automation) (ct-3pc215bnwb6p7) that provides options for TCP and ICMP ingress and egress rules. If those rules are adequate, the Create (auto) change type will execute more quickly than this change type. For details, see [ Security Group | Create](https://docs.aws.amazon.com/managedservices/latest/ctref/deployment-advanced-security-group-create.html). @@ -138 +138 @@ Outbound rules are not required; however, if they are not specified, then a "127 -This is a "review required" change type (an AMS operator must review and run the CT), which means that the RFC can take longer to run and you might have to communicate with AMS through the RFC details page correspondance option. Additionally, if you schedule a "review required" change type RFC, be sure to allow at least 24 hours, if approval does not happen before the scheduled start time, the RFC is rejected automatically. +This is a manual change type (an AMS operator must review and run the CT), which means that the RFC can take longer to run and you might have to communicate with AMS through the RFC details page correspondance option. Additionally, if you schedule a "review required" change type RFC, be sure to allow at least 24 hours, if approval does not happen before the scheduled start time, the RFC is rejected automatically.