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

AWS Lambda currently supports Node v10.x
Can you please support it.

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https

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

• Main website searches through sourcecode OR public services
• Dashboard searches through your services
• Docs search through docs

More importantly, almost all widgets look the same.

I think we need consistency here: either give all widgets the same functionality (dropdown for public services, sourcecode, your services, and docs) or change how they look. I think first option is ideal.

Currently, logging routes just uses console.log. Gets pretty annoying when you're trying to suppress serverless. (i.e. serverless.cli = { log: () => {} }

https://github.com/dherault/serverless-offline/blob/59ff77f18745c11d527aaff78220b6c9b36a7249/src/serverlessLog.js#L60-L70

we want to use swagger integrated with API document under aws-serverless-express framework, so any document/guideline to follow?
if we follow some code rule to define the API method then generate the API document and show in swagger it is perfect

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

In the documentation it says that a disadvantage of using the api gateway directly is that there is no https redirect. Ref: https://bref.sh/docs/websites.html#architectures

I'm new to aws but I basically used the api gateway and configured a custom domain and I noticed that there is a https redirect. Try: curl -v 'http://symfony-bootstrap.marco.zone'

Now I'm questioning: is that new and no

Issue type

• Bug Report

Build number

master branch

Configuration

Deployed as a Stack Set, with a CloudWatch Rule triggering the function

Summary

Can't confirm completely, but I believe the logger which is created from main.go 's setupLogging function does not get created, and therefore

Hello, first of all thanks for the amazing tool!

So, I got bit by the aforementioned warning and since it's quite elusive, it was kinda hard to debug. Turns out I was trying to return a next() call from an async middleware, because I scanned too quickly past the Promises support part of the docs.

I think adding a quick FAQ item telling users that this warning is related to that part of th

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

Hi,

Is there a guide or step by step how to instruction to deploy this in aws? If not may i suggest to put few lines as in how to get this up and working in aws.

Ok Since I read something about lambda by now I understood few things, I am listing it here so that it might help, someone like me.

Install aws CLI

• Check if the python is already installed by using $ python --version
• Downl

When serving the model locally, a nice swagger documentation page becomes accessible that allows you to send requests to the model by clicking the "Try it out" button.
As part of the swagger specification it is possible to specify the schema the endpoint expects. When doing that, the "Try it out" button will be prefilled with values, so that the API end users can experiment with the endpoint more

The build command in scripts/lambda uses keyword arguments that are inconsistent with the build function in aws_lambda.py
def build(use_requirements, local_package, config_file): aws_lambda.build( CURRENT_DIR, use_requirements=use_requirements, local_package=local_package, config_file=config_file, )
aws_lambda build function signature looks like

The forwarder basically works but I don't know what happens if the lambda fails. It'd be great to get some alert.

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

Currently we inline the Architect logo svg for the init template.
In order to reuse this logo in multiple places it would be ideal to host it.