Deploying and operating in the AWS Cloud

You can reach AWS through the console, the CLI, SDKs, and APIs, and you can describe infrastructure as code. Pick the method that fits a one-off task versus a repeatable process, and know the cloud deployment models.

Ways to access AWS

• AWS Management Console: Web interface. Good for learning, exploring, and one-time tasks.
• AWS CLI: Command line tool for scripting and automating tasks.
• AWS SDKs: Libraries for programming languages (JavaScript, Python, Java, and more) to call AWS from your code.
• APIs: Every AWS action is an API call; the console, CLI, and SDKs all use the APIs underneath.

Provisioning and operating

• Infrastructure as code (IaC): Define resources in templates so environments are repeatable, version-controlled, and reviewable. AWS CloudFormation is the native IaC service.
• One-time vs. repeatable: Use the console for a quick one-off action; use IaC, scripts, or the CLI/SDK when you must repeat a process reliably (for example, building identical dev, test, and prod environments).
• AWS Elastic Beanstalk: Upload application code and Beanstalk provisions and manages the capacity, load balancing, and scaling for you.
• AWS Systems Manager: Operational hub to view and manage fleets of servers: patching, running commands, and storing parameters.

Management and governance tools

• AWS Control Tower: Sets up and governs a secure multi-account environment (a landing zone) with built-in guardrails, on top of AWS Organizations.
• AWS Service Catalog: Lets administrators publish approved products (for example, CloudFormation templates) that users can launch on their own, within guardrails.
• Service Quotas: View and request increases to the limits (quotas) on resources in your account, such as the number of instances per Region.
• AWS License Manager: Track and control software license usage (for example, BYOL licenses) across AWS and on premises.
• AWS Compute Optimizer: Recommends optimal resource sizes based on actual usage.

Deployment models

• Cloud (all-in): All parts of the application run in the cloud.
• Hybrid: Connects cloud resources to on-premises infrastructure, for example with AWS Direct Connect, VPN, or AWS Outposts.
• On-premises (private cloud): Resources run in your own data center, often using virtualization and resource management tools.