[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cheat-sheet---en":3,"domain-info---en":3,"topic-info----en":3,"lesson-cloud-computing-fundamentals-cloud-services-and-architecture-cloud-service-models-platform-as-a-service-en":4,"next-cloud-computing-fundamentals-cloud-services-and-architecture-cloud-service-models-platform-as-a-service-en":255,"prev-cloud-computing-fundamentals-cloud-services-and-architecture-cloud-service-models-platform-as-a-service-en":482},null,{"locked":5,"reason":3,"meta":6,"item":16},false,{"title":7,"description":8,"isFree":5,"estimatedMinutes":9,"difficulty":10,"learningObjectives":11},"Platform as a Service (PaaS)","The service model that takes the operating system and runtime off your plate, so you push code and the platform runs it, with AWS Elastic Beanstalk, Heroku, and Google App Engine as the products that deliver it.",15,"beginner",[12,13,14,15],"Define Platform as a Service (PaaS) using the NIST framework","Identify which layers move from customer to provider between IaaS and PaaS","Contrast deploying the same application through IaaS and through PaaS","Explain the boundary between PaaS and the serverless model covered later in this course",{"id":17,"title":7,"body":18,"description":8,"difficulty":10,"estimatedMinutes":9,"extension":196,"infographics":197,"isFree":5,"learningObjectives":198,"meta":199,"navigation":200,"path":201,"quiz":202,"seo":252,"stem":253,"__hash__":254},"courses/courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/02-platform-as-a-service.md",{"type":19,"value":20,"toc":183},"minimark",[21,26,30,34,37,40,44,114,117,121,149,153,159,162,166,169,173,176,180],[22,23,25],"h2",{"id":24},"what-if-you-never-wanted-to-touch-the-operating-system-at-all","What if you never wanted to touch the operating system at all",[27,28,29],"p",{},"The previous lesson ended with you owning an EC2 instance: patching its OS, installing a runtime, configuring a firewall. Now picture a solo developer with a web app to ship by Friday and zero interest in any of that. They do not want to choose an AMI, size a load balancer, or read a patch changelog. They want to hand over code and have it run. Platform as a Service is the model built for exactly that handoff.",[22,31,33],{"id":32},"the-nist-definition-in-practice","The NIST definition, in practice",[27,35,36],{},"NIST defines PaaS as the capability to \"deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages, libraries, services, and tools supported by the provider.\" The consumer does not manage the underlying infrastructure, including network, servers, operating systems, or storage, but does control the deployed application and, often, configuration settings for the environment that hosts it.",[27,38,39],{},"Read that against the IaaS definition from the last lesson and the shift is precise: the operating system, which was yours in IaaS, now belongs to the provider. What is left for you is the application itself and the settings around how it runs.",[22,41,43],{"id":42},"who-manages-what-updated","Who manages what, updated",[45,46,47,63],"table",{},[48,49,50],"thead",{},[51,52,53,57,60],"tr",{},[54,55,56],"th",{},"Layer",[54,58,59],{},"IaaS",[54,61,62],{},"PaaS",[64,65,66,77,87,96,105],"tbody",{},[51,67,68,72,75],{},[69,70,71],"td",{},"Networking, servers, virtualization",[69,73,74],{},"Provider",[69,76,74],{},[51,78,79,82,85],{},[69,80,81],{},"Operating system",[69,83,84],{},"You",[69,86,74],{},[51,88,89,92,94],{},[69,90,91],{},"Runtime and middleware",[69,93,84],{},[69,95,74],{},[51,97,98,101,103],{},[69,99,100],{},"Application code",[69,102,84],{},[69,104,84],{},[51,106,107,110,112],{},[69,108,109],{},"Data",[69,111,84],{},[69,113,84],{},[27,115,116],{},"The whole shift is in one row: the operating system and runtime cross the line from \"you\" to \"provider.\" That is the entire difference between the 2 models, and it deserves more attention than a single row suggests, because it is exactly the line an exam scenario tests.",[22,118,120],{"id":119},"real-products-that-deliver-paas","Real products that deliver PaaS",[122,123,124,132,143],"ul",{},[125,126,127,131],"li",{},[128,129,130],"strong",{},"AWS Elastic Beanstalk:"," packages EC2 instances, a load balancer, and auto-scaling behind one deployment, still built on AWS's IaaS underneath, but you never touch those pieces directly",[125,133,134,137,138,142],{},[128,135,136],{},"Heroku:"," you run ",[139,140,141],"code",{},"git push heroku main",", and Heroku detects your language, installs dependencies, and deploys, with zero server configuration for standard frameworks",[125,144,145,148],{},[128,146,147],{},"Google App Engine and Azure App Service:"," the same trade, upload code, the platform runs it",[22,150,152],{"id":151},"worked-example-the-same-app-2-ways","Worked example: the same app, 2 ways",[27,154,155,156,158],{},"Shipping a small Ruby web app through EC2 means launching an instance, installing Ruby and its dependencies, configuring a web server, attaching a load balancer, and setting up an auto-scaling group, several separate steps, each one yours to get right and keep patched. Shipping the same app through Heroku means running ",[139,157,141],{},". Heroku reads the code, recognizes it needs a Ruby runtime, builds it, and starts serving traffic, all from that 1 command.",[27,160,161],{},"That is not a smaller version of the same job. It is a different job: you stopped managing infrastructure and started managing only your application.",[22,163,165],{"id":164},"the-misconception-paas-is-not-zero-infrastructure-decisions","The misconception: PaaS is not \"zero infrastructure decisions\"",[27,167,168],{},"It is tempting to assume PaaS removes infrastructure thinking completely. It does not. You still pick a dyno or instance size, still set environment variables, and still pay for the capacity you have allocated whether or not it is handling traffic right now, a Heroku dyno you provision keeps running, and keeps billing, until you scale it down yourself. A model that only charges for the moment your code actually executes is a different idea again, serverless computing, and this course covers it later in the Modern Cloud Architectures topic. PaaS narrows your infrastructure job. It does not delete it.",[22,170,172],{"id":171},"the-boundary-ahead-paas-versus-saas","The boundary ahead: PaaS versus SaaS",[27,174,175],{},"PaaS still asks you to write the application. That is the line the next lesson erases entirely.",[22,177,179],{"id":178},"where-this-leaves-you","Where this leaves you",[27,181,182],{},"PaaS trades some of the control IaaS gave you for speed: you stop managing servers and start shipping code straight to a platform that runs it. The next lesson covers what happens when even the code is no longer yours to write.",{"title":184,"searchDepth":185,"depth":185,"links":186},"",3,[187,189,190,191,192,193,194,195],{"id":24,"depth":188,"text":25},2,{"id":32,"depth":188,"text":33},{"id":42,"depth":188,"text":43},{"id":119,"depth":188,"text":120},{"id":151,"depth":188,"text":152},{"id":164,"depth":188,"text":165},{"id":171,"depth":188,"text":172},{"id":178,"depth":188,"text":179},"md",[],[12,13,14,15],{},true,"/courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/02-platform-as-a-service",{"passingScore":203,"questions":204},70,[205,212,218,226,236,244],{"question":206,"type":207,"options":208,"correctAnswer":62,"explanation":211},"A developer wants to deploy a web app without choosing an operating system, patching it, or configuring a web server manually. Which service model fits?","single",[59,209,62,210],"Traditional on-premises hosting","None of these","PaaS takes the operating system and runtime off the developer's plate, leaving only the application code and its configuration. IaaS still requires choosing and patching an OS, and traditional on-premises hosting requires even more of that work.",{"question":213,"type":207,"options":214,"correctAnswer":216,"explanation":217},"In Platform as a Service, the customer is still responsible for patching the operating system the application runs on.",[215,216],"True","False","PaaS is defined by the provider taking over the operating system and runtime, which is exactly what separates it from IaaS. The customer keeps control of the application code and its configuration, but OS patching moves to the provider.",{"question":219,"type":207,"options":220,"correctAnswer":223,"explanation":225},"Compared to IaaS, what does PaaS additionally take off the customer's plate?",[221,222,223,224],"Nothing, IaaS and PaaS manage identical layers","The physical network","The operating system and runtime","Application code and data","The single row that moves between IaaS and PaaS is the operating system and runtime, both of which shift from the customer to the provider. Application code and data stay with the customer in both models.",{"question":227,"type":228,"options":229,"correctAnswers":234,"explanation":235},"Which of the following are PaaS products? (Select all that apply.)","multiple",[230,231,232,233],"AWS EC2","AWS Elastic Beanstalk","Heroku","Google App Engine",[231,232,233],"Elastic Beanstalk, Heroku, and Google App Engine all let you deploy code without managing the operating system underneath it, the defining PaaS trait. AWS EC2 hands you a virtual machine with the OS layer still yours to manage, which makes it IaaS instead.",{"question":237,"type":207,"options":238,"correctAnswer":242,"explanation":243},"A team deploys their app on Heroku and assumes they no longer pay for anything unless their app is actively serving a request. Why is this assumption wrong?",[239,240,241,242],"Heroku does not charge for dynos at all","Heroku is a SaaS product, not a PaaS product","PaaS only charges for storage, never for compute","A provisioned dyno keeps running, and billing, until you scale it down yourself, whether or not it is handling traffic","PaaS still requires choosing and paying for allocated capacity, a dyno or instance size, that keeps running and billing regardless of whether it is currently serving traffic. A model that only charges for the moment code actually executes is a different idea, serverless computing, covered later in this course.",{"question":245,"type":207,"options":246,"correctAnswer":247,"explanation":251},"Deploying an app via Heroku instead of directly via EC2 mainly changes which job the developer is doing. What is that change?",[247,248,249,250],"The developer stops managing infrastructure and manages only the application","The developer now manages the physical hardware instead of AWS","The developer takes on more responsibility for network security","There is no real change, the number of steps stays the same","Shipping through EC2 means installing a runtime, configuring a web server, and setting up a load balancer and auto-scaling group, several separate steps the developer owns. Shipping through Heroku collapses that into a single deploy command, because the developer's job has shifted from managing infrastructure to managing only the application.",{"title":7,"description":8},"courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/02-platform-as-a-service","ERzC9aKGOJ1IGuITkecV6OlXj68W2tYhsKzklnJiklM",{"locked":5,"reason":3,"meta":256,"item":265},{"title":257,"description":258,"isFree":5,"estimatedMinutes":259,"difficulty":10,"learningObjectives":260},"Software as a Service (SaaS)","The service model where the provider runs the entire application and you just use it, from Gmail to Salesforce to Slack, and the multi-tenant architecture that makes running one application for millions of customers affordable.",14,[261,262,263,264],"Define Software as a Service (SaaS) using the NIST framework","Explain multi-tenancy and why it makes SaaS pricing possible","Identify what a SaaS customer can and cannot configure","Distinguish genuine SaaS from a locally installed, subscription-priced application",{"id":266,"title":257,"body":267,"description":258,"difficulty":10,"estimatedMinutes":259,"extension":196,"infographics":431,"isFree":5,"learningObjectives":432,"meta":433,"navigation":200,"path":434,"quiz":435,"seo":479,"stem":480,"__hash__":481},"courses/courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/03-software-as-a-service.md",{"type":19,"value":268,"toc":422},[269,273,276,278,281,284,288,347,350,354,357,360,364,410,414,417,419],[22,270,272],{"id":271},"you-already-used-saas-today","You already used SaaS today",[27,274,275],{},"You did not install a mail server this morning. You did not patch an operating system, provision a virtual machine, or write a line of code. You typed a password into a browser, and your inbox was already there, running on hardware you have never seen, maintained by a team you have never met. That is Software as a Service, and unlike the last 2 lessons, you almost certainly used it before you finished breakfast.",[22,277,33],{"id":32},[27,279,280],{},"NIST defines SaaS as the capability to \"use the provider's applications running on a cloud infrastructure,\" reachable \"through either a thin client interface, such as a web browser... or a program interface.\" The consumer does not manage or control the underlying cloud infrastructure, including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.",[27,282,283],{},"That exception is doing real work in the sentence. You cannot install a plugin on Gmail's servers or change which programming language Salesforce is written in. You can set up an email filter or customize a Salesforce dashboard. The application itself, and everything beneath it, belongs entirely to the provider.",[22,285,287],{"id":286},"who-manages-what-complete","Who manages what, complete",[45,289,290,303],{},[48,291,292],{},[51,293,294,296,298,300],{},[54,295,56],{},[54,297,59],{},[54,299,62],{},[54,301,302],{},"SaaS",[64,304,305,315,326,336],{},[51,306,307,309,311,313],{},[69,308,71],{},[69,310,74],{},[69,312,74],{},[69,314,74],{},[51,316,317,320,322,324],{},[69,318,319],{},"Operating system, runtime",[69,321,84],{},[69,323,74],{},[69,325,74],{},[51,327,328,330,332,334],{},[69,329,100],{},[69,331,84],{},[69,333,84],{},[69,335,74],{},[51,337,338,341,343,345],{},[69,339,340],{},"Data and user configuration",[69,342,84],{},[69,344,84],{},[69,346,84],{},[27,348,349],{},"Data and your own configuration are the one row that never moves. Every other layer eventually crosses to the provider by the time you reach SaaS.",[22,351,353],{"id":352},"multi-tenancy-the-architecture-that-makes-this-affordable","Multi-tenancy: the architecture that makes this affordable",[27,355,356],{},"A SaaS vendor is not running a separate copy of Gmail for each of its billions of users. Gartner describes multitenancy as software where a single instance serves multiple customers, logically isolated from each other but physically sharing the same infrastructure underneath. Your inbox and a stranger's inbox run on the same application instance, the same servers, with the provider's software guaranteeing neither of you can see the other's data.",[27,358,359],{},"That sharing is exactly what makes SaaS pricing work. Spreading one application instance across millions of tenants is dramatically cheaper per customer than running a dedicated copy for each one, which is why a SaaS subscription usually costs a small fraction of what building and hosting the same application yourself would.",[22,361,363],{"id":362},"real-products-by-category","Real products, by category",[45,365,366,376],{},[48,367,368],{},[51,369,370,373],{},[54,371,372],{},"Category",[54,374,375],{},"Examples",[64,377,378,386,394,402],{},[51,379,380,383],{},[69,381,382],{},"Email and productivity",[69,384,385],{},"Gmail, Microsoft 365",[51,387,388,391],{},[69,389,390],{},"Customer relationship management",[69,392,393],{},"Salesforce",[51,395,396,399],{},[69,397,398],{},"Team communication",[69,400,401],{},"Slack, Zoom",[51,403,404,407],{},[69,405,406],{},"File storage and collaboration",[69,408,409],{},"Dropbox, Google Workspace",[22,411,413],{"id":412},"the-misconception-a-subscription-is-not-the-same-thing-as-saas","The misconception: a subscription is not the same thing as SaaS",[27,415,416],{},"It is tempting to call anything billed monthly \"SaaS.\" It is not. A boxed application you install on your own laptop, and personally keep updated, does not become SaaS just because its license renews every month. The test is not the billing model, it is who runs it and where. If the provider hosts, patches, and operates the application on infrastructure you never touch, and you reach it through a browser or an API, it is SaaS. If you installed it yourself and you are the one applying its updates, it is not, no matter how the invoice arrives.",[22,418,179],{"id":178},[27,420,421],{},"SaaS is the end of the handoff that started with IaaS: the provider now runs the operating system, the runtime, and the application itself, and the only thing left on your side of the line is your data and your own settings. You have now met all 3 service models individually. The next lesson puts them side by side and gives you the boundary an exam actually tests: not what each one is, but which one a scenario is describing.",{"title":184,"searchDepth":185,"depth":185,"links":423},[424,425,426,427,428,429,430],{"id":271,"depth":188,"text":272},{"id":32,"depth":188,"text":33},{"id":286,"depth":188,"text":287},{"id":352,"depth":188,"text":353},{"id":362,"depth":188,"text":363},{"id":412,"depth":188,"text":413},{"id":178,"depth":188,"text":179},[],[261,262,263,264],{},"/courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/03-software-as-a-service",{"passingScore":203,"questions":436},[437,445,449,457,463,471],{"question":438,"type":207,"options":439,"correctAnswer":443,"explanation":444},"Which of these best matches the NIST definition of SaaS?",[440,441,442,443],"The consumer provisions virtual machines and manages the operating system","The consumer deploys their own code onto infrastructure they do not manage","The consumer builds and hosts their own web application","The consumer uses the provider's application, reached through a browser or API, without managing anything underneath it","SaaS means the provider runs the entire application, network, servers, OS, and the application itself, and the consumer just uses it through a thin client like a browser or a program interface. The first 2 options describe IaaS and PaaS, and the third describes building software yourself, not consuming it as a service.",{"question":446,"type":207,"options":447,"correctAnswer":216,"explanation":448},"According to NIST, a SaaS customer has no ability to configure anything about the application, not even their own account settings.",[215,216],"NIST's SaaS definition specifically carves out an exception for limited user-specific application configuration settings, such as setting up an email filter or customizing a dashboard. What the customer cannot do is change the underlying infrastructure or the application's core code.",{"question":450,"type":207,"options":451,"correctAnswer":452,"explanation":456},"In a multi-tenant SaaS application, how are different customers' data typically kept separate?",[452,453,454,455],"Customers share the same application instance and underlying infrastructure, but the provider logically isolates each tenant's data","Each customer gets an entirely separate copy of the application running on dedicated hardware","Data is not actually separated, all customers can see all data","Each customer must build their own isolation layer","Multitenancy means many customers share one application instance and its infrastructure, with the provider's software guaranteeing logical isolation between them even though they are physically integrated. A dedicated copy per customer describes single-tenant architecture, which is the more expensive alternative SaaS providers generally avoid.",{"question":458,"type":228,"options":459,"correctAnswers":461,"explanation":462},"Which of the following are genuinely SaaS products? (Select all that apply.)",[393,230,460,233],"Gmail",[393,460],"Salesforce and Gmail are complete applications the provider runs entirely, which you access through a browser without managing anything underneath, the SaaS pattern. AWS EC2 hands you a virtual machine to manage yourself, IaaS, and Google App Engine runs your own code for you, PaaS, so neither qualifies as SaaS.",{"question":464,"type":207,"options":465,"correctAnswer":468,"explanation":470},"A company sells a desktop application under a monthly subscription. Customers install it themselves on their own laptops and are responsible for applying its updates. Is this SaaS?",[466,467,468,469],"Yes, because it is billed monthly like a subscription","Yes, because all modern software subscriptions count as SaaS","No, because the customer installs and maintains it themselves rather than the provider hosting and running it","No, because SaaS must always be free","The test for SaaS is not the billing model, it is who runs the application and where. Software the customer installs and personally updates on their own device is not SaaS, no matter how the invoice arrives, because the provider never hosts or operates it.",{"question":472,"type":207,"options":473,"correctAnswer":475,"explanation":478},"Why does multi-tenancy typically make SaaS pricing cheaper per customer than a dedicated, self-hosted version of the same application?",[474,475,476,477],"It doesn't, self-hosting is always cheaper","One application instance and its infrastructure are shared across many customers instead of duplicated for each one","SaaS vendors do not have to pay for servers at all","Multi-tenancy has nothing to do with pricing","Spreading one application instance across millions of tenants is dramatically cheaper per customer than running a dedicated copy for each one, which is exactly why SaaS subscriptions usually undercut the cost of building and hosting the same application privately. SaaS vendors still pay for servers, they just divide that cost across every tenant sharing them.",{"title":257,"description":258},"courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/03-software-as-a-service","Bz80kzlz2lf2a_WX0U_WjpUYEdYVwZpvHa09s8CmK5E",{"locked":5,"reason":3,"meta":483,"item":491},{"title":484,"description":485,"isFree":200,"estimatedMinutes":9,"difficulty":10,"learningObjectives":486},"Infrastructure as a Service (IaaS)","The service model that hands you raw compute, storage, and networking and leaves the operating system, runtime, and application on your side of the line, with AWS EC2, Azure Virtual Machines, and Google Compute Engine as the products that deliver it.",[487,488,489,490],"Define Infrastructure as a Service (IaaS) using the NIST framework","Identify which layers of the stack IaaS leaves for the customer versus the provider","Name IaaS products from major providers and what each one delivers","Explain why virtualized infrastructure still leaves real operational work on the customer",{"id":492,"title":484,"body":493,"description":485,"difficulty":10,"estimatedMinutes":9,"extension":196,"infographics":641,"isFree":200,"learningObjectives":642,"meta":643,"navigation":200,"path":644,"quiz":645,"seo":686,"stem":687,"__hash__":688},"courses/courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/01-infrastructure-as-a-service.md",{"type":19,"value":494,"toc":632},[495,499,502,504,507,510,514,580,583,587,607,610,614,617,620,624,627,629],[22,496,498],{"id":497},"the-layer-a-hypervisor-hands-you","The layer a hypervisor hands you",[27,500,501],{},"You already know a hypervisor can slice one physical server into dozens of isolated virtual machines, and that a real cloud service lets you request one of those machines yourself, on demand, with no ticket and no wait. What you have not seen yet is what a provider actually sells you once that machine exists, and how much of the stack above it lands in your lap instead of theirs. Infrastructure as a Service is the model that hands you the most: raw compute, storage, and networking, with the operating system and everything above it left for you to install, configure, and patch.",[22,503,33],{"id":32},[27,505,506],{},"NIST's definition of IaaS is precise about the split: the consumer can \"provision processing, storage, networks, and other fundamental computing resources\" and \"deploy and run arbitrary software, which can include operating systems and applications.\" The consumer does not manage the underlying cloud infrastructure, but has control over operating systems, storage, and deployed applications, and possibly limited control of select networking components, such as host firewalls.",[27,508,509],{},"That last clause matters. You do not touch the physical switch or the hypervisor, but you do configure the firewall rules that decide which traffic reaches your own virtual machine. IaaS gives you a box, full control of everything inside it, and a narrow window into the network path that reaches it.",[22,511,513],{"id":512},"who-manages-what","Who manages what",[45,515,516,525],{},[48,517,518],{},[51,519,520,522],{},[54,521,56],{},[54,523,524],{},"Who manages it in IaaS",[64,526,527,534,541,548,554,560,566,572],{},[51,528,529,532],{},[69,530,531],{},"Networking (physical)",[69,533,74],{},[51,535,536,539],{},[69,537,538],{},"Servers and storage hardware",[69,540,74],{},[51,542,543,546],{},[69,544,545],{},"Virtualization (the hypervisor)",[69,547,74],{},[51,549,550,552],{},[69,551,81],{},[69,553,84],{},[51,555,556,558],{},[69,557,91],{},[69,559,84],{},[51,561,562,564],{},[69,563,100],{},[69,565,84],{},[51,567,568,570],{},[69,569,109],{},[69,571,84],{},[51,573,574,577],{},[69,575,576],{},"Host firewall rules",[69,578,579],{},"You (limited networking control)",[27,581,582],{},"Compare that to the 5 characteristics from the previous topic: resource pooling and rapid elasticity are what let the provider hand you that virtual machine in seconds. IaaS is where those characteristics get packaged into an actual product you can buy.",[22,584,586],{"id":585},"real-products-that-deliver-iaas","Real products that deliver IaaS",[122,588,589,595,601],{},[125,590,591,594],{},[128,592,593],{},"Virtual machines:"," AWS EC2 (Elastic Compute Cloud), Azure Virtual Machines, Google Compute Engine",[125,596,597,600],{},[128,598,599],{},"Block and object storage:"," AWS EBS and S3, Azure Managed Disks and Blob Storage, Google Persistent Disk and Cloud Storage",[125,602,603,606],{},[128,604,605],{},"Virtual networking:"," AWS VPC, Azure Virtual Network, Google VPC",[27,608,609],{},"Every one of these gives you a resource you provision, configure, and are responsible for keeping patched and running. None of them ships an application. They ship the pieces you build one from.",[22,611,613],{"id":612},"worked-example-what-launching-a-vm-actually-commits-you-to","Worked example: what launching a VM actually commits you to",[27,615,616],{},"Launch an EC2 instance and AWS asks 2 questions first: which OS image (an AMI, for example Amazon Linux 2023) and which instance type. Pick a t3.micro, 2 vCPUs and 1 GiB of memory, and AWS's on-demand rate in US East (N. Virginia) is $0.0104 an hour, about $7.59 for a 730-hour month, with storage and data transfer billed separately.",[27,618,619],{},"That price buys you a running Linux box and nothing else. Nobody at AWS installs a web server on it, applies its security patches, or configures its firewall. You do all 3, the same way you would on a physical machine, except you never touched a data center, ordered hardware, or waited for a shipment.",[22,621,623],{"id":622},"the-misconception-its-in-the-cloud-does-not-mean-its-someone-elses-problem","The misconception: \"it's in the cloud\" does not mean \"it's someone else's problem\"",[27,625,626],{},"It is tempting to hear \"cloud\" and assume the provider now handles security and maintenance for you. IaaS does not work that way. The provider took the procurement, power, cooling, and physical maintenance off your plate, the exact burden the first lesson in this course described. It did not take the operating system off your plate. An unpatched IaaS virtual machine is just as vulnerable as an unpatched physical server sitting in your own building; the vulnerability is still yours to close.",[22,628,179],{"id":178},[27,630,631],{},"IaaS gives you the most control of the 3 service models, and, in exchange, the most responsibility: everything from the operating system up is yours to run. The next lesson covers what happens when a provider takes the operating system and runtime off your plate too, and what you get, and give up, in return.",{"title":184,"searchDepth":185,"depth":185,"links":633},[634,635,636,637,638,639,640],{"id":497,"depth":188,"text":498},{"id":32,"depth":188,"text":33},{"id":512,"depth":188,"text":513},{"id":585,"depth":188,"text":586},{"id":612,"depth":188,"text":613},{"id":622,"depth":188,"text":623},{"id":178,"depth":188,"text":179},[],[487,488,489,490],{},"/courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/01-infrastructure-as-a-service",{"passingScore":203,"questions":646},[647,652,656,663,672,678],{"question":648,"type":207,"options":649,"correctAnswer":59,"explanation":651},"A team needs to install a specific Linux kernel version required by a legacy driver, with full root access to configure it. Which service model gives them that?",[302,650,59,62],"Traditional on-premises hosting only","IaaS is the only cloud service model that hands the customer the operating system layer, including root access to install a specific kernel version. PaaS and SaaS both take the OS off the customer's hands, and on-premises hosting is not a cloud service model at all, just the alternative the cloud replaces.",{"question":653,"type":207,"options":654,"correctAnswer":216,"explanation":655},"In Infrastructure as a Service, the provider manages the guest operating system running inside your virtual machine.",[215,216],"In IaaS, the customer manages the guest operating system, along with the runtime, applications, and data. The provider's responsibility stops at the hypervisor: it manages the physical servers, storage, networking, and virtualization layer that the virtual machine runs on.",{"question":657,"type":207,"options":658,"correctAnswer":660,"explanation":662},"Under the NIST definition of IaaS, which of these might the consumer have limited control over, in addition to the operating system, storage, and deployed applications?",[221,659,660,661],"The physical network switches","Select networking components, such as host firewalls","The hypervisor itself","NIST's IaaS definition specifically calls out possible limited control of select networking components, like host firewalls, alongside full control of the OS, storage, and applications. The physical switches and the hypervisor stay firmly on the provider's side in every case.",{"question":664,"type":228,"options":665,"correctAnswers":670,"explanation":671},"Which of the following are the customer's responsibility under IaaS? (Select all that apply.)",[666,667,668,669],"Patching the operating system","Maintaining the physical server hardware","Installing and configuring the application runtime","Managing the hypervisor",[666,668],"Patching the OS and installing the runtime both sit above the hypervisor, which is exactly where the customer's responsibility begins in IaaS. Physical hardware maintenance and hypervisor management stay with the provider in every one of the 3 service models, not just IaaS.",{"question":673,"type":207,"options":674,"correctAnswer":676,"explanation":677},"Which of these is an IaaS product?",[393,675,676,231],"Google Workspace","Google Compute Engine","Google Compute Engine provisions virtual machines and leaves the OS, runtime, and application to the customer, which is the IaaS pattern. Salesforce and Google Workspace are complete applications you just use, SaaS, and Elastic Beanstalk manages the OS and runtime for you, which makes it PaaS.",{"question":679,"type":207,"options":680,"correctAnswer":682,"explanation":685},"A team runs a t3.micro EC2 instance priced at $0.0104 per hour continuously for a 730-hour month, before counting storage or data transfer. Approximately what does the compute cost that month?",[681,682,683,684],"$0.76","$7.59","$75.90","$759.00","$0.0104 multiplied by 730 hours comes to about $7.59. That figure only covers the compute hours themselves; a real bill would add storage and any data transfer on top of it.",{"title":484,"description":485},"courses/cloud-computing-fundamentals/en/domains/02-cloud-services-and-architecture/01-cloud-service-models/01-infrastructure-as-a-service","E2TtoH5uaTA_XFqzAN-GojxuORCUsRcIDLg93LcegCI"]