Overview: Perbedaan revisi
(→Security) |
(→Servers) |
||
Baris 18: | Baris 18: | ||
==Servers== | ==Servers== | ||
− | The VPC | + | The VPC consists of a number of different servers dedicated to different tasks: |
− | Database | + | * NAT (for controlling access to the VPC) |
− | Web | + | * Database (master and read-replica slave servers) |
− | Messaging | + | * Web servers (for hosting the web site) |
− | Processing | + | * Messaging server (for managing SMS, IM and email) |
− | Reporting | + | * Processing (for processing incoming requests on email) |
+ | * Reporting (for analysing data and generating outputs) | ||
+ | * Wiki (for managing this Wiki server) | ||
+ | |||
+ | While some of these servers are single fixed instances, others are Elastic Cloud Computing (EC2) instances. This means that, as demand increases, the server is automatically replicated to increase capacity. As demand decreases, servers no longer in use are shut down. | ||
==Storage== | ==Storage== |
Revisi per 2 September 2014 14.00
Daftar isi
iSIKHNAS Server Infrastructure
iSIKHNAS is hosted in a Virtual Private Cloud (VPC) on Amazon Web Services (AWS) cloud servers. The VPC consists of a number of different components (servers, queues, storage) that expand and contract according to need.
Security
Access security
The Virtual Private Cloud allows computers within the could to communicate between themselves rapidly and easily, while blocking all access from outside the VPC. Access is controlled by a single, highly secure NAT server.
All communications with iSIKHNAS are encrypted using secure industry standard Transport Layer Security (TLS) encryption, preventing interception of any data exchanged between the user and the VPC.
Administrative access through the NAT server is controlled using digital certificates.
Data security and redundancy
The iSIKHNAS database runs on a single master database, with multiple slave databases providing real-time replication. Some of the slaves are always in a different physical location to the master. In case of failure of the master, one of the slaves is automatically promoted to be the master, resulting in down-time of only a few seconds.
In addition to database replication, the full system is automatically backed up every 12 hours and stored in replicated off-site storage.
The VPC is spread across two security zones, representing different physical locations, with servers and queues replicated in each zone. This means that should there be a catastrophic failure of an entire data centre, the system will continue to run uninterrupted.
Servers
The VPC consists of a number of different servers dedicated to different tasks:
- NAT (for controlling access to the VPC)
- Database (master and read-replica slave servers)
- Web servers (for hosting the web site)
- Messaging server (for managing SMS, IM and email)
- Processing (for processing incoming requests on email)
- Reporting (for analysing data and generating outputs)
- Wiki (for managing this Wiki server)
While some of these servers are single fixed instances, others are Elastic Cloud Computing (EC2) instances. This means that, as demand increases, the server is automatically replicated to increase capacity. As demand decreases, servers no longer in use are shut down.
Storage
Buckets