πŸ•ΉοΈ
Ghoulsec Vault
Website Toolbase
  • Welcome !
  • πŸ—ƒοΈExam Prep Notes
    • πŸ“”CEH V13 (Master Edition)
      • Module 02: Footprinting and Reconnaissance
      • Module 03: Scanning Networks
      • Module 04: Enumeration
      • Module 05: Vulnerability Analysis
      • Module 06: System Hacking
      • Module 07: Malware Threats
      • Module 08: Sniffing
      • Module 09 : Social Engineering
      • Module 10: Denial of Service
      • Module 11: Session Hijacking
      • Module 12: Evading IDS, Firewalls , Honeypots
      • Module 13: Hacking web servers
      • Module 14: Hacking Web Applications
      • Module 15:SQL Injection
      • Module 16: Wireless Attacks
      • Module 17: Hacking Mobile Platforms
      • Module 18: IoT & OT Hacking
      • Module 19 : Cloud Computing
      • Module 20 : Cryptography
    • πŸ“˜ISC2 -Certified in Cyber Security
      • Chapter -1 Security Principals
      • Chapter -2 Disaster Recovery,Business Continuity & Incident Response
      • Chapter -3 Access Control Concepts
      • Chapter -4 Network Security
      • Chapter -5 Security Operations
    • πŸ“—AZ - 900
      • Basics of Cloud Computing
        • Economic of Scale
        • CapEx & OpEx
        • Consumption based model
        • Cloud Deployment Models
        • Shared Responsibility Model
        • Data centers, Regions & Availability Zones & Geographyies in Azure
        • Resources & Resource Group
        • Azure Access Tools
        • Azure Service Lifecycle
        • Azure SLAs
        • Azure Cloud Adoption Framework
      • Azure Services
        • Azure Computing Services
        • Azure Networking Services
        • Azure Storage Services
        • Azure Database Service
        • Azure Marketplace
        • Big Data & Azure
        • Azure Serverless Computing
        • IoT & Azure
        • Other Azure Services
        • Azure Resource Locks & Resource Tags
        • Azure Security Services
          • Security Groups
          • Routing Tables
          • Azure Firewall
          • Azure DDOS Protection
          • Azure Identity & Access Management (Azure AD)
          • Azure RBAC
          • Azure Security Center
          • Azure Key Vault
      • Azure policies & Blueprints
      • Azure Cost Management
      • Azure Core Tenents
    • πŸ“—SC - 900
      • Zero Trust Model
      • Shared Responsibility Model
      • Defense in Depth
      • Security Controls
      • CIA Triad
      • Encryption / Hashing / Signing
      • Microsoft Security & Compliance Principals
      • Common Identity Attacks
      • Microsoft Identity as Primary Security Perimeter
      • Modern Authentication with Azure AD
      • Azure AD Identity Types
      • Azure External Identities
      • Hybrid Identities
      • Authentication Methods & Password Protection
      • Conditional Access
      • Azure AD Roles & RBAC
      • Governance in Azure AD
      • Azure Identity Protection
      • Azure NSG, DDOS, Firewall
      • Azure Bastion & Keyvault
      • Azure Encryption
      • Azure CSPM
      • Azure Security Center
      • Azure Defender
        • Microsoft O365 Defender
        • Azure Sentinel
      • Microsoft Cloud App Security
      • Microsoft Intune
      • Microsoft Complaince Manager
      • Information Protection
      • Microsoft insider risk capabilities
    • πŸ“”AWS Cloud Practitioner
      • Cloud Deployment
        • AWS Global Infrastructure
      • AWS Cloud Essentials
        • AWS SNS
          • AWS SQS
      • AWS Compute & Container Services
        • AWS EC2
          • Elasticity & Agility
        • AWS Serverless Computing
        • AWS Container Services
        • AWS Beanstalk
        • AWS Load Balancing
      • AWS Storage & Databases
      • AWS Networking
      • AWS Security
        • AWS Organisation
        • AWS Compliance
        • AWS DDOS
        • Additional Security Services
      • AWS Monitoring & Analytics
        • Other Analytics Services
      • AWS Pricing & Support
      • AWS Migration & Innovation
        • Migration Statergies
        • AWS Snow Family
        • AWS Transfer Family
        • Innovation on AWS
      • AWS Well Architecture Framework
      • Other AWS Services
  • πŸ§‘β€πŸ’»Cyber Security Base
    • Ghoul's Den
    • Cheatsheets
    • SSL Handbook
      • Installing OpenSSL
      • Encrypting Web Servers using SSL
      • Compiling .pfx file using openssl
      • De-compiling .pfx file
      • Zimbra Mail Server SSL renew
      • SSL Certificates
    • ☁️Cloud Security
      • Amazon Web Services (AWS)
        • AWS - IAM & Policy Management
        • AWS Organization
        • AWS - Roles (Assume Role)
        • AWS - EC2 (Elastic Computing)
        • AWS - VPC
        • AWS - Bastion Host
        • AWS Application Load Balancer
        • AWS Auto Scaling Group
        • AWS WAF
        • AWS - VPC Peering
        • AWS Transit Gateway
        • AWS NAT Gateway
        • AWS - Route 53
        • AWS Certificates Manager
        • AWS Network Load Balancer (NLB)
    • πŸ•ΈοΈNetwork Security
      • Firewalls
        • Sophos - Security Suite
          • Sophos Firewalls
      • VPN
        • VPNs
          • Wireguard Tunneling
          • StrongSwan Gateway VPN Server on Ubuntu
      • IP Address and IP Subnetting
      • Basic to Advance Networking Materials
    • πŸ§‘β€πŸ’»VAPT
      • Sample Report Templete
      • OWASP
        • OWASP Web Application Security & WebGoat
      • Web Application testing checklist
        • Client Side Penetration Testing
          • Clickjacking
          • Websockets
          • CSRF
          • XSS Filters
        • Server Side Penetration Testing
        • Advanced Web Application Pentesting
          • OAuth
          • JWT Injection
          • Server Side Templete Injection
    • β˜„οΈGRC
      • ISMS AUDIT PLAN
      • CIS Compliance Windows
    • πŸ”Forensic
      • Forensic Tools
      • EMAIL Forensics
      • File header forensics
    • Trend Micro
      • Deep Security
        • Installation & Prerequisite
          • Microsoft SQL server 2022
          • Postgres 16 Core
          • Installation
    • Practical Malware Analysis & API Threats
  • πŸ•ΉοΈServer are fun !
    • Securing Linux
      • Securing SSH
      • Sudoers
      • UFW (Uncomplicated FW)
      • Unattended Upgrades
      • Password Complexiety
      • Auditing Linux
      • Samba - SMB
      • NFS - Network File System
      • FTP
      • AIDE
    • Servers
      • Linux Sever
        • OpenLDAP Server Setup
          • ldap-account-manager
          • Securing OpenLDAP
          • OpenLDAP client setup
          • Checking LDAP setup
        • Users & Groups
        • Password Policy
        • File & File Permissions
        • Automatic Updates
        • Adding GUI to Ubuntu Server
        • DNS Server
        • NTP Server
      • Windows Sever
        • Deep dive into Windows Server
        • Windows server Installation
        • Disable IPv6
        • Disable Server Manager on startup
        • Promoting OS to AD server
        • AD DNS
        • AD DHCP
        • AD Activation
        • AD Users & Groups
        • AD FileServer
        • Adding Users into AD
        • Bulk Importing users into Domain
        • Windows AD Resources
        • Group Policy Editor
          • Creating First Policy
          • Restricting CMD & Powershell
          • Password Policies
          • Audit Policies
          • Log Retention Policy
          • Windows Defender Firewall
          • Patch Management & Window Updates
        • Setting Up local accounts for windows hosts
    • Hacking Systems
      • Linux Systems
        • Battery Charge Threshold (Linux)
        • Metasploitable OS Complete Solved
      • Tricking Windows
        • Bitlocker & Time based policy bypass
    • Monitoring HeartBeats
    • RAID Technology
    • Managing Partitions
      • Parted
      • Fdisk
      • LVM
        • Re-claiming unused disk space
        • Adding physical volume into VG
        • Removing physical volume from VG
      • SWAP Memory
    • Virtualization
      • Proxmox
        • Proxmox VE Installation
        • Default Storage Expansion
        • Proxmox Network Link Aggegration
        • NAT Interface Configuration
        • Importing disk into proxmox
        • Creating an LVM Thin Pool
        • Proxmox IAM
  • πŸ™β€β™‚οΈDan the AI Expert
    • Ollama Ollama ...
      • Ollama
        • Ollama models
        • Open Web UI & Ollama Integration
    • Microsoft Presentation using AI
  • πŸ›‘οΈSecurity Operations
    • Wazuh - Open Source XDR. Open Source SIEM.
      • Components
      • Deployment Methods
      • Installation
        • Single Node Installation
          • Wazuh Indexer Installation
          • Wazuh Server Installation
          • Wazuh Dashboard Installation
          • Single node deployment with Script
        • Managing multiple Wazuh clusters with Cross-Cluster Search
          • Cluster Configuration
          • Set up Cross-Cluster Search
        • Upgrading Wazuh Central Components
        • Uninstalling Wazuh
      • Custom Decoder & Rules
        • Pfsense Decoders
        • Pfsense Rules
      • Security Operations Center Tools (Wazuh)
    • IRIS-DFIR / Case Management
    • Graylog & ElasticSearch
    • Zabbix NMS
      • Zabbix Installation
      • Zabbix Database Management
        • Zabbix Database backup
        • Zabbix Database restore
        • MySQL Replication (M-M)
        • MySQL Replication (M-W)
      • Zabbix Geomap Setup
      • Adding Hosts into Zabbix
      • Zabbix Hostgroups
      • Auto Registration Hosts Zabbix
      • Zabbix Globalscrips
      • Zabbix HA Cluster
      • Zabbix Proxy
      • Zabbix Notifications
      • Zabbix Maintainance
      • Zabbix User Management & Authentication
      • Zabbix Housekeeping
      • Scheduled Reporting
      • Service Monitoring using Zabbix
  • Git the master!!
    • Configuring git
    • Git Branches
    • Undoing changes
    • Git - Cheat sheet
    • My first git...
Powered by GitBook
On this page
  1. Exam Prep Notes
  2. AZ - 900

Basics of Cloud Computing

PreviousAZ - 900NextEconomic of Scale

Last updated 2 months ago

Cloud computing is the delivery of various services like storage, computing power, networking, analytics, and more, all over the internet. Instead of having physical servers or local systems, these services are hosted in the cloud, which means you can access them remotely anytime, anywhere. It's like using a powerful computer or storing files without needing to own or manage the actual hardware. Cloud computing makes it easier, faster, and more cost-effective for businesses and individuals to use technology without worrying about maintenance or infrastructure.

Characteristics of Cloud Computing :

Scalability in Cloud

Scalability is the ability of a cloud computing system to handle increasing workloads or user demand by adding resources, either vertically or horizontally. It allows a system to grow or shrink in capacity as needed, ensuring that performance remains optimal without over-provisioning.

Vertical Scaling (Scaling Up)

  • Definition: Vertical scaling, also known as scaling up, involves adding more resources (such as CPU, memory, or storage) to an existing server or instance to enhance its capacity.

  • Example: If a virtual machine (VM) starts experiencing performance issues due to increased load, you can upgrade its CPU or RAM to handle more requests or data.

  • Use Case: Vertical scaling is suitable for applications or services that are optimized to run on a single server and require increased performance within that system.

  • Pros:

    • Easier to implement since only one machine is involved.

    • No need to manage multiple servers or systems.

  • Cons:

    • There’s a limit to how much you can scale a single server (e.g., hardware limitations).

    • Can be more expensive as you have to upgrade to larger, more powerful machines.

Horizontal Scaling (Scaling Out)

  • Definition: Horizontal scaling, also known as scaling out, involves adding more instances or servers to distribute the workload across multiple machines rather than upgrading a single server.

  • Example: Instead of making a single server more powerful, you add more servers to form a cluster and distribute traffic or processing across them.

  • Use Case: Horizontal scaling is often used in large-scale web applications, databases, and cloud environments that require distributed computing and can benefit from being spread across multiple servers.

  • Pros:

    • Virtually unlimited scaling, as more servers can be added as needed.

    • Improved fault tolerance and redundancy since multiple servers are used.

  • Cons:

    • More complex to manage because it involves multiple machines, load balancing, and networking.

    • Can be challenging to maintain consistency and synchronization between multiple instances.

Scaling In & Scaling Out

  • Scaling Out: This refers to adding more instances or servers to a system to handle higher loads, which is another term for horizontal scaling. It’s like spreading the workload across more machines to distribute processing power and storage.

  • Scaling In: Scaling in is the opposite of scaling out. It refers to reducing the number of instances or servers when the demand decreases. This can save costs by eliminating unnecessary resources that aren't being used.

For example, if the traffic to an application decreases after peak hours, scaling in would involve shutting down or deallocating extra servers that were added during higher demand.

Elasticity in Cloud Computing

Elasticity refers to the ability of a cloud computing system to automatically and dynamically scale resources up or down in response to changes in demand. This means that the system can quickly adapt to increasing or decreasing workloads, ensuring efficient use of resources without manual intervention.

  • Scaling Up (or Out) when Demand Increases: When there’s a sudden spike in demand, such as more users accessing a service, the cloud platform automatically adds more computing resources (like additional servers or storage) to handle the increased load.

  • Scaling Down (or In) when Demand Decreases: When the demand drops, such as fewer users or less data to process, the cloud system reduces the resources it uses, releasing unneeded capacity and optimizing costs.

Key Points of Elasticity:

  • On-demand: Elasticity enables resources to be provisioned or decommissioned quickly, depending on current needs.

  • Cost-efficient: You only pay for the resources you actually use, reducing unnecessary costs during periods of low demand.

  • Automatic & Dynamic: Elastic systems adjust without the need for human intervention, ensuring continuous optimal performance without manual effort.

Example:

If you run an online store and experience a surge in traffic during a sale, elasticity allows your cloud infrastructure to automatically add more servers to handle the traffic. Once the sale ends and traffic drops, the system scales down, reducing costs by freeing up unused resources.

Elasticity ensures cloud environments can respond efficiently to fluctuating workloads, making them more adaptable and cost-effective.

Agility in cloud computing refers to the ability to quickly and efficiently adapt to changing business needs, customer demands, or market conditions. It enables organizations to rapidly develop, test, deploy, and scale applications and services with minimal delay, ensuring they can stay competitive and responsive to new opportunities.

With cloud computing, agility is achieved because resources and services are readily available and can be quickly provisioned or reconfigured without the need for long-term commitments or complex infrastructure changes. This allows businesses to experiment, innovate, and scale rapidly as needed.

Key Characteristics of Agility in Cloud Computing:

  1. Fast Deployment: Cloud services allow businesses to launch new applications and services in a fraction of the time it would take using traditional on-premises infrastructure. This enables faster time-to-market for products or updates.

  2. Flexibility: The cloud offers flexible resources that can be easily reconfigured to meet changing demands, whether that’s scaling up resources for a new project or scaling down after a project's completion.

  3. Innovation: With cloud resources available on-demand, businesses can experiment with new technologies or develop prototypes without the upfront investment or long wait times typically associated with physical infrastructure.

  4. Cost-Efficiency: Agility in the cloud also helps with cost control. You pay only for the resources you need, which helps businesses adjust their budgets as they scale their operations up or down based on real-time demand.

Example:

If a tech company needs to quickly launch a new feature for its app to meet customer demand or stay ahead of a competitor, cloud computing allows the team to rapidly provision additional computing power, storage, and development tools without waiting for hardware installations or setups. Once the feature is successful, the company can scale back resources, reducing costs.

In essence, agility in cloud computing helps businesses become more responsive and adaptable, ensuring they can meet new challenges and opportunities quickly and effectively.

ON PREMISE INFRASTRUCTURE
CLOUD ENVIRONMENT

Deployment Time : Hour / Sec / Mins

Deployment Time : Days / Weeks / Month / Years

Fault tolerance in cloud computing refers to the ability of a system to continue operating properly in the event of a failure of one or more of its components. It ensures that services, applications, and systems remain available and functional, even if part of the infrastructure (like hardware or software) experiences an issue or crash. This is critical for ensuring reliability and minimizing downtime, which is essential for maintaining user trust and service continuity.

Cloud platforms achieve fault tolerance through redundancy, distribution, and self-healing mechanisms that automatically detect and recover from failures.

How Fault Tolerance Works:

  1. Redundancy: Cloud systems often replicate data and services across multiple servers or locations. If one server or data center goes down, traffic or data can be redirected to another server or data center, ensuring uninterrupted service.

    • Example: If a cloud application has its database spread across multiple servers (or regions), and one server fails, another server can continue to serve the application without impacting users.

  2. Automatic Failover: When a failure occurs, cloud systems can automatically switch to a backup or redundant system (failover) without manual intervention. This process happens seamlessly, allowing users to continue using the service with little to no interruption.

    • Example: If a cloud-based website experiences issues with its primary web server, the system can automatically switch to a backup server, maintaining the website’s availability.

  3. Distributed Architecture: Many cloud applications are built on distributed systems, meaning the workload is spread across multiple nodes (servers, data centers, etc.). If one part of the system fails, the rest of the system can continue to function without significant impact.

  4. Self-Healing: Some cloud services include mechanisms to detect failures and automatically replace faulty components. For example, a failed virtual machine (VM) might be automatically restarted or replaced with a new one, ensuring the application or service keeps running smoothly.

Benefits of Fault Tolerance in Cloud Computing:

  • High Availability: With fault-tolerant systems, cloud services are designed to be always available, minimizing downtime and disruptions.

  • Reliability: Fault tolerance helps ensure that even if individual components fail, the overall system will still function correctly, providing consistent performance.

  • Business Continuity: By maintaining operations during failures, businesses can avoid the financial and reputational costs associated with downtime.

Example:

Imagine an e-commerce platform hosted on the cloud. If one of the servers hosting customer data or payment processing fails, the cloud system can automatically shift that load to another server, ensuring that customers can still browse products and complete transactions without disruption. If multiple servers in one region fail, traffic can be routed to another region, maintaining service continuity.

In summary, fault tolerance in cloud computing is about building systems that can detect, recover from, and adapt to failures, ensuring high availability and reliable service even in the face of unexpected issues.

Disaster recovery (DR) in cloud computing refers to the process of preparing for and recovering from unexpected events or disasters that can disrupt normal business operations, such as system failures, natural disasters, cyberattacks, or human errors. The goal of disaster recovery is to ensure that data is protected and systems can be quickly restored to minimize downtime and business interruption.

Cloud computing provides powerful tools and strategies for disaster recovery by leveraging its flexibility, redundancy, and geographic distribution to quickly recover from failures.

How Disaster Recovery Works in Cloud Computing:

  1. Data Backup & Replication: Cloud platforms often provide automated backup services, where critical data and applications are continuously replicated across multiple servers, storage systems, or geographic regions. If one location fails, the backup data stored in another location can be quickly restored.

    • Example: A company’s critical data might be replicated in multiple data centers around the world. If one data center experiences a failure due to a natural disaster, the company can immediately access the backup data from another location.

  2. Geographic Redundancy: Cloud services often offer disaster recovery solutions with geographic redundancy. Data and applications can be spread across multiple regions or availability zones. This ensures that if a natural disaster or regional failure impacts one location, the system can still function from another region without interruption.

    • Example: A business running in the U.S. can store backup copies of its critical data in a different region, such as Europe or Asia, so that if there is a disaster in the U.S., operations can continue using the data from the alternate region.

  3. Automated Failover: Cloud platforms can be configured with automatic failover systems. When a failure occurs, the system can automatically switch to a backup or disaster recovery system, ensuring continuity of operations without manual intervention.

    • Example: If a cloud server hosting a critical application goes down, an automatic failover process can redirect traffic to another server or cloud region with an identical application, ensuring there is no service disruption.

  4. Cloud-based DR as a Service (DRaaS): Many cloud providers offer Disaster Recovery as a Service (DRaaS), a solution where businesses can pay for cloud-based disaster recovery resources. This eliminates the need for businesses to maintain separate physical disaster recovery sites and reduces the overall cost and complexity of disaster recovery.

    • Example: A company can use a DRaaS solution to replicate its servers in the cloud, and in the event of a disaster, the company can quickly spin up its systems in the cloud without needing to rely on its own infrastructure.

Benefits of Disaster Recovery in Cloud Computing:

  1. Cost-Effective: Cloud-based disaster recovery solutions are typically more affordable than maintaining a physical disaster recovery site. The pay-as-you-go model allows businesses to only pay for the resources they use, reducing upfront costs.

  2. Speed & Efficiency: Cloud systems enable rapid failover and recovery, reducing downtime and ensuring business continuity. In some cases, recovery can happen in a matter of minutes or hours, depending on the severity of the disaster.

  3. Scalability & Flexibility: Cloud disaster recovery solutions can be scaled up or down as needed, depending on the size and complexity of the organization. It provides flexibility to customize recovery plans based on business requirements.

  4. Geographic Independence: With cloud computing, businesses are no longer limited to having their disaster recovery systems in the same geographic area as their primary data centers. This reduces the risk of both being affected by the same disaster.

  5. Automatic Updates & Maintenance: Cloud providers ensure that the disaster recovery system is always up-to-date, reducing the risk of outdated software or systems that could slow down recovery efforts.

Example:

Consider an online service that relies on cloud hosting for its website and databases. If the primary cloud region goes down due to a disaster like a power outage or earthquake, the service could automatically fail over to a backup region in a different area. The data and application are seamlessly restored, and users can continue accessing the site with minimal disruption, all without the need for physical recovery efforts.

In summary, disaster recovery in cloud computing ensures that businesses can quickly recover and continue operations even after major disruptions, thanks to the cloud's redundancy, scalability, and automation features. It provides businesses with a reliable, cost-effective, and efficient way to protect data and maintain service availability during times of crisis.


πŸ—ƒοΈ
πŸ“—