Cloud Specific Details

Cloud vendor specific tool installations and environment variables are required at certain steps based on your deployment path

Prerequisites

Provision Enabling Systems

For quick deployment, mainly for development and testing purposes, you may wish to use cloud marketplaces, managed providers or Rierino playbooks for enabling systems:

AWS

AWS Marketplace: MongoDB(R) VM packaged by Bitnamiaws.amazon.com

MongoDB

For this MongoDB package, configuration updates and restart details can be found from the vendor site.

AWS Marketplace: Bitnami package for Apache Kafkaaws.amazon.com

Kafka

https://aws.amazon.com/marketplace/pp/prodview-5bryl7uliw4euaws.amazon.com

Keycloak

If you will be using Keycloak with http for development / testing purposes, you may need to open up the port on local firewall (e.g. sudo ufw allow 8080/tcp) and set "Require SSL" option to false on master realm.

AWS Marketplace: Bitnami Elasticsearch Stackaws.amazon.com

Elasticsearch

GCP

Managed Service

Rierino Playbook

Set-up Initial Deployment Host

Ansible playbooks require access to VM inventory as well as kubernetes cluster from initial deployment host, which requires installation of certain collections and tools:

AWS

Installing or updating to the latest version of the AWS CLI - AWS Command Line InterfaceAWS Command Line Interface

AWS CLI Installation

ansible-galaxy collection install amazon.aws community.aws

Set-up environment variables used by Ansible and AWS tools:

export KUBECONFIG=[kubeconfig file path]
export K8S_AUTH_KUBECONFIG=[same as KUBECONFIG]
export AWS_REGION=[AWS deployment region]
export AWS_ACCESS_KEY_ID=[AWS access key id]
export AWS_SECRET_KEY=[AWS secret key]
export AWS_SECRET_ACCESS_KEY=[same as AWS_SECRET_KEY]

If you are using WSL for initial deployment and receive error on valid AWS credentials, your instance's time may be out of sync with Amazon servers.

You may use a command such as sudo hwclock -s for synchronization.

As a best practice, it is recommended not to use AWS account root user credentials for these environment variables which are used during deployment.

GCP

Provision a Kubernetes Cluster

AWS

Note that for AWS installations, you may need to manually update kubeconfig file contents output from "terraform apply" step, setting authentication apiVersion to "v1beta1" if you are receiving "invalid apiVersion client.authentication.k8s.io/v1alpha1"error.

This is due to a compatibility bug between AWS CLI and recent helm/kubectl versions.

It is possible to deploy Rierino platform on any AWS region that has EKS and ELB availability. For the latest list of regions supported for these services, please refer to AWS availability listing.

GCP

AWS

Configure Network Connectivity

AWS

You can use security groups for configuring connectivity between kubernetes cluster and enabling systems (such as one group allowing ingress from all sources within the group and another granting access to static admin IPs).

Control traffic to your AWS resources using security groups - Amazon Virtual Private CloudAmazon Virtual Private Cloud

Amazon Security Groups

You can issue SSL certificates using ACM for your domain.

Certificate Manager- AWS Certificate Manager - AWSAmazon Web Services, Inc.

AWS Certificate Manager

You can reserve static IPs to assign them to external facing load balancers.

Elastic IP addresses - Amazon Elastic Compute CloudAmazon Elastic Compute Cloud

Amazon Elastic IPs

You can map your static IPs to DNS records.

DNS Service - Amazon Route 53 - AWSAmazon Web Services, Inc.

Amazon Route 53

GCP

Deployments

Load Balancer Variables

AWS

For ansible-playbook deployments including external facing load balancers (admin gateway and admin UI), include the following variables for static IP and certificate assignments:

Variable	Definition	Default
awsACMARN	ARN for ACM certificate (if certificate is used)	-
awsLBSubnets	List of subnets on which static IPs shall be assigned (if static ip is used)	-