Completing and submitting the second deployment template
Open the second CloudFormation template, fill in the required information, and submit the template.
Procedure
Before you submit the second template, make sure that the Db2® Warehouse on Cloud instance you want to connect to already exists. To submit the second template:
- Log in to your AWS account with your IAM user ID. See Signing in to AWS for more information.
- On the AWS console, enter CloudFormation in the search field.
- Click CloudFormation under Services on the search result list.
- Click Create Stack.
- Enter the following URL in the Amazon S3 URL field:
- Under Parameters, you see all required parameters with their
default values. Where needed, change these values according to the requirements of your AWS environment. Use the following table as a reference:
Table 1. Data Gate on Cloud instance configuration Parameter Description Availability Zone One of the availability zone that the ROSA cluster is available in. The Data Gate on Cloud instance is provisioned in the private subnet of the selected availability zone. In the public subnet of this availability zone, a boot node is created to start the installation of the instance.
VPC ID The ID of the VPC created by the first template. Public subnet 1 ID The ID of the public subnet in availability zone 1, as created by the first template. Boot node external access CIDR The range of IP addresses in CIDR notation that is permitted to access the boot node instance of the ROSA cluster in the public VPC. Limit the range of IP addresses with access to the boot node. If necessary, you can add addresses later on from the EC2 Console on AWS. Key pair name The name of an existing AWS key pair that enables encrypted (secure) connections to your VPC instance. For more information, see Key pair. ROSA cluster name The name of the ROSA cluster on AWS. Secrets to be created in the AWS Secret Manager are based on this name. Attention: Make sure to specify a name that is not already in use (unique name). Reusing an existing name might result in the overwriting of parts of the existing cluster, which would make the existing cluster unusable.ROSA cluster API server The name of the ROSA cluster API server. ROSA cluster login user name The name of the user (ID) connecting to the ROSA cluster. Note: You can enter user name and password or the ROSA token (see upcoming rows).ROSA cluster login password The password of the ROSA cluster login user (see previous row). ROSA token The ROSA token assigned to the ROSA cluster login user ID. S3 output bucket name The name of an S3 bucket to write the ROSA cluster deployment logs to. The deployment logs contain information about the boot strap scripting actions, and are useful for problem determination if the deployment fails. IBM entitlement key The IBM entitlement key is needed to download software images from the IBM Container Registry. License agreement The license agreement for the IBM® Data Gate on Cloud configuration. OpenShift® project The name of the OpenShift project to be created for the deployment of Data Gate on Cloud. You can use any lowercase string for this name. S3 output bucket name The name of another S3 bucket to write the CloudFormation deployment logs to. The deployment logs contain information about the boot strap scripting actions, and are useful for problem determination if the deployment fails. Host name of Db2 Warehouse on Cloud The DNS name of the Db2 Warehouse on Cloud host. You can search for the host from the AWS Console (under VPC), and then copy the DNS name to paste it in here. Secure SSL port of Db2 Warehouse on Cloud The SSL port for connecting to Db2 Warehouse on Cloud. Db2 Warehouse on Cloud user name User name (user ID) for connecting to Db2 Warehouse on Cloud. Db2 Warehouse on Cloud user password The password associated with the specified Db2 Warehouse on Cloud user ID (see previous row). S3 URI of Db2 Warehouse on Cloud certificate file The URI of the Db2 Warehouse on Cloud certificate file after uploading it to the AWS cloud. The file must be uploaded to an S3 bucket that the AWS CloudFormation service can access. - Click Next.
- Click Next.
- Verify the entered parameters. When finished, select the check box
in this window:

- Click Submit. Note: The deployment takes about 20 minutes to finish.