@sapessi Stefano, I was actually working in the AWS API Gateway and writing docs to instruct people on how to build and use the java swagger importer when today's API Gateway UI update went out! I noticed the new option and stopped my complicated documentation to instead just point people at the new feature. Thanks! On another note, I watched your 2015 ReInvent talk on API Gateway (the one with the Pet Store) last week. I'm confused about one thing and was wondering if you could point me to something that would help me understand. When binding an Integration Request to a Lambda function in the AWS web console, when you select "Lambda Function" as the Integration type, the UI pops up a window confirming that you want to grant API Gateway access to invoke your Lambda function. Where is this grant of access recorded? I've looked to see if an IAM Role is created which allows assumption by API Gateway and has permission to invoke the Lambda function but find nothing. I've looked through the Get and Describe calls in the API Gateway to see if there's some kind of policy attached to api, the resource, the method, etc. but haven't found anything. In reading the docs ( http://docs.aws.amazon.com/apigateway/latest/developerguide/integrating-api-with-aws-services-lambda.html#api-as-lambda-proxy-expose-get-method-with-query-strings-to-call-lambda-function ) they talk about using the "AWS Service Proxy" Integration type and there you can define an Execution role, but I can't find anything the explains what's going on when you choose "Lambda function" as the integration type. Any help would be appreciated, thanks!