reference deployment

Rafay Systems for Amazon EKS

Kubernetes infrastructure to assist in the management of containerized applications

Rafay’s Kubernetes Management Cloud (KMC) lets users deploy, operate, and manage the lifecycle of Kubernetes clusters and containerized applications in both public-cloud and on-premises environments.

This Quick Start is for IT and DevOps professionals who want to deploy Kubernetes clusters in the AWS Cloud, in data centers, and at network edges. KMC’s SaaS-based management console can automate multicluster provisioning, configuration management, and upgrades for Kubernetes clusters.

KMC automates the deployment of containerized applications and enables access to Kubernetes clusters through a zero-trust connectivity model. Through a single UI, KMC provides enterprise-grade capabilities, such as monitoring and visibility across AWS Regions, role-based access control, and governance.

rafay-systems-logo-284x70

This Quick Start was developed by Rafay Systems in partnership with AWS. Rafay Systems is an AWS Partner.

  •  What you'll build
  •  How to deploy
  •  Cost and licenses
  •  What you'll build
  • Use this Quick Start to set up the following Rafay Systems MKP for Amazon Elastic Kubernetes Service (Amazon EKS). Note that this module is based on the Modular and Scalable Amazon EKS Architecture Quick Start.

    • A highly available architecture that spans three Availability Zones.*
    • A virtual private cloud (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*
    • In the public subnets:
      • Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.*
      • Linux bastion hosts in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in the private subnets. The bastion host is configured with the Kubernetes Kubectl command line interface for managing the Kubernetes cluster.
    • In the private subnets, Kubernetes worker nodes in an Auto Scaling group that automatically sets up the Rafay Operator software, which connects to the Rafay Kubernetes Management Cloud.
    • An Amazon EKS cluster, which creates the Kubernetes control plane.

    * The template that deploys the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To deploy Rafay KMC for Amazon EKS, follow the instructions in the deployment guide. The deployment process takes about 45–60 minutes and includes these steps:

    1. If you don't already have an AWS account, sign up at https://aws.amazon.com, and sign in to your account.
    2. Launch the Quick Start by choosing from the following options. Before you create the stack, choose the Region from the top toolbar.
    3. Test the deployment.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.  

  •  Cost and licenses
  • You are responsible for the cost of the AWS services and third-party licenses used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.

    The AWS CloudFormation template for this Quick Start includes configuration parameters that you can customize. Some of these settings, such as instance type, affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you use. Prices are subject to change.

    This Quick Start requires a license for MKP. For a production environment, sign up for a Rafay account.

    Tip: After you deploy the Quick Start, enable the  AWS Cost and Usage Report to track costs associated with the Quick Start. This report delivers billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. It provides cost estimates based on usage throughout each month, and aggregates the data at the end of the month. For more information about the report, see  What are AWS Cost and Usage Reports?