Deploying ROSA in STS mode
This content is authored by Red Hat experts, but has not yet been tested on every supported configuration.
Tip The official documentation for installing a ROSA cluster in STS mode can be found here .
Quick Introduction by Ryan Niksch (AWS) and Shaozen Ding (Red Hat) on YouTube
STS allows us to deploy ROSA without needing a ROSA admin account, instead it uses roles and policies with Amazon STS (secure token service) to gain access to the AWS resources needed to install and operate the cluster.
This is a summary of the official docs that can be used as a line by line install guide and later used as a basis for automation in your favorite automation tool .
Prerequisites
If this is your first time deploying ROSA you need to do some preparation as described here .
Once completing those steps you can continue below.
Deploy ROSA cluster
set some environment variables
export ROSA_CLUSTER_NAME=mycluster export AWS_ACCOUNT_ID=`aws sts get-caller-identity \ --query Account --output text` export REGION=us-east-2 export AWS_PAGER=""
Make you your ROSA CLI version is correct (v1.2.25 or higher)
rosa version
Run the rosa cli to create your cluster
Note there are many configurable installation options that you can view using
rosa create cluster -h
. The following will create a cluster with all of the default options.rosa create cluster --sts --cluster-name ${ROSA_CLUSTER_NAME} \ --region ${REGION} --mode auto --yes
Watch the install logs
rosa logs install -c $ROSA_CLUSTER_NAME --watch --tail 10
Validate the cluster
Once the cluster has finished installing we can validate we can access it
Create an Admin user
rosa create admin -c $ROSA_CLUSTER_NAME
Wait a few moments and run the
oc login
command it provides. If it fails, or if you get a warning about TLS certificates, wait a few minutes and try again.Run
oc whoami --show-console
, browse to the provided URL and log in using the credentials provided above.
Cleanup
Delete the ROSA cluster
rosa delete cluster -c $ROSA_CLUSTER_NAME
Clean up the STS roles
Once the cluster has been deleted we can delete the STS roles.
Tip You can get the correct commands with the ID filled in from the output of the previous step.
rosa delete operator-roles -c <id> --yes --mode auto rosa delete oidc-provider -c <id> --yes --mode auto