Acante for AWS

Identify, Understand & Reduce Data Risks in the Cloud With a completely agentless deployment that takes less than 15 mins, the process described below will enable a holistic assessment of Data Risk in your cloud environment. The Key Product Ca...

Customer Managed Key Permissions for S3 If the S3 buckets or objects are encrypted using a Customer Managed Key with customized permissions, then the Acante classifier needs permissions to use this Key to decrypt and classify the data. Note: Thi...

Customer Managed Key Permissions for RDS If the RDS instances are encrypted using a Customer Managed Key with customized permissions, then the Acante lambda needs permissions to use this Key to decrypt and restore the RDS snapshots for classificat...

Upgrading an Existing Deployment From time to time Acante will push updates to the components deployed within the customer VPC. Some of these changes will require an upgrade to the deployment, such as: Change in permissions assumed by the cros...

When extending the Acante deployment to additional regions in an account, follow a similar deployment process for each region with a different terraform workspace for each region. Start in the same folder where the terraform code for the primar...

When extending the Acante deployment to an additional 1-4 accounts, the simplest approach is to follow the similar deployment process (as the Product Deployment Guide - Deploy Acante Components ). When deploying in a large number (> 5) of accoun...

Hybrid SaaS Architecture: Secure by Design Acante's is deployed as a "Hybrid SaaS" architecture to provide both ease of deployment and ensure security of customer data. All sensitive customer data remains in the customer environment, only meta-dat...