Deploying a multi-node CloudFormation stack

Last Updated : Oct 28, 2020 |
Prolog information
Metadata
Keywords:
Before you begin
  • Use standard Amazon Web Services procedures to create the required network setup, including Virtual Private Cloud (VPC) settings and Security Groups.
  • Ensure that you have network access to the Amazon VPC before deploying an AMI.
  • Create a multi-node CloudFormation template.
  1. Sign in to the AWS console and navigate to Services Management & Governance CloudFormation.
  2. Click Create Stack.
    ADDITIONAL INFORMATION:
    The AWS EC2 Management console displays the first page of the Create stack wizard.
  3. On the Select Template page, in the Choose a template area, click Upload a template to Amazon S3.
  4. Click Browse, and choose the multi-node yaml CloudFormation template file that you generated.
  5. Click Next.
    ADDITIONAL INFORMATION:
    The system displays the Specify Details page.
  6. In the Stack name field, type a name for the stack.
    ADDITIONAL INFORMATION:
    This stack name must match the stack name portion of the FQDN of the load balancer.
    Note:
    The stack name must start with a letter and must contain letters, numbers, and dashes.
  7. In the Amazon Machine Image ID field, type the Amazon Machine Image ID (AMI ID) of the image that you imported.
    ADDITIONAL INFORMATION:
    Tip:
    You can obtain the AMI ID of an image from the EC2 AMI page. On a separate browser tab, navigate to Services EC2 Images AMIs.
  8. Use the public/private key pair for initial login to the node. You can login to the node by using the ssh. For more information, see https://docs.aws.amazon.com/.
    ADDITIONAL INFORMATION:
    The nodes are evenly distributed among subnets. One subnet for each availability zone (AZ). All subnets belong to the same VPC, and you can select from the drop down. All AZs are in the same AWS region. If existing subnets are used, you can select them from the drop down.
  9. In the Network area, select the required Virtual Private Cloud.
  10. Do one of the following depending on whether you selected the Create subnets check box when creating the multi-node CloudFormation template:
    • If you have selected the check box, configure the required IPv4 address range in each subnet CIDR block field.
      In CIDR notation, the number of bits in the network portion of the address follows a slash. For example, 192.0.2.10/28. The address range for the subnets must fall within the address range of the VPC and must not overlap any existing subnet within the VPC.
    • If you did not select the check box, select the required subnets from each Subnet field.
      Note:
      When using existing subnets, each subnet must be in a different availability zone.
      Important:
      When using existing subnets, if any of the subnets do not have access to a VPC endpoint, enter this subnet route table ID in the Route Table. To separate multiple IDs, use a comma.
  11. In the Load balancer certificate ARN field, type the ARN.
    ADDITIONAL INFORMATION:
    In AWS, an application load balancer distributes messaging traffic to the nodes. Client HTTPS connections terminate on the ALB. So, a certificate must be provisioned. The certificate and its private key must be loaded into AWS certificate manager, which identifies them using an ARN.
  12. In the DNS area, do the following:
    1. In the Load balancer host name field, type the DNS load balancer host name.
    2. In the Server-to-server host name field, type the server-to-server host name.
    3. In the Host name field, type the DNS host name.
    4. In the DNS Domain field, type the name of the private DNS domain to use.
  13. If the domain is a new domain in this VPC, set Create domain to Y. Otherwise, set it to N.
    ADDITIONAL INFORMATION:
    For FQDN of Avaya Breeze® platform Management Network Interface on node N, use <host><N>.<domain>.
    For FQDN of Avaya Breeze® platform Security Module Network Interface on node N, use <host><N>-sm100.<domain>.
    For FQDN of load balancer, use <lb>.<domain>.
    Note:
    Multimedia messaging server address in Equinox client must be set to FQDN of load balancer.
    For FQDN for server-to-server communication, use <s2s>.<domain>.
  14. Click Create.
    STEP RESULT:
    The system displays the Stacks page, which shows the stack creation status.