Using Existing Application Load Balancers (ALB) in Production Environments

As you build your AWS infrastructure in CloudShell Colony, you may want to attach pre-configured ALBs to your production environments. Do this for the following use-cases:

1. You want to add more control to your specific load balancer's configuration settings. 
2. You want to terminate the production environment with the specially configured load balancer and recreate it at the same IP address that was associated with it. 

You can satisfy both use-cases with Colony Production templates.

To implement this capability, review the example production YAML details below:

infrastructure: 
  stack: STACK_NAME
  green_host: green.lv-colony-prod.com 
  connectivity: 
    virtual_network:  
      id: {virtual network id}  

Notes:

• The stack parameter is optional. If it is not defined, Colony will automatically create the ALB when the production environment is launched and delete the ALB when the environment ends.
• STACK_NAME must contain a stack that contains an ALB with the name "MainALB". Note that when a production environment that uses an existing ALB ends, Colony will keep the ALB and use it for future production environments that are set to use it.

To employ this capability, provide a cloud provider stack with your ALB. You can download this AWS CloudFormation template to review an example CloudFormation that creates the production resources, including an ALB. 

To learn more about your Production Environment's blueprint, review this article on updating your production environment blueprint.

Related Topics

• Disabling the Use of Load Balancers in Your Blueprint