AWS Core Services - amitbhilagude/userfullinks GitHub Wiki

  1. Core Resources
    1. AWS Management Console(Azure Portal)
    2. AWS CLI(Azure CLI or PowerShell)
      1. Access key can be generated in AWS Management Console and it is used AWS CLI. Azure doesn't have this option. Instead, Azure AD App is used.CLI will have a profile with this access key and for every Azure CLI call, is passed.
    3. Elastic BeanStock ->Azure App Service
    4. AWS Lambda -> Azure Function
    5. CDN and Networking
    6. Virtual Private Cloud -> Vnet in azure
    7. Direct Connect -> Express Route
    8. Route 53 -> Azure DNS and Traffic manager
    9. AWS Software Development KIT(SDK)
  2. User Types
    1. Root user: First user which is creating while activating AWS subscription and selected the support plan during the activation process.
    2. IAM User:
  3. Compute Services
    1. Amazon EC2(Elastic compute2) ->VMs into Azure
      1. Instance Type
        1. General-Purpose -> Same in Azure
        2. Compute, Memory, and Storage Optimised -> Same in Azure
        3. Accelerated computing -> GPU in Azure
        4. Amazone Machine Image(AMI) -> OS Image in Azure
      2. Purchase Option
        1. VMs configuration is based on vCore(CPU), Memory and OS Type(Linux or Windows) e.g. T, M, I and P series
        2. On-demand(Create when necessary charge based on hours running), Reserved(Reserve instance for 1-3 years), Saving plan(Similar to Reserved but applicable not on only VMs but other cloud offering like BeanStack and Lambda, Spot(Cheapest option with biding option) and dedicated options(Dedicated instances)
    2. BeanStack -> App services in Azure
      1. Advantages
        1. PaaS offering
        2. No operation overhead
        3. Built-in deployment and monitoring capabilities
    3. Lambda -> Azure Function in Azure
      1. Serverless offering with pay-as-go.
  4. Networking
    1. VPC -> vnet in Azure
      1. Features
        1. Peering
        2. Subnet
        3. Route Table
        4. IP address range
        5. Network gateways
    2. Route 53 -> DNS and Traffic manager
      1. Edge location service and highly available
      2. DNS and global routing
    3. Elastic Load Balancer
      1. Types
        1. Application Load Balancer(ALB - Level 7) ->> App gateway in Azure
        2. Network Load balancer(NLB - Level 4) -> Standard Load Balancer
        3. Classic Load Balancer -> Old load balancer supports both levels 4 and 7. Only supported for Classic VMs now.
    4. CloudFront -> CDN in Azure
      1. Utilised edge locations
      2. AWS Shield for DDoS -> Azure DDos
      3. AWS WAF -> Azure WAF
    5. API Gateway -> Azure API Management in Azure
  5. S3 -> Blob storage in Azure
    1. Overview
      1. Bucket -> Container in Azure
      2. Storage class -> Account type in Azure(Hot, Cool, and Archive)
        1. Types: Archival and Non-Archival
          1. Non-Archival types
            1. S3 Standard - Frequent access-> Hot
            2. S3 Intelligent Tiering -> automatically chooses storage class based on usage. It is like moving data from Hot and cool automatically based on Access.
            3. S3 Standard Infrequent Access(IA)-> Cool
            4. S3 One zone IA -> Cool access with locally redundant
          2. Archival Types (Glacier and Glacier Deep Storage)
          3. Glacier - minimum 90 days of archival, can access per minutes and hours - 5 times less expensive than Standard plan 2, Glacier - minimum 180 days of archival, can access per hour, 23 times less than expensive than standard
      3. Object -> Blob in Azure
      4. Elastic Block Store -> Data disk in Azure Blob storage
        1. Files can be uploaded in EBS and attached to an EC2 instance. It follows the same HDD plans
      5. Elastic File System(EFS) -> Azure files
        1. Fully managed NFS file system
        2. Support TBs and PBs
        3. Designed for Linux workload
        4. Advantages over EBS is it supports availability zones. One instance will be used in multiple zones.
        5. Amazon FSx: EFS system design for Windows workload with some built-in integration like AD
      6. AWS Snowball and Snowmobile -> Azure Data box
        1. Both are used large scale data transfer in PBs and exabytes
        2. Snowball device will be sent to you where on-prem data will transfer into that and ship it into the courier
        3. Snowmobile similar to snowball but Shipping container transfer to you. Data transfer to the snowmobile and then to the S3.
  6. Database Service
    1. Category
      1. IaaS - Run DB on EC2 instances
      2. PaaS -> Amazon RDS. Relational Database management Service
      3. SaaS -> Dynamo DB No-SQL
    2. Amazon RDS
      1. Supported DB
        1. SQL
        2. MySQL
        3. Oracle
        4. Maria
        5. PostgreSQL
        6. Amazon Aurora - Server-less offering
    3. Database Management Service (DMS)
      1. Database migration service to migrate data one time or continuous sync
      2. Pay-as-go offering
    4. Dynamo DB -> Cosmos DB
      1. No-SQL DB with highly scalable
    5. Elastic cache -> Azure cache for Redis
      1. Support In-memory and Redis cache both
    6. Redshift -> Synapse Analytics
      1. Data warehouse solution
  7. App integration services
    1. Simple Notification Service(SNS) -> Service Bus Topic- Subscribe and Push notifications in azure
      1. Used for Pub-sub model
      2. Support for SMS, and email notifications as well
    2. Simple Queue Service(SQS) -> Service bus queue
      1. Types
        1. Standard -> Storage queue in Azure
        2. FIFO -> Service bus queue. Guaranteed FIFO delivery
    3. AWS Step Functions -> Logic app in Azure
      1. Workflow service