Completing and submitting the first deployment template

Open the first CloudFormation template, fill in the required information, and submit the template.

Procedure

To submit the first template:

  1. Log in to your AWS account with your IAM user ID. See Signing in to AWS for more information.
  2. On the AWS console, enter CloudFormation in the search field.
  3. Click CloudFormation under Services on the search result list.
  4. Click Create Stack.
  5. Enter the following URL in the Amazon S3 URL field:
    https://s3.amazonaws.com/awsmp-fulfillment-cf-templates-prod/ec166b38-7a15-43f9-8442-d3785ce28a41/d3119082c8424d30a6bbdf18593352e2.template
  6. Click Next.
  7. 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. VPC network configuration
    Parameter Default Description
    Number of Availability Zones (NumberOfAZs) 3 The number of availability zones to be used for the deployment. Currently, the only supported setup is a setup with 3 availability zones. Therefore, leave the default value as is.
    VPC CIDR (VPCCIDR) 10.0.0.0/24

    This definition allows you to use 254 IP addresses in the entire VPC network, that is, from 10.0.0.1 to 10.0.0.254.

    		 The IP address range of the VPC to be created, in CIDR notation.
    Note: You can certainly change the IP address ranges you want to use, but for the number of available IP addresses in the VPC or a subnet, stick to the recommended range sizes (numbers after the slash) as shown in the column on the left. This way, you do not waste IP addresses unnecessarily.
    Private subnet 1 CIDR (PrivateSubnet1CIDR) 10.0.0.64/26

    This range gives you 62 IP addresses in private subnet 1, that is, from 10.0.0.65 to 10.0.0.126.

    		 The IP address range of the private subnet in availability zone 1, in CIDR notation.
    Private subnet 2 CIDR (PrivateSubnet2CIDR) 10.0.0.128/26

    This range gives you 62 IP addresses in private subnet 2, that is, from 10.0.0.129 to 10.0.0.190.

    		 The IP address range of the private subnet in availability zone 2, in CIDR notation.
    Private subnet 3 CIDR (PrivateSubnet3CIDR) 10.0.0.192/26

    This definition gives you 62 IP addresses in private subnet 3, that is, from 10.0.0.193 to 10.0.0.254.

    		 The IP address range of the private subnet in availability zone 3, in CIDR notation.
    Public subnet 1 CIDR (PublicSubnet1CIDR) 10.0.0.0/28

    This range gives you 14 IP addresses in public subnet 1, that is, from 10.0.0.1 to 10.0.0.14.

    		 The IP address range of the public subnet in availability zone 1, in CIDR notation.
    Public subnet 2 CIDR (PrivateSubnet2CIDR) 10.0.0.16/28

    This range gives you 14 IP addresses in public subnet 2, that is, from 10.0.0.17 to 10.0.0.30.

    		 The IP address range of the public subnet in availability zone 2, in CIDR notation.
    Public subnet 3 CIDR (PrivateSubnet3CIDR) 10.0.0.32/28

    This range gives you 14 IP addresses in public subnet 3, that is, from 10.0.0.33 to 10.0.0.46.

    		 The IP address range of the public subnet in availability zone 3, in CIDR notation.
    Boot node access CIDR (BootNodeAccessCIDR)   The range of IP addresses that is permitted to access the boot node of the ROSA cluster, in CIDR notation. You can change this value to a narrower (subnet) range, or even a single IP address. If necessary, you can add addresses later on from the EC2 Console on AWS.
    Cluster name dgoc A short name for the ROSA cluster. The name in the column on the left is an example. You can choose any name, but certain characters are not allowed, such as periods for example. An error message is shown if you try to submit an invalid name.
    Key pair name   The name of an existing AWS key pair (certificate in pem file format) that enables encrypted (secure) connections to your VPC instance. For more information, see Key pair.
    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.

    The bucket must exist before you submit the template.
    License agreement   The license agreement for the Data Gate on Cloud configuration.
    ROSA token   Enter your ROSA token in this field.
  8. Click Next.
  9. Click Next.
  10. Verify the entered parameters. When finished, select the check box in this window:
  11. Click Submit.
    Note: The deployment takes about one hour to finish.