Planning Deployments

Should you choose to host your own instance of Cogynt, planning the deployment is critical. The following planning tasks should be completed prior to installation:

1. Understand all (prerequisites)[#prerequisites] and ensure that they have been met.
2. Determine which person in your organization will be the Super User.
3. Determine the name of the deployment's Kubernetes cluster.
4. Determine your authentication provider.

Prerequisites

The following prerequisites must be understood and completed before continuing:

1. Possess a signed license with Cogility
2. Possess an AWS or GCP account
3. Possess the following knowledge:
   1. Kubernetes
   2. Auto-Scaling
   3. Cloud Compute
   4. Cloud Storage
   5. DNS
   6. Virtual Private Cloud
   7. Terraform
   8. Linux Based OS
   9. Application Load Balancer
   10. Key Management Service

AWS-Specific Prerequisites

If your organization uses AWS, the following additional prerequisites apply:

1. IAM user account that possesses full Amazon Elastic Kubernetes Service (service prefix: eks) policies
2. Do not use your root account to deploy Cogynt’s Terraform template
3. IAM users who create or delete stacks will also require additional permissions that depend on the stack template
4. Select a region where EKS is available (See EKS / Region List)

GCP-Specific Prerequisites

If your organization uses GCP, the following additional prerequisites apply:

1. IAM user account that possesses the GKE roles/container.admin policy
2. Do not use your root account to deploy Cogynt’s Terraform template
3. IAM users who create or delete stacks will also require additional permissions that depend on the stack template
4. Select a region where GKE is available (See GKE / Region List)

Super User

For Cogynt versions 2.8.2 and earlier, the first person to sign in to Cogynt becomes the "Super User". This user inherits full admin permissions within Cogynt.

It is important to designate who should be the Super User, and have that person sign in to Cogynt immediately after installation.

Kubernetes Cluster Name

After installing Cogynt, you'll need to request a license and provide a cluster name at this time. We recommend creating a name prior to installation that adheres to the following constraints:

1. Must be alphanumeric and may contain dashes (-)
2. Must be less than 150 characters

Authentication Service Provider

As of v2.8.2, Cogynt supports the following authentication services:

• Any ASP with SAML 2.0 support
• Google