npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@lendi/serverless-simplify-default-exec-role-plugin

v1.0.0

Published

serverless-simplify-default-exec-role-plugin

Downloads

1,609

Readme

serverless-simplify-default-exec-role-plugin

** This is a fork of serverless-simplify-default-exec-role-plugin by woebot

which in itself was a fork of serverless-simplify-default-exec-role-plugin by shelfio **

A quick solution for the IamRoleLambdaExecution error: Maximum policy size of 10240 bytes exceeded.

  • This plugin modifies the IamRoleLambdaExecution policy to reduce its size.
  • Unlike the original version, this maintains any custom IAM statements attached to the Lambda role.
  • It also doesn't collapse "logs:CreateLogStream", "logs:CreateLogGroup", and "logs:PutLogEvents" permissions into the same IAM statement.

Installation

$ npm install --dev @lendi/serverless-simplify-default-exec-role-plugin

Usage

In your serverless.yml file:

plugins:
  - "@lendi/serverless-simplify-default-exec-role-plugin"

IAM simplification for logs: statements

By default the Serverless framework adds something like the IAM statement below in order to allow write access to CloudWatch log groups that are part of the deployment stack. For stacks with a lot of lambda functions, this can cause the role to exceed the maximum allowed size of 10240 bytes. This plugin reduces the size of the generated lambda role by replacing the resource list with a single ARN to grants write access to all log groups that are part of the same region and account.

Before

{
  "Effect": "Allow",
  "Action": ["logs:CreateLogStream", "logs:CreateLogGroup"],
  "Resource": [
    {
      "Fn::Sub": "arn:${AWS::Partition}:logs:${AWS::Region}:${AWS::AccountId}:log-group:/aws/lambda/production-users-createUser:*",
    },
    {
      "Fn::Sub": "arn:${AWS::Partition}:logs:${AWS::Region}:${AWS::AccountId}:log-group:/aws/lambda/production-users-updateUser:*",
    },
    {
      "Fn::Sub": "arn:${AWS::Partition}:logs:${AWS::Region}:${AWS::AccountId}:log-group:/aws/lambda/production-users-deleteUser:*",
    },
    // ... and so on, for each lambda function that logs to cloudwatch
  ],
}

After

{
  "Effect": "Allow",
  "Action": ["logs:CreateLogStream", "logs:CreateLogGroup"],
  "Resource": [
    {
      "Fn::Sub": "arn:${AWS::Partition}:logs:${AWS::Region}:${AWS::AccountId}:log-group:*",
    },
  ],
}

IAM simplification for kinesis:* statements

Needs more testing

When you attach a kinesis stream as an event source, it creates an IAM policy per kinesis stream

Before

{
    "Effect": "Allow",
    "Action": [
        "kinesis:GetRecords",
        "kinesis:GetShardIterator",
        "kinesis:DescribeStreamSummary",
        "kinesis:ListShards"
    ],
    "Resource": [
        "arn:aws:kinesis:<region>:<account>:stream/<stream-name>"
    ]
},
...many depending on number of input events to lambdas
{
    "Effect": "Allow",
    "Action": [
        "kinesis:GetRecords",
        "kinesis:GetShardIterator",
        "kinesis:DescribeStreamSummary",
        "kinesis:ListShards"
    ],
    "Resource": [
        "arn:aws:kinesis:<region>:<account>:stream/<stream-name>"
    ]
},

After

{
    "Effect": "Allow",
    "Action": [
        "kinesis:GetRecords",
        "kinesis:GetShardIterator",
        "kinesis:DescribeStreamSummary",
        "kinesis:ListShards"
    ],
    "Resource": [
        "arn:aws:kinesis:<region>:<account>:stream/<stream-name>"
    ]
},

tests

We have every intention of creating more tests to validate this plugin...

License

MIT ©