The AWS-v3 integration's Organizations-based multi-account discovery requires the management-account role and every member-account role to share the exact same IAM role name. When Organizations discovery is enabled via , the integration builds each member account's role ARN by reusing that same role's name and only swapping in the account ID. There is no way to configure a different role name for member accounts, even though the underlying trust model (each account trusting the integration's identity directly) doesn't require the names to match.

This blocks migration to AWS-v3 for organizations where the org-discovery role (used to list AWS Organization accounts) is named differently from the read-only role deployed to member accounts, a common pattern when these roles are owned or deployed by different teams.