diff --git a/cloud/lambda/lambda-jsonapi.js b/cloud/lambda/lambda-jsonapi.js
index bc6ed2b8f9115c781071b5c7b16827e3c98498ee..90bf51a08e55f5370c6d4ee5865ac224ef096742 100644
--- a/cloud/lambda/lambda-jsonapi.js
+++ b/cloud/lambda/lambda-jsonapi.js
@@ -271,9 +271,7 @@ const patchMethod = (event, context, callback) => {
                   'Id': id
               },
               'ReturnValues': 'ALL_OLD'
-          };
-      const body=event['body-json'];
-  
+          };  
       let dbDelete = (params) => { return dynamo.delete(params).promise() };
       dbDelete(params).then( (data) => {
           if (!data.Attributes) {
@@ -281,7 +279,8 @@ const patchMethod = (event, context, callback) => {
               return;
           }
           console.log(`DELETED ITEM OF TYPE ${type} SUCCESSFULLY WITH id = ${id}`);
-          callback(null, body);
+          const empty = {'data': []};
+          callback(null, empty);
       }).catch( (err) => { 
           console.log(`DELETE ITEM OF TYPE ${type} FAILED FOR id = ${id}, WITH ERROR: ${err}`);
           callback(null, createResponse(500, err));
diff --git a/cloud/lambda/lambda-jsonapi.zip b/cloud/lambda/lambda-jsonapi.zip
index 4c88a99dae208b141ce3294d9ead26ee0d7b52e3..da0dfaa843db5d4a703258544c83ee6185245453 100644
Binary files a/cloud/lambda/lambda-jsonapi.zip and b/cloud/lambda/lambda-jsonapi.zip differ
diff --git a/cloud/terraform/README.md b/cloud/terraform/README.md
index f965987cfa2fb1fd735c7ea4a93260c1da401778..518115d20fb406ad166d89e77948fec405d30744 100644
--- a/cloud/terraform/README.md
+++ b/cloud/terraform/README.md
@@ -14,23 +14,15 @@ AWS JSON API server relies on 3 main components, plus the needed IAM roles :
 - A lambda function in charge of the translation from JSON API format to dynamoDB objects and managing the relationships and the optional parameters provided in the request
 - An API Gateway configured to received the REST HTTP requests and proxying the Lambda
 
+It also create three S3 buckets, one for storing the lambda code (nammed lambda-jsonapi-code-bucket) and the two other for receiving the ‘staging’ and ‘production’ version of the application (respectively nammed ember-aws-ehipster-staging and ember-aws-ehipster-production)
+
 Several Terraform files are available, each one creating the needed component and their relationships with each other.
 
 Installation
 ------------------------------------------------------------------------------
 
-The lambda code needs to be stored in a S3 bucket before running the Terraform scripts.
-The script is available in the cloud/lambda directory of this project.
-The following operations need to be performed (adapting the region you are using):
-
-```
-cp ../lambda/lambda-jsonapi.js .
-zip lambda-jsonapi.zip lambda-jsonapi.js
-aws s3api create-bucket --bucket=lambda-jsonapi-code-bucket --region=us-east-1
-aws s3 cp lambda-jsonapi.zip s3://lambda-jsonapi-code-bucket/v1.0.0/lambda-jsonapi.zip
-```
 One this is done, simply run the terraform script :
 ```
+terraform init
 terraform apply -var bucket_name=<bucket name for static web site>
-```
-For a strange reason I don't understand, the first time you run the terraform command, the mapping for the integration response fails. You have to run the command again to have your complete setup.
\ No newline at end of file
+```
\ No newline at end of file