[ https://issues.apache.org/jira/browse/RANGER-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658309#comment-16658309 ]
Bolke de Bruin commented on RANGER-1300: ---------------------------------------- Update we have set a team to work at this. We have created a S3 proxy that is now MVP. It works for on prem situations in front of Ceph/RadosGW or (with some modifications) in case you can assure a proxy in front of Amazon S3. We have created 2 different services to support this. * [https://github.com/ing-bank/airlock-sts] which implements a subset of Amazon's STS * [https://github.com/ing-bank/airlock] the actual proxy Lineage is recorded in Atlas if configured to do so. We probably split this off when Airlock starts supporting bucket notifications per S3 bucket notifications. Both are Apache 2 licensed and we do accept pull requests. Have a look at the architecture and try it out. P.S. It obviously does not sync Ranger policies with S3 policies. We dont have such a need (yet). We will accept changes to support this if required. > S3 support > ---------- > > Key: RANGER-1300 > URL: https://issues.apache.org/jira/browse/RANGER-1300 > Project: Ranger > Issue Type: New Feature > Components: plugins > Reporter: Jose > Priority: Major > Attachments: ranger-servicedef-aws-s3.json > > > As more and more people are deploying hadoop into AWS and as S3 is used in > lots of application. It'd be nice to have S3 support built into Ranger. > It's not a trivial task. Right now Ranger Storage support (only hdfs) runs > directly in the Namenode -- This message was sent by Atlassian JIRA (v7.6.3#76005)