- PrivaceraCloud Release 7.4
- Enhancements and updates in PrivaceraCloud release 7.4
- Known Issues in PrivaceraCloud 7.4
- PrivaceraCloud User Guide
- Overview of PrivaceraCloud
- Connect applications with the setup wizard
- Connect applications
- About applications
- Connect Azure Data Lake Storage Gen 2 (ADLS) to PrivaceraCloud
- Connect Amazon Textract to PrivaceraCloud
- Athena
- Privacera Discovery with Cassandra
- Connect Databricks to PrivaceraCloud
- Databricks SQL
- Databricks SQL Overview and Configuration
- Planning and general process
- Prerequisites
- Databricks SQL with Privacera Hive
- Connect Databricks SQL application
- Grant Databricks SQL permissions to PrivaceraCloud users
- Define a resource policy
- Test the policy
- Databricks SQL PolicySync fields
- Configuring column-level access control
- View-based masking functions and row-level filtering
- Create an endpoint in Databricks SQL
- Databricks SQL Fields
- Databricks SQL Hive Service Definition
- Databricks SQL Masking Functions
- Databricks SQL Encryption
- Use a custom policy repository with Databricks
- Connect Databricks SQL to Hive policy repository on PrivaceraCloud
- Databricks SQL Overview and Configuration
- Connect Databricks Unity Catalog to PrivaceraCloud
- Connect S3 to PrivaceraCloud
- Prerequisites in AWS console
- Connect S3 application to PrivaceraCloud
- Enable Privacera Access Management for S3
- Enable Data Discovery for S3
- S3 AWS Commands - Ranger Permission Mapping
- S3
- AWS Access with IAM
- Access AWS S3 buckets from multiple AWS accounts
- Add UserInfo in S3 Requests sent via Dataserver
- Control access to S3 buckets with AWS Lambda function on PrivaceraCloud
- Dremio Plugin
- DynamoDB
- Connect Elastic MapReduce from Amazon application to PrivaceraCloud
- Connect EMR application
- EMR Spark access control types
- PrivaceraCloud configuration
- AWS IAM roles using CloudFormation setup
- Create a security configuration
- Create EMR cluster
- How to configure multiple JSON Web Tokens (JWTs) for EMR
- EMR Native Ranger Integration with PrivaceraCloud
- Connect EMRFS S3 to PrivaceraCloud
- Files
- GBQ
- Google Cloud Storage
- Connect Glue to PrivaceraCloud
- Google BigQuery for PolicySync
- Connect Kinesis to PrivaceraCloud
- Connect Lambda to PrivaceraCloud
- Microsoft SQL Server
- MySQL for Discovery
- Open Source Apache Spark
- Oracle for Discovery
- PostgreSQL
- Connect Power BI to PrivaceraCloud
- Presto
- Redshift
- Snowflake
- Starburst Enterprise with PrivaceraCloud
- Starburst Enterprise Presto
- Trino
- Connect users
- Data access Users, Groups, and Roles
- UserSync
- Portal user LDAP/AD
- Datasource
- Okta Setup for SAML-SSO
- Azure AD setup
- SCIM Server User-Provisioning
- User Management
- Identity
- Access Manager
- Access Manager
- Resource Policies
- Tag Policies
- Scheme Policies
- Service Explorer
- Reports
- Audit
- About data access users, groups, and roles resource policies
- Security zones
- Discovery
- Classifications via random sampling
- Privacera Discovery scan targets
- Propagate Privacera Discovery Tags to Ranger
- Enable offline scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Real-time Scanning of S3 Buckets
- Enable Real-time Scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Discovery Realtime Scanning Using IAM Role
- Encryption
- Overview of Privacera Encryption
- Encryption schemes
- Presentation schemes
- Masking schemes
- Create scheme policies
- Privacera-supplied encryption schemes for the Privacera API
- Privacera-supplied encryption schemes for the Bouncy Castle API
- API date input formats
- Deprecated encryption formats, algorithms, and scopes
- Privacera Encryption REST API
- PEG API endpoint
- PEG REST API encryption endpoints
- Prerequisites
- Common PEG REST API fields
- Construct the datalist for the /protect endpoint
- Deconstruct the response from the /unprotect endpoint
- Example data transformation with the /unprotect endpoint and presentation scheme
- Example PEG API endpoints
- Make encryption API calls on behalf of another user
- Privacera Encryption UDF for masking in Databricks on PrivaceraCloud
- Privacera Encryption UDFs for Trino on PrivaceraCloud
- Syntax of Privacera Encryption UDFs for Trino
- Prerequisites for installing Privacera Crypto plug-in for Trino
- Download and install Privacera Crypto jar
- Set variables in Trino etc/crypto.properties
- Restart Trino to register the Privacera encryption and masking UDFs for Trino
- Example queries to verify Privacera-supplied UDFs
- Privacera Encryption UDF for masking in Trino on PrivaceraCloud
- Encryption UDFs for Apache Spark on PrivaceraCloud
- Launch Pad
- Settings
- Dashboard
- Usage statistics
- Operational status of PrivaceraCloud and RSS feed
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- PrivaceraCloud Previews
- Preview: File Explorer for S3
- Preview: File Explorer for Azure
- Preview: File Explorer for GCS
- Preview: Scan Generic Records with NER Model
- Preview: Scan Electronic Health Records with NER Model
- Preview: OneLogin setup for SAML-SSO
- Preview: Azure Active Directory SCIM Server UserSync
- Preview: OneLogin UserSync
- Preview: PingFederate UserSync
- Quickstart for Databricks Unity Catalog on PrivaceraCloud
- What do I need to do in my Databricks Workspace?
- Where is the sample dataset in my Databricks Workspace?
- What should I do in the PrivaceraCloud web portal?
- Access use-case - How do I give a user access to a table or restrict from running a SQL select query?
- Access use-case - How do I restrict a user from seeing contents of a column in the result of a SQL select query?
- Column masking use-case - How do I restrict a user from seeing contents of a column by masking the values in the result of a SQL select query?
- Access use-case - How do I disallow a user from seeing certain rows of a table?
- PrivaceraCloud documentation changelog
Recommended CloudFormation setup: IAM roles
The following three IAM roles need to be created before launching the cluster.
A custom Amazon EC2 instance profile for Amazon EMR, this will be attached to all the cluster nodes: EmrNativePrivaceraInstanceRole.
An IAM role for Apache Ranger Engines, this will be used for data access from S3: EmrNativePrivaceraDataAccessRole
An IAM role for other AWS services, this will be used to attach any other required permissions for the user on EMR cluster: *EmrNativePrivaceraUserAccessRole
These can be created easily with required minimal permission using the following CloudFormation template. You can modify the template based on your requirements (if required).
Sample CloudFormation template:
{ "AWSTemplateFormatVersion": "2010-09-09", "Description": "Create roles and policies for use by Emr-Native Ranger with Privacera", "Parameters": { "EmrNativePrivaceraInstanceRole": { "Description": "IAM Role which will be attached to all Instances in the cluster. Should have minimal permissions. e.g. emr_native_privacera_restricted_instance_role", "Type": "String", "Default": "emr_native_privacera_restricted_instance_role" }, "EmrNativePrivaceraDataAccessRole": { "Description": "IAM Role which will be used by EMR Applications for accessing actual S3 Data. e.g. emr_native_privacera_data_access_role", "Type": "String", "Default": "emr_native_privacera_data_access_role" }, "EmrNativePrivaceraUserAccessRole": { "Description": "IAM Role which will allows users to interact with AWS Services. Shouldn't be used to access s3 Data. e.g. emr_native_privacera_user_access_role", "Type": "String", "Default": "emr_native_privacera_user_access_role" }, "RangerPluginKeyPairSecretArn": { "Description": "Full ARN of secret [stored in AWS Secrets Manager] for ranger plugin key-pair. e.g. arn:aws:secretsmanager:us-east-1:999999999999:secret:ranger-plugin-cert-k4xsLM", "Type": "String", "Default": "" }, "RangerAdminPublicSecretArn": { "Description": "Full ARN of secret [stored in AWS Secrets Manager] for ranger admin public cert. e.g arn:aws:secretsmanager:us-east-1:999999999999:secret:ranger-admin-cert-3W5Zdt", "Type": "String", "Default": "" }, "Region": { "Description": "AWS Region where cluster will be created. e.g. us-east-1", "Type": "String", "Default": "us-east-1" }, "CloudwatchLogGroupName": { "Description": "CloudWatch Log group name which will be used to store RangerAudits. This should be an existing one e.g. emr_native_privacera_audits", "Type": "String", "Default": "" }, "AwsAcctId": { "Description": "Account ID of your Amazon Account. e.g. 999999999999", "Type": "String", "Default": "" }, "LogsBucketS3": { "Description": "S3 path to store emr logs (without the protocol). e.g. privacera-logs/emr-native-logs", "Type": "String", "Default": "" } }, "Resources": { "EmrPrivaceraInstanceRole": { "Type": "AWS::IAM::Role", "Properties": { "RoleName": { "Fn::Sub": "${EmrNativePrivaceraInstanceRole}" }, "AssumeRolePolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "ec2.amazonaws.com" ] }, "Action": [ "sts:AssumeRole" ] } ] }, "Path": "/" } }, "EmrPrivaceraInstancePolicy": { "Type": "AWS::IAM::Policy", "Properties": { "PolicyName": { "Fn::Join": [ "", [ "emr_native_privacera_instance_policy" ] ] }, "PolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Sid": "EmrServiceLimited", "Effect": "Allow", "Resource": "*", "Action": [ "ec2:Describe*", "elasticmapreduce:Describe*", "elasticmapreduce:ListBootstrapActions", "elasticmapreduce:ListClusters", "elasticmapreduce:ListInstanceGroups", "elasticmapreduce:ListInstances", "elasticmapreduce:ListSteps", "glue:CreateDatabase", "glue:UpdateDatabase", "glue:DeleteDatabase", "glue:GetDatabase", "glue:GetDatabases", "glue:CreateTable", "glue:UpdateTable", "glue:DeleteTable", "glue:GetTable", "glue:GetTables", "glue:GetTableVersions", "glue:CreatePartition", "glue:BatchCreatePartition", "glue:UpdatePartition", "glue:DeletePartition", "glue:BatchDeletePartition", "glue:GetPartition", "glue:GetPartitions", "glue:BatchGetPartition", "glue:CreateUserDefinedFunction", "glue:UpdateUserDefinedFunction", "glue:DeleteUserDefinedFunction", "glue:GetUserDefinedFunction", "glue:GetUserDefinedFunctions" ] }, { "Sid": "EmrS3Limited", "Effect": "Allow", "Action": "s3:*", "Resource": [ "arn:aws:s3:::*.elasticmapreduce/*", "arn:aws:s3:::elasticmapreduce/*", "arn:aws:s3:::elasticmapreduce", { "Fn::Sub": "arn:aws:s3:::${LogsBucketS3}" }, { "Fn::Sub": "arn:aws:s3:::${LogsBucketS3}/*" } ] }, { "Sid": "AllowAssumeOfRolesAndTagging", "Effect": "Allow", "Action": [ "sts:TagSession", "sts:AssumeRole" ], "Resource": [ { "Fn::Sub": "arn:aws:iam::${AwsAcctId}:role/${EmrNativePrivaceraDataAccessRole}" }, { "Fn::Sub": "arn:aws:iam::${AwsAcctId}:role/${EmrNativePrivaceraUserAccessRole}" } ] }, { "Sid": "AllowSecretsRetrieval", "Effect": "Allow", "Action": "secretsmanager:GetSecretValue", "Resource": [ { "Fn::Sub": "${RangerPluginKeyPairSecretArn}" }, { "Fn::Sub": "${RangerAdminPublicSecretArn}" } ] } ] }, "Roles": [ { "Ref": "EmrPrivaceraInstanceRole" } ] } }, "EmrPrivaceraUserAccessRole": { "Type": "AWS::IAM::Role", "Properties": { "RoleName": { "Fn::Sub": "${EmrNativePrivaceraUserAccessRole}" }, "AssumeRolePolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "ec2.amazonaws.com" ] }, "Action": [ "sts:AssumeRole" ] }, { "Effect": "Allow", "Principal": { "AWS": { "Fn::GetAtt": [ "EmrPrivaceraInstanceRole", "Arn" ] } }, "Action": "sts:AssumeRole" } ] }, "Path": "/" } }, "EmrPrivaceraDataAccessRole": { "Type": "AWS::IAM::Role", "Properties": { "RoleName": { "Fn::Sub": "${EmrNativePrivaceraDataAccessRole}" }, "AssumeRolePolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "ec2.amazonaws.com" ] }, "Action": [ "sts:AssumeRole" ] }, { "Effect": "Allow", "Principal": { "AWS": { "Fn::GetAtt": [ "EmrPrivaceraInstanceRole", "Arn" ] } }, "Action": "sts:AssumeRole" } ] }, "Path": "/" } }, "DataAccessPolicy": { "Type": "AWS::IAM::Policy", "Properties": { "PolicyName": { "Fn::Join": [ "", [ "emr_native_privacera_data_access_policy" ] ] }, "PolicyDocument": { "Version": "2012-10-17", "Statement": [ { "Sid": "CloudwatchLogsPermissions", "Action": [ "logs:CreateLogGroup", "logs:CreateLogStream", "logs:PutLogEvents" ], "Effect": "Allow", "Resource": [ { "Fn::Sub": "arn:aws:logs:${Region}:${AwsAcctId}:log-group:${CloudwatchLogGroupName}:*" } ] }, { "Sid": "BucketPermissionsInS3Buckets", "Action": [ "s3:CreateBucket", "s3:DeleteBucket", "s3:ListAllMyBuckets", "s3:ListBucket" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::examplebucket" ] }, { "Sid": "ObjectPermissionsInS3Objects", "Action": [ "s3:GetObject", "s3:DeleteObject", "s3:PutObject" ], "Effect": "Allow", "Resource": [ "arn:aws:s3:::examplebucket/*" ] } ] }, "Roles": [ { "Ref": "EmrPrivaceraDataAccessRole" } ] } }, "EmrPrivaceraInstanceProfile": { "Type": "AWS::IAM::InstanceProfile", "Properties": { "InstanceProfileName": { "Ref": "EmrNativePrivaceraInstanceRole" }, "Roles": [ { "Ref": "EmrPrivaceraInstanceRole" } ] } }, "EmrNativePrivaceraDataAccessProfile": { "Type": "AWS::IAM::InstanceProfile", "Properties": { "InstanceProfileName": { "Ref": "EmrNativePrivaceraDataAccessRole" }, "Roles": [ { "Ref": "EmrPrivaceraDataAccessRole" } ] } }, "EmrNativePrivaceraUserAccessProfile": { "Type": "AWS::IAM::InstanceProfile", "Properties": { "InstanceProfileName": { "Ref": "EmrNativePrivaceraUserAccessRole" }, "Roles": [ { "Ref": "EmrPrivaceraUserAccessRole" } ] } } }, "Outputs": { "EmrNativePrivaceraInstanceRole": { "Value": { "Ref": "EmrPrivaceraInstanceRole" } }, "EmrNativePrivaceraDataAccessRole": { "Value": { "Ref": "EmrPrivaceraDataAccessRole" } }, "EmrNativePrivaceraUserAccessRole": { "Value": { "Ref": "EmrPrivaceraUserAccessRole" } } } }
To know about how to create a stack using CloudFormation template, see Create CloudFormation stack.
After the above stack is created successfully, you will have three IAM roles. Use EmrNativePrivaceraDataAccessRole IAM Role, to give access for S3 data to the Apache Ranger services.
For detailed information, see IAM roles for native integration with Apache Ranger