AWS solutions documentation change
Summary
Formatting changes including apostrophe corrections, typo fixes (e.g., 'Ket' to 'Key'), and restructuring image placement for KMS key documentation.
Security assessment
Changes involve typographical corrections and document structure adjustments. No new security content or vulnerability fixes are introduced.
Diff
diff --git a/solutions/latest/instance-scheduler-on-aws/security-1.md b/solutions/latest/instance-scheduler-on-aws/security-1.md index f861afd35..277809230 100644 --- a/solutions/latest/instance-scheduler-on-aws/security-1.md +++ b/solutions/latest/instance-scheduler-on-aws/security-1.md @@ -17 +17 @@ The solution creates an AWS managed Customer managed key, which is used to confi -The solution's Lambda functions require permissions to access hub account resources and access to get/put Systems Manager parameters, access to CloudWatch log groups, AWS KMS key encryption/decryption, and publish messages to SNS. In addition, Instance Scheduler on AWS will also create Scheduling Roles in all managed accounts that will provide access to start/stop EC2, RDS, Autoscaling resurces, DB instances, modify instance attributes, and update tags for those resources. All the necessary permissions are provided by the solution to Lambda service role created as part of the solution template. +The solution’s Lambda functions require permissions to access hub account resources and access to get/put Systems Manager parameters, access to CloudWatch log groups, AWS KMS key encryption/decryption, and publish messages to SNS. In addition, Instance Scheduler on AWS will also create Scheduling Roles in all managed accounts that will provide access to start/stop EC2, RDS, Autoscaling resurces, DB instances, modify instance attributes, and update tags for those resources. All the necessary permissions are provided by the solution to Lambda service role created as part of the solution template. @@ -27 +27 @@ When scheduling EC2 instances attached to EBS volumes encrypted by AWS KMS, you -To grant permission to use an AWS KMS key with Instance Scheduler on AWS, add the AWS KMS key's ARN to the Instance Scheduler on AWS stack (hub or spoke) in the same account as the EC2 instance(s) using the key(s): +To grant permission to use an AWS KMS key with Instance Scheduler on AWS, add the AWS KMS key’s ARN to the Instance Scheduler on AWS stack (hub or spoke) in the same account as the EC2 instance(s) using the key(s): @@ -29 +29 @@ To grant permission to use an AWS KMS key with Instance Scheduler on AWS, add th - +**KMS Key Arns for EC2** @@ -31 +31 @@ To grant permission to use an AWS KMS key with Instance Scheduler on AWS, add th -_**KMS Ket Arns for EC2**_ +