This is what we do in the implementation phase:
|2||Set up a domain name system (DNS).|
|3||Set up an SMTP server.|
|4||Set up an NTP server.|
Set up the environments (e.g., Development, Test, Pre-Production, and Production).
Commit the artifacts such as scripts , diagrams, and documents to the repository and diagrams for versioning and history.
Hand over the production environment to the customer.
Set up remote access to
the customer's Amazon EC2 instants
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. This virtual network closely resembles a traditional network, but with improved security and scalability.
We access your the customer's Amazon EC2 instants 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 the customer's datacenter as depicted in the diagrams below:
- The Bastian host is in the VPC: The Bastion host is in the public subnet and allows SSH traffic only to the WSO2 network via a non-standard port. All other hosts are configured to accept SSH requests from the Bastion host only.
- The Bastian host in your the customer's datacenter: The Bastion host is in your the customer's datacenter, and the other hosts are configured to accept SSH requests from the Bastion host only. When WSO2 DevOps want to connect to the Bastion host via SSH, they do it remotely via a client console.
The Domain Name System (DNS) is a server that translates domain names, which are alphanumeric and can be easily remembered by humans, to numerical IP addresses that are recognized by the Internet. The DNS is the Internet's primary directory service that determines which physical server a request should be routed to when a visitor calls a domain name over the Internet.
For the servers in your the customer's datacenter to connect to the virtual machines in the Amazon VPC, you we need to have a domain name to IP mappings set up in a DNS server. You Customers can either use your their own DNS server servers for this or allow WSO2 to use the Amazon Route53 service as depicted in the diagrams below:
SMTP is shortened for Simple Mail Transfer Protocol, which is an Internet standard for email transmission. An SMTP server is a computer running SMTP, and which delivers email messages to their corresponding recipients.
You The customers can either use your their own SMTP server servers or let allow WSO2 to use Amazon SES. Shown below is how an SMTP server in your the customer's datacenter communicate the WSO2 EC2 instant in the Amazon VPC.
The WSO2 Managed Cloud offering is for hosting and maintaining WSO2 products in a Amazon EC2 instant that you purchaseinstance that the customer purchases. Here are the tasks performed by the WSO2 Managed Cloud team when setting up the environments. For additional services, you the customer can purchase WSO2 Support.
|Tasks within the WSO2 Managed Cloud SLA||Tasks covered by WSO2 Support services|
|Set up an AWS account upon the customer's request (excluding the costs pertaining to the hosting services).|
Application and service development and deployment.
Set up the virtual machines and networking in the customer's AWS.
IT management (creating users
Deploy the WSO2 products that the customer purchased according to the deployment architecture that was created in the Planning phase.
System quality assurance.
Create user accounts with admin privileges for the customer to log in to the WSO2 products' Management Consoles.
Vulnerability assessment testing.
Penetration testing (WSO2 will outsource to third-party consultants).
|Guarantee the availability of the Managed Cloud (See Support and Maintenance).||WSO2 product training.|
|Upgrade WSO2 product and install patches upon request.|