AWS batch documentation change
Summary
Minor punctuation fixes (adding periods to list items) and rephrasing of a recommendation sentence from 'Blue/green updates are particularly recommended' to 'We recommend blue/green updates'.
Security assessment
The changes are purely editorial and grammatical, adding periods to the end of list items and slightly rephrasing a recommendation for clarity. There is no mention of security vulnerabilities, incidents, or security features. The content remains focused on operational best practices for updates.
Diff
diff --git a/batch/latest/userguide/blue-green-updates.md b/batch/latest/userguide/blue-green-updates.md index c7f0b0d39..78b977f6a 100644 --- a//batch/latest/userguide/blue-green-updates.md +++ b//batch/latest/userguide/blue-green-updates.md @@ -19 +19 @@ You must use blue/green updates in the following situations: - * When your compute environment uses `BEST_FIT` allocation strategy (doesn't support infrastructure updates) + * When your compute environment uses `BEST_FIT` allocation strategy (doesn't support infrastructure updates). @@ -21 +21 @@ You must use blue/green updates in the following situations: - * When your compute environment doesn't use the _AWSServiceRoleForBatch_ service-linked role + * When your compute environment doesn't use the _AWSServiceRoleForBatch_ service-linked role. @@ -23 +23 @@ You must use blue/green updates in the following situations: - * When you need to transition between different service role types + * When you need to transition between different service role types. @@ -30 +30 @@ You must use blue/green updates in the following situations: -Blue/green updates are particularly recommended for production environments where zero downtime is critical for your workloads. This approach works well when you need to test new configurations before transitioning production workloads, ensuring that changes meet your performance and reliability requirements. Choose blue/green updates when quick rollback capability is important for your operations, especially if you're updating custom AMIs with significant changes. This method is also ideal when you want to validate performance characteristics and behavior before fully committing to changes, providing confidence in your update process. +We recommend blue/green updates for production environments where zero downtime is critical for your workloads. This approach works well when you need to test new configurations before transitioning production workloads, ensuring that changes meet your performance and reliability requirements. Choose blue/green updates when quick rollback capability is important for your operations, especially if you're updating custom AMIs with significant changes. This method is also ideal when you want to validate performance characteristics and behavior before fully committing to changes, providing confidence in your update process. @@ -36 +36 @@ Before performing a blue/green update, ensure you have: - * Appropriate [IAM permissions](./IAM_policies.html#IAM_policies.title) to create and manage compute environments + * Appropriate [IAM permissions](./IAM_policies.html#IAM_policies.title) to create and manage compute environments. @@ -38 +38 @@ Before performing a blue/green update, ensure you have: - * Access to view and modify job queue settings + * Access to view and modify job queue settings. @@ -44 +44 @@ Before performing a blue/green update, ensure you have: - * A recent, approved version of the Amazon ECS optimized AMI (used by default) + * A recent, approved version of the Amazon ECS optimized AMI (used by default). @@ -48 +48 @@ Before performing a blue/green update, ensure you have: - * Using the **Image ID override** field in the EC2 configuration + * Using the **Image ID override** field in the EC2 configuration. @@ -50 +50 @@ Before performing a blue/green update, ensure you have: - * Specifying it in a launch template + * Specifying it in a launch template.