IBM Cloud Private on AWS
You can deploy an IBM Cloud Private cluster on Amazon Web Services (AWS) by using either AWS CloudFormation or Terraform.
The decision to use AWS CloudFormation or Terraform is a matter of preference. There are some minor differences in what specifically gets deployed.
Note: If you have an issue with any of the samples and templates, use the GitHub project to gain support.
Deploying IBM Cloud Private on AWS by using AWS CloudFormation
IBM Cloud Private has a Quick Start that automatically deploys IBM Cloud Private into a new virtual private cloud (VPC) on the AWS Cloud. A regular deployment takes about 60 minutes, and a high availability (HA) deployment takes about 75 minutes to complete. The Quick Start includes AWS CloudFormation templates and a deployment guide.
This Quick Start is for users who want to explore application modernization and want to accelerate meeting their digital transformation goals, by using IBM Cloud Private and IBM tools. The Quick Start helps users rapidly deploy a high availability (HA), production-grade, IBM Cloud Private reference architecture on AWS.
For all of the details and the deployment guide, see IBM Cloud Private on AWS Quick Start .
Deploying IBM Cloud Private on AWS by using Terraform
IBM Cloud Private can run on the AWS cloud platform by using Terraform. To deploy IBM Cloud Private in an AWS EC2 environment, see Installing IBM Cloud Private on AWS .
For details on AWS Identity and Access Management (IAM) roles, see the cloud-provider-aws project .
There are some additional attributes that you can define when you create your Kubernetes service on AWS that helps you with the configuration of the corresponding AWS Elastic Load Balancing (ELB)s. There are also attributes that can be passed to the storage class to manage the way the PVCs are created. For more information, see the Kubernetes documentation on AWS and AWS Elastic Block Store (EBS) .