0% found this document useful (0 votes)
247 views

AWS Architecture

The document provides an overview of S. Suresh's background and qualifications. It mentions that S. Suresh has 30 years of experience in the IT industry working for major companies like IBM, Wipro and Oracle. It also states that S. Suresh is an AWS Solution Architect Professional and that their areas of focus include cloud, storage and Linux.

Uploaded by

fno investments
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
247 views

AWS Architecture

The document provides an overview of S. Suresh's background and qualifications. It mentions that S. Suresh has 30 years of experience in the IT industry working for major companies like IBM, Wipro and Oracle. It also states that S. Suresh is an AWS Solution Architect Professional and that their areas of focus include cloud, storage and Linux.

Uploaded by

fno investments
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

▪ S.

Suresh, Founder & CEO of CloudSiksha


▪ 30 yrs of experience in IT industry
▪ Worked in major IT companies like IBM, Wipro and Oracle
▪ Range of assignments including Developer, Architect and Manager
▪ AWS Solution Architect Professional Certified
▪ Cloud, Storage and Linux the focus areas
All brand names, trademarks, logos are the All the images, unless credited, have been
property of the respective owners taken from the Amazon AWS website

3
▪ We will be working on the labs using the
free tier provided by Amazon. While we
will try to ensure that none of the labs
IMPORTANT cross the free tier threshold, it is possible
for various reasons that this threshold
DISCLAIMER could be breached and the user could be
charged. We will not be responsible for
any additional charge that may incur in
your account for any reason.
This course is about AWS Infrastructure

How do you design infrastructure in order to host an


application?

How do you provide isolation when required?

How do you secure your infrastructure?

How do you provide high availability & fault tolerance?

How to design for Hybrid cloud cases?

How do you monitor the performance of your infrastructure?


▪ Started in 2004
▪ SQS Service Offered

AMAZON WEB ▪ Storage Service in 2006

▪ Large suite of services

SERVICES ▪ Keeps increasing at a rapid pace

▪ The largest Public Cloud Service provider


8
▪ http://docs.aws.amazon.com/AWSEC2/l
atest/UserGuide/using-regions-
availability-zones.html
▪ When architecting on AWS, AWS suggests that we use
their Well Architected Framework
▪ https://aws.amazon.com/architecture/well-
architected/?wa-lens-whitepapers.sort-
by=item.additionalFields.sortDate&wa-lens-
whitepapers.sort-order=desc
▪ Six Pillars
▪ Operation Excellence
▪ Reliability
▪ Performance Efficiency
▪ Security
▪ Cost Optimization
▪ Sustainability

▪ Well Architected Lenses


▪ Architectural Guidance to specific industries
▪ General Design Principles for Financial
Industry
▪ Documented operational planning
▪ Automated infrastructure and application
deployment
▪ Security by design
▪ Automated Governance
▪ Access to financial data for workloads running in the
cloud is a key component for the operations of
financial services institutions
▪ Real-time and historical market data, alternative
data such as consumer movement, and buying
decisions

▪ Data has strict requirements around user entitlements


and data redistribution
▪ Low latency requirements that vary depending on how
the market data is used
▪ Trade decision vs. post trade analytics
▪ Can vary from seconds to sub-millisecond

▪ Reliable network connectivity for market data


providers and exchanges
▪ Every financial institution deals with volumes of
information for regulatory reporting
▪ Financial services data lake architectures supporting
these use cases share the following characteristics:
▪ They implement data quality, integrity, and lineage
into the ingest and processing pipelines
▪ They require that data is encrypted at rest and in
transit
▪ They mask or tokenize personally Identifiable
Information (PII) data to meet regulatory
requirements (e.g. EU General Data Protection
Regulation)
▪ They use Data Catalog with fine-grained access
control and entitlements
▪ In Open Banking, banks use Application Programming
Interfaces (APIs) to securely share their customer data
with third-party developers and service providers
▪ Allowing automated and secure access to the
functionality of their core banking platform

▪ Open Banking architectures supporting these use


cases share the following characteristics:
▪ They use an OAuth 2.0 authorization standard.
▪ They have an API driven infrastructure and elastic
and scalable environment.
▪ They provide instant or near-instant access to
customer account data.
▪ They have tamper-resistant logging and audit
capabilities.
▪ Financial institutions are increasingly investing in their own customer-facing
channels
▪ Mobile applications, web portals, call center agents and chatbots, advisors/brokers
▪ To enhance the overall customer experience

▪ User engagement architectures supporting these use cases share the following
characteristics
▪ They use high volumes of real-time data ingestion from public and private sources
▪ Require different data protection considerations based on data classification
▪ Employ event-driven architectures to leverage on-demand scalability and pay-per-use
model
▪ Includes real-time and archival data flows
▪ 3 tier architecture model
▪ Understand current and legacy
deployments
▪ Hybrid cloud
▪ Global Deployment

▪ Event Driven Architecture model


▪ Increasingly used for customer
engagements
▪ Microservices Model
▪ Modern App development and
Deployment
[email protected]
▪ AWS Local Zones are a new type of AWS
infrastructure deployment
▪ Places AWS compute, storage, database, and other
select services closer to large population, industry,
and IT centers
AWS LOCAL ▪ Where no AWS Region exists today

ZONES
▪ Services which can run in Local Zones
▪ EC2
▪ EBS
▪ VPC
▪ FSx
▪ ELB

You might also like