This is what we do in the implementation phase:
- Set up remote access from WSO2 to your Amazon EC2 instances. See Managing Remote Access.
- Set up the environments (e.g., Dev, Test, Pre-Prod, and Prod).
- Implement monitoring and alerting. See Implementing Monitoring and Alerting for details.
- Implement backup and disaster recovery.
- Commit all scripts, diagrams, and documents to the repository for versioning and history.
Note that WSO2 can facilitate the following upon your request:
- Arrange a third-party consultant to carry out pen tests.
- Reports and dashboards on the Prod environment.
Managing remote access
WSO2 recommends you to do all Managed Cloud deployments in an Amazon Virtual Private Cloud (Amazon VPC). A VPC enables you to launch Amazon Web Services (AWS) into a virtual network that you define. A VPC improves the security of your data by providing network-level control and isolation for the AWS. You can keep your data and configurations in a private space and expose them through the DMZ. This virtual network closely resembles a traditional network, but with improved security and scalability.
To set up your Cloud environments, WSO2 requires access to your Amazon EC2 instances. We access these instances over SSH only, with a Bastion host working as the SSH gateway. The Bastian host can either reside in the VPC or in your own datacenter. The diagrams below depict both scenarios.
Bastian host in the VPC
Bastian host in your datacenter
In addition to the AWS instances, WSO2 requires access to the following resources:
|Need access to||Purpose||Prerequisites|
|AWS management console||To access and manage your AWS.|
WSO2 needs separate user accounts with the following form you:
|AWS API service||To execute automated tools to bring up the infrastructure services such as the VPC, network setup, databases etc.|
WSO2 needs the following from you:
Implementing monitoring and alerting
<coming up soon>
Next, go to Handover.