reference deployment

CloudBees Core on AWS

CI/CD solution based on Jenkins and integrated with Amazon EKS

This Quick Start deploys CloudBees Core on the Amazon Web Services (AWS) Cloud, to provide a continuous integration and continuous delivery (CI/CD) solution that’s based on Jenkins and integrated with Amazon Elastic Kubernetes Service (Amazon EKS).

The Quick Start sets up a CI/CD environment that meets architectural best practices, including high availability, automatic scaling, segregation of agent workloads, and Kubernetes-native integration with Amazon Elastic Compute Cloud (Amazon EC2) Spot Instances.

The Quick Start is automated by AWS CloudFormation templates that deploy CloudBees Core in about 45 minutes in your AWS account. You can choose to install CloudBees Core into a new virtual private cloud (VPC), into your existing VPC, or into your existing Kubernetes cluster. After you deploy the Quick Start, you can use Jenkins plugins to add functionality to your CI/CD environment.

This reference deployment uses the Amazon EKS Architecture Quick Start as a foundation to provide a fully managed, highly available, and certified Kubernetes-conformant control plane for CloudBees Core.

portworx logo

This Quick Start was developed by CloudBees, Inc.
in collaboration with AWS. CloudBees, Inc. is
an APN Partner.

  •  What you'll build
  •  How to deploy
  •  Cost and licenses
  •  What you'll build
  • Use this Quick Start to automatically set up the following environment on AWS:

    • A highly available architecture that spans three Availability Zones.*
    • A VPC configured with three public and three private subnets (one public and one private subnet in each Availability Zone).*
    • In the public subnets:
      • Managed NAT gateways to allow outbound internet access for resources in the private subnets.*
      • A Linux bastion host in an Auto Scaling group, to allow inbound Secure Shell (SSH) access to the Amazon EKS nodes in the private subnets.*
    • In the private subnets, the following Amazon EKS nodes in Auto Scaling groups:
      • Three CloudBees Core master nodes.
      • Three CloudBees Core regular agent nodes.
      • Three CloudBees Core Spot agent nodes. These nodes are in an Auto Scaling group that is configured for multiple instance types.
    • Helm and kubectl installed and configured on the bastion host.
    • CloudBees Core installed on Amazon EKS as a Kubernetes StatefulSet.**
    • An Amazon Elastic File System (Amazon EFS) file system and efs-provisioner for Multi-AZ file storage. You can also configure the Quick Start to use Amazon Elastic Block Store (Amazon EBS) instead of Amazon EFS.

    *  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.

    ** The template that deploys the Quick Start into an existing Kubernetes cluster installs only this component. 

  •  How to deploy
  • To deploy CloudBees Core on AWS, follow the instructions in the deployment guide. The deployment process takes about 45 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, choosing from the following options:
    3. Activate CloudBees Core.

    To customize your deployment, you can configure infrastructure settings, the number of nodes in the Amazon EKS cluster partitions, instance types and storage sizes, Kubernetes version, and storage type.

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

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

    Tip     After you deploy the Quick Start, we recommend that you enable the AWS Cost and Usage Report to track costs associated with the Quick Start. This report delivers billing metrics to an S3 bucket in your account. It provides cost estimates based on usage throughout each month, and finalizes the data at the end of the month. For more information about the report, see the AWS documentation.

    After you deploy the Quick Start, you can request a free, 15-day trial license for CloudBees by choosing Request a trial license in the CloudBees Core Cloud Operations Center, or submit a pricing request on the CloudBees website.