Skip to main content
Version: Next

Prerequisites

Before you begin the process of deploying Glasswall's CDR Platform, check that you have the following tools and resources installed and setup.

Required Tools​

Required AWS Resources​

1. EKS cluster​

  • Recommended total of at least 8 vCPU and 32 GB RAM.
  • Minimum node size is 4 vCPU and 16 GB RAM.
  • For production workloads a minimum of 2 nodes is recommended.
  • In the steps below, the EKS cluster is referred to as: eksname

Note: Glasswall CDR platform does not support ARM64 node VMs.

For guidance on creating an EKS cluster please refer to:

2. EFS​

  • An AWS Elastic filesystem is used to create Perisistent volumes in EKS. Create the EFS in the same VPC where EKS is created.

For guidance on creating EFS please refer to:

3. S3 bucket​

  • An S3 bucket is used to store reports for each file processed by the platform.

4. IAM Roles for service accounts​

Two IAM roles need to be created for 2 kubernetes service accounts deployed through the helm charts. The ARN's of these roles are required during deployment of the helm charts.

a. role-cdrp-efs-csi-<suffix> b. role-cdrp-ext-secrets-<suffix>

  • The shell script attached to this page can be used to create the IAM roles.
  • Pass AWS region, EKS cluster name, filesystem id and suffix as 4 arguments to the script. For e.g.
bash create-aws-roles.sh eu-west-1 eks-cdrp-dev fs-582a03f3 dev

For guidance on creating IAM roles for service accounts, please refer to AWS Documentation

5. MongoDB​

  • MongoDB is used to store the CDR Platform content management policies. The MongoDB is used by cdrplatform-policy-api service
  • Deploy a DocumentDB which is MongoDB API compatible.
  • If DocumentDB is not available in AWS Gov Cloud, MongoDB kubernetes operator can be used to deploy the MongoDB in the EKS cluster.

NOTE - Alternatively, MonogoDB can deployed directly inside of your cluster. Deployable using the MongoDB Helm Charts, as seen in Step 7.

Access to Glasswall Artifact Registry​

  • You are provided with a Token & Token ID to access Glasswall's Artifact Registry - glasswallhub.azurecr.io.
  • This allows you to directly pull container images and Helm charts from your AKS cluster.
  • In the steps below, the Token and Token ID will be referred to as: token and token_ID.