{"id":25322525,"url":"https://github.com/izzypt/aws_cloud_practicioner","last_synced_at":"2026-01-19T23:06:16.361Z","repository":{"id":273861982,"uuid":"921109329","full_name":"izzypt/AWS_cloud_practicioner","owner":"izzypt","description":"Prepare for the AWS Certified Cloud Practitioner Certification (CLF-C02) and pass!","archived":false,"fork":false,"pushed_at":"2025-01-29T10:17:24.000Z","size":114,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-04-07T22:25:12.134Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/izzypt.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-01-23T10:59:11.000Z","updated_at":"2025-01-29T10:17:27.000Z","dependencies_parsed_at":"2025-01-23T12:31:18.426Z","dependency_job_id":null,"html_url":"https://github.com/izzypt/AWS_cloud_practicioner","commit_stats":null,"previous_names":["izzypt/aws_cloud_practicioner"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/izzypt/AWS_cloud_practicioner","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/izzypt%2FAWS_cloud_practicioner","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/izzypt%2FAWS_cloud_practicioner/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/izzypt%2FAWS_cloud_practicioner/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/izzypt%2FAWS_cloud_practicioner/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/izzypt","download_url":"https://codeload.github.com/izzypt/AWS_cloud_practicioner/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/izzypt%2FAWS_cloud_practicioner/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28588971,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-19T20:45:59.482Z","status":"ssl_error","status_checked_at":"2026-01-19T20:45:41.500Z","response_time":67,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-02-13T23:41:02.983Z","updated_at":"2026-01-19T23:06:16.344Z","avatar_url":"https://github.com/izzypt.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"# AWS_cloud_practicioner\n\nThe AWS Certified Cloud Practitioner certificate is an entry-level certification \"offered\" (100$) by Amazon Web Services (AWS) designed for individuals who want to build a foundational understanding of the AWS Cloud.\n\nIt’s a great first step for anyone considering a career in cloud computing or seeking to understand how AWS works in the broader context of IT and business.\n\n\n# List of items\n\n- [AWS Cloud Practiociner Exam tips](#0)\n- [AWS Global Infrastructure](#1)\n- [AWS Well-Architected](#2)\n- [AWS EC2](#3)\n- [AWS EBS - Elastic Block Store](#4)\n- [AWS VPC - Virtual Private Cloud](#5)\n- [AWS Cloud Economics](#6)\n\n\n\n\u003ca id=\"0\"\u003e\u003c/a\u003e\n# AWS Cloud Practiociner Exam tips\n\nTo pass the **AWS Certified Cloud Practitioner** exam, you need to focus on gaining a foundational understanding of AWS services, cloud concepts, security, and pricing. Here’s a step-by-step guide on what to read and study:\n\n---\n\n### 1. **AWS Cloud Practitioner Exam Guide**\n   - **Start here**: Download the [AWS Certified Cloud Practitioner Exam Guide](https://aws.amazon.com/certification/certified-cloud-practitioner/) to understand the topics covered and their weight in the exam:\n     - **Cloud Concepts** (26% of the exam)\n     - **Security and Compliance** (25%)\n     - **Technology** (33%)\n     - **Billing and Pricing** (16%)\n\n- [Exam guide pdf (23/01/2025)](https://d1.awsstatic.com/training-and-certification/docs-cloud-practitioner/AWS-Certified-Cloud-Practitioner_Exam-Guide.pdf)\n\n---\n\n### 2. **AWS Training Resources**\nAWS offers free and paid resources to help you prepare:\n   - **AWS Cloud Practitioner Essentials Course** (Free or Paid):\n     - Available on AWS Training or Coursera.\n     - Covers all key concepts in a structured manner.\n   - **AWS Skill Builder** (Free):\n     - Explore the free [Skill Builder platform](https://explore.skillbuilder.aws/) for self-paced training.\n   - **AWS Whitepapers** (Free):\n     - **Recommended Reading**:\n       - [Overview of Amazon Web Services](https://aws.amazon.com/whitepapers/).\n       - [AWS Well-Architected Framework](https://aws.amazon.com/architecture/well-architected/).\n       - [Pricing Overview](https://aws.amazon.com/pricing/).\n\n---\n\n### 3. **Topics to Study**\nFocus on these areas:\n   - **Cloud Concepts**:\n     - What is cloud computing? (e.g., scalability, elasticity, global reach)\n     - Benefits of cloud computing (e.g., cost-efficiency, pay-as-you-go model).\n     - Cloud deployment models (Public, Private, Hybrid).\n   - **AWS Core Services**:\n     - **Compute**: EC2, Lambda.\n     - **Storage**: S3, EBS.\n     - **Networking**: VPC, Route 53, CloudFront.\n     - **Databases**: RDS, DynamoDB.\n   - **Security and Compliance**:\n     - Shared responsibility model.\n     - IAM (Identity and Access Management) basics.\n     - AWS Trusted Advisor and compliance programs.\n   - **Billing and Pricing**:\n     - AWS pricing models: Pay-as-you-go, Reserved Instances, Savings Plans.\n     - AWS Cost Management tools: Cost Explorer, Billing Dashboard.\n     - AWS Free Tier.\n   - **Support Plans**:\n     - AWS Basic, Developer, Business, and Enterprise Support Plans.\n\n---\n\n### 4. **Practice Exams**\n   - Take **official AWS practice exams** or free mock tests to assess your readiness:\n     - **AWS Certified Cloud Practitioner Practice Exam** (Available on the AWS website).\n     - Platforms like Udemy, Whizlabs, and Tutorials Dojo offer high-quality practice exams.\n\n---\n\n### 5. **Study Timeframe**\n   - If you’re consistent, you can prepare in **2–4 weeks**, dedicating 1–2 hours daily.\n   - For beginners, spending 6–8 weeks ensures a solid understanding.\n\n---\n\n### 6. **Recommended Resources**\n   - **Books**:\n     - *AWS Certified Cloud Practitioner Study Guide* by Ben Piper.\n   - **Video Courses**:\n     - [Stephane Maarek’s AWS Cloud Practitioner Course](https://www.udemy.com/) (Highly recommended on Udemy).\n   - **Flashcards**:\n     - Quizlet or Tutorials Dojo flashcards for on-the-go revision.\n\n---\n\n![image](https://github.com/user-attachments/assets/e2f01f5e-cbae-4fdb-ade4-ca53a9fe6b55)\n\n![image](https://github.com/user-attachments/assets/62fa8dc1-975e-40ae-81c8-8ccc366bc7db)\n\n![image](https://github.com/user-attachments/assets/8b8a9762-7d73-4a71-a5d9-5d7fa17d840e)\n\n\n\u003ca id=\"1\"\u003e\u003c/a\u003e\n# AWS Global Infrastructrure\n\nDeliver a cloud infrastrucutre, companies can depend on no matter their size.\n\n![image](https://github.com/user-attachments/assets/b1861a71-115b-464e-b0b8-4911b78e1ee7)\n\n- 105 availability zones\n\n- 33 geographic regions\n\n\n  ![image](https://github.com/user-attachments/assets/b8f65318-b75d-487f-8477-d9b927ec8917)\n\n- **AWS Region**s are geographically isolated areas containing multiple data centers, designed to provide services close to users and meet regulatory requirements. \n\n- **AWS Availability Zones (AZs)** are physically separate data centers within a Region, connected via low-latency networks, ensuring fault isolation and high availability.\n\n![image](https://github.com/user-attachments/assets/2121b7e1-781b-47ba-a22a-0ffadffd8aa1)\n\n![image](https://github.com/user-attachments/assets/485442bc-6029-47c8-94b0-62b140c251d4)\n\n\u003cimg width=\"1574\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e7f883f0-a27a-4bc4-aa04-3be286767f08\" /\u003e\n\n\n\u003ca id=\"2\"\u003e\u003c/a\u003e\n# AWS Well-Architected\n\nHelps cloud architects design infrastructure that is built arround 6 pillars:\n\n1 - Operational excellence\n  - Focuses on running and monitoring systems and continually improving processes and procedures.\n\n2 - Security\n  - Focuses on protecting information and systems\n\n3 - Reliability\n  - Focuses on ensuring workloads perform their assigned functions and recover qucickly from any faillure to meet demands.\n\n4 - Performance efficiency\n  - Focuses on selecting suitable resource types and sizes. Monitoring performance and maintining efficiency.\n\n5 - Cost optimization\n  - Focuses on understanding spending trends, contorlling fund allocation and scaling to meet the business needs without overspending.\n\n6 - Sustainability\n  - Minimizing environmental impact\n  \n![image](https://github.com/user-attachments/assets/058c0b8b-2444-4ab6-a34e-b29405fa37cf)\n\n![image](https://github.com/user-attachments/assets/6757c11e-6dea-436c-9da5-bfa7423c69a5)\n\n\u003ca id=\"3\"\u003e\u003c/a\u003e\n# AWS EC2\n\n![image](https://github.com/user-attachments/assets/b1078f85-8fd9-4722-83a2-86f891ffe2f9)\n\n**Amazon EC2 Basics Summary**  \n\nAmazon Elastic Compute Cloud (EC2) is a core service of AWS that provides scalable, on-demand computing power in the cloud. It allows users to run virtual servers, known as instances, to host applications, process data, or handle workloads. Here are the key basics of EC2:  \n\n1. **Instances**:  \n   - EC2 instances are virtual servers that can be launched and configured as needed.  \n   - Instances come in various types (e.g., General Purpose, Compute Optimized, Memory Optimized) to suit specific workloads.  \n\n2. **AMI (Amazon Machine Image)**:  \n   - An AMI is a pre-configured template that includes the operating system and any software or configuration needed to launch an instance.  \n\n3. **Instance Sizes**:  \n   - Instances have different sizes (CPU, memory, and storage capacities) to accommodate small to large-scale applications.  \n\n4. **Elasticity and Scalability**:  \n   - EC2 supports dynamic scaling, enabling you to add or remove instances based on workload demand.  \n\n5. **Pricing Models**:  \n   - **On-Demand**: Pay per hour or second, with no long-term commitment.  \n   - **Reserved**: Commit to a fixed term (1 or 3 years) for significant cost savings.  \n   - **Spot Instances**: Purchase unused capacity at a discount, suitable for flexible and fault-tolerant workloads.  \n\n6. **Storage**:  \n   - EC2 instances use Amazon Elastic Block Store (EBS) for persistent storage. Instance Store is an alternative for temporary, non-persistent storage.  \n\n7. **Networking**:  \n   - EC2 instances can be deployed within a Virtual Private Cloud (VPC) to provide secure, isolated networking. Public or private IPs can be assigned.  \n\n8. **Security**:  \n   - EC2 uses security groups (firewalls) to control inbound and outbound traffic. Key pairs (SSH keys) ensure secure access to instances.  \n\n9. **Load Balancing and Auto Scaling**:  \n   - Amazon EC2 works with Elastic Load Balancing (ELB) to distribute traffic and Auto Scaling to automatically adjust instance counts based on demand.  \n\n10. **Monitoring**:  \n    - Amazon CloudWatch provides monitoring of EC2 instances, offering metrics like CPU usage, disk I/O, and network traffic.  \n\nEC2 is highly flexible, allowing users to scale resources up or down to match their application needs, ensuring cost-efficiency and adaptability in the cloud.\n\n![image](https://github.com/user-attachments/assets/fcb54f6e-9720-4b05-ac05-b0fb66991a7d)\n\n**EC2 Storage and Networking Summary**  \n\nAmazon EC2 provides flexible storage and networking options to meet diverse application needs. Here’s a breakdown:  \n\n### **Storage Options**  \n\n1. **Elastic Block Store (EBS)**:  \n   - Provides persistent block storage for EC2 instances.  \n   - Data persists even after the instance is stopped or terminated.  \n   - Storage types include:\n     - **General Purpose SSD (gp3, gp2)**: Balanced performance for most workloads.  \n     - **Provisioned IOPS SSD (io1, io2)**: High performance for I/O-intensive applications.  \n     - **Throughput Optimized HDD (st1)**: Low-cost, high-throughput for big data and analytics.  \n     - **Cold HDD (sc1)**: Low-cost storage for infrequently accessed data.  \n\n2. **Instance Store**:  \n   - Temporary, high-speed storage directly attached to the instance.  \n   - Data is lost if the instance stops or terminates.  \n\n3. **Amazon S3**:  \n   - Object storage for scalable and durable storage of unstructured data.  \n   - Suitable for backups, media storage, and data lakes.  \n\n4. **Elastic File System (EFS)**:  \n   - Managed file storage for EC2 instances.  \n   - Automatically scales storage capacity as needed.  \n   - Provides shared access across multiple instances.  \n\n5. **AWS Storage Gateway**:  \n   - Hybrid solution for on-premises and cloud storage integration.  \n\n---\n\n### **Networking in EC2**  \n\n1. **Virtual Private Cloud (VPC)**:  \n   - EC2 instances are deployed within a VPC for secure and isolated networking.  \n   - Each instance gets private IPs within the VPC and optionally a public IP for internet access.  \n\n2. **Elastic Network Interface (ENI)**:  \n   - Virtual network interfaces that can be attached to EC2 instances.  \n   - Used for high availability and fault-tolerant setups.  \n\n3. **Elastic IP Addresses (EIPs)**:  \n   - Static, public IP addresses that can be assigned to EC2 instances for consistent accessibility.  \n\n4. **Security Groups**:  \n   - Act as virtual firewalls, controlling inbound and outbound traffic at the instance level.  \n\n5. **Network Access Control Lists (NACLs)**:  \n   - Stateless firewalls that operate at the subnet level, providing additional layer security.  \n\n6. **Elastic Load Balancing (ELB)**:  \n   - Distributes incoming traffic across multiple EC2 instances to ensure high availability and fault tolerance.  \n\n7. **Amazon PrivateLink**:  \n   - Enables secure private connectivity to AWS services and applications without using the public internet.  \n\n8. **AWS Direct Connect**:  \n   - Provides a dedicated network connection between on-premises environments and AWS for high throughput and low latency.  \n\n9. **Elastic Fabric Adapter (EFA)**:  \n   - Enhances high-performance computing (HPC) applications by improving network performance.  \n\n10. **AWS Global Accelerator**:  \n    - Boosts application availability and performance by routing traffic through the AWS global network.  \n\n### **Key Features**  \n- EC2 instances can leverage **high-speed networking** with options like Enhanced Networking (SR-IOV) and AWS Nitro System.  \n- Networking and storage services are designed to scale dynamically, supporting high throughput and low-latency demands.  \n\nThese storage and networking options make EC2 a powerful and adaptable service for both simple and complex workloads.\n\n\u003ca id=\"4\"\u003e\u003c/a\u003e\n# AWS EBS - Elastic Block Store\n\n### **AWS Elastic Block Store (EBS) Summary**\n\nAmazon Elastic Block Store (EBS) is a scalable and high-performance block storage service designed for use with Amazon EC2 instances. It provides persistent storage that retains data independently of the EC2 instance lifecycle. Here are the key features and details:\n\n---\n\n### **Key Features**  \n1. **Persistent and Reliable Storage**:  \n   - EBS volumes store data redundantly across multiple physical devices in an Availability Zone to ensure durability.  \n   - Data persists even after the associated EC2 instance is stopped or terminated.  \n\n2. **Types of EBS Volumes**:  \n   - EBS offers multiple volume types optimized for different use cases:\n     - **General Purpose SSD (gp3, gp2)**: Cost-effective storage for general workloads (databases, boot volumes).  \n     - **Provisioned IOPS SSD (io1, io2)**: High-performance storage for I/O-intensive applications like transactional databases.  \n     - **Throughput Optimized HDD (st1)**: Low-cost, high-throughput storage for big data and analytics.  \n     - **Cold HDD (sc1)**: Low-cost storage for infrequently accessed data.  \n\n3. **Snapshot Capability**:  \n   - EBS volumes can be backed up as snapshots stored in Amazon S3.  \n   - Snapshots can be used to restore volumes, migrate data, or create new volumes.  \n\n4. **Scalability and Elasticity**:  \n   - Volumes can be resized dynamically without downtime, allowing easy scaling of storage.  \n\n5. **Encryption**:  \n   - EBS supports encryption at rest and in transit using AWS-managed or customer-managed keys (via AWS KMS).  \n   - Encryption includes volume data, snapshots, and all data in transit.  \n\n6. **Performance Optimization**:  \n   - Volumes can be optimized for throughput or IOPS, depending on workload needs.  \n   - gp3 volumes allow customization of IOPS and throughput independently of storage size.  \n\n7. **Attach and Detach Flexibility**:  \n   - EBS volumes can be attached to or detached from EC2 instances, even across different instances within the same Availability Zone.  \n\n---\n\n### **Use Cases**  \n1. **Boot Volumes**:  \n   - EBS is commonly used as the primary storage for booting EC2 instances.  \n\n2. **Databases**:  \n   - High-performance volumes like io2/io1 are ideal for database workloads requiring low latency and high throughput.  \n\n3. **Data Warehousing**:  \n   - st1 volumes offer affordable storage for large-scale data processing and analytics.  \n\n4. **Backup and Disaster Recovery**:  \n   - EBS snapshots enable efficient backups and recovery solutions.  \n\n---\n\n### **Pricing**  \n- EBS pricing is based on volume type, size, and provisioned performance (IOPS/throughput).  \n- Snapshots are billed separately based on the storage used in S3.  \n\n---\n\n### **Advantages**  \n- **High Availability**: Redundant storage within a single Availability Zone.  \n- **Flexibility**: Customizable volumes to fit workload demands.  \n- **Integration**: Seamlessly integrates with EC2 and other AWS services.  \n- **Data Durability**: Snapshots enable easy backup and restoration.  \n\nEBS provides a versatile and dependable block storage solution for a wide variety of workloads, making it an essential component for managing EC2 instances efficiently.\n\n\n![image](https://github.com/user-attachments/assets/e7340704-e47c-4bf6-80a9-66c9b8fcbf58)\n\n\u003ca id=\"5\"\u003e\u003c/a\u003e\n# AWS Virtual Private Cloud\n\n![image](https://github.com/user-attachments/assets/a7b9dd23-b2d2-4cfd-9394-1060b41a2d69)\n\nA **Virtual Private Cloud (VPC)** is a logically isolated network environment in the cloud. It allows you to define and manage a virtual network that closely resembles a traditional on-premises data center network, but with the scalability, flexibility, and resources of the cloud. \n\nHere's an overview of key aspects of a VPC:\n\n### 1. **Isolation**\n   - A VPC is isolated from other networks in the cloud provider's infrastructure, ensuring security and control.\n   - You can control inbound and outbound traffic for resources within the VPC using network access control lists (ACLs) and security groups.\n\n### 2. **Subnetting**\n   - A VPC can be divided into smaller subnets, which are segments of the network that can be either **public** (accessible from the internet) or **private** (accessible only within the VPC or via a VPN/Direct Connect).\n\n### 3. **Customizable IP Address Range**\n   - When creating a VPC, you define its IP address range using **CIDR (Classless Inter-Domain Routing)** notation, such as `10.0.0.0/16`.\n   - This range determines how many IP addresses are available within the VPC.\n\n### 4. **Networking Features**\n   - You can connect your VPC to the internet via an **Internet Gateway** for public resources.\n   - For private connectivity, you can use a **VPN** or **Direct Connect** to link the VPC to your on-premises network.\n   - A **NAT Gateway** allows private resources to access the internet without exposing them to inbound traffic.\n   - You can also use **VPC Peering** to connect multiple VPCs or services within the same or different regions.\n\n### 5. **Security**\n   - **Security Groups** act as virtual firewalls for your instances, controlling inbound and outbound traffic.\n   - **Network Access Control Lists (NACLs)** provide an additional layer of security at the subnet level.\n\n### 6. **Use Cases**\n   - Hosting web applications or APIs with tightly controlled access.\n   - Isolating sensitive workloads and databases in private subnets.\n   - Creating hybrid cloud environments by extending on-premises networks to the cloud.\n   - Setting up multi-tier architectures with public and private subnets.\n\n### 7. **Cloud Provider Support**\n   - Major cloud providers like AWS, Google Cloud, and Microsoft Azure all offer VPCs as part of their infrastructure services:\n     - **AWS VPC**: Amazon's implementation allows full customization of networking.\n     - **Azure Virtual Network (VNet)**: Similar concept with features for Azure's ecosystem.\n     - **Google Cloud VPC**: A global VPC architecture with per-region subnets.\n\nIn essence, a VPC gives you the tools to build and manage a secure, scalable network environment in the cloud, making it fundamental for most cloud-based architectures.\n\n### more on route tables...\n\nA **route table** is a critical component of a cloud or network infrastructure that defines how network traffic is directed within a network or between networks. In the context of a **Virtual Private Cloud (VPC)**, a route table acts as a set of rules that determine where data packets should go based on their destination IP address.\n\n### Key Concepts of Route Tables:\n\n#### 1. **Routes**\n   - Each entry in a route table is called a **route**.\n   - A route defines a **destination** (IP range) and a **target** (where the traffic should be sent).\n   - For example:\n     - **Destination**: `0.0.0.0/0` (default route for all traffic)\n     - **Target**: Internet Gateway, NAT Gateway, or another network device.\n\n#### 2. **Types of Route Tables**\n   - **Main Route Table**: The default route table for a VPC, automatically created when the VPC is set up. All subnets in the VPC are initially associated with this route table unless explicitly changed.\n   - **Custom Route Table**: A user-defined route table that you can associate with specific subnets to customize routing for certain parts of your network.\n\n#### 3. **Subnet Association**\n   - Subnets in a VPC must be associated with a route table. \n   - A single route table can be associated with multiple subnets, but a subnet can only be associated with one route table at a time.\n\n#### 4. **Targets**\n   Route tables use targets to determine where traffic should be sent. Common targets include:\n   - **Internet Gateway**: For traffic destined for the internet.\n   - **NAT Gateway**: For private subnets to access the internet without exposing resources to inbound traffic.\n   - **VPC Peering Connection**: For traffic between VPCs.\n   - **Virtual Private Gateway**: For traffic routed through a VPN connection to an on-premises network.\n   - **Local**: For traffic within the VPC itself.\n\n#### 5. **Default Routes**\n   - The most common route is the **default route** (`0.0.0.0/0`), which directs traffic to the internet or other external networks.\n   - You can also define specific routes, such as `10.0.1.0/24`, for traffic within specific subnets.\n\n---\n\n### Example in AWS VPC\n\n- **Scenario**: You have a VPC with two subnets: a public subnet and a private subnet.\n  - Public subnet: Needs access to the internet.\n  - Private subnet: Needs access to the internet through a NAT Gateway.\n\n- **Route Table Setup**:\n  - **Public Subnet's Route Table**:\n    - `Destination: 0.0.0.0/0` → `Target: Internet Gateway`\n  - **Private Subnet's Route Table**:\n    - `Destination: 0.0.0.0/0` → `Target: NAT Gateway`\n    - `Destination: 10.0.0.0/16` → `Target: Local` (for internal communication within the VPC)\n\n---\n\n### How Route Tables Work\n1. **Packet Matching**: When traffic is sent from an instance, the route table looks for a matching destination in its rules. If no match is found, the packet is dropped.\n2. **Priority**: The most specific route (longest prefix match) is selected first. For example:\n   - Traffic to `10.0.1.1` will use a route with `10.0.1.0/24` before a broader `10.0.0.0/16` route.\n\n---\n\n### Common Use Cases\n- Controlling internet access for different subnets (e.g., public vs. private).\n- Routing traffic between VPCs in a peered network.\n- Directing traffic to on-premises networks via a VPN.\n- Segmenting traffic for multi-region or hybrid architectures.\n\nBy customizing route tables, you can fine-tune how your network traffic flows, ensuring security, performance, and proper routing for different workloads.\n\n\n\u003ca id=\"6\"\u003e\u003c/a\u003e\n# AWS Cloud Economics\n\nAWS offers you a pay-as-you-go approach for pricing for most of our cloud services.\n\nYou pay only for the individual services you need, for as long as you use them and without requiring ling-term contracts.\n\nAWS pricing is similar to how you pay for utilities such as water and electricity.\n\n### key principles\n\n- start early with cost optimization\n- Maximize the power of flexibility\n- Use the right pricing model\n\n\u003cimg width=\"1548\" alt=\"image\" src=\"https://github.com/user-attachments/assets/92870573-ccf7-4119-8eeb-686a75892f0b\" /\u003e\n\nWith AWS your resources are elastic.\n\nMeaning you can provision the services that you need on demand and you pay only for what you use.\n\nYour infrastructure matches your demand, a concept called **scaling**.\n\nUsing the AWS Pricing calculator, you can generate an estimate with no commitment and explore AWS services and pricing for your architecture need.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fizzypt%2Faws_cloud_practicioner","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fizzypt%2Faws_cloud_practicioner","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fizzypt%2Faws_cloud_practicioner/lists"}