AWS msk documentation change
Summary
Added 'Maximum Autoscaling Task Count' configuration option and reordered connector creation steps (worker configuration and service execution role steps swapped).
Security assessment
The changes introduce a new autoscaling parameter and adjust procedural steps without modifying security content. No security vulnerabilities or security features are mentioned in the diff.
Diff
diff --git a/msk/latest/developerguide/mkc-create-connector-intro.md b/msk/latest/developerguide/mkc-create-connector-intro.md index 66e4cbe84..4006cc91c 100644 --- a//msk/latest/developerguide/mkc-create-connector-intro.md +++ b//msk/latest/developerguide/mkc-create-connector-intro.md @@ -46 +46 @@ This procedure describes how to create a connector using the AWS Management Cons - 10. Choose either the default worker configuration or a custom worker configuration. For information about creating custom worker configurations, see [Understand MSK Connect workers](./msk-connect-workers.html). + 10. (Optional) In the **Maximum Autoscaling Task Count** section, use the Maximum Autoscaling Task Count field to enter the maximum number of tasks you want to allocate to the connector during autoscaling operations. The value must be at least equal to your maximum worker count. If you don't specify a value, the connector uses the standard calculation without any limit. For more information, see [Understand maximum autoscaling task count](./msk-connect-max-autoscaling-task-count.html). @@ -48 +48 @@ This procedure describes how to create a connector using the AWS Management Cons - 11. Next, you specify the service execution role. This must be an IAM role that MSK Connect can assume, and that grants the connector all the permissions that it needs to access the necessary AWS resources. Those permissions depend on the logic of the connector. For information about how to create this role, see [Understand service execution role](./msk-connect-service-execution-role.html). + 11. Choose either the default worker configuration or a custom worker configuration. For information about creating custom worker configurations, see [Understand MSK Connect workers](./msk-connect-workers.html). @@ -50 +50 @@ This procedure describes how to create a connector using the AWS Management Cons - 12. Choose **Next** , review the security information, then choose **Next** again. + 12. Next, you specify the service execution role. This must be an IAM role that MSK Connect can assume, and that grants the connector all the permissions that it needs to access the necessary AWS resources. Those permissions depend on the logic of the connector. For information about how to create this role, see [Understand service execution role](./msk-connect-service-execution-role.html). @@ -52 +52 @@ This procedure describes how to create a connector using the AWS Management Cons - 13. Specify the logging options that you want, then choose **Next**. For information about logging, see [Logging for MSK Connect](./msk-connect-logging.html). + 13. Choose **Next** , review the security information, then choose **Next** again. @@ -54 +54,3 @@ This procedure describes how to create a connector using the AWS Management Cons - 14. On the **Review and create** page, review your connector configuration and choose **Create connector**. + 14. Specify the logging options that you want, then choose **Next**. For information about logging, see [Logging for MSK Connect](./msk-connect-logging.html). + + 15. On the **Review and create** page, review your connector configuration and choose **Create connector**.