wso2 / aws-cicd-deployment-scripts Goto Github PK

Description:
Current cloud formation templates use tailon for logging. Since we have ELK in the AWS Pipeline tailon should be removed.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@shafanaS

Description:
Monitoring master and logging master instances in each environment should be exposed via a load balancer. Instances should reside in a private subnet.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@shafanaS

Description
When the stacks are being created, during the specified timeout, it rollback not receiving the cfn signal from auto scaling group. This happens intermittently in different regions.

Description:
The ability to use the cloud formation scripts any of the AWS available region. The cloud formation scripts should have AMIs supporting the all available AWS regions.

Description:
Include ELK for centralized logging for WSO2 product deployments.
In the AWS Pipeline we would have an EC2 instance for logging for each environment. Each environment will have their own Kibana Dashboard to monitor logs of products deployed.

Description:
The Cloud formation scripts used to deploy environments in AWS pipeline should have AMI's for all AWS regions. Thus pipeline can be setup in any region.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@shafanaS

Description:
Decouple product and network deployment in the CF scripts. Environments should be able to share the network resources.

Suggested Labels:
Type/NewFeature

Description:
Use Prometheus as the monitoring solution to monitor and Grafana Dashboard for visualizing of WSO2 product deployments. An AMI with all prometheus and Grafana configurations is used.