RANGER-1300 Ranger S3 Plugin Integration - #1177
Open
dishtikundra wants to merge 1 commit into
Open
Conversation
dishtikundra
force-pushed
the
RANGER-1300-dk
branch
from
August 24, 2026 10:29
cd09390 to
9720776
Compare
dishtikundra
force-pushed
the
RANGER-1300-dk
branch
from
August 24, 2026 10:40
9720776 to
10c2b09
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Ranger-S3 plugin extends Ranger's authorization capabilities to Amazon S3 resources, enabling centralized access control, and policy management for S3 buckets and objects accessed through various big data ecosystem components. This shall facilitate the Hadoop and data platform teams in managing S3 resource access internally without continuous DevOps support.
Ranger S3 service contains two types of S3 policies:
The user is required to create separate policies for buckets and objects with respective permissions.
Additionally, the plugin supports bi-directional sync between Ranger and IAM resource-based policy, with permissions set in Ranger taking precedence. Bi-directional sync here states that if IAM has additional users for given resource, changes in Ranger will be appended in existing policy at the IAM end. Additional users will not be visible on Ranger UI. If IAM resource-based policy has certain permissions to a user, and permissions are changed from Ranger UI for same user, then Ranger permissions shall be overwritten onto the resource-based policy in IAM.
The resultant statements in IAM policies shall be applied when Hadoop services access respective S3 resource (s).