AWS Cloud Practitioner Essentials T3.1

AWS Cloud Provisioning and Operation

• AWS Management Console: Web-based GUI for managing AWS resources. Easy for simple tasks like creating S3 buckets or launching EC2 instances. Suitable for beginners or small-scale operations. Used for tasks like creating and monitoring resources. Launching an EC2 instance is a common use case.

• AWS Command Line Interface (CLI): Text-based tool for managing AWS using commands. Ideal for automation of repetitive tasks, like batch file uploads, instance management. Enables automated resource management. Example: automating multiple S3 bucket creation using a script.

• AWS Software Development Kits (SDKs): Programming libraries (Python, Java, Node.js) for interacting with AWS services programmatically. Allows developers to integrate AWS services into applications, offering fine-grained control for custom workflows. Useful for integrating AWS into applications. Example: uploading files to an S3 bucket using a Python program.

• Infrastructure as Code (IaC): Automates resource provisioning using code templates (like AWS CloudFormation, AWS CDK). Repeatable and consistent resource creation; enables better disaster recovery and scaling. Beneficial for multi-region deployments and disaster recovery scenarios. Example: deploying a web application stack (EC2, RDS, and S3) automatically using AWS CloudFormation.

AWS API Fundamentals

• API (Application Programming Interface): A way for software to communicate with AWS services programmatically. Enables creation, configuration, and management of AWS resources without the console. Enables programmatic resource control. Example use case: translating text dynamically in a mobile app using the Amazon Translate API.

• API Usage in Provisioning: Useful for automating tasks, integrating with applications, and handling complex workflows. API use is ideal for handling multiple tasks across AWS services.

• API Comparison: The AWS Management Console leverages APIs behind the scenes. The CLI executes APIs, and SDKs simplify API interactions.

AWS Cloud Deployment Models

• Cloud Deployment: Resources hosted entirely in the cloud (e.g., website on AWS). Completely managed, scalable, and cost-effective. Example: hosting a global e-commerce website entirely on AWS.

• Hybrid Deployment: Combines on-premises infrastructure with cloud resources (e.g., on-premises database with AWS backups). Useful for phased cloud deployments. Example: connecting an on-premises database to AWS services for analytics using Amazon Redshift.

• On-Premises (Private Cloud): Cloud-like environment managed in your own data center. Offers greater control and compliance for sensitive workloads. Example deployment scenario: deploying AWS services in a data center using AWS Outposts.

AWS Connectivity Options

• AWS VPN (Virtual Private Network): Encrypted connection between your on-premises network and AWS. Cost-effective, suitable for low-volume data transfers. Example scenario: securely connecting an on-premises office network to a VPC.

• AWS Direct Connect: Dedicated network connection. High bandwidth, low latency, suited for large-scale or high-performance workloads. Example use case: transferring large datasets to AWS for better speed and reliability.

• Public Internet: Standard internet connection to AWS. Easy access, but less secure. Suitable for public-facing resources. Example scenario: allowing end-users to access a website hosted on an S3 bucket.