Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



Set up remote access from WSO2 to your Amazon EC2 instances. See Managing Manage Remote Access.


Set up the environments (e.g., Development, Test, Pre-Production, and Production).


Implement monitoring and alerting. See Implementing Monitoring and Alerting for details.


Implement backup and disaster recovery.


Commit all artifacts such as scripts, diagrams, and documents to the repository for versioning and history. See Commit the artifacts.


Hand over the Production environment to you with WSO2 Carbon user accounts that have admin privileges to access the Management Consoles.


Note that WSO2 can facilitate the following upon your request:

  • Arrange a third-party consultant to carry out penetration tests.
  • Provide reports and dashboards on the Production environment.
  • Arrange trainings and workshops for you.
  • Provide read-only access to the monitoring dashboards and the log viewer.




Manage remote access

WSO2 does 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. T his virtual network closely resembles a traditional network, but with improved security and scalability.


Need access toPurposePrerequisites
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:

  • AWS IAM user with admin privileges for Amazon VPC, Amazon EC2, Amazon RDS and Amazon S3.

  • Access key and secret key generated for the same user.



Implement monitoring and alerting

WSO2  hosts all monitoring services in a separate subnet in the same VPC where your Cloud services are hosted.  We configure Nagios Remote Plugin Executor (NRPE)  in all Linux hosts to monitor the resource utilization and set thresholds. If any resource gets utilized beyond a certain threshold, or if an application isn’t responding properly, NRPE triggers alerts and notifications. 


We maintain application logs using the the LogstashElasticSearch and Kibana solutions. WSO2 configures a Logstash agent in each host to collect application data and send over to ElasticSearch that is running on the monitoring host in a different subnet in the same VPC. The Kibana dashboard is exposed only to the WSO2 network over HTTP/S.


If the customer wants to synchronize their monitoring with that of WSO2, DevOps teams from both sides need to agree on certain technical requirements such as additional agents that must be installed on hosts, how to expose dashboards to other networks, send alerts to additional email addresses, phones, etc.

Implement backup and disaster recovery

<coming up soon>

Commit the artifacts

<coming up soon>

Next, go to Handover Support and Maintenance.