AWS Lambda struggling to get ListFunctions working












0















I'm struggling to get any sort of response from ListFunctions that isn't null. I have 3 functions in a single region and have played around with the params and AWS.config.region a fair bit. I'm consistently getting null as a return and in my console logs, I don't get anything back. Any help would be greatly appreciated!



let AWS = require('aws-sdk');
//AWS.config.region = 'ca-central-1';
let lambda = new AWS.Lambda({ "apiVersion": "2015-03-31" });

module.exports.handler = async (event, context) => {
let params = {
//MasterRegion: 'ALL',
//FunctionVersion: 'ALL',
MaxItems: 10
};

lambda.listFunctions(params, function(err,data) {
if(err){
console.log(err);
}
else {
console.log(data);
}
context.done(null, "function finished");
}
}


serverless.yml changes



provider:
name: aws
runtime: nodejs8.10
profile: [PROFILE_NAME]
region: [ca-central-1]
iamRoleStatements:
- Effect: "Allow"
Action:
- "lambda:*"
Resource:
- "*"









share|improve this question























  • Try making your function not async. When it's marked as async and the function returns it returns that values. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.

    – cementblocks
    Nov 21 '18 at 20:42











  • And there it is..... thank you kind sir.

    – user3026715
    Nov 21 '18 at 20:49
















0















I'm struggling to get any sort of response from ListFunctions that isn't null. I have 3 functions in a single region and have played around with the params and AWS.config.region a fair bit. I'm consistently getting null as a return and in my console logs, I don't get anything back. Any help would be greatly appreciated!



let AWS = require('aws-sdk');
//AWS.config.region = 'ca-central-1';
let lambda = new AWS.Lambda({ "apiVersion": "2015-03-31" });

module.exports.handler = async (event, context) => {
let params = {
//MasterRegion: 'ALL',
//FunctionVersion: 'ALL',
MaxItems: 10
};

lambda.listFunctions(params, function(err,data) {
if(err){
console.log(err);
}
else {
console.log(data);
}
context.done(null, "function finished");
}
}


serverless.yml changes



provider:
name: aws
runtime: nodejs8.10
profile: [PROFILE_NAME]
region: [ca-central-1]
iamRoleStatements:
- Effect: "Allow"
Action:
- "lambda:*"
Resource:
- "*"









share|improve this question























  • Try making your function not async. When it's marked as async and the function returns it returns that values. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.

    – cementblocks
    Nov 21 '18 at 20:42











  • And there it is..... thank you kind sir.

    – user3026715
    Nov 21 '18 at 20:49














0












0








0








I'm struggling to get any sort of response from ListFunctions that isn't null. I have 3 functions in a single region and have played around with the params and AWS.config.region a fair bit. I'm consistently getting null as a return and in my console logs, I don't get anything back. Any help would be greatly appreciated!



let AWS = require('aws-sdk');
//AWS.config.region = 'ca-central-1';
let lambda = new AWS.Lambda({ "apiVersion": "2015-03-31" });

module.exports.handler = async (event, context) => {
let params = {
//MasterRegion: 'ALL',
//FunctionVersion: 'ALL',
MaxItems: 10
};

lambda.listFunctions(params, function(err,data) {
if(err){
console.log(err);
}
else {
console.log(data);
}
context.done(null, "function finished");
}
}


serverless.yml changes



provider:
name: aws
runtime: nodejs8.10
profile: [PROFILE_NAME]
region: [ca-central-1]
iamRoleStatements:
- Effect: "Allow"
Action:
- "lambda:*"
Resource:
- "*"









share|improve this question














I'm struggling to get any sort of response from ListFunctions that isn't null. I have 3 functions in a single region and have played around with the params and AWS.config.region a fair bit. I'm consistently getting null as a return and in my console logs, I don't get anything back. Any help would be greatly appreciated!



let AWS = require('aws-sdk');
//AWS.config.region = 'ca-central-1';
let lambda = new AWS.Lambda({ "apiVersion": "2015-03-31" });

module.exports.handler = async (event, context) => {
let params = {
//MasterRegion: 'ALL',
//FunctionVersion: 'ALL',
MaxItems: 10
};

lambda.listFunctions(params, function(err,data) {
if(err){
console.log(err);
}
else {
console.log(data);
}
context.done(null, "function finished");
}
}


serverless.yml changes



provider:
name: aws
runtime: nodejs8.10
profile: [PROFILE_NAME]
region: [ca-central-1]
iamRoleStatements:
- Effect: "Allow"
Action:
- "lambda:*"
Resource:
- "*"






node.js amazon-web-services lambda aws-lambda amazon-iam






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 21 '18 at 20:03









user3026715user3026715

268




268













  • Try making your function not async. When it's marked as async and the function returns it returns that values. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.

    – cementblocks
    Nov 21 '18 at 20:42











  • And there it is..... thank you kind sir.

    – user3026715
    Nov 21 '18 at 20:49



















  • Try making your function not async. When it's marked as async and the function returns it returns that values. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.

    – cementblocks
    Nov 21 '18 at 20:42











  • And there it is..... thank you kind sir.

    – user3026715
    Nov 21 '18 at 20:49

















Try making your function not async. When it's marked as async and the function returns it returns that values. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.

– cementblocks
Nov 21 '18 at 20:42





Try making your function not async. When it's marked as async and the function returns it returns that values. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.

– cementblocks
Nov 21 '18 at 20:42













And there it is..... thank you kind sir.

– user3026715
Nov 21 '18 at 20:49





And there it is..... thank you kind sir.

– user3026715
Nov 21 '18 at 20:49












1 Answer
1






active

oldest

votes


















1














Make your function not be async.
When it's marked as async and the handler function returns, lambda returns that value. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.



You can also switch from using callbacks



module.exports.handler = async (event, context) => {
let params = {
//MasterRegion: 'ALL',
//FunctionVersion: 'ALL',
MaxItems: 10
};

try {
let result = await lambda.listFunctions(params).promise() {
console.log(result);
} catch (err) {
console.log(err);
throw err; // this try catch isn't really necessary
}
return "function finished";
}





share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419706%2faws-lambda-struggling-to-get-listfunctions-working%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Make your function not be async.
    When it's marked as async and the handler function returns, lambda returns that value. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.



    You can also switch from using callbacks



    module.exports.handler = async (event, context) => {
    let params = {
    //MasterRegion: 'ALL',
    //FunctionVersion: 'ALL',
    MaxItems: 10
    };

    try {
    let result = await lambda.listFunctions(params).promise() {
    console.log(result);
    } catch (err) {
    console.log(err);
    throw err; // this try catch isn't really necessary
    }
    return "function finished";
    }





    share|improve this answer




























      1














      Make your function not be async.
      When it's marked as async and the handler function returns, lambda returns that value. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.



      You can also switch from using callbacks



      module.exports.handler = async (event, context) => {
      let params = {
      //MasterRegion: 'ALL',
      //FunctionVersion: 'ALL',
      MaxItems: 10
      };

      try {
      let result = await lambda.listFunctions(params).promise() {
      console.log(result);
      } catch (err) {
      console.log(err);
      throw err; // this try catch isn't really necessary
      }
      return "function finished";
      }





      share|improve this answer


























        1












        1








        1







        Make your function not be async.
        When it's marked as async and the handler function returns, lambda returns that value. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.



        You can also switch from using callbacks



        module.exports.handler = async (event, context) => {
        let params = {
        //MasterRegion: 'ALL',
        //FunctionVersion: 'ALL',
        MaxItems: 10
        };

        try {
        let result = await lambda.listFunctions(params).promise() {
        console.log(result);
        } catch (err) {
        console.log(err);
        throw err; // this try catch isn't really necessary
        }
        return "function finished";
        }





        share|improve this answer













        Make your function not be async.
        When it's marked as async and the handler function returns, lambda returns that value. You don't have an explicit return but nodejs returns undefined if a function ends without an explicit return value.



        You can also switch from using callbacks



        module.exports.handler = async (event, context) => {
        let params = {
        //MasterRegion: 'ALL',
        //FunctionVersion: 'ALL',
        MaxItems: 10
        };

        try {
        let result = await lambda.listFunctions(params).promise() {
        console.log(result);
        } catch (err) {
        console.log(err);
        throw err; // this try catch isn't really necessary
        }
        return "function finished";
        }






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 21 '18 at 21:21









        cementblockscementblocks

        1,899815




        1,899815
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419706%2faws-lambda-struggling-to-get-listfunctions-working%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to change which sound is reproduced for terminal bell?

            Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents

            Can I use Tabulator js library in my java Spring + Thymeleaf project?