Connector Improvement: Allow for user-specific value of CloudWatch Log Service External ID
AnsweredHello,
We are interested in using your connector Log Service feature for CloudWatch, but it currently contains a significant drawback. When configuring this feature, the External ID field is not editable and locked to the ID of the connector's parent group. This creates a maintenance burden for any client that needs to setup many (100+) connectors, where they now have to create separate IAM Roles in AWS for each connector. Ideally, we would like to specify this External ID and make it common across many connectors, thus only requiring a single IAM Role.
-
Official comment
Hi Colin,
Thanks for writing in. I'm not sure I understand the use case you're describing here. Why is it that one IAM role is required per connector? In your scenario, is each connector syncing to a unique destination?
Best,Ray
Please sign in to leave a comment.
Comments
1 comment