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

Currently the TLS version defaults to 1.0. I have to manually upgrade it to 1.2. So it would be nice if it could be specifed in the custom

Description

The build process doesn't copy over .so files when building a Python Lambda function.

Steps to reproduce

Install the ptvsd library:

pip install

In README.md there is the following command:

docker run --it  --name tgr -p 5000:5000 -e CLIENT_ID="xxxxxxx" -e CLIENT_SECRET="xxxxxxxxxxxxxxx" -e DEBUG="True" tgr

There is two issues with that:

1. It should be -it, rather than --it, since the first one is invalid
2. You also need to specify -e HOST="0.0.0.0" and -e PORT="5000" in order for the app to start.

Addi

Describe the bug
In https://www.getambassador.io/reference/core/ambassador/#lua-scripts-lua_scripts
the URL for "Envoy Lua filter documentation" leads to a 404. The URL is missing a "/http/" segment in the middle of the path. The correct URL should be:

https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/lua_filter

Docs will render fine locally without layouts/shortcodes/versioned_link_path.html https://github.com/solo-io/hugo-theme-soloio#examples-1 , but may be invalid once published to the live site.

We need some kind of validation to ensure we never publish docs with broken links

The file 'conf/nginx.conf' can be generated automatically before run Apache APISIX.

Implementations: Spring Boot / AWS Lambda Function/API Gateway

Expected behavior
Should process the requests and give response in 30 seconds when lambda is invoked from API Gateway

Actual behavior
Timeout Error for the first call made from API Gateway and gives response for the calls after

How to avoid timeout error on API Gateway and bring response in <10 seconds when using java framew

sls invoke is useful for testing our API one request at a time.

It would be nice to spin up a local version of the API on localhost to enable us to develop our frontend apps against it, and to more easily run integration and E2E tests.

Currently, this excellent plugin creates API Gateway managed cloud front distribution, which is not visible in CloudFront management.

Also, WAF is cannot be assigned to this distribution right now.

https://forums.aws.amazon.com/thread.jspa?threadID=227000

It would be good to have a switch which allows creating customer managed CloudFront distributions (default is API gateway managed)

https://github.com/serverless/components/tree/master/templates

Would allow to get started much faster from an official boilerplate :)