Alerta on AWS EC2
- VPC with at least two public subnets
- Google Tracking ID (optional)
The following table lists the Cloudformation template parameters that can be set. There are sensible defaults where possible.
|VpcId||ID of the VPC onto which to launch the application eg. vpc-1234abcd|
|Subnets||Public subnets to use in VPC for internet-facing ELB, instances and RDS eg. subnet-abcd1234|
|KeyName||Name of an existing EC2 KeyPair for SSH access|
|SSHLocation||IP range that can be used to SSH to the EC2 instances (default: 0.0.0.0/0)|
|AllowedDomain||Allowed email domain eg. gmail.com or example.com|
Use the AWS console to upload and launch the stack or use the
aws cloudformation create-stack command-line tool.
The Alerta Web UI is available at the following:
And the Alerta API is available at the following:
The exact values are dependent on the actual deployment and can be found in the CloudFormation "Outputs" tab of the AWS console once the Alerta stack has been successfully created.
There are many improvements that should be made to this template before it is used in a production environment. These include, but are not limited to:
- using private VPC subnets for the web servers and database instances
- copying the web console static assets to S3 and serving them from Cloudfront
- creating an SSL certificate and using HTTPS instead of HTTP
These and other enhancements are specific to every deployment environment so this is left as an exercise for the reader.
Copyright (c) 2015-2016,2018 Nick Satterly. Available under the MIT License.