Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

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

Along with the General Guides, it might be helpful to add a niche guide section, which is broken down by AWS service. Happy to issue a PR with some quality tutorials as an example.

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

Hi,

It would great if there was documentation on the steps taken by sam build. My concrete use case is that I'd like to know how it finds and installs packages for Python Lambda functions so I can figure out the best way to structure my project. More specifically, does it just do a pip install -r and copies the source files or does it build my package with setuptools?

Thanks!

(Edit

this will very quickly get out of hand if we allow it, i realize we don't have principles written down anywhere but to date one of them has been that binaries 'just work' without having to do any configuration. currently a user must set FN_MAX_REQUEST_SIZE, FN_MAX_RESPONSE_SIZE -- neither of these should be required to run.

test case:

cd tests/fn-system-tests/
go test -v

this

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

As a new custodian user, I'm trying to understand the usage of variables in policies. There seems to be multiple types of variables.

A non-exhaustive list for a beginner can be:

• vars in a policy yaml
• [standard runtime variables for in

When following the "Connect app..." workflow in the Amplify Console with a GitHub.com repository, it's clear that the Amplify Console requires more than just read only access to the user's GitHub account yet the Amplify console sets conflicting expectations and the workshop module's README.md does not set the degree of access expectations with the user so that the user can make a more informed dec

This is:

• Feature request

Expected Behavior

In order to make DX better, let's automatically execute the following check for our users, and throw a clear error message if the credentials are incorrect / missing.

While trying to fix iron-io/functions#559, i've faced with problem: can't mount volume from through Docker API (basically, inside container mounting folder is empty, see [1] and [2]. It is worth having a doc that will tell workaround steps for

If you'd like to have your company represented and are using Komiser please give formal written permission below via a comment and email to [email protected].

We will need a URL to a svg or png logo, a text title and a company URL.

Due to the security repercussions, of deploying this incorrectly, Are they any docs that go into more detail on a proper installation?

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 ---------------

Background

Having added some streamalert-cli commands, the documentation on the command line via -h and ReadTheDocs varies and is laborious to maintain.

Description

A fantastic tool, to reduce this headache is sphinx-argparse. In short, it adds the ability to take an argparse parser and create documentation from the descriptions and everything else in the parser. A live e

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

Checklist

• [X ] Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
• [ X] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a questi

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):