Ideation

CS7201

To ideate the solution for the

identified problem statement

Under the Guidance of

Sourabh Sharma

Sheikh M. Tadeeb AU19B1014

TABLE OF CONTENTS

Brainstorming..................................................... 01

User Need & Requirements ............................. 02

Filteration ........................................................... 03

Current System Architecture ......................... 04

Concept-1 ........................................................... 05

Flowchart (Concept-1) ..................................... 06-07

Concept-2 ........................................................... 08

Flowchart (Concept-2) ..................................... 09-10

Concept-3 ........................................................... 11

Flowchart (Concept-3) ..................................... 12-13

Comparison Chart ............................................. 14

Selection Criteria .............................................. 15

In a nutshell, brainstorming is one of the most creative ways of problem-
solving in which we work on ideas. We can either come up with a new idea
or build on an existing idea as well. Since there is no rule of thumb in
brainstorming, it can be applied individually or in a group.

01
02
03
04
1 . SYSTEM CONSOLIDATION
I'll be rehosting everything over AWS Cloud.

Using AWS-ORGANIZATION we can remove department silo's and also

take the advantage of consolidated billing.

Allowing Admin to navigate freely in all departments & Limit-restriction of

one department over another by giving proper roles and using SCP.

2 . AVAILABILITY & SCALIBILITY

Putting all the infrastructure in Multi Availability Zone with replication

Allowing Dynamic Scaling based on CPUUtilization & Disk read/writes

Automatic replacement of infrastructure based on Applications health

3 . SYSTEM MONITORING
Using inbuilt AWS CloudWatch to monitor all the infrastructure based on Matrics

For custom matrix I'll install CloudWatch agent over instances and use AWS
CloudWatch to monitor all the infrastructure based on Matrics

4. WEBSITE DELIVERY
If the website is static, then deploying the website on s3 and enabling S3-static
website hosting.

If the website is Dynamic, then deploying the website on instance and Utilizing
S3 for static or media contents, fetching them using Pre-Signed URL

Utilizing CloudFront feature for Fast and Global delivery. Using Origin-Access-
Identity to restrict and secure the access over the origin.

05
01

02

06
03

04

07
1 . SYSTEM CONSOLIDATION
I'll be rehosting everything over AWS Cloud.

Using AWS-Control Tower we can remove department silo's and also take the
advantage of consolidated billing and lot of other features like Account
Factory etc.

Allowing Admin to navigate freely in all departments & Limit-restriction of one

department over another by giving proper roles and using Guard Rails.

2 . AVAILABILITY & SCALIBILITY

Putting all the infrastructure in single Availability Zone with replication

Doing manual scaling of infrastructure based on our needs.

Automatic replacement of infrastructure based on Instance health

3 . SYSTEM MONITORING
Storing all the logs in S3 and then using Kinesis Data Analytics Product

Utilizing s3 & using 3rd party tools for analysis eg: Grafana

4. WEBSITE DELIVERY
If the website is static, then deploying the website on s3 and enabling S3-static
website hosting.

Using Latency Based routing for Domain.

Using Global Accelerator for fast access to the website.

08
01

02

09
03

04

10
1 . SYSTEM CONSOLIDATION

I'll be rehosting everything over AWS Cloud with some private services
running from On-premise cloud.

Using AWS Direct link or VPN or both we can remove Cloud & On-premise
silo's and also take the advantage of fast speed and lower latency over a
secured encrypted network

Allowing Admin to navigate freely in all departments & Limit-restriction of one

department over another by giving proper roles and using AWS-config
policies.

2 . AVAILABILITY & SCALIBILITY

Putting all the infrastructure in muti-region with replication in 2 AZ

Doing manual scaling of infrastructure based on our needs.

Automatic replacement of infrastructure based on Instance health

3 . SYSTEM MONITORING
Storing all the logs in S3 and then using 3rd party Analytics Product

4. WEBSITE DELIVERY
Hosting website in elastic beanstack.

Or using containers to host different microservice of the website.

11
01

02

12
03

04

13
14
 Clearly Concept-1 is best suited for our
needs as:

1. Its Cost effective, compared to Concept-2

which implements Control tower which is more
feature rich but our company won't be
requiring all the features at this stage and
anytime soon

2. It is easy & fast to implement, diagnose and work

with compared to Concept-2 and Concept-3 which
required addtional technical skills to handle and
sometime are more complex.

3. It implements or deploys our website very

quickly. Also allowing us to cache our website
static contents globally at very minimal charges or
depending on our load its free sometimes.

15