Introduction and Overview

Company Background: A Medical Company

A Medical Company is a startup software as a service (SaaS) company.

It has built an online medical social networking and diagnosis assistance application for users in APAC, the US, and Europe.

The application connects patients and doctors to:

Allow online appointments, remote consultation, remote diagnosis, electronic prescription transfer, and payment services.

Allow customers to upload documents and images. Text is extracted from documents, and images are converted into multiple formats.

The application has not yet been launched publicly.

The Request

A Medical Company has hired you to architect an infrastructure in AWS to meet their application needs.

In preparation for your meeting with them, they provided information about their current environment.

A Medical Company: Current Environment

For your preparations, the customer provided this information on their current environment.

A Medical Company:

Deployed its current development and test infrastructure with a server hosting company.

Uses Microsoft Windows servers to host their web and application tiers with Microsoft SQL Server Standard Edition backend databases.

The application launch date is coming soon and they expect many users to start using the application.

Believes it would be best to use cloud technologies to support its rapid growth.

Thinks the new cloud platform could host the development, test, and production environments.

Web Tier:

Two physical servers (Two CPUs / 4-GB memory)

Microsoft Windows 2016 Base with Internet Information Services (IIS)

High Availability Proxy load balancer used to balance traffic between the web servers

Application Tier:

Two physical servers (Four CPUs / 16-GB memory)

Microsoft Windows 2016 Base with Internet Information Services (IIS)

High Availability Proxy load balancer used to balance traffic between app servers

Database Tier:

One physical server (Eight CPUs / 32-GB memory / 5-TB storage)

SQL Server Standard Edition with Microsoft Windows 2016 Base

DBAs access and manage the database, but no RDMBS or advanced configuration is

required.

A Medical Company Customer Requirements

The requirements include:

1. Configuring access permissions to conform with AWS best practices.

2. Building networks that conform to AWS best practices while providing all the necessary

network services to the application in their different environments.

3. Building an architecture that matches the current architecture at the server hosting

company and that can handle doubling the number of servers.

4. Securing all medical information, as medical information usually contains highly sensitive

personally identifiable information (PII).

5. Utilizing load balancers for web tier and application tier that must support HTTP, HTTPS,

TCP protocols plans to move their application into AWS.

6. Architecture should be resilient (built for business continuity).

7. Configuring auditing to track all user actions.

Design a AWS solution with:

1. Networks that conform to AWS best practices while providing all the necessary network

services to the application in their different environments.

2. An architecture that matches the current architecture at the server hosting company and

that can handle doubling the number of servers.

3. Security for all medical information, as medical information usually contains highly

sensitive personally identifiable information (PII).

4. Load balancers for web tier and application tier that must support HTTP, HTTPS, TCP

protocols plans to move their application into AWS.

Image of 3 tier System: Web Tier- 2 CPUs, 4-GB memory, MS Windows ke Web Tier- 2 CPUs, 4-GB memory, MS Windows App Tier- 4 CPUs, 16-GB memory, MS Windows App Tier- 4 CPUs, 16-GB memory, MS Windows Database Tier- 8 CPUs, 32-GB memory, 5-TB storage, MS Windows, SQL Server SE Existing 3-Tier Architecture Web Tier: Two physical servers (Two CPUs / 4-GB memory) Image of 3 tier System: Web Tier- 2 CPUs, 4-GB memory, MS Windows ke Web Tier- 2 CPUs, 4-GB memory, MS Windows App Tier- 4 CPUs, 16-GB memory, MS Windows App Tier- 4 CPUs, 16-GB memory, MS Windows Database Tier- 8 CPUs, 32-GB memory, 5-TB storage, MS Windows, SQL Server SE Existing 3-Tier Architecture Web Tier: Two physical servers (Two CPUs / 4-GB memory)