Skip to content

Instantly share code, notes, and snippets.

@undefobj
Last active August 17, 2022 18:28
Show Gist options
  • Save undefobj/abb8a42a5c59606fb4126f47a383c48a to your computer and use it in GitHub Desktop.
Save undefobj/abb8a42a5c59606fb4126f47a383c48a to your computer and use it in GitHub Desktop.
Calling AppSync from Lambda
const https = require('https');
const AWS = require("aws-sdk");
const urlParse = require("url").URL;
const appsyncUrl = process.env.API_BACKENDGRAPHQL_GRAPHQLAPIENDPOINTOUTPUT;
const region = process.env.REGION;
const endpoint = new urlParse(appsyncUrl).hostname.toString();
const graphqlQuery = require('./query.js').mutation;
const apiKey = process.env.API_KEY;
exports.handler = async (event) => {
const req = new AWS.HttpRequest(appsyncUrl, region);
const item = {
input: {
title: "Lambda Item",
Content: "Item Generated from Lambda"
}
};
req.method = "POST";
req.headers.host = endpoint;
req.headers["Content-Type"] = "application/json";
req.body = JSON.stringify({
query: graphqlQuery,
operationName: "createLambdaGraphQL",
variables: item
});
if (apiKey) {
req.headers["x-api-key"] = apiKey;
} else {
const signer = new AWS.Signers.V4(req, "appsync", true);
signer.addAuthorization(AWS.config.credentials, AWS.util.date.getDate());
}
const data = await new Promise((resolve, reject) => {
const httpRequest = https.request({ ...req, host: endpoint }, (result) => {
result.on('data', (data) => {
resolve(JSON.parse(data.toString()));
});
});
httpRequest.write(req.body);
httpRequest.end();
});
return {
statusCode: 200,
body: data
};
};
module.exports = {
mutation: `mutation createLambdaGraphQL($input: CreateLambdaGraphQLInput!) {
createLambdaGraphQL(input: $input) {
id
title
Content
}
}
`
}
@janhesters
Copy link

BTW, line 40 (signer.addAuthorization(AWS.config.credentials, AWS.util.date.getDate());) always throws TypeError: Data must be a string or a buffer for me. Do you have any clue about what's going wrong?

Full stack trace:

2019-06-25T13:26:54.957Z	6527b6ef-df88-4936-9050-ff8e176ab8ea	TypeError: Data must be a string or a buffer
at Hmac.update (crypto.js:99:16)
at Object.hmac (/var/task/node_modules/aws-sdk/lib/util.js:423:50)
at Object.getSigningKey (/var/task/node_modules/aws-sdk/lib/signers/v4_credentials.js:74:35)
at V4.signature (/var/task/node_modules/aws-sdk/lib/signers/v4.js:98:36)
at V4.authorization (/var/task/node_modules/aws-sdk/lib/signers/v4.js:93:36)
at V4.addAuthorization (/var/task/node_modules/aws-sdk/lib/signers/v4.js:35:12)
at /var/task/app.js:72:12
at Layer.handle [as handle_request] (/var/task/node_modules/express/lib/router/layer.js:95:5)
at next (/var/task/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/var/task/node_modules/express/lib/router/route.js:112:3)

@abubakar491
Copy link

@janhesters did you find the cause of this issue or any work around.
Facing same issue.

@janhesters
Copy link

@abukabar491 I did. But I don't remember what fixed it. I think I started working backwards. I copy and pasted the example verbatim and then began changing the code to my needs after I made sure the verbatim code worked.

I ended up going with a slightly different approach as described in my article "How To Use AWS AppSync in Lambda Functions". Hope this helps.

@undefobj
Copy link
Author

undefobj commented Jul 9, 2019

@janhesters I made a few updates above. Remember this was a gist as a quick sample, so yes most likely the credentials aren't needed I just need to double check the default Lambda SDK import is setting credentials. The host endpoint is needed as a signer param but I moved it to use a spread operator for readability. I'm not sure why you're seeing the error on line 40, maybe it was a typo or something copied/pasted wrong? It also might be that you didn't have the environment variables set for the region or graphql endpoint.

@undefobj
Copy link
Author

Confirmed - The latest code above works. BTW I also verified I think the reason you were getting that "Data must be string or buffer" was because you didn't have the env vars in your lambda for the endpoint and region. If you didn't use the CLI to create your function after creating an AppSync backend, you would need to manually create them.

@bjq-dev
Copy link

bjq-dev commented Jul 25, 2019

the line #5:
const region = process.env.REGION;

should be:
const region = process.env.AWS_REGION;

Thanks for this gist.

@jobyjohnkj
Copy link

Thanks a lot for this gist!

@staticinteger
Copy link

staticinteger commented Jul 29, 2020

Just FYI, this was taken from the official AWS Amplify docs here: https://docs.amplify.aws/cli/function#signing-a-request-from-lambda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment