wso2 / aws-apim Goto Github PK

What would be the reason for creating a new repository for maintaining WSO2 API Manager Cloud Formation Templates while already having another?
https://github.com/wso2/cloudformation-apim

Description:
Network, DB creation, product deployment are all in a single Cloudformation script. The network creation should be able to run whenever needed.

Description:
The current repo only contains a CloudFormation template to deploy API Manager pattern 1. Allow users deploy API Manager pattern 2 in AWS using CloudFormation.

Description:
The current AMIs are created using Ubuntu base AMIs. Allow users to choose their preferred Operating System using parameters in the CloudFormation template.

Allowed Operating Systems - RHEL and CentOS

Description:
Currently, the default JDK version is 1.8.0. Add an option for users to choose a different JDK version using parameters in the Cloudformation template.

Allowed versions - 1.8.0 and 1.7.0

Affected Product Version
2.2.0

Description:
Network, DB creation, product deployment are all in a single Cloudformation script. The network creation should be able to run whenever needed.

Description:
The current Cloudformation stack is a Puppet "masterless" setup. Each product (APIM and APIM Analytics) has a corresponding AMI with the product pack and puppet modules. Create a puppetmaster AMI and add all the products and the corresponding puppet modules to the puppetmaster.

Description:
Currently, the default RDBMS is MySQL. Add an option for users to choose a different RDBMS version using parameters in the Cloudformation template.

Allowed vendors - Oracle, Postgres, MS SQL

Description:
Need to add puppet resources for,

• APIM 4.0.0
• MI 4.0.0

Need to remove puppet resources for

• APIM Analytics

Description:
Add the following images to the Readme.

1. APIM deployment pattern diagram
2. Architecture of the VPC

Description:
The CloudFormation template is hardcoded with the instance type of "t2.medium". Allow the users to have the option to choose a preferred EC2 instance type. Add a parameter in the CloudFormation template to select the instance type with allowed values.

Description:
The current resources are only created for APIM Pattern 1. Two APIM active active nodes configured with analytics. Create similar resources for APIM pattern 2 ( distributed ).

Suggested Labels:
Type/Improvement

Suggested Assignees:
@ctienshi

Affected Product Version:
APIM 3.0.0

Description:
Install Puppet into WSO2 APIM and Analytics AMIs. Use Puppet to mount configuration files and perform other necessary installments while deployment.

Description:
This issue is regarding creating the basic AWS Cloudformation template. The template describes the resources that needs to be provisioned in the AWS CloudFormation stack. This CF template should consist of creating the following resources.

1. VPC
2. Two Public Subnets
3. Two Private Subnets
4. Load Balancer
5. An Internet Gateway
6. Public Route Table
7. A Bastion Instance
8. RDS DB Instance
9. An Elastic File System (EFS)

Suggested Labels:
Priority/High
Type/Task

Description:
Install WUM client and create AMIs to allow users with a subscription to deploy WSO2 APIM and APIM Analytics with it's latest updates. The GA packs (without updates) should be deployed for users without a valid subscription. Update the MOTD displayed when connecting into an Instance via SSH according to the product version deployed.

Description:
Update the Basic CF template to deploy WSO2 API Manager with WSO2 API Manager Analytics in AWS. API Manger and API Manager Analytics should be configured and deployed in the two private subnets in two different availability zones. Use an AWS RDS instance in the private subnets to configure the databases.

Suggested Labels:
Type/Improvement

Description:
The current CF template uses the IP address of the Analytics instance [1] for publishing API statistics from the API manager nodes. As a result, if the Analytics instance becomes unavailable and gets recovered by the autoscaling group, analytics would not work after that point due to IP address being changed. One way of resolving this issue is to use an internal hosted zone with Route 53 and create a domain name for Analytics instances.

In addition, we may need to create two Analytics instances for providing HA with the above approach.

Suggested Labels:
Severity/Major
Type/Improvement

Suggested Assignees:
@ctienshi

Related Issues:
https://github.com/wso2/cloudformation-apim/issues/24

Description:
While creating a Loadbalancer, the DNS name includes the name of the AWS region in which the load balancer is created. The DNS name created for WSO2 APIM Loadbalancer is similar to something "AWSCloudF-WSO2APIM-*************.us.east-1.elb.amazonaws.com". Since it is lengthy and complicated, a simple hostname should be set to the loadbalancer using AWS Route53.

Description:
Define specific outbound rules in product-specific AWS Security Groups. Currently, since no outbound rules are defined, by default the "allow all" rule has been applied.
Thus, it is suggested to move Ubuntu package updates and software installations defined under Launch Configuration user data to AMI creation since these require connection to the Internet from the private subnets containing product auto scaling groups.

Suggested Labels:
Type/Bug

Suggested Assignees:
@ctienshi

Related Issues:
https://github.com/wso2/cloudformation-apim/issues/25

Description:
The current APIM 3.0.0 Pattern 1 resources contain only MySQL as a DB option. Add postgresql, mssql and oracle support for Pattern 1.

Suggested Labels:
Type/Improvement

Suggested Assignees:
@ctienshi

Affected Product Version:
API 3.0.0

OS, DB, other environment details and versions:
DB - Oracle, MSSQL and Postgre

Description:
Network, DB creation, product deployment are all in a single Cloudformation script. The network creation should be able to run whenever needed.

Description:
Need to update AWS CF scripts to support the new pattern-1 (APIM + MI).