- PrivaceraCloud Release 4.5
- PrivaceraCloud User Guide
- PrivaceraCloud
- What is PrivaceraCloud?
- Getting Started with Privacera Cloud
- User Interface
- Dashboard
- Access Manager
- Discovery
- Usage statistics
- Encryption and Masking
- Privacera Encryption core ideas and terminology
- Encryption Schemes
- Encryption Schemes
- System Encryption Schemes Enabled by Default
- View Encryption Schemes
- Formats, Algorithms, and Scopes
- Record the Names of Schemes in Use and Do Not Delete Them
- System Encryption Schemes Enabled by Default
- Viewing the Encryption Schemes
- Formats, Algorithms, and Scopes
- Record the Names of Schemes in Use and Do Not Delete Them
- Encryption Schemes
- Presentation Schemes
- Masking schemes
- Create scheme policies on PrivaceraCloud
- Encryption formats, algorithms, and scopes
- Deprecated encryption formats, algorithms, and scopes
- PEG REST API on PrivaceraCloud
- PEG API Endpoint
- Request Summary for PrivaceraCloud
- Prerequisites
- Anatomy of a PEG API endpoint on PrivaceraCloud
- About constructing the datalist for /protect
- About deconstructing the response from /unprotect
- Example of data transformation with /unprotect and presentation scheme
- Example PEG REST API endpoints for PrivaceraCloud
- Audit details for PEG REST API accesses
- Make calls on behalf of another user on PrivaceraCloud
- Privacera Encryption UDF for masking in Databricks
- Privacera Encryption UDFs for Trino
- Syntax of Privacera Encryption UDFs for Trino
- Prerequisites for installing Privacera Crypto plug-in for Trino
- Variable values to obtain from Privacera
- Determine required paths to crypto jar and crypto.properties
- Download Privacera Crypto Jar
- Set variables in Trino etc/crypto.properties
- Restart Trino to register the Privacera Crypto UDFs for Trino
- Example queries to verify Privacera-supplied UDFs
- Azure AD setup
- Launch Pad
- Settings
- General functions in PrivaceraCloud settings
- Applications
- About applications
- Azure Data Lake Storage Gen 2 (ADLS)
- Athena
- Privacera Discovery with Cassandra
- Databricks
- Databricks SQL
- Dremio
- DynamoDB
- Elastic MapReduce from Amazon
- EMRFS S3
- Files
- File Explorer for Google Cloud Storage
- Glue
- Google BigQuery
- Kinesis
- Lambda
- Microsoft SQL Server
- MySQL for Discovery
- Open Source Spark
- Oracle for Discovery
- PostgreSQL
- Power BI
- Presto
- Redshift
- Redshift Spectrum
- Kinesis
- Snowflake
- Starburst Enterprise with PrivaceraCloud
- Starburst Enterprise Presto
- Trino
- Datasource
- User Management
- API Key
- About Account
- Statistics
- Help
- Apache Ranger API
- Reference
- Okta Setup for SAML-SSO
- Azure AD setup
- SCIM Server User-Provisioning
- AWS Access with IAM
- Access AWS S3 buckets from multiple AWS accounts
- Add UserInfo in S3 Requests sent via Dataserver
- EMR Native Ranger Integration with PrivaceraCloud
- Spark Properties
- Operational Status
- How-to
- Create CloudFormation Stack
- Enable Real-time Scanning of S3 Buckets
- Enable Discovery Realtime Scanning Using IAM Role
- How to configure multiple JSON Web Tokens (JWTs) for EMR
- Enable offline scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Real-time Scanning on Azure Data Lake Storage Gen 2 (ADLS)
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- PrivaceraCloud
- PrivaceraCloud Previews
- Privacera documentation changelog
Enable Discovery Realtime Scanning Using IAM Role
In this topic, you will learn how to use IAM roles to configure AWS S3 service for Privacera Discovery realtime scanning.
Create an IAM role with AWS S3 permissions
Log in to the AWS console.
Go to Identity and Access Management (IAM) and navigate to Access management > Roles.
Create a role or edit an existing AWS IAM role. Refer to AWS documentation on how to create an IAM Role.
Navigate to the role created or the role you are editing.
Open the role.
The role Summary page is displayed.
Copy the Role ARN.
Use the ARN in IAM Role ARN field when providing Application Properties details for the data source.
Add a policy to AWS IAM role.
Open the role you are editing.
Click Permissions tab.
On the Permissions Policies section, click Attach Policies or Add inline policy.
The Create policy page is displayed.
Click the JSON tab to add the policy and permissions.
Refer to the following sample permission JSON for the role on S3 bucket. Ensure your have Get and List actions in the permissions policy of the role and enter the bucket name in
bucket-name
.Note
You can scan multiple buckets in multiple regions or same region from a single IAM role that is configured as part of data source. This single IAM role should have access permission to access these buckets.
{ "Version": "2012-10-17", "Statement": [ { "Sid": "AllowAccountLevelS3Actions", "Effect": "Allow", "Action": [ "s3:ListAllMyBuckets", "s3:Get*" ], "Resource": "*" }, { "Sid": "AllowListAndReadS3ActionOnMyBucket", "Effect": "Allow", "Action": [ "s3:Get*", "s3:List*" ], "Resource": [ "arn:aws:s3:::bucket-name/*", "arn:aws:s3:::bucket-name", "arn:aws:s3:::bucket1-name/*", "arn:aws:s3:::bucket1-name", "arn:aws:s3:::bucket2-name/*", "arn:aws:s3:::bucket2-name", "arn:aws:s3:::bucket3-name/*", "arn:aws:s3:::bucket3-name", "arn:aws:s3:::bucket4-name/*", "arn:aws:s3:::bucket4-name", "arn:aws:s3:::bucket5-name/*", "arn:aws:s3:::bucket5-name", "arn:aws:s3:::bucket6-name/*", "arn:aws:s3:::bucket6-name" ] }, { "Sid": "AllowReadS3ActionOnMyQueue", "Effect": "Allow", "Action": [ "sqs:ReceiveMessage", "sqs:DeleteMessage", "sqs:GetQueueUrl" ], "Resource": [ "<ARN of SQS queue>" ] } ] }
Note
Multiple buckets of the same region can be configured to a single SQS queue. Bucket should be mapped to the configured SQS queue in the above policy.
Click Review policy.
The Review policy section is displayed.
Enter the policy Name and click Create policy.
Establish IAM Role Trust Relationship with Discovery Data Access Role.
Open the role role you are editing.
Click the Trust relationships tab.
Click Edit trust relationship.
Refer to the following JSON to add a new policy document.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::870790086151:role/DISCOVERY_PROD_DATA_ACCESS_ROLE", "Service": "s3.amazonaws.com" }, "Action": "sts:AssumeRole" } ] }
Click Update Trust Policy to save this revision.
Configure AWS S3 access using IAM role
Connect application
Go to Settings > Applications.
On the Applications screen, select S3.
Enter the application Name and Description, and then click Save.
You can see Privacera Access Management and Data Discovery with the toggle buttons.
Note
If you don't see Data Discovery in your application, enable it in Settings > Account > Discovery. For more information, see About Account
Enable Data Discovery
Click the toggle button to enable Data Discovery for your application.
On the BASIC tab, enter values in the following fields.
With Use IAM Role disabled:
AWS Access Key: AWS data repository host account Access Key.
AWS Secret Key: AWS data repository host account Secret Key.
AWS Region: AWS S3 bucket region.
For the first time, real-time discovery is disabled. See About Account for details on how to enable it.
With Use IAM Role enabled:
IAM Role ARN: Enter the actual IAM Role using a full AWS ARN.
AWS Region: AWS S3 bucket region.
On the ADVANCED tab, you can add custom properties.
Using the IMPORT PROPERTIES button, you can browse and import application properties.
Click the TEST CONNECTION button to check if the connection is successful, and then click Save.
Go to PrivaceraCloud > Privacera Discovery > Data Source to add a resources using this connection as Discovery targets. See Privacera Discovery scan targets for quick start steps.