[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cheat-sheet---en":3,"domain-info---en":3,"topic-info----en":3,"lesson-aws-certified-cloud-practitioner-cloud-technology-and-services-deploying-and-operating-infrastructure-as-code-en":4,"prev-aws-certified-cloud-practitioner-cloud-technology-and-services-deploying-and-operating-infrastructure-as-code-en":18,"next-aws-certified-cloud-practitioner-cloud-technology-and-services-deploying-and-operating-infrastructure-as-code-en":305},null,{"locked":5,"reason":6,"meta":7,"item":3},true,"paywall",{"title":8,"description":9,"isFree":10,"estimatedMinutes":11,"difficulty":12,"learningObjectives":13},"Infrastructure as Code","Understand what Infrastructure as Code (IaC) is, why it beats manual setup, and how AWS CloudFormation and the AWS CDK let you provision resources from templates and code.",false,15,"beginner",[14,15,16,17],"Define Infrastructure as Code and explain why it replaces manual setup","Compare declarative and imperative approaches to provisioning","Describe AWS CloudFormation, its templates, and stacks","Explain how the AWS CDK relates to CloudFormation",{"locked":10,"reason":3,"meta":19,"item":28},{"title":20,"description":21,"isFree":5,"estimatedMinutes":22,"difficulty":12,"learningObjectives":23},"Ways to Access AWS","Learn the main ways to work with AWS services: the Management Console, the CLI, the SDKs, and the underlying API, plus when to reach for each one.",14,[24,25,26,27],"Identify the four main ways to access AWS: Console, CLI, SDKs, and the API","Explain what the AWS Management Console is and when it fits best","Describe how the CLI and SDKs support scripting and automation","Explain that the Console, CLI, and SDKs all call the same AWS API",{"id":29,"title":20,"body":30,"description":21,"difficulty":12,"estimatedMinutes":22,"extension":248,"infographics":249,"isFree":5,"learningObjectives":260,"meta":261,"navigation":5,"path":262,"quiz":263,"seo":302,"stem":303,"__hash__":304},"courses/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/01-deploying-and-operating/01-ways-to-access-aws.md",{"type":31,"value":32,"toc":238},"minimark",[33,38,42,45,50,54,57,60,64,67,70,114,117,121,124,127,131,134,137,141,208,211,215,234],[34,35,37],"h2",{"id":36},"why-this-matters","Why this matters",[39,40,41],"p",{},"Once you have an AWS account, you need a way to actually create and manage resources. AWS does not lock you into one method. You can click through a web interface, type commands in a terminal, or call services straight from your application code. The method you pick depends on the task: a quick one-off change, a repeatable script, or a feature inside an app.",[39,43,44],{},"There are 4 main ways to work with AWS: the Management Console, the Command Line Interface (CLI), the Software Development Kits (SDKs), and the API that sits underneath them all. Knowing what each one is for is enough for the exam, and it shapes how you work day to day.",[46,47],"infographic",{"alt":48,"slug":49},"A layered diagram showing the AWS Management Console, CLI, and SDKs all sending requests to the AWS API, which in turn reaches the AWS services.","ways-to-access-aws-layers",[34,51,53],{"id":52},"aws-management-console","AWS Management Console",[39,55,56],{},"The AWS Management Console is a web-based graphical interface. You sign in with a browser, and you point and click to launch instances, create storage buckets, view dashboards, and check on your resources. It groups services into menus and shows visual feedback, so it is the easiest place to start when you are learning or exploring.",[39,58,59],{},"The Console is a good fit for one-off tasks, for trying out a new service, and for getting a visual picture of what you have running. It is less suited to work you need to repeat exactly, because every step depends on a person clicking the same buttons in the same order. There is also a mobile app version of the Console for checking resources on the go.",[34,61,63],{"id":62},"aws-command-line-interface-cli","AWS Command Line Interface (CLI)",[39,65,66],{},"The AWS CLI is a single tool that lets you control AWS services from a terminal. With one tool installed and configured, you can manage many services by typing commands instead of clicking. It runs on Windows, macOS, and Linux.",[39,68,69],{},"The real strength of the CLI is automation. Because commands are just text, you can put them in a script and run that script on a schedule or as part of a larger process. This makes your work repeatable: the same script produces the same result every time, with no manual clicking. A command looks like this:",[71,72,77],"pre",{"className":73,"code":74,"language":75,"meta":76,"style":76},"language-bash shiki shiki-themes material-theme-lighter github-light github-dark","aws s3 ls\naws ec2 describe-instances --region us-east-1\n","bash","",[78,79,80,96],"code",{"__ignoreMap":76},[81,82,85,89,93],"span",{"class":83,"line":84},"line",1,[81,86,88],{"class":87},"sbgvK","aws",[81,90,92],{"class":91},"s_sjI"," s3",[81,94,95],{"class":91}," ls\n",[81,97,99,101,104,107,111],{"class":83,"line":98},2,[81,100,88],{"class":87},[81,102,103],{"class":91}," ec2",[81,105,106],{"class":91}," describe-instances",[81,108,110],{"class":109},"stzsN"," --region",[81,112,113],{"class":91}," us-east-1\n",[39,115,116],{},"AWS also offers CloudShell, a browser-based shell that you launch from inside the Console. It comes pre-authenticated and has the CLI already installed, so you can run commands without setting anything up on your own machine.",[34,118,120],{"id":119},"aws-sdks","AWS SDKs",[39,122,123],{},"The AWS SDKs (Software Development Kits) let your application talk to AWS services directly from code. Instead of shelling out to the CLI, you call AWS using functions in your programming language. AWS provides SDKs for many languages, including Python, JavaScript, Java, .NET, Go, Ruby, and others.",[39,125,126],{},"SDKs are the right choice when AWS access is part of an application you are building. For example, a web app that stores user uploads in Amazon S3 would use the SDK for its language to send and retrieve those files. The SDK handles the lower-level work for you, such as signing requests and retrying failed calls, so you write less plumbing code.",[34,128,130],{"id":129},"the-aws-api-underneath","The AWS API underneath",[39,132,133],{},"Every method above is a front end over the same thing: the AWS API. The API is a set of HTTPS requests that AWS services accept. When you click a button in the Console, it sends an API call. When you run a CLI command or call an SDK function, those also turn into the same API calls.",[39,135,136],{},"You rarely call the API by hand, because the Console, CLI, and SDKs are easier. But it helps to understand the picture: there is one API per service, and the friendlier tools are just different ways to reach it. This is why anything you can do in the Console you can usually also do with the CLI or an SDK.",[34,138,140],{"id":139},"choosing-the-right-method","Choosing the right method",[142,143,144,160],"table",{},[145,146,147],"thead",{},[148,149,150,154,157],"tr",{},[151,152,153],"th",{},"Method",[151,155,156],{},"Interface",[151,158,159],{},"Best for",[161,162,163,175,186,197],"tbody",{},[148,164,165,169,172],{},[166,167,168],"td",{},"Management Console",[166,170,171],{},"Web graphical interface",[166,173,174],{},"Learning, exploring, one-off tasks, visual checks",[148,176,177,180,183],{},[166,178,179],{},"CLI",[166,181,182],{},"Terminal commands",[166,184,185],{},"Scripting, automation, repeatable tasks",[148,187,188,191,194],{},[166,189,190],{},"SDKs",[166,192,193],{},"Code in your language",[166,195,196],{},"AWS access built into an application",[148,198,199,202,205],{},[166,200,201],{},"API",[166,203,204],{},"HTTPS requests",[166,206,207],{},"The low-level layer the others call",[39,209,210],{},"There is no single \"correct\" method. Many teams use all of them: the Console to explore and check, the CLI to automate operations, and the SDKs inside their applications.",[34,212,214],{"id":213},"exam-tips","Exam tips",[216,217,218,222,225,228,231],"ul",{},[219,220,221],"li",{},"The Management Console is the web-based graphical interface; best for learning and one-off tasks.",[219,223,224],{},"The CLI controls services from the command line and is built for scripting and automation.",[219,226,227],{},"SDKs let application code call AWS services in a specific programming language.",[219,229,230],{},"The Console, CLI, and SDKs all send requests to the same AWS API.",[219,232,233],{},"CloudShell is a browser-based shell, launched from the Console, with the CLI pre-installed and pre-authenticated.",[235,236,237],"style",{},"html pre.shiki code .sbgvK, html code.shiki .sbgvK{--shiki-light:#E2931D;--shiki-default:#6F42C1;--shiki-dark:#B392F0}html pre.shiki code .s_sjI, html code.shiki .s_sjI{--shiki-light:#91B859;--shiki-default:#032F62;--shiki-dark:#9ECBFF}html pre.shiki code .stzsN, html code.shiki .stzsN{--shiki-light:#91B859;--shiki-default:#005CC5;--shiki-dark:#79B8FF}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":76,"searchDepth":239,"depth":239,"links":240},3,[241,242,243,244,245,246,247],{"id":36,"depth":98,"text":37},{"id":52,"depth":98,"text":53},{"id":62,"depth":98,"text":63},{"id":119,"depth":98,"text":120},{"id":129,"depth":98,"text":130},{"id":139,"depth":98,"text":140},{"id":213,"depth":98,"text":214},"md",[250],{"slug":49,"concept":251,"style":252,"aspectRatio":253,"labels":254},"Three front ends, the Management Console, the CLI, and the SDKs, sit side by side at the top and converge into one shared AWS API layer that reaches the AWS services below. Each front end carries a short cue: the Console for clicking through one-off tasks, the CLI for scriptable text commands, the SDKs for calls from application code. The shared API layer gets the orange accent, because it is the single band every path passes through. The takeaway: pick the front end that fits the task, since they all become the same API calls underneath.","diagram","16:9",[255,256,257,258,259],"Console: click through, one-off tasks","CLI: text commands, scriptable","SDKs: calls from application code","One shared AWS API underneath","AWS services",[24,25,26,27],{},"/courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/01-deploying-and-operating/01-ways-to-access-aws",{"passingScore":264,"questions":265},70,[266,275,281,289,295],{"question":267,"type":268,"options":269,"correctAnswer":271,"explanation":274},"Which way to access AWS is a web-based graphical interface that you sign in to and click through?","single",[270,271,272,273],"The AWS CLI","The AWS Management Console","An AWS SDK","The AWS API","The Management Console is the browser-based graphical interface where you point and click to work with services. The CLI and SDKs are text-based and programmatic, and the API is the low-level layer they all call.",{"question":276,"type":268,"options":277,"correctAnswer":270,"explanation":280},"Your team wants to provision the same set of resources every night using a scheduled script with no human clicking through screens. Which access method fits best?",[271,270,278,279],"A support ticket","The AWS Health Dashboard","The CLI is a single tool that controls AWS services from the command line, so it can be placed inside scripts and run on a schedule. The Console needs a person to click through it and does not fit unattended automation.",{"question":282,"type":268,"options":283,"correctAnswer":285,"explanation":288},"What is the main purpose of an AWS SDK?",[284,285,286,287],"To give non-technical users a drag-and-drop dashboard","To let your application code call AWS services in a specific programming language","To replace the need for an AWS account","To monitor billing alerts","An SDK is a language-specific library that lets your application talk to AWS services directly from code, handling request signing and retries for you. SDKs exist for languages like Python, JavaScript, Java, .NET, and Go.",{"question":290,"type":268,"options":291,"correctAnswer":292,"explanation":294},"The AWS Management Console, the CLI, and the SDKs ultimately send requests to the same underlying AWS API.",[292,293],"True","False","Every access method is a different front end over the same AWS API. The Console turns your clicks into API calls, and the CLI and SDKs turn your commands and code into the same calls.",{"question":296,"type":297,"options":298,"correctAnswers":300,"explanation":301},"Which of these are valid ways to interact with AWS services? (Select all that apply.)","multiple",[53,63,120,299],"AWS CloudShell",[53,63,120,299],"All four are real ways to reach AWS. The Console is the graphical interface, the CLI and SDKs are programmatic, and CloudShell is a browser-based shell with the CLI already installed and signed in.",{"title":20,"description":21},"courses/aws-certified-cloud-practitioner/en/domains/03-cloud-technology-and-services/01-deploying-and-operating/01-ways-to-access-aws","vPWYsgLIPOzbMi8OlF8mODU2CPm3nfYssN3ydjsMGBM",{"locked":5,"reason":6,"meta":306,"item":3},{"title":307,"description":308,"isFree":10,"estimatedMinutes":22,"difficulty":12,"learningObjectives":309},"Cloud Deployment Models","Learn the three cloud deployment models AWS defines: cloud-based, on-premises (private cloud), and hybrid, plus how to match each one to a real situation.",[310,311,312,313,314],"Identify the three cloud deployment models: cloud, on-premises, and hybrid","Explain what a fully cloud-based deployment is","Describe on-premises (private cloud) deployment and its trade-offs","Explain hybrid deployment and the AWS services that support it","Match a real scenario to the right deployment model"]