Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Current »

What is WSO2 Managed Cloud?

WSO2 Managed Cloud is a service that allows you to get a team of WSO2 product specialists to run your Cloud for you. These are the typical tasks carried out by the WSO2 Managed Cloud team:

How can I get started?

If you are a WSO2 production support customer, contact your WSO2 account manager, or leave a request at to discuss your Cloud requirements.

How is WSO2 involved?

Although the level of involvement can vary from customer to customer, here are the typical things done by the WSO2 Managed Cloud team:

  • Set up remote access to the customer's Amazon EC2 instance.
  • Set up a domain name system (DNS).
  • Set up a connection to the customer's data center.
  • Set up the environments (e.g., Development, Test, Pre-Production, and Production).
  • Carry out system monitoring and alerting.
  • Implement backup and disaster recovery.
  • Commit the artifacts such as scripts and diagrams for versioning and history.
  • Support and maintain the system. This includes activities like sending weekly updates, handling issues, and managing deployment artifacts such as patches.

Any other tasks such as continuous integration and deployment that are not listed here are handled separately.

Where does WSO2 set up the Cloud?

We use Amazon Virtual Private Cloud (VPC).

It lets you provision a logically isolated section of the Amazon Web Services (AWS) Cloud where you can launch AWS resources in a virtual network that you define. VPCs provide network-level control and isolation for the AWS deployment. You can create a multi-tier network structure on AWS that allows you to keep your data and configurations in the private space and expose them through the DMZ. We always recommend to use VPCs for production deployments on AWS, considering data isolation and security.

What Amazon services does WSO2 use?

WSO2 uses the following unless the customer provides alternatives:

What are the AWS account requirements?

Following is the list of AWS specifics that WSO2 needs:

  • The customer's Amazon Web Services (AWS) account ID.
  • A multi-factor-authentication-enabled Identity and Access Management (IAM) user with access to the customer's AWS Management Consoles.
  • IAM users with privileges to invoke APIs.
  • IAM users with admin privileges to Amazon VPC, EC2, RDS and optionally, to Amazon S3, SES, Route53, and Glacier.

Can I get WSO2 to take over and maintain an existing WSO2 product deployment that I have?

Although WSO2 does not maintain existing customer environments, we will set up a new environment for you by following the WSO2 Managed Cloud standards and best practices and maintain the new environment according to the Managed Cloud Service Level Agreement (SLA).

What does WSO2 use for deployment synchronization?

For artifact synchronization, we currently recommend SVN. Git support is still in the early stages of implementation. We plan to make it available in a future Carbon release.

  • No labels