WSO2 APIM -External Vs Internal Gateway Implementation

When we require to setup separate external and internal gateway to server the traffic for external and internal consumers. WSO2 support multiple gateway deployment pattern.

Below describes the approach to deploy the internal and external WSO2 gateway in AWS environment.

Architecture -

Possible Approaches:

1. By using different EC2 instances for both internal and external gateways:
This way new EC2 instance will be deployed which double the cost for setting up new internal GW at AWS side.

Process:

i. New EC2 instance need to be created.

ii. To serve within the AWS network, internal DNS will be needed and LB is not required.

iii. Then GW service will be deployed over internal DNS and required PORT opening and listener configuration to be in place.

iv. Finally, we will need to request for a DNS record to be used by internal customers and record data mapping should be done.

Pros:
i. High availability will also be there even if other instances go down, no impact will be there on internal GW setup and vice versa.

Cons:
i. Cost will be increased by double almost.
ii. Entire setup needs to be done freshly which will be time consuming activity.

2. By using same EC2 instance for both internal and external gateways:

Process:

i. New Internal DNS to be created , LB not needed.

ii. same wso2 GW service which is in use by external GW will be deployed over 2 separate containers in the existing EC2 instance.
iii. Same ports can be used but connectivity need to be established.

iv. Need to order new DNS and record data mapping to be done for the same.

Pros:
i. By utilizing same EC2 instance, Cost can be optimized.
ii. Setup can be completed quite fast as compare to other approach.

Cons:
i. High availability & scalability will be quite less as compare to other approach.