In {product-title} version {product-version}, you can install a cluster on Amazon Web Services (AWS) that uses infrastructure that you provide.
One way to create this infrastructure is to use the provided CloudFormation templates. You can modify the templates to customize your infrastructure or use the information that they contain to create AWS objects according to your company’s policies.
|
Important
|
The steps for performing a user-provisioned infrastructure installation are provided as an example only. Installing a cluster with infrastructure you provide requires knowledge of the cloud provider and the installation process of {product-title}. Several CloudFormation templates are provided to assist in completing these steps or to help model your own. You are also free to create the required resources through other methods; the templates are just an example. |
-
You reviewed details about the {product-title} installation and update processes.
-
You read the documentation on selecting a cluster installation method and preparing it for users.
-
You configured an AWS account to host the cluster.
ImportantIf you have an AWS profile stored on your computer, it must not use a temporary session token that you generated while using a multi-factor authentication device. The cluster continues to use your current AWS credentials to create AWS resources for the entire life of the cluster, so you must use key-based, long-term credentials. To generate appropriate keys, see Managing Access Keys for IAM Users in the AWS documentation. You can supply the keys when you run the installation program.
-
You downloaded the AWS CLI and installed it on your computer. See Install the AWS CLI Using the Bundled Installer (Linux, macOS, or UNIX) in the AWS documentation.
-
If you use a firewall, you configured it to allow the sites that your cluster requires access to.
NoteBe sure to also review this site list if you are configuring a proxy.
-
If the cloud identity and access management (IAM) APIs are not accessible in your environment, or if you do not want to store an administrator-level credential secret in the
kube-systemnamespace, you can manually create and maintain long-term credentials.
-
See Configuration and credential file settings in the AWS documentation for more information about AWS profile and credential configuration.
-
You can view details about the CloudFormation stacks that you create by navigating to the AWS CloudFormation console.
-
You can view details about the CloudFormation stacks that you create by navigating to the AWS CloudFormation console.
-
You can view details about your hosted zones by navigating to the AWS Route 53 console.
-
See Listing public hosted zones in the AWS documentation for more information about listing public hosted zones.
-
You can view details about the CloudFormation stacks that you create by navigating to the AWS CloudFormation console.
-
You can view details about the CloudFormation stacks that you create by navigating to the AWS CloudFormation console.
-
See {op-system} AMIs for the AWS infrastructure for details about the {op-system-first} AMIs for the AWS zones.
-
You can view details about the CloudFormation stacks that you create by navigating to the AWS CloudFormation console.
-
You can view details about the CloudFormation stacks that you create by navigating to the AWS CloudFormation console.
-
See Monitoring installation progress for details about monitoring the installation, bootstrap, and control plane logs as an {product-title} installation progresses.
-
See Gathering bootstrap node diagnostic data for information about troubleshooting issues related to the bootstrap process.
-
You can view details about the running instances that are created by using the AWS EC2 console.
You can configure registry storage for user-provisioned infrastructure in AWS to deploy {product-title} to hidden regions. See Configuring the registry for AWS user-provisioned infrastructure for more information.
-
See Accessing the web console for more details about accessing and understanding the {product-title} web console.
-
See Working with stacks in the AWS documentation for more information about AWS CloudFormation stacks.
-
If necessary, you can opt out of remote health reporting.
-
If necessary, you can remove cloud provider credentials.