 Hi, my name's Rhys Oxenham and I manage the Field Product Management Team within the Cloud Platforms Business Unit here at Red Hat. Today we're going to look at Red Hat OpenShift Service on AWS, or ROSA for short, and we're going to demonstrate how customers can easily deploy fully managed OpenShift clusters in the public cloud. Red Hat has worked closely with Amazon to integrate this service by the Amazon Web Services Management Console, allowing existing Amazon customers to onboard OpenShift capabilities via a simple subscription, with all billing centralized just as it is today. Here you can see the landing page for ROSA and that I've already got this service enabled. There's extensive documentation for the ROSA service that walks customers through all of the prerequisites, including requirements for setting up the AWS account and how to instantiate clusters after they've subscribed to the service. I'm going to walk you through a deployment end to end today. First things first, we need to set up an AWS account with identity and access management permissions. The documentation describes how to create this user and the policies that need to be in place. This is easy to set up either with a standard AWS user or if your user is part of an AWS organization. Here you can see that I've pre-created an IAM user called ADO ROSA and that it has administrator access and hence has full control. Next we need to configure the AWS command line interface with the access key and the secret that reflects this IAM user and this can be done with AWS Configure. Here you can see that I've already set the credentials. You can also specify your default region where I've selected London. Now we can verify that the AWS credentials are correctly configured by requesting the caller identity, verifying that it's an IAM account and that it's ADO ROSA as expected. We can also further verify access to EC2 by requesting a list of instances. Here it's showing zero. Now that we have AWS configured we need to download the ROSA Client. This is a dedicated command line utility that controls all aspects of deploying a fully managed OpenShift cluster on AWS via the service. From the AWS Management Console we have an option for downloading the CLI and there are options for Linux, macOS and Windows. I've already downloaded and installed the Linux Client. Let's go ahead and ensure that the ROSA Client can utilize the AWS CLI that we just set up and ensure that our account is properly configured so that it has the correct permissions and enough quota to satisfy deployment in our region of choice. The next step is to log into our Red Hat account via the ROSA CLI. This ensures that resulting clusters are linked to the OpenShift cluster manager and associates the cluster to us for any future support requirements. For this we need to grab a token from cloud.redhat.com via the link provided. We'll copy this back into ROSA and you can see that we're logged in properly. A further ROSA Who Am I will expand on that and we'll give further clarity on how things are set up with my AWS account ID, the region I want to deploy into, the IAM user we're going to leverage and the link to the Red Hat account. Now that we've verified that we're ready to start deploying our ROSA cluster. The first step is to run ROSA in it. This will run a short cloud formations template that configures the AWS account ready for the deployment and management of our cluster. This usually takes a minute or two so we'll speed this section up. All being well we're now ready to go ahead and actually deploy the ROSA cluster. For this we simply request the cluster to be created via the ROSA CLI and we'll give it a name. Here I'll use Arduino ROSA. This will now start the deployment behind the scenes and some configuration details will be printed to the console. The ROSA CLI also allows us to optionally watch the deployment logs where we get the output of the OpenShift installer so we can closely monitor progress. The deployment of the cluster takes approximately 40 minutes so we'll jump forward pretty quickly here. So there we go, install complete. This can be verified by listing the clusters with the ROSA CLI and we can ask you to further describe the cluster. Here showing the API URL, the console URL and the link to the OpenShift cluster manager page which we'll dive into first. The OpenShift cluster manager page gives us deep dive insights into the cluster including the cluster specifications, versions used, number of nodes, networking configuration and much more. From here we can also go ahead and configure access control. Any changes invoked through OpenShift cluster manager will be enacted on our ROSA cluster so if we want to set up identity management this can be done here or it can absolutely be done in the ROSA CLI too. It's possible to set up a wide variety of identity providers from GitHub, Google to LDAP but in this case to keep things simple for the video we can set up a standard administrator user that exists within the cluster only. For that we'll need to ask ROSA to create this user for us. Once complete we'll get the OpenShift command line parameters that can be used to log directly into the cluster and we can verify that it's working. We can also verify that we are the cluster admin that we're using the 472 version of OpenShift and that we have all of our nodes in a ready state. Given that we've now set up a user let's go ahead and connect to the OpenShift web console. There's a handy link in the OpenShift cluster manager page and we can grab the password from the previous admin creation command from the ROSA CLI. As we can see the OpenShift cluster is fully functional. Let's take a look at some of the other capabilities of the OpenShift cluster manager as it relates to a ROSA based cluster. We're able to view networking configurations. We can then go ahead and see and configure machine pools and here you can see how easy it is to scale the number of worker nodes from two nodes to three. And behind the scenes the machine set will be scaled and a new AWS instance will be provisioned automatically for us. It's possible to also raise support cases for the specific cluster right from the OpenShift cluster manager automatically associating it to the clustering question. It will then take us directly through to the support portal to hugely simplify the creation of a support case. Finally it's also possible to change the update schedule. By default cluster updates are manual and left to the cluster operator to invoke. Alternatively you can specify an automatic update schedule where the latest version will be applied at a date and time of your choosing. There's also the ability to enable cluster logging where logs from the cluster will be automatically shipped to AWS CloudWatch so they're easily visible from the AWS console. This functionality is defined as an add-on and can be enabled by the OpenShift cluster manager or via the ROSA CLI. Here we'll enable it via the OpenShift cluster manager turning all options on. We'll then watch for the logging pods to be started automatically on our cluster. Once they're up and running we can then go into AWS CloudWatch and validate that it's starting to receive log files from our cluster. Making this OpenShift cluster just another part of a customer's infrastructure within AWS. Lastly we can verify that the ROSA CLI is also showing the installation of the logging add-on as ready. And that concludes the demonstration of ROSA. The only thing left to do now is to delete the cluster which we'll do via the ROSA CLI. This will then take care of the teardown of the cluster within AWS and the deletion within OpenShift cluster manager. This step typically takes some time and also allows you to watch the output when available with the watch option. Thank you for your time. I hope that this was useful for you. Please don't hesitate to get in touch if you have any questions.