Manage a Cloudformation Stack
Once you have deployed a Zilla Cloudformation stack you can manage it in the following ways.
The CloudFormation template used to deploy the Zilla proxy includes a Network Load Balancer that can be monitored via CloudWatch to verify continuous health.
Network Load Balancers have many available metrics, including the following.
TCP_Target_Reset_Count- The total number of reset (RST) packets sent from a target to a client. These resets are generated by the target and forwarded by the load balancer.
UnHealthyHostCount- The number of targets that are considered unhealthy.
You can use CloudWatch to create a dashboard to monitor these metrics and set alarms to alert you when specific metric thresholds are reached.
Navigate to your AWS Marketplace subscriptions and select
Zilla Plus for * to show the manage subscription page.
- From the
Actionsmenu > select
Launch CloudFormation stack
- Select the
CloudFormation Templatefulfillment option with the same
Secure Public Accesstemplate used to deploy the proxy
- Make sure you have selected the desired region selected, such as
Continue to Launch
- Choose the action
- Choose the action
Launchto show the URL of the CloudFormation template
- Copy the CloudFormation template Amazon S3 URL
- Select your existing CloudFormation Stack from a previous deployment of
Zilla Plus for *
Replace current templatewith the copied Amazon S3 URL
- Complete the wizard to deploy the updated stack.
CloudFormation will incrementally deploy the Zilla proxies for the new version behind the same Network Load Balancer, checking for successful deployment before terminating the Zilla proxies for the previous version.
Connected clients will see their connections drop, and when they reconnect automatically, the Network Load Balancer will direct them to the new Zilla proxies. If the stack update is unsuccessful, then CloudFormation will rollback to use the previous stack deployment.