Table 2 Infrastructure of the customized content management system
Infrastructure services from AWS | Function |
|---|---|
EC2 | EC2 and Amazon Machine Image used to create the virtual machine. Then Apache Server and PHP programming environment inside each instance were installed as our web/app server environment. |
S3 Storage | Used for saving our application development files |
CloudFront | Used CloudFront as a Content Delivery Network (CDN) in order to provide a contents distribution to end users with low latency, high data transfer speeds. |
Mongo lab | This document oriented database service on top of AWS EC2 provided the persistence layer for our contents storage and back-up service |
VPC | Put our EC2 servers and RDS database into the VPC group in order to provide a more secured and isolated private network for all our cloud services. |
IAM and Trusted Advisor | Security is always a top priority for a clinical study related application. By adopting these 2 services, we can create a secured strategy to enables us to securely control access to AWS services and resources for our users. Using IAM, we can create and manage AWS users and groups, and use permissions to allow and deny their access to our CERTAIN CMS application resources |
Elastic load balancer | This AWS on-demand scaling load balancer and monitor system assured our application can be elastically expanded to support global usage in a most efficient way. |
Software components: | |
CERTAIN CMS web admin | HTML5 based web admin portal manages all the medical cards |
CMS contents APIs | The web service server to be used by different CERTAIN client software (flash, CMS admin and mobile app) |
MongoDB | MongoDB is the persistence layer for our content management system |