WIXLIB

Serverless DefinedCourse NavigationSer ver less Ar ch it ect u r esCou r se I n t r odu ct ionSection 1Ser ver less App Com pon en t sSer ver less Def in edSection 2Fr on t En dApplicat ionDat aPer sist en ceWh y Use Ser ver less?Why Use Serverless?Ser ver lessArchitecturesAr ch it ect u r esServerlessLim itations of ServerlessFr on t -En d Ser ver lessLayer : S3 an dClou dFr on tSection 3Applicat ion Layer : AWSLam bda Fu n ct ion sSection 4Back -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessSection 5M on it or in g Ser ver lessApplicat ion M et r icsA ser ver less applicat ion doesn't necessarily need all thecom ponents defined above to work. It all depends on your u secase an d app bu sin ess logic.Ser ver less App Ar ch it ect u r esEven t -Dr ivenAr ch it ect u r eM icr oser vices-BasedAr ch it ect u r eSer ver less ser vices are excellent for m icroservices- and event-basedarchitectures,where withinyou canbreak downproverbialm onolithic m onster and- Com ponentsapplicationarethelooselycou pled.focus- t at doingM odu lar design ? com ponents are independentlyaredeployable.one taskveryefficiently.- Componentscom m unicate via ligh t w eigh t pr ot ocols such as HTTP.- Works well with con t in u ou s deliver y m et h odologies an dIn additionthe HAarthateventot -basedch itserverlessect u r es. services inherently offer, having a m odular,event-based m icroservices architecture application on top of it also providesadded st abilit y an d disast er r ecover y.Section 6BackBack t o M ainNext

Serverless DefinedCourse NavigationLim it at ion s of Ser ver lessCou r se I n t r odu ct ionSection 1Ser ver less Def in ed. An d t h e Lim it at ion sSection 2- Testing and debugging is ch allen gin gWh y Use Ser ver less?Why Use Serverless?Ser ver lessArchitecturesAr ch it ect u r esServerlessLimLimitationsit at ion sofofServerlessSer ver less- Security con cer n s- Not built for lon g-r u n n in g processes- Cold start tim es can affect resources/functions that are notused frequently, cau sin g lat en cy- Best for applications with short-running processes, as you'reFr on t -En d Ser ver lessLayer : S3 an dClou dFr on tSection 3Applicat ion Layer : AWSLam bda Fu n ct ion sSection 4charged for the t im e you r pr ocess/ code r u n sSer ver less on t h e RiseWith an in cr easin g am ount of users, the serverless com m unity isgrowing at a fast pace and finding ways to m it igat e or er adicat e allthe lim its m entioned above as m uch as possible. For exam ple, withAWS Lam bda serverless functions (FaaS), you can now use AWS X-RayBack -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessservice to debug in depth as well as use Clou dWat ch Events to keepyour functions ready and "warm ed" up.Section 5M on it or in g Ser ver lessApplicat ion M et r icsSection 6BackBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontCourse NavigationOver viewCou r se I n t r odu ct ionTr adit ion al Web Ser ver Fr on t En dSection 1http/httpsSer ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tSection 3UserWWW- With traditional server "full" architectures, scalin gn eeds t o be m on it or ed ? extra stress- Servers to m ain t ain !- Overkill for sin gle-page, static websiteOver viewOverviewSer ver less Fr on t En dSetting Up AWS S3 as aStandalone Website viaConsoleAWS CloudFront as anHTTPS Endpoint ProviderApplicat ion Layer : AWSLam bda Fu n ct ion sSection 4Back -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessUser-WWWAWS - Clou dFr on tS3 - Websit eS3 scales au t om at ically as traffic burstsHighly available thanks to being AWS S3 backedNo servers to m ain t ain at allDevelopers can easily leverage SDK/ API for end-to-endsetup processSection 5AWS - Clou dFr on tS3 - Websit eNextBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontCourse NavigationOver viewCou r se I n t r odu ct ionTr adit ion al Web Ser ver Fr on t En dSection 1http/httpsSer ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tSection 3UserWWW- With traditional server "full" architectures, scalin gn eeds t o be m on it or ed ? extra stress- Servers to m ain t ain !- Overkill for sin gle-page, static websiteOver viewOverviewSetting Up AWS S3 as aStandalone Website viaConsoleAWS CloudFront as anHTTPS Endpoint ProviderApplicat ion Layer : AWSLam bda Fu n ct ion sSection 4Back -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessSer ver less Fr on t En d-Scalable-Integration with AWS CloudFront-UserEasy integrationwith AWS RouteDNSWWWAWS - 53CloudFr on t- For individual web pages or client-side scripts-S3 - Websit eS3scales mauatict omaccessat icallytraffic burstsProgramviaasSDK/APIsHighly available thanks to being AWS S3 backedNo servers to m ain t ain at allDevelopers can easily leverage SDK/ API for end-to-endsetup processSection 5AWS - Clou dFr on tS3 - Websit eNextBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontCourse NavigationOver viewCou r se I n t r odu ct ionTr adit ion al Web Ser ver Fr on t En dSection 1Ser ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tSection 3- Content delivery network of edge locationshttp/https- Caches static files for lower latency- DDos protection- UserOffloads website WWW- Integrates well with AWS S3OffersHTTPS terminationACM- - Withtraditionalserver"full" viaarchitectures,scalin g- n eedsProgramm atict o bem onaccessit or edvia? SDK/APIsextra stress- Servers to m ain t ain !- Overkill for sin gle-page, static websiteOver viewOverviewSer ver less Fr on t En dSetting Up AWS S3 as aStandalone Website viaConsoleAWS CloudFront as anHTTPS Endpoint ProviderApplicat ion Layer : AWSLam bda Fu n ct ion sSection 4Back -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessUser-WWWAWS - Clou dFr on tS3 - Websit eS3 scales au t om at ically as traffic burstsHighly available thanks to being AWS S3 backedNo servers to m ain t ain at allDevelopers can easily leverage SDK/ API for end-to-endsetup processSection 5AWS - Clou dFr on tS3 - Websit eNextBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontCourse NavigationSet t in g Up AWS S3 as a St an dalon e Websit e via Con soleCou r se I n t r odu ct ionSection 1S3 Bu ck etwith ObjectsSer ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tSection 3Over viewOverviewSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon soleAWS CloudFront as anHTTPS Endpoint ProviderApplicat ion Layer : AWSLam bda Fu n ct ion sSection 4Back -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessS3 St at icWebsite- St at ic w ebsit e: A website with fixed content. Shows thesam e content to all viewers.- S3 st at ic w ebsit e bu ck et is sim ply a bucket with aproperty enabled to allow it to host content.- Rem em ber : S3 website URL is not the sam e as an S3bucket URL!- Content hosted by a website bucket has to be pu bliclyr eadable ? i.e., s3:GetObject allowed on it.- You cannot have ser ver -side code execu t ion sincethere's no back-end servers to run code on. Onlyclien t -side scr ipt in g an d in dividu al w eb pages can behosted.- S3 policies and ACLs still apply here, so beware ofallowing read access on your publicly visible contentwithin the bucket.Section 5Con f igu r in g S3 via CLIBackBack t o M ainNext

Front-End Serverless Layer: S3 and CloudFrontCourse NavigationSet t in g Up AWS S3 as a St an dalon e Websit e via Con soleCou r se I n t r odu ct ionAWS CloudConfigureS3WebsiteOverviewSection 1I AM Role w it hAt t ach ed I AM PolicyS3 Bu ck etwith ObjectsSer ver less Def in edSection 2St at ic Con t en t1- St at ic w ebsit e: A website with fixed content. Shows thesam e content to all viewers.Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tSSHSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon sole- Rem em ber : S3 website URL is not the sam e as an S3Su m mbucketar y BrURL!eak dow n of St eps1AWS CloudFront as anHTTPS Endpoint ProviderSection 4Section 5AWShostedCLI API byin staalled.I n our case,hasw e tologbein puviabliclySSH- HaveContentwebsitebuckett roeadablean EC2 in?st ance s3:GetObjectalr eady set u pallowedw it h it . on it.i.e.,n t er mediat ehavebu t import ant st ep:- IYoucannotserver-sidecode execu t ion sinceCreateandattachan I AM serversr ole (allowingS3read/access)tothere'snoback-endto runcode writeon. OnlyyourEC2in st anceiptso itincanassumthat rolealandm akesuccessfulclient -sidescrg and inedividuw ebpagescan APIbecalls.hosted.Applicat ion Layer : AWSLam bda Fu n ct ion sBack -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessEC2- S3 st at ic w ebsit e bu ck et is sim ply a bucket Uploadwith aHTM Lproperty enabledtoallowittohostcontent.index.h t m l FileSecurity Group Allowing SSHSection 3Over viewOverview2S3 St at icWebsiteS3 Bu ck et Host in g2ssupoliciese t h e cor randect AWScomm anhere,ds t o cre an d m- I S3ACLsCLIstillapplysoeatbewareofodif yS3 bu ck et an d u pload you r w ebsit e f iles in t h e m ost basicallowing read access on your publicly visible contentin st an ce, n am ely: in dex.h t m l.within the bucket.Su ppor t s t w o URL f or m at s:1. bucket-nam e .s3-website. AWS-region .amazonaws.comCon f igu r in g S3 via CLI2. bucket-nam e .s3-website- AWS-region .am azonaws.com- S3 static website requires public read access on bucket- Does not support HTTPSBackNextBackBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontAWS Clou dFr on t as an HTTPS En dpoin t Pr oviderCourse NavigationCou r se I n t r odu ct ionClou dFr on t via CLISection 1Ser ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tAm azonClou dFr on t-Worldwide group of edge (caching) locations.-On initial creation, a Clou dFr on t dist r ibu t ion takes about 20m inutes to sync across the globe.Section 3Over viewOverviewto the origin (server, bucket, EC2 instance, etc.) from where yourSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon sole-AWSCloudFrontClou dFr on tasasananAWSHTTPSEndpointEn dpoin tProviderPr oviderHTTPS-Applicat ion Layer : AWSLam bda Fu n ct ion sWorks via " w eb dist r ibu t ion s" in our scenario, which are hookedcontent is to be served and cached from .User can change value of " view er pr ot ocol policy " in webdistribution to redirect all HTTP traffic to HTTPS.CloudFront provides default SSL cer t if icat es you can use forHTTPS; however, users can upload their own custom certs androute to CloudFront from a DNS such as Route 53.Section 4Back -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessLow-LatencyAccess to Contentvia CachingSection 5BackBack t o M ainDDoSPreventionHTTPSEndpoint

Front-End Serverless Layer: S3 and CloudFrontAWS Clou dFr on t as an HTTPS En dpoin t Pr oviderCourse NavigationCou r se I n t r odu ct ionClou dFr on t via CLISection 1Ser ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tI n t er n etAm azonClou dFr on t-Worldwide group of edge (caching) locations.-On initial creation, a Clou dFr on t dist r ibu t ion takes about 20-m inutesto sync across the globe.EdgeEdgeEdgeLocat ionLocat ionLocat ionWorks via " w eb dist r ibu t ion s" in our scenario, which are hookedSection 3Over viewOverviewto the origin (server, bucket, EC2 instance, etc.) from where yourSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon sole-User can change value of " view er pr ot ocol policy " in webAWSCloudFrontClou dFr on tasasananAWSHTTPSEndpointEn dpoin tProviderPr oviderHTTPS-distribution to redirect all HTTP traffic to HTTPS.CloudFront provides default AWSSSL cer t if icat es you can use forClou dFr on tHTTPS; however, users can upload their own custom certs andApplicat ion Layer : AWSLam bda Fu n ct ion scontent is to be served and cached from .3 as Route 53.route to CloudFront from4 a DNS suchSection 4Back -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessLow-LatencyAccess to ContentS3 Websit evia CachingBucketSection 5BackBack t o M ain2DDoSPreventionAWSCLI1HTTPSEndpointOAI

Front-End Serverless Layer: S3 and CloudFrontAWS Clou dFr on t as an HTTPS En dpoin t Pr oviderCourse NavigationCou r se I n t r odu ct ionClou dFr on t via CLISection 1Ser ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tAm azonClou dFr on t-Worldwide group of edge (caching) locations.-On initial creation, a Clou dFr on t dist r ibu t ion takes about 20m inutes to sync across the globe.Section 3-Works via " w eb dist r ibu t ion s" in our scenario, which are hookedOver viewOverviewto the origin (server, bucket, EC2 instance, etc.) from where yourSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon sole-AWSCloudFrontClou dFr on tasasananAWSHTTPSEndpointEn dpoin tProviderPr oviderHTTPS-content is to be served and cached from .User can change value of " view er pr ot ocol policy " in webdistribution to redirect all HTTP traffic to HTTPS.CloudFront provides default SSL cer t if icat es you can use forHTTPS; however, users can upload their own custom certs andApplicat ion Layer : AWSLam bda Fu n ct ion sroute to CloudFront from a DNS such as Route 53.Section 4Low-LatencyAccess to Contentvia CachingBack -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessSection 5DDoSPreventionHTTPSEndpoint1Create an or igin access iden t it y in CloudFront. It is a special CloudFrontuser that can access an S3 bu ck et on beh alf of u ser s accessing objectsin a website bucket via the CloudFront service.BackBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontAWS Clou dFr on t as an HTTPS En dpoin t Pr oviderCourse NavigationCou r se I n t r odu ct ionClou dFr on t via CLISection 1Ser ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tAm azonClou dFr on t-Worldwide group of edge (caching) locations.-On initial creation, a Clou dFr on t dist r ibu t ion takes about 20m inutes to sync across the globe.Section 3Over viewOverviewWorks via " w eb dist r ibu t ion s" in our scenario, which are hookedto the origin (server, bucket, EC2 instance, etc.) from where yourSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon sole-AWSCloudFrontClou dFr on tasasananAWSHTTPSEndpointEn dpoin tProviderPr oviderHTTPS-content is to be served and cached from .User can change value of " view er pr ot ocol policy " in webdistribution to redirect all HTTP traffic to HTTPS.CloudFront provides default SSL cer t if icat es you can use forHTTPS; however, users can upload their own custom certs andApplicat ion Layer : AWSLam bda Fu n ct ion sroute to CloudFront from a DNS such as Route 53.Section 4Low-LatencyAccess to Contentvia CachingBack -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessSection 5DDoSPreventionHTTPSEndpoint2Attach an S3 bu ck et policy to the already created S3 bucketwebsite to allow CloudFront OAI user s3:Get Object access on allobjects within the bucket.BackBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontAWS Clou dFr on t as an HTTPS En dpoin t Pr oviderCourse NavigationCou r se I n t r odu ct ionClou dFr on t via CLISection 1Ser ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tAm azonClou dFr on t-Worldwide group of edge (caching) locations.-On initial creation, a Clou dFr on t dist r ibu t ion takes about 20m inutes to sync across the globe.Section 3Over viewOverviewWorks via " w eb dist r ibu t ion s" in our scenario, which are hookedto the origin (server, bucket, EC2 instance, etc.) from where yourSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon sole-AWSCloudFrontClou dFr on tasasananAWSHTTPSEndpointEn dpoin tProviderPr oviderHTTPS-content is to be served and cached from .User can change value of " view er pr ot ocol policy " in webdistribution to redirect all HTTP traffic to HTTPS.CloudFront provides default SSL cer t if icat es you can use forHTTPS; however, users can upload their own custom certs andApplicat ion Layer : AWSLam bda Fu n ct ion sroute to CloudFront from a DNS such as Route 53.Section 4Low-LatencyAccess to Contentvia CachingBack -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessSection 5DDoSPreventionHTTPSEndpoint3Create a Clou dFr on t distribution using CLI . It caches and serves yourcontent via edge locations.BackBack t o M ain

Front-End Serverless Layer: S3 and CloudFrontAWS Clou dFr on t as an HTTPS En dpoin t Pr oviderCourse NavigationCou r se I n t r odu ct ionClou dFr on t via CLISection 1Ser ver less Def in edSection 2Fr on t -En d Ser ver lessLayer : S3 an dClou dFr on tAm azonClou dFr on t-Worldwide group of edge (caching) locations.-On initial creation, a Clou dFr on t dist r ibu t ion takes about 20m inutes to sync across the globe.Section 3Over viewOverviewWorks via " w eb dist r ibu t ion s" in our scenario, which are hookedto the origin (server, bucket, EC2 instance, etc.) from where yourSettingSet t in gUpUpAWSAWSS3S3asasaaStandaloneSt an dalon eWebsiteWebsit eviaviaConsoleCon sole-AWSCloudFrontClou dFr on tasasananAWSHTTPSEndpointEn dpoin tProviderPr oviderHTTPS-content is to be served and cached from .User can change value of " view er pr ot ocol policy " in webdistribution to redirect all HTTP traffic to HTTPS.CloudFront provides default SSL cer t if icat es you can use forHTTPS; however, users can upload their own custom certs andApplicat ion Layer : AWSLam bda Fu n ct ion sroute to CloudFront from a DNS such as Route 53.Section 4Low-LatencyAccess to Contentvia CachingBack -En d Dat aPer sist en ce Layer : AWSAu r or a Ser ver lessSection 5DDoSPreventionHTTPSEndpoint4Get the configuration of the Clou dFr on t dist r ibu t ion you ju st cr eat ed,m odify it (PriceClass, OAI, redirect all to HTTPS), and update the orig

event-based microservices architecture application on top of it also provides added stability and disaster recovery. - Actions/code/functions are triggered in reaction to events. - An event could be a change in state. - Normally, events are triggered via front-end layer and consumed by