# Meaning of warning: You're using the LAMBDA-PROXY in combination with request / response configuration

**URL:** <https://forum.serverless.com/t/meaning-of-warning-youre-using-the-lambda-proxy-in-combination-with-request-response-configuration/1041>\
**Category:** Serverless Framework\
**Created:** [January 2, 2017, 4:44pm UTC](https://forum.serverless.com/t/meaning-of-warning-youre-using-the-lambda-proxy-in-combination-with-request-response-configuration/1041 "2017-01-02T16:44:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ashishtilara](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/ashishtilara/32/378_2.png) [@ashishtilara](https://forum.serverless.com/u/ashishtilara)\
**Post date:** [January 2, 2017, 4:44pm UTC](https://forum.serverless.com/t/meaning-of-warning-youre-using-the-lambda-proxy-in-combination-with-request-response-configuration/1041/1 "2017-01-02T16:44:45Z")

</div>

I am new to Serverless, and i have following

```
handler: handler.hello
events:
  - http:
      path: v1/{id}
      method: post
      cors: true
      integration: lambda-proxy
      request:
          parameters:
              paths:
                id: true

```

And I am seeing following message so just wondering what does it mean.

```
Serverless: Warning! You're using the LAMBDA-PROXY in combination with request / response configuration in your function "hello". This configuration will be ignored during deployment.

```

Appreciate any guidance.

cheers

---

<div class="post-metadata">

**Author:** ![bbilger](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/bbilger/32/1066_2.png) [@bbilger](https://forum.serverless.com/u/bbilger)\
**Post date:** [January 2, 2017, 6:34pm UTC](https://forum.serverless.com/t/meaning-of-warning-youre-using-the-lambda-proxy-in-combination-with-request-response-configuration/1041/2 "2017-01-02T18:34:05Z")

</div>

there are two types of integrations:

1. lambda
2. lambda-proxy (default and recommended)

see: [https://serverless.com/framework/docs/providers/aws/events/apigateway](https://serverless.com/framework/docs/providers/aws/events/apigateway)

The difference is that with _lambda_ you have to model your event object (request) and you are also quite limited regarding your response (dynamic headers, status codes, etc.)

With _lambda-proxy_ a default event model is used which looks like this: [https://github.com/bbilger/jrestless/tree/master/aws/gateway/jrestless-aws-gateway-handler#request-schema](https://github.com/bbilger/jrestless/tree/master/aws/gateway/jrestless-aws-gateway-handler#request-schema) and you also have more freedom regarding responses but your response object must follow the schema: [https://github.com/bbilger/jrestless/tree/master/aws/gateway/jrestless-aws-gateway-handler#response-schema](https://github.com/bbilger/jrestless/tree/master/aws/gateway/jrestless-aws-gateway-handler#response-schema)

To make it short: either use _lambda_ and “model” your request via the request parameter in your serverless.yml, or use _lambda-proxy_ without the request parameter in your serverless.yml.

Internally serverless removes the request parameter when you use _lambda-proxy_, thus the warning.