Amazon web services

Business case:
Introduction to business:

AWS (Amazon Web Services) is Amazon's complete cloud computing platform, which comprises
infrastructure as a service (IaaS), platform as a service (PaaS), and packaged software as a service (SaaS)
products. AWS services may provide a company with resources like computational power, database
storage, and content distribution. Amazon Web Services (AWS) was founded in 2006 as an extension of
Amazon.com's internal infrastructure for handling its online retail activities. AWS is among one of the
very first firms to provide a pay-as-you-go cloud-based platform, which expands to meet users' needs for
computation, storage, and throughput. AWS provides a variety of tools and solutions for businesses and
software developers which may be utilized in data centers throughout the globe (Gillis, A. S. (2020, April
7).

Current challenges faced by AWS:

AWS provides a vast number of services as well as an almost limitless amount of configuration options
for them to be used in conjunction with your application deployment. Most businesses struggle to find out
how to set up their environments in one of the most cost-effective manners while still meeting their
scalability and reliability needs. Because there are so many choices, it's easy to pick the least expensive
alternative. Cost-cutting also necessitates keeping track of consumption. It's simple to lose sight of a
deployed resource that's no longer required. You can be paying needless expenses if you don't keep track
of resources like Amazon EC2, RDS, DynamoDB, and others. You could have Amazon EBS volumes
that aren't associated with any resources, for example.

Moreover, some challenges that we came across regarding the migration of AWS are:

1. Determining the most important business goals

2. Achieving the correct quality and performance 
3. Acknowledge the whole cost as soon as possible
4. Accepting modern technology

AWS cloud migration involves a lot of preparation and skill, but changing in the correct way saves
money and satisfies company goals. As a result, it's critical to enlist the support of AWS migration
professionals or partners who provide AWS services & solutions and benefit from their expertise.
System Architecture (as per IEEE Standard 1471-2000 Recommended
Practice):
System of interest:

System: placing orders into the system regarding services or merchandise

Hardware: Database servers, computers, inventory systems

Software: Web application, cloud services, architectural services, mobile application, websites.

Processes: fulfilling orders, keeping an inventory, ensuring purchases

People: employees, customers, managers

Data: inventory, order details

Utilization: the system is being utilized for placing and fulfilling orders by the customers

The mission of the company:

AWS defines its mission statement as:

“Amazon is guided by four principles: customer obsession rather than competitor focus, passion for invention,
commitment to operational excellence, and long-term thinking. Customer reviews, 1-Click shopping, personalized
recommendations, Prime, Fulfillment by Amazon, AWS, Kindle Direct Publishing, Kindle, Fire tablets, Fire TV,
Amazon Echo, and Alexa are some of the products and services pioneered by Amazon."

Which can basically be shortened to be guided through competition and innovation that guarantees excellence in
terms of being both future and short run-oriented. For these very reasons, AWS has come up with many different
services that prove to be beneficial for its customers by valuing their reviews above all.

Environment:
Internal:

Due to the recent pandemic, there has been a surge in online orders and hence it was important to keep
inventory and track orders that were being placed on the website and through the application. Moreover,
cloud services had been very popular among customers in recent years.

External:

External factors such as growing competition from giant companies like Ali Baba and other e-commerce
websites have put a strain on the orders that were being placed. Moreover, this stunted the business’
growth in recent years.
Interaction among the system interconnected with both the environments are seen through the customers
and companies which acquire the service both within UAE as well as abroad.

Stakeholders:

The key stakeholders of AWS are:

Stakeholders Roles and description

Consumers (C) Different teams participating in OS administration, including:

 Development studios that administer full-stack

application environments
 Employ the patch management solution for long-running
instances.
 Teams in charge of the application server's operating
system

Cloud engineering (CE) The group in charge of:

 Constantly improving the patch management solution.

 Automating cloud-based services.
 Assisting with automation.

Cloud business office The team in charge of 

(CBO)
 Managing the solution's consumer experience.
 User engagement and enablement
 Assuring the patch design connects with the demands of
customers.

Cloud service/product Employees in charge of:

owner (CPO)
 Aiding through cloud services to users is the
responsibility of this individual.

 Collaborating with the administration team to ensure that

services are delivered in accordance with standards and
 expectations.

 Managing all platform-related customer expectations and

escalations.

 Being in charge of the platform's roadmap.

Security operations (SO) Managing patch baselines and their approvals

The security operations The person in charge of path compliance
manager (SOM)
1. Consumers
2. Cloud engineers
3. Cloud business officers
4. Cloud product owner
5. Security operation officers
6. Security operations manager

Concerns of stakeholders:

 Security governance:
Develop, manage, and convey security duties, obligations, obligations, principles, practices, and
procedures in an effective and efficient manner. The efficiency of any security program depends
on having clear lines of consistency and accountability.
 Assuring security:
Establish provable privacy and security measures that satisfy those objectives by documenting
controls into a complete control architecture. Examine your cloud vendor's audited financial
statements, compliance licenses, or attestations to learn more about the rules they already had in
place, how all those controls have now been tested, and whether the measures in your stretched IT
network are working properly.
 Access management:
At a large scale, manage identities and permissions. You can build identities in AWS or link your
identity source, then give users the rights they need to sign in, access, provision, and coordinate
AWS resources and associated apps.
  Determining threat:
Recognize and detect possible security flaws, dangers, or unusual actions. You'll be able to
prioritize defensive controls if you have a better grasp of security concerns. You will be able to
respond to attacks quicker and benefit from security incidents if you have effective threat
detection.
 Managing vulnerability:
Identify, categorize, fix, and remediate security vulnerabilities on a regular basis. Changes to
current systems or the installation of new systems might potentially cause vulnerabilities. Scan
for vulnerabilities on a regular basis to assist guard against emerging threats. To correlate systems
with known vulnerabilities, use detection software and endpoint agents.
 Protecting infrastructure:
Verify that your workload's systems and services are secured from unexpected and illegal access,
as well as potential vulnerabilities. Protecting your infrastructure against unwanted and
unintended access, as well as a potential vulnerability, will help you improve your cloud security
posture.
 Protecting data:
Retain knowledge and transparency over data in your business, as well as how it is viewed and
utilized. One of the main goals of your security program is to protect your data against
unexpected and unauthorized access, as well as potential vulnerabilities.
 Incident response:
By properly responding to security problems, you can lessen the potential for harm. So that they
can mitigate the possible impact by responding quickly, effectively, and consistently to security
issues. 

Performance: concerns regarding the efficiency and effectiveness of the system

Reliability: to keep in check whether the system can be trusted to fulfill the task at hand

Security: ensuring data protection and regular vulnerability checks

Scalability: the extent to which the system can handle the workload

Evolvability: the updates that the system uptakes to improve performance.

Architectural description views:

Use Case: In use case diagrams we present a high-level picture of the system and describe its
needs to our system's stakeholders.

The Zachman Framework: divides the organization's architecture into multiple viewpoints and
classifies it. This makes finding issues to consider inside the architecture much easier. 

BPMN Models: The BPMN gives businesses the opportunity to explain the internal dynamics of
a system using graphics and graphical notations, making it easier to comprehend the system's
functionalities.

Component diagram

From: (How to Quickly Design AWS Architecture Diagrams. (2021, September 27).

Use case diagram:

From: (Use case: distribution - AWS Elemental MediaConnect. (n.d.)

Zachman Framework:

Zachman
What How Where Who When Why
Framework

Identifying Identifying Identifying Allocating Identifying Identifying

Executive inventory processes appropriate responsibility timings key

perspective through types through the distribution types motivators

types types

Business Defining Determining Business Business role Defining Defining

managemen business business location and and work business business

t perspective entity and transformation correction product intervals and environment

relationship and inputs and identification movements and means

outputs through

responsibilitie
 s

Representing Process Illustrating Responsibility Illustrating Presenting

inventory representation distribution division business system ends

through through in respect to through roles movements and key

Architect
system entity transforming loactions and work motivators
perspective
and and realizing products

relationship inputs and

outputs

Specifying Narrowing Specifying Allocating technologica Technology

technological down technologica responsibility l movements is seen as a

entities and technological l connections with respect to were seen in motivator in

relationships transformation seen within workloads and regard to aiding the

Engineer
s and paths of the system job roles business system
perspective
inputs and and drawing outcomes

outputs seen links to

within the location for

system strategy

Configuring Coding Configuring Responsibility Timing Finding tool

inventory and processes that distribution assessing configuratio and meaning

Technician relationships transform channels through the n through through

perspective inputs into through tool division of tool motivation

outputs connection roles and work movement configuratio

and location product and interval n

Operational Process Role division Operations The Operation

Enterprise
instantiation’ outlook of and work location and movements tools that are
perspective
s thorough operations product are connections are seen as in place to
 inventory including seen as ups and boost

converting responsibilit downs in the motivation

inputs to y operations of instantiation

outputs instantiations the business s

Process modeling and performance analysis:

Process identification and description:

AWS offers more services and features than any other cloud provider, ranging from traditional
infrastructure technologies like computation, storage, and databases to new technologies like artificial
intelligence and machine learning, data lakes and analytics, and the Internet of Things. This enables
moving your existing apps to the cloud and building practically just about everything you can imagine
faster, simpler, and more cost-effective.

Within those services, AWS provides the most advanced capabilities. For example, AWS has the most
datasets which are intended for various sorts of applications, allowing you to pick the best tool for the job
in terms of cost and performance.

We may utilize perfectly alright security controls to offer your workers, apps, and equipment the access
they must have AWS facilities and benefits under readily deployable governance guardrails for
applications operating on AWS. AWS Identity Services gives a clear lot of flexibility in where and how
you handle your staff, vendor, and customer identities, so you can transfer existing workloads to AWS
with confidence. AWS Identity Services enables to development of a unified authentication and
authorization approach across your physical and AWS environments for hybrid workload deployments.
We may use AWS Identity Services for customer-facing web and phone applications to easily add sign-up
and sign-in capabilities for your app users, which are supported by scalable cloud directories.

The process requires accessing the service either through the application available for download on both
androids and IOS software. We can also access the service through the web browser at the website. Once
done, we must create an account to further utilize the services. Once an account is made through an email
and by entering basic information, you can access the services you are looking for. One may even
upgrade to a premium to access specialized service offerings.
Business process modeling notation (BPMN):

Taken from: (Ruecker, B. R. (2017, December).

Process performance management:

EC2 Instance type Software/hr EC2/hr Total/hr

t2.micro $0 $0.012 $0.012

t2.small $0 $0.023 $0.023

t2.medium
$0 $0.046 $0.046
Vendor Recommended

t2.large $0 $0.093 $0.093

m3.medium $0 $0.067 $0.067

m3.large $0 $0.133 $0.133

EC2 Instance type Software/hr EC2/hr Total/hr

m3.xlarge $0 $0.266 $0.266

m3.2xlarge $0 $0.532 $0.532

m4.large $0 $0.10 $0.10

m4.xlarge $0 $0.20 $0.20

m4.2xlarge $0 $0.40 $0.40

m4.4xlarge $0 $0.80 $0.80

m4.10xlarge $0 $2.00 $2.00

c3.large $0 $0.105 $0.105

c3.xlarge $0 $0.21 $0.21

c3.2xlarge $0 $0.42 $0.42

c3.4xlarge $0 $0.84 $0.84

c3.8xlarge $0 $1.68 $1.68

c4.large $0 $0.10 $0.10

c4.xlarge $0 $0.199 $0.199

c4.2xlarge $0 $0.398 $0.398

c4.4xlarge $0 $0.796 $0.796

cc2.8xlarge $0 $2.00 $2.00

cr1.8xlarge $0 $3.50 $3.50

r3.large $0 $0.166 $0.166

r3.xlarge $0 $0.333 $0.333

 EC2 Instance type Software/hr EC2/hr Total/hr

r3.2xlarge $0 $0.665 $0.665

r3.4xlarge $0 $1.33 $1.33

r3.8xlarge $0 $2.66 $2.66

g2.2xlarge $0 $0.65 $0.65

g2.8xlarge $0 $2.60 $2.60

hs1.8xlarge $0 $4.60 $4.60

i2.xlarge $0 $0.853 $0.853

i2.2xlarge $0 $1.705 $1.705

i2.4xlarge $0 $3.41 $3.41

i2.8xlarge $0 $6.82 $6.82

d2.xlarge $0 $0.69 $0.69

d2.2xlarge $0 $1.38 $1.38

d2.4xlarge $0 $2.76 $2.76

d2.8xlarge $0 $5.52 $5.52

Taken from: (AWS Marketplace: Bonita BPM powered by System Sector. (n.d.). Awsmarketplace.)

Process evaluation summary:

Through our analysis we were able to conclude several problems that needed action to be taken in order
to optimize the system. The very first problem that was identified was the dependence of actions on
digital means. Although there is human monitoring of the actions that take place, we feel that it is
necessary to increase the frequency of these monitoring sessions in order to ensure complete transparency
and to identify any discrepancies that may be a result of mechanized software dependence. This led us to
convert the system into one that involved greater human interaction through integrated roles that ensured
monitoring and human involvement. This made the whole system more effective in the sense that it had
little to no errors and any discrepancies that were recorded were immediately tracked and taken care of.

Service-oriented architecture:

Taken from: (DeCandia, G., Hastorun, D., Jampani, M., Kakulapati, G., Lakshman, A., Pilchin, A.,
Sivasubramanian, S., Vosshall, P., & Vogels, W. (2007)

By using the restful api:

API gateway
Compute resource Amazon RDS

/cart
GET AWS Lambda
 Method/verb GET
URI www.aws/awslambda/regional/amazonrds.com
JSON {“item”: “compute”, “database”: “RDS”}

References:

Gillis, A. S. (2020, April 7). Amazon Web Services (AWS). SearchAWS.

https://www.techtarget.com/searchaws/definition/Amazon-Web-Services
How to Quickly Design AWS Architecture Diagrams. (2021, September 27). Createrly.

https://www.google.com/url?sa=i&url=https%3A%2F%2Ffanyv88.com%3A443%2Fhttps%2Fcreately.com%2Fblog%2Fdiagrams

%2Faws-templates-for-architecture-diagrams

%2F&psig=AOvVaw1Zk8V9JKbCMIxeN5NxEWYt&ust=1649693851295000&source=images

&cd=vfe&ved=0CAoQjRxqFwoTCLDLo9PyifcCFQAAAAAdAAAAABAD

Use case: distribution - AWS Elemental MediaConnect. (n.d.). Amazon.Com.

https://docs.aws.amazon.com/mediaconnect/latest/ug/use-cases-distribution.html

AWS Marketplace: Bonita BPM powered by System Sector. (n.d.). Awsmarketplace.

https://aws.amazon.com/marketplace/pp/prodview-phheiroj6liqo

Ruecker, B. R. (2017, December). Kennisgeving voor omleiding. Camundaforum.

https://www.google.com/url?sa=i&url=https%3A%2F%2Ffanyv88.com%3A443%2Fhttps%2Fforum.camunda.org%2Ft

%2Fbpmn-vs-aws-step-function

%2F5460&psig=AOvVaw2jydrV9L0eFkngJiOArCXb&ust=1649700696225000&source

=images&cd=vfe&ved=0CAoQjRxqFwoTCLCM-8KMivcCFQAAAAAdAAAAABAD

DeCandia, G., Hastorun, D., Jampani, M., Kakulapati, G., Lakshman, A., Pilchin, A.,

Sivasubramanian, S., Vosshall, P., & Vogels, W. (2007). Dynamo. ACM SIGOPS

Operating Systems Review, 41(6), 205–220. https://doi.org/10.1145/1323293.1294281