Serverless-Dev-Tools

Serverless-Dev-Tools

  • Docs

›Guardian Rules

Installation and Use

  • Installation and use

Pricing

  • Cloudwatch Pricing

Guardian Rules

  • no-max-timeout
  • no-max-memory
  • no-shared-roles
  • no-identical-code
  • no-default-memory
  • no-default-timeout

no-max-memory

No Functions Have Memory Configuration To Maximum Limit (no-max-memory)

Lambda Functions memory is configurable and should be configured for the use-case. This can impact the speed and running cost of the Lambda Function.

Note: Any increase in memory size triggers an equivalent increase in CPU available to your function


Suggested Actions:

  • Look into your CloudWatch Logs for the Lambda function to find Max Memory Used more information
REPORT RequestId: 3604209a-e9a3-11e6-939a-754dd98c7be3  Duration: 12.34 ms  Billed Duration: 100 ms Memory Size: 128 MB Max Memory Used: 18 MB
  • Power-tune using aws-lambda-power-tuning
← no-max-timeoutno-shared-roles →
  • Suggested Actions:
Serverless-Dev-ToolsTheodo
Docs
Installation and useAWS pricing
Community
Follow @SlsDevTools
More
BlogGitHubStar