Explanation of AWS MSK Connector Execution Role

Please add a picture description The book "Big Data Platform Architecture and Prototype Realization: Actual Combat in Data Center Construction" was carefully created by the blogger for three years, and has now been published by the famous IT book brand Electronics Industry Publishing House. Click "Heavy Recommendation: Jianda The data platform is too difficult! Send me an engineering prototype! " Learn more about books, JD book purchase link: https://item.jd.com/12677623.html , scan the QR code on the left to enter the JD mobile phone book purchase page.

Although Execution Role is a required item when creating AWS MSK Connector, as follows:
insert image description here
and the Execution Role sample given in the official document: https://docs.aws.amazon.com/msk/latest/ In developerguide/msk-connect-service-execution-role.html, the operation authority for a certain MSK cluster is often configured. This will lead to a misunderstanding, that is, it will make people mistakenly think that: MSK Connector must configure permissions for a certain MSK cluster, and then use Execution Role to obtain these permissions to access this MSK cluster, but in fact The logic is this:

1. Execution Role is indeed mandatory for MSK Connector!
2. The permission configuration for a certain MSK cluster in Execution Role is not necessary! In fact, it is only valid when the MSK cluster uses IAM authentication.
3. For a non-IAM-authenticated MSK cluster, the Execution Role of the MSK Connector may not contain any real Policy

Guess you like

Origin blog.csdn.net/bluishglc/article/details/131725002