Please enable JavaScript.

Coggle requires JavaScript to display documents.

M5 (lamda, AWS batch, ECS, ECR) - Coggle Diagram

- - - - My function will receive high amounts of traffic. What should I do to make sure AWS Lambda can support it?
        
        The first thing that you have to do is to load test your function. Load testing will allow you to know how much
        
        memory your function needs to finish its processes. Once that is done and you can predict the amount of
        
        traffic that will arrive, increase your concurrency limits to allow your function to scale better. That way, you
        
        won’t have to worry about running out of resources for your Lambda functions.
        
        If you did not load test and just increased your function’s RAM capacity, it might not have any large benefit to
        
        your function’s overall performance. It will also hog more of your resources than necessary which will
        
        decrease your ability to scale. The same goes with increasing function timeout.
    - - Invocation Errors
        
        ○ User: arn:aws:iam::123456789012:user/developer is not authorized to perform:
        
        lambda:InvokeFunction on resource: my-function
        
        ■ Your IAM user, or the role that you assume, needs permission to invoke a function
    - - ○ Function execution takes too long.
        
        ■ If your code takes much longer to run in Lambda than on your local machine, it may be
        
        constrained by the memory or processing power available to the function. Configure the
        
        function with additional memory to increase both memory and CPU.
        
        ○ Function returns before code finishes executing
        
        ■ Many libraries, including the AWS SDK, operate asynchronously. To wait for the promise
        
        to resolve into a response, use the await keyword
  - - - Function memory allocation ( can’t be changed)
      - 128 MB to 3,008 MB, (Max 3GB can’t be change)
      - Concurrent executions - default is 1,000 which can increase to Hundreds of thousands
      - Duration is 15 minute- this limit also can’t change
      - Per region
      - Invocation requests per Region (requests per second) -10 x concurrent executions quota
      - Deployment package size
      - Deployment package is
      - the client creates a ZIP archive of your code when you author functions in the Lambda console or a toolkit
      - Deployment package size -50 MB (zipped)
  - - - Function – a script or program that runs in Lambda. Lambda passes invocation events to your function.
      - The function processes an event and returns a response.
      - ● Runtimes – Lambda runtimes allow functions in different languages to run in the same base execution
      - environment. The runtime sits in-between the Lambda service and your function code, relaying
      - invocation events, context information, and responses between the two.
      - ● Layers – Lambda layers are a distribution mechanism for libraries, custom runtimes, and other function
      - dependencies. Layers let you manage your in-development function code independently from the
      - unchanging code and resources that it uses.
      - ● Event source – an AWS service or a custom service that triggers your function and executes its logic.
      - ● Downstream resources – an AWS service that your Lambda function calls once it is triggered.
      - ● Log streams – While Lambda automatically monitors your function invocations and reports metrics to
      - CloudWatch, you can annotate your function code with custom logging statements that allow you to
      - analyze the execution flow and performance of your Lambda function.
      - ● AWS Serverless Application Model