[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cheat-sheet---en":3,"domain-info---en":3,"topic-info----en":3,"next-aws-certified-cloud-practitioner-cloud-technology-and-services-storage-services-storage-gateway-and-backup-en":4,"lesson-aws-certified-cloud-practitioner-cloud-technology-and-services-storage-services-storage-gateway-and-backup-en":364,"prev-aws-certified-cloud-practitioner-cloud-technology-and-services-storage-services-storage-gateway-and-backup-en":375},null,{"locked":5,"reason":3,"meta":6,"item":17},false,{"title":7,"description":8,"isFree":9,"estimatedMinutes":10,"difficulty":11,"learningObjectives":12},"Databases on AWS","Understand how databases work on AWS, the difference between a managed service and self-managing on EC2, relational versus non-relational data, and the idea of purpose-built databases.",true,14,"beginner",[13,14,15,16],"Explain what a managed database service is and how it differs from running a database on Amazon EC2","Compare relational and non-relational databases","Describe the idea of purpose-built databases","Identify the main database categories AWS offers and what each is for",{"id":18,"title":7,"body":19,"description":8,"difficulty":11,"estimatedMinutes":10,"extension":308,"infographics":309,"isFree":9,"learningObjectives":310,"meta":311,"navigation":9,"path":312,"quiz":313,"seo":361,"stem":362,"__hash__":363},"courses/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/05-database-services/01-databases-on-aws.md",{"type":20,"value":21,"toc":298},"minimark",[22,27,31,34,38,41,44,47,50,144,147,151,154,162,168,171,175,178,272,275,279],[23,24,26],"h2",{"id":25},"why-this-matters","Why this matters",[28,29,30],"p",{},"Almost every application needs to store data somewhere, and the database is where that data lives. On the CLF-C02 exam, you do not need to design schemas or write queries. You need to recognize the AWS database services, know whether a service is relational or non-relational, and match a described need to the right one.",[28,32,33],{},"This lesson sets up the rest of the topic. It covers what a managed database service is, how it differs from running a database yourself, the split between relational and non-relational data, and the idea of purpose-built databases. The next lessons go deeper into the specific services.",[23,35,37],{"id":36},"managed-service-versus-self-managing","Managed service versus self-managing",[28,39,40],{},"You can run a database on AWS in two broad ways.",[28,42,43],{},"The first is to launch an Amazon EC2 instance, install the database software yourself, and manage everything: the operating system, patches, backups, scaling, and recovery. This gives you full control, but you carry all the operational work, and small mistakes during a manual patch or upgrade can cause downtime.",[28,45,46],{},"The second is to use a managed database service such as Amazon RDS. AWS provisions the database, applies patches, takes automated backups, detects failures, and handles recovery. You focus on your data and your application instead of the plumbing underneath. AWS recommends a managed service as the default for most workloads.",[28,48,49],{},"The table below shows who handles what across three options.",[51,52,53,72],"table",{},[54,55,56],"thead",{},[57,58,59,63,66,69],"tr",{},[60,61,62],"th",{},"Task",[60,64,65],{},"On-premises",[60,67,68],{},"Database on EC2",[60,70,71],{},"Managed service (RDS)",[73,74,75,88,100,111,122,133],"tbody",{},[57,76,77,81,84,86],{},[78,79,80],"td",{},"Application and query tuning",[78,82,83],{},"You",[78,85,83],{},[78,87,83],{},[57,89,90,93,95,97],{},[78,91,92],{},"Database software install and patching",[78,94,83],{},[78,96,83],{},[78,98,99],{},"AWS",[57,101,102,105,107,109],{},[78,103,104],{},"Operating system patching",[78,106,83],{},[78,108,83],{},[78,110,99],{},[57,112,113,116,118,120],{},[78,114,115],{},"Backups and recovery",[78,117,83],{},[78,119,83],{},[78,121,99],{},[57,123,124,127,129,131],{},[78,125,126],{},"Server and hardware maintenance",[78,128,83],{},[78,130,99],{},[78,132,99],{},[57,134,135,138,140,142],{},[78,136,137],{},"Power, network, and cooling",[78,139,83],{},[78,141,99],{},[78,143,99],{},[28,145,146],{},"Notice the pattern: as you move to a managed service, AWS takes on more of the routine work. One thing never moves. Tuning your own queries stays with you in every model, because it depends on your data and how your application uses it.",[23,148,150],{"id":149},"relational-and-non-relational-databases","Relational and non-relational databases",[28,152,153],{},"Databases fall into two high-level groups, and the exam expects you to tell them apart.",[28,155,156,157,161],{},"A ",[158,159,160],"strong",{},"relational database"," (often called SQL) stores data in tables made of rows and columns, with a defined schema. You can link, or join, tables to answer questions that span related data, such as matching customers to their orders. Relational databases are a strong fit for structured data and transactions where accuracy matters, like finance, orders, and inventory.",[28,163,156,164,167],{},[158,165,166],{},"non-relational database"," (often called NoSQL) uses other data models that trade some of the strict structure for scale, speed, and flexibility. Instead of fixed tables, it might store key-value pairs, JSON-like documents, graphs, or time-stamped points. These models shine when you need very high throughput, low latency, or a flexible schema that changes often.",[28,169,170],{},"Neither group is \"better.\" They solve different problems, which is exactly why AWS offers both.",[23,172,174],{"id":173},"purpose-built-databases","Purpose-built databases",[28,176,177],{},"AWS does not push one database for every job. Instead it offers a range of purpose-built databases, each optimized for a specific data model and workload. The idea is simple: choose the right tool for each task. A single application can use several at once, such as a relational database for billing and a key-value database for a shopping cart.",[51,179,180,193],{},[54,181,182],{},[57,183,184,187,190],{},[60,185,186],{},"Category",[60,188,189],{},"What it is for",[60,191,192],{},"AWS service",[73,194,195,206,217,228,239,250,261],{},[57,196,197,200,203],{},[78,198,199],{},"Relational",[78,201,202],{},"Structured data in tables, transactions, joins",[78,204,205],{},"Amazon RDS, Amazon Aurora",[57,207,208,211,214],{},[78,209,210],{},"Key-value",[78,212,213],{},"High-traffic web apps at any scale",[78,215,216],{},"Amazon DynamoDB",[57,218,219,222,225],{},[78,220,221],{},"In-memory",[78,223,224],{},"Caching and microsecond response times",[78,226,227],{},"Amazon ElastiCache, Amazon MemoryDB",[57,229,230,233,236],{},[78,231,232],{},"Document",[78,234,235],{},"JSON-like documents with flexible fields",[78,237,238],{},"Amazon DocumentDB",[57,240,241,244,247],{},[78,242,243],{},"Graph",[78,245,246],{},"Highly connected data and relationships",[78,248,249],{},"Amazon Neptune",[57,251,252,255,258],{},[78,253,254],{},"Wide-column",[78,256,257],{},"High-scale Apache Cassandra workloads",[78,259,260],{},"Amazon Keyspaces",[57,262,263,266,269],{},[78,264,265],{},"Time-series",[78,267,268],{},"Data that changes over time, such as IoT",[78,270,271],{},"Amazon Timestream",[28,273,274],{},"You do not need deep detail on every service for the exam. You do need to recognize the name, know which category it belongs to, and match a scenario to it. The next three lessons cover the most tested services in each group, starting with relational databases.",[23,276,278],{"id":277},"exam-tips","Exam tips",[280,281,282,286,289,292,295],"ul",{},[283,284,285],"li",{},"A managed service (like Amazon RDS) means AWS handles patching, backups, failover, and hardware. Running a database on EC2 means you handle all of that yourself.",[283,287,288],{},"Query tuning is always your job, even with a managed service.",[283,290,291],{},"Relational (SQL) = tables, rows, columns, joins, fixed schema. Non-relational (NoSQL) = key-value, document, graph, and other flexible models built for scale.",[283,293,294],{},"Purpose-built means AWS offers a database for each kind of workload, and you pick the right one rather than forcing everything into a single database.",[283,296,297],{},"Learn to map a category to its service: relational to RDS and Aurora, key-value to DynamoDB, in-memory to ElastiCache, graph to Neptune, document to DocumentDB.",{"title":299,"searchDepth":300,"depth":300,"links":301},"",3,[302,304,305,306,307],{"id":25,"depth":303,"text":26},2,{"id":36,"depth":303,"text":37},{"id":149,"depth":303,"text":150},{"id":173,"depth":303,"text":174},{"id":277,"depth":303,"text":278},"md",[],[13,14,15,16],{},"/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/05-database-services/01-databases-on-aws",{"passingScore":314,"questions":315},70,[316,325,333,343,349,353],{"question":317,"type":318,"options":319,"correctAnswer":321,"explanation":324},"What is the main difference between a managed database service like Amazon RDS and running a database yourself on Amazon EC2?","single",[320,321,322,323],"RDS can only run open-source engines, while EC2 can run any engine","With RDS, AWS handles tasks like patching, backups, and failover; on EC2 you do that work yourself","RDS stores data in S3, while EC2 stores it on local disks","There is no real difference; the names are interchangeable","A managed service takes over routine database administration: provisioning, patching, backups, and failover. On EC2 you control the full stack, which means you also carry the work of installing, patching, and backing up the database yourself.",{"question":326,"type":318,"options":327,"correctAnswer":328,"explanation":332},"Which description best fits a relational database?",[328,329,330,331],"It stores data in tables of rows and columns and supports joins across tables","It stores data only as JSON documents with no fixed schema","It keeps all data in memory and loses it on restart","It is designed only for time-stamped sensor data","Relational databases use a structured schema of tables, rows, and columns, and you can join tables to answer questions across related data. The other options describe non-relational models such as document, in-memory, and time-series databases.",{"question":334,"type":335,"options":336,"correctAnswers":341,"explanation":342},"Which tasks does AWS take over when you use a managed relational database service instead of self-managing? (Select all that apply.)","multiple",[337,338,339,340],"Operating system and database software patching","Automated backups and recovery","Hardware provisioning and maintenance","Tuning your SQL queries for your specific application",[337,338,339],"AWS manages the infrastructure and routine admin: patching, backups, recovery, and hardware. Query tuning stays your responsibility, because it depends on your schema, data, and access patterns, which only you know.",{"question":344,"type":318,"options":345,"correctAnswer":347,"explanation":348},"AWS recommends using one single database type for every workload.",[346,347],"True","False","AWS promotes purpose-built databases: pick the database model that fits each workload. A single application often combines several, such as a relational database for orders and a key-value database for the shopping cart.",{"question":350,"type":318,"options":351,"correctAnswer":221,"explanation":352},"An application needs to cache frequently accessed data and return it with microsecond latency. Which database category fits best?",[199,243,221,265],"In-memory databases keep data in RAM, so they return results in microseconds, which makes them ideal for caching and session stores. Relational, graph, and time-series databases serve very different needs.",{"question":354,"type":318,"options":355,"correctAnswer":357,"explanation":360},"What does 'purpose-built database' mean on AWS?",[356,357,358,359],"A database that AWS builds custom for each customer on request","A range of database services, each optimized for a specific data model and workload","A single database that can perfectly handle every workload","A database that only runs during business hours","Purpose-built means AWS offers many database services, each tuned for one kind of job: relational, key-value, document, in-memory, graph, and more. You choose the right tool for each workload rather than forcing everything into one database.",{"title":7,"description":8},"courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/05-database-services/01-databases-on-aws","hq4pdksDD_PH0G-GyODJ3ADIPYDC-2woUC_vY8jnMvU",{"locked":9,"reason":365,"meta":366,"item":3},"paywall",{"title":367,"description":368,"isFree":5,"estimatedMinutes":369,"difficulty":11,"learningObjectives":370},"AWS Storage Gateway and AWS Backup","Learn how AWS Storage Gateway bridges on-premises systems to AWS cloud storage, and how AWS Backup centralizes and automates backups across many AWS services.",15,[371,372,373,374],"Explain what hybrid cloud storage is and the role of AWS Storage Gateway","Identify the main AWS Storage Gateway types and their use cases","Describe AWS Backup as a centralized, automated backup service","Explain how backup plans, vaults, and Vault Lock protect data",{"locked":9,"reason":365,"meta":376,"item":3},{"title":377,"description":378,"isFree":5,"estimatedMinutes":369,"difficulty":11,"learningObjectives":379},"File Storage with Amazon EFS and Amazon FSx","Learn what shared file storage is, how Amazon EFS provides an elastic NFS file system for Linux, and how Amazon FSx delivers managed Windows, Lustre, NetApp, and OpenZFS file systems.",[380,381,382,383],"Define file storage and explain how it differs from block and object storage","Describe Amazon EFS as an elastic, shared NFS file system for Linux","Identify the Amazon FSx file system types and their use cases","Choose between Amazon EFS and Amazon FSx for Windows File Server for a given scenario"]