serverless-iam-roles-per-function
plugins
serverless-iam-roles-per-function | plugins | |
---|---|---|
2 | 5 | |
410 | 970 | |
0.7% | 0.4% | |
0.0 | 1.5 | |
5 months ago | 3 months ago | |
TypeScript | JavaScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
serverless-iam-roles-per-function
-
Fine-grained access control using leading keys in dynamo and serverless-iam-roles-per-function
We are using https://github.com/functionalone/serverless-iam-roles-per-function/ .
-
Insecure Serverless Plugins: Why You Should Inspect the Source Code
Configure AWS IAM policies per function
plugins
-
The Top 10 GitHub Repositories Making Waves ๐๐
Plugins
-
How To Write Your First Plugin For The Serverless Framework โ Part 1
You can ease your pain by using plugins. Some are already built for the most common problems (check them out in the official Serverless Plugins Github repo), but there are always some project-specific issues that plugins can help you resolve. Fortunately, writing a plugin for the Serverless Framework is easier than you might think.
-
How to manage your AWS Step Functions with Serverless
Before getting started, you need to install the plugin. This is hosted on the Serverless Plugins registry, so you can install this via the plugin install command which is introduced since v1.22.0.
-
IBM Auto AI Predict Early Stage Diabetes - Part 3
service: functions useDotenv: true provider: name: openwhisk functions: autoai: handler: handler.autoai parameters: api_key: ${env:api_key} events: - http: POST /autoai # extend the framework using plugins listed here: # https://github.com/serverless/plugins plugins: - serverless-openwhisk - serverless-dotenv-plugin
-
Insecure Serverless Plugins: Why You Should Inspect the Source Code
The plugins are built by the Serverless community. Anyone can create a plugin. The Serverless Framework company lists plugins, but only a subset are "approved." This means we should be cognizant of what we are using.
What are some alternatives?
lambda-cobol - Serverless Legacy Modernization : AWS Lambda + Cobol
serverless-plugin-ifelse - A Serverless Plugin to write If Else conditions in serverless YAML file
lift - Expanding Serverless Framework beyond functions using the AWS CDK
serverless-prune-plugin - Serverless Framework plugin to reap unused versions of deployed functions from AWS
subscriptionless - GraphQL subscriptions (and more) on serverless infrastructure
serverless-stack-termination-protection - Serverless plugin to update the CloudFormation stack termination protection.
serverless-offline-ssm - Read SSM parameters from a .env file instead of AWS
serverless-alexa-skills - Manage your Alexa Skills with Serverless Framework
terraform-aws-github-runner - Terraform module for scalable GitHub action runners on AWS
fullstack-serverless - Serverless Plugin - Simplify creating a full stack serverless web app
serverless-mocha-plugin - Plugin for Serverless Framework which adds support for test-driven development using Mocha