Please enable JavaScript.

Coggle requires JavaScript to display documents.

Serverless - Coggle Diagram

- - - - IAM AuthN
        
        Access to cluster using IAM principals is enabled by the AWS IAM Authenticator for Kubernetes, which runs on the EKS control plane. The authenticator gets its configuration information from the aws-auth ConfigMap
        
        EKS uses IAM to provide authN to your K8s cluster, but it relies on native K8s RBAC for authZ
      - OpenID Connect (OIDC)
        
        EKS supports using OpenID Connect (OIDC) identity providers as a method to authenticate users to your cluster
        
        OIDC identity providers can be used with, or as an alternative to AWS IAM
- - - - You responsible for underlying OS
        
        EC2 price model (cost less)
        
        Long-running containers
        
        Multiple containers share the sam host
    - - No OS system access
        
        Pay per resources allocated and execution time (cost more)
        
        Short-running tasks
        
        Isolated environments
        
        Easier to use
  - - - Better for more consistent workloads
        
        Allows greater control level by developers
    - - Better for inconsistent or unpredictable workloads
        
        Perfect for app that can be expressed as a single function
        
        Good for tasks that need to integrate with AWS services
- - - - Define app with AWS SAM template
      - Set to private by default
      - Publishing app makes app available for others to find and deploy.
      - Must explicitly shared if desired
    - - Browse public apps without an AWS account
      - Browse in the Lambda Console
      - Find and deploy published app
      - Be careful of trusting all apps
- - - - Updates done manually with CLI or Flux
      - Curated packages offer extended core functionalities of K8s. This requires Enterprise Subscription
      - Located within customer DC or operations center
      - K8s control plane operated by the customer
  - - - You must first register external instances as SSM Managed Instances
      - You can install all on on-premise VM / bare-metal with script from ECS console
      - You must have the SSM Agent, ECS agent and Docker installed
      - Deploy containers using External launch type