I have created a serverless project for python on AWS, which works fine... until I try to re-use the project directly after checkout. Any CLI command exits with the following error:

 sls help
 
 Serverless Error ---------------------------------------
 
  Serverless plugin "serverless-python-requirements" not found. Make sure it's installed and listed in the "plugins" section of your ser

The README at https://github.com/Miserlou/Zappa#custom-aws-iam-roles-and-policies-for-execution talks about using manage_roles: false to manually set a role for custom permissions.

This along with Miserlou/Zappa#244 led me down a rabbit hole.

However, if all you want to do is restrict the permissions of the Lambda itself, it seems that the partially documented `at

I tried to install the dotnet example using:

install -u https://github.com/serverless/examples/tree/master/aws-dotnet-rest-api-with-dynamodb -n dotnet_example

but it responds with:

Serverless Error ---------------------------------------

serverless.yml not found in .../dotnet_example

So I think the "-n my-project" in the README is perhaps not what is actually needed he

Hello,
Thanks for the job you've done! Chalice is the very easy framework for newcomers and flask developers.

I've been learning the framework only for 2 weeks and regularly getting errors related with aws policies. The official content about the policies is minimal. And auto-policy can't do this job by the right way if you want to add more than just a 'hello world' function.

Run **chalice

Serverless Stack tutorial showing use of Angular instead of React, with hosting in AWS using serverless-s3-sync instead of netlify for a purely AWS services based development stack experience ?
Any plans for that?
If not, I'm willing to contribute, as I have certain degree of experience with it.

I'm trying to follow the quick guide, I've done these steps:

1. serverless create -u https://github.com/adieuadieu/serverless-chrome/tree/master/examples/serverless-framework/aws
2. export AWS_PROFILE=serverless
3. npm run deploy

However at point 3, I'm not in the right folder am I?

If I cd aws and the run npm run deploy I get an error:

Serverless Error ---------------

A great, simple and cheap use case for a component is a URL shortener that might just only require API Gateway proxies with a custom domain name. Lambda & DynamoDB wouldn't be required here.

shortner:
  component: @serverless/url-shortner
  inputs:
    domain: sls.io
    urls:

     # You could provide a custom path => sls.io/NewRelease
      - name: NewRelease
         url: htt

I'm submitting a...

[x ] Bug report  
[ ] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[x] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/f

Describe the bug
When using [email protected], navigating to an invalid URL does not show the 404 error page. Instead, you see 200 | An unexpected error has occurred.

To Reproduce
Steps to reproduce the behavior:

1. Clone this repository: https://github.com/sidarthar/serverless-nextjs-404-error
2. Run npx serverless to deploy

Is there a plugin to support Step Functions in offline mode?

This would require an implementation of State Machine which is described by Amazon States Language.

For starters it would

Is there anyway to specify log group name to be AppSync's api name instead of API ID. I see this code is used to fetch the loggroupname

LogGroupName: { 'Fn::Join': ['/', ['/aws/appsync/apis', { 'Fn::GetAtt': [logicalIdGraphQLApi, 'ApiId'] }]] },

is there a way to make this API name instead. In cloudwatch - pointing at correct appsync loggroup becomes little difficult as we have to know s

synk report issue

Description

We are synk (https://snyk.io/) for checking used packages.

Synk is complaining about a security issue for serverless-step-functions.
https://snyk.io/vuln/SNYK-JS-DOTPROP-543489

Additional Data

• Serverless Framework Core Version you're using: 1.64.1
• The Plugin Version you're using: 2.17.1
• Operating System: macOS Majove 10.14

I get the following in my console:

added 901 packages from 528 contributors and audited 23650 packages in 264.328s
found 364 vulnerabilities (44 low, 309 moderate, 11 high)
  run `npm audit fix` to fix them, or `npm audit` for details

When I run npm audit I get this

 === npm audit security report ===

# Run  npm install --save-dev [email protected]  to resolve 136 vulnerabili

Typescript 3 supports references:

• https://blogs.msdn.microsoft.com/typescript/2018/07/30/announcing-typescript-3-0/#project-references
• https://github.com/Soul-Master/typescript3-composite-project

Does this plugin respect references and include dependencies from depended upon packages in a mono repo?

Here are 3 sequence diagrams of how this works, that you can plug into https://www.websequencediagrams.com/ when you are making slides or whatever.

title Authentication
Browser->Sign In: Initial request
Sign In -> Facebook: Redirect
note over Facebook: Approve login
Facebook -> Callback: Redirect
Callback -> FaunaDB: Find or create user
FaunaDB -> Callback: Database secret for user

Hi,

on the Authentication Guide there's a missing link on this sentence "Also see Chat App IoT Topic Explanation for an explanation of the topic space used for this application."

https://github.com/aws-samples/aws-iot-chat-example/blob/master/docs/iot_topics.md

Does this explanation exist?

Thank you

I would love to see a tutorial on how to do per function IAM role to added to the website.
This https://serverless.com/framework/docs/providers/aws/guide/iam/#custom-iam-roles but explained in a much better way :)

Description

Add content to the Development/Debugging section of the guide.

We should update the main API reference page:

• Include links to latest release API references
• Include links to past releases of API references
• Use same UI as skygear-JS-SDK

Dashboards cost real money beyond a small free tier : https://aws.amazon.com/cloudwatch/pricing/

It would be good to have alerts in all stages, but the dashboard only in live/prod (not dev,stage).

The descriptions for these sub-projects are missing descriptions in both the root README.md as well as their respective readme files