rangareddy commented on issue #16909: URL: https://github.com/apache/hudi/issues/16909#issuecomment-5056598859
This issue was reviewed as part of the JIRA-migrated backlog triage. Findings: Cross-account access for the DynamoDB lock provider is already supported. `DynamoDBBasedLockProviderBase.getDynamoDBClient(...)` builds the DynamoDb client with `HoodieAWSCredentialsProviderFactory.getAwsCredentialsProvider(lockConfig.getProps())`. When `hoodie.aws.role.arn` is set, that factory installs `HoodieConfigAWSAssumedRoleCredentialsProvider` (STS `AssumeRole`) at the head of the credential chain, so the lock provider assumes the given role and can operate on a DynamoDB lock table in another AWS account. Optional `[hoodie.aws.role.external.id](http://hoodie.aws.role.external.id/)` and `hoodie.aws.role.session.name` are also supported (PR #11134 / HUDI-7699). This wiring has been in place since at least 0.14.0. To use a DynamoDB lock table in a different account, set `hoodie.aws.role.arn` (a role in the target account, trusted by your caller) together with your `hoodie.write.lock.dynamodb.*` configs — no code change is required. If this doesn't cover your use case, please reopen with details. Closing as already supported. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
