Aws-sam-cli: Support for Lambda integration
The README mentions aws-sam-local uses Lambda proxy integration by default. Is there a way to tell aws-sam-local to use Lambda integration instead?
c11v
All 5 comments
No, SAM defaults to proxy integration when you define the APIs. We are keeping the behavior consistent here with SAM Local.
sanathkr
on 11 Aug 2017
I switched to lambda proxy integration. Lambda integration not really needed.
c11v
on 18 Aug 2017
With SAM, it is possible to define your Api configuration using AWS::Serverless::Api. When you then define x-amazon-apigateway-integration, you can choose to have type "aws" or "aws_proxy". Shouldn't this "aws" type option be supported by sam-local? Then it would make sense to support lambda integration.
alexiaallanic-myob
on 9 Nov 2017
I agree with @alexiaallanic-myob lambda integration should also be supported.
dgoradia
on 2 Mar 2018
Will this never be supported? If not that means I can _only_ use the proxy integration with SAM.
Otherwise whats the point if I can't test locally the same as the deployed version?
red8888
on 18 Sep 2018
Related issues
ericallam
路
24Comments
burck1
路
45Comments
alanchavez88
路
53Comments
kyeljmd
路
31Comments
uvaisTrivecta
路
40Comments
Most helpful comment
With SAM, it is possible to define your Api configuration using AWS::Serverless::Api. When you then define x-amazon-apigateway-integration, you can choose to have type "aws" or "aws_proxy". Shouldn't this "aws" type option be supported by sam-local? Then it would make sense to support lambda integration.