-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathlambda_ngx_proxy.conf
26 lines (20 loc) · 1.17 KB
/
lambda_ngx_proxy.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
# Don't allow any headers from the client to avoid messing with Lambda at all.
proxy_pass_request_headers off;
# Enable passing of the server name through TLS Server Name Indication extension.
proxy_ssl_server_name on;
proxy_ssl_name $lambda_host;
# HTTP signed headers to include in the AWS signature.
proxy_set_header x-amz-date $awsDate;
proxy_set_header x-amz-content-sha256 $awsPayloadHash;
proxy_set_header x-amz-security-token $awsSessionToken;
# Use keep alive connections to improve performance.
proxy_http_version 1.1;
proxy_set_header Connection '';
# We strip off all of the AWS specific headers from the server so that there is
# nothing identifying the object as having originated in the Lambda.
js_header_filter lambdagateway.editHeaders;
# Comment out to catch all errors from Lambda and sanitize them so that the user
# can't gain intelligence about the Lambda being proxied.
#proxy_intercept_errors on;
# Comment out to receive the error messages returned by Lambda
#error_page 400 401 402 403 405 406 407 408 409 410 411 412 413 414 415 416 417 418 420 422 423 424 426 428 429 431 444 449 450 451 500 501 502 503 504 505 506 507 508 509 510 511 =404 @error404;