Serverless create snspolicy fails with invalid parameter












0















Here is the error.



An error occurred: SNSTopicPolicy - Invalid parameter:
Policy Error: null (Service: AmazonSNS;
Status Code: 400; Error Code: InvalidParameter;
Request ID: 38a567df-2cff-50bf-8f0e-33a91775cc6e).


I cannot find a place to look into logs to tell me what parameter is missing.?.? I'm pretty sure I have everything that is required. I'm using this site and their api pages.



SNSTopic:
Type: AWS::SNS::Topic
Properties:
DisplayName: Aura main Topic
TopicName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.auraSnsTopicName}

SNSTopicPolicy:
Type: AWS::SNS::TopicPolicy
Properties:
PolicyDocument:
Id: auraAllowSQSsendrobelrobel
Statement:
-
Effect: Allow
Action:
- sns: Publish
Resource: { "Fn::GetAtt":["SQSQueue" ,"Arn"]}
Principle:
AWS: "*"
Topics:
- { "Ref": "SNSTopic" }


SQSQueue:
Type: AWS::SQS::Queue
Properties:
QueueName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.eeegPagesQueueName}
RedrivePolicy:
deadLetterTargetArn: {"Fn::GetAtt" : [ "SQSQueueDLQ", "Arn" ]}
maxReceiveCount: 2


SQSQueuePolicy:
Type: AWS::SQS::QueuePolicy
Properties:
PolicyDocument:
Id: allowSNSSourceAndLambdaTrigger
Statement:
-
Effect: Allow
Action:
- SQS:ReceiveMessage
- SQS:SendMessage
- SQS:ChangeMessageVisibility
- SQS:ListDeadLetterSourceQueues
- SQS:GetQueueUrl
# - lambda:CreateEventSourceMapping
# - lambda:ListEventSourceMappings
# - lambda:ListFunction
Resource: {"Ref": "SNSTopic"}
Queues:
- { "Ref": "SQSQueue" }


I have an SQS Policy statement that is working just fine.



  Your Environment Information ----------------------------
OS: Mac darwin
Node Version: 8.12.0
Serverless Version: 1.32.0









share|improve this question























  • it might be the wrong indentation you have there, check this article (the yaml part) and ident accordingly: docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/…

    – AlexK
    Nov 26 '18 at 20:31











  • Thanks @alexk Indentation is fine. I'm using Serverless and this was a subset of the whole doc.

    – Robel Robel Lingstuyl
    Nov 26 '18 at 21:47











  • Cool, glad you got your answer. I have encountered problem with copying files from Windows to Linux and indentation got messed up hence my guess

    – AlexK
    Nov 26 '18 at 21:49
















0















Here is the error.



An error occurred: SNSTopicPolicy - Invalid parameter:
Policy Error: null (Service: AmazonSNS;
Status Code: 400; Error Code: InvalidParameter;
Request ID: 38a567df-2cff-50bf-8f0e-33a91775cc6e).


I cannot find a place to look into logs to tell me what parameter is missing.?.? I'm pretty sure I have everything that is required. I'm using this site and their api pages.



SNSTopic:
Type: AWS::SNS::Topic
Properties:
DisplayName: Aura main Topic
TopicName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.auraSnsTopicName}

SNSTopicPolicy:
Type: AWS::SNS::TopicPolicy
Properties:
PolicyDocument:
Id: auraAllowSQSsendrobelrobel
Statement:
-
Effect: Allow
Action:
- sns: Publish
Resource: { "Fn::GetAtt":["SQSQueue" ,"Arn"]}
Principle:
AWS: "*"
Topics:
- { "Ref": "SNSTopic" }


SQSQueue:
Type: AWS::SQS::Queue
Properties:
QueueName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.eeegPagesQueueName}
RedrivePolicy:
deadLetterTargetArn: {"Fn::GetAtt" : [ "SQSQueueDLQ", "Arn" ]}
maxReceiveCount: 2


SQSQueuePolicy:
Type: AWS::SQS::QueuePolicy
Properties:
PolicyDocument:
Id: allowSNSSourceAndLambdaTrigger
Statement:
-
Effect: Allow
Action:
- SQS:ReceiveMessage
- SQS:SendMessage
- SQS:ChangeMessageVisibility
- SQS:ListDeadLetterSourceQueues
- SQS:GetQueueUrl
# - lambda:CreateEventSourceMapping
# - lambda:ListEventSourceMappings
# - lambda:ListFunction
Resource: {"Ref": "SNSTopic"}
Queues:
- { "Ref": "SQSQueue" }


I have an SQS Policy statement that is working just fine.



  Your Environment Information ----------------------------
OS: Mac darwin
Node Version: 8.12.0
Serverless Version: 1.32.0









share|improve this question























  • it might be the wrong indentation you have there, check this article (the yaml part) and ident accordingly: docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/…

    – AlexK
    Nov 26 '18 at 20:31











  • Thanks @alexk Indentation is fine. I'm using Serverless and this was a subset of the whole doc.

    – Robel Robel Lingstuyl
    Nov 26 '18 at 21:47











  • Cool, glad you got your answer. I have encountered problem with copying files from Windows to Linux and indentation got messed up hence my guess

    – AlexK
    Nov 26 '18 at 21:49














0












0








0








Here is the error.



An error occurred: SNSTopicPolicy - Invalid parameter:
Policy Error: null (Service: AmazonSNS;
Status Code: 400; Error Code: InvalidParameter;
Request ID: 38a567df-2cff-50bf-8f0e-33a91775cc6e).


I cannot find a place to look into logs to tell me what parameter is missing.?.? I'm pretty sure I have everything that is required. I'm using this site and their api pages.



SNSTopic:
Type: AWS::SNS::Topic
Properties:
DisplayName: Aura main Topic
TopicName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.auraSnsTopicName}

SNSTopicPolicy:
Type: AWS::SNS::TopicPolicy
Properties:
PolicyDocument:
Id: auraAllowSQSsendrobelrobel
Statement:
-
Effect: Allow
Action:
- sns: Publish
Resource: { "Fn::GetAtt":["SQSQueue" ,"Arn"]}
Principle:
AWS: "*"
Topics:
- { "Ref": "SNSTopic" }


SQSQueue:
Type: AWS::SQS::Queue
Properties:
QueueName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.eeegPagesQueueName}
RedrivePolicy:
deadLetterTargetArn: {"Fn::GetAtt" : [ "SQSQueueDLQ", "Arn" ]}
maxReceiveCount: 2


SQSQueuePolicy:
Type: AWS::SQS::QueuePolicy
Properties:
PolicyDocument:
Id: allowSNSSourceAndLambdaTrigger
Statement:
-
Effect: Allow
Action:
- SQS:ReceiveMessage
- SQS:SendMessage
- SQS:ChangeMessageVisibility
- SQS:ListDeadLetterSourceQueues
- SQS:GetQueueUrl
# - lambda:CreateEventSourceMapping
# - lambda:ListEventSourceMappings
# - lambda:ListFunction
Resource: {"Ref": "SNSTopic"}
Queues:
- { "Ref": "SQSQueue" }


I have an SQS Policy statement that is working just fine.



  Your Environment Information ----------------------------
OS: Mac darwin
Node Version: 8.12.0
Serverless Version: 1.32.0









share|improve this question














Here is the error.



An error occurred: SNSTopicPolicy - Invalid parameter:
Policy Error: null (Service: AmazonSNS;
Status Code: 400; Error Code: InvalidParameter;
Request ID: 38a567df-2cff-50bf-8f0e-33a91775cc6e).


I cannot find a place to look into logs to tell me what parameter is missing.?.? I'm pretty sure I have everything that is required. I'm using this site and their api pages.



SNSTopic:
Type: AWS::SNS::Topic
Properties:
DisplayName: Aura main Topic
TopicName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.auraSnsTopicName}

SNSTopicPolicy:
Type: AWS::SNS::TopicPolicy
Properties:
PolicyDocument:
Id: auraAllowSQSsendrobelrobel
Statement:
-
Effect: Allow
Action:
- sns: Publish
Resource: { "Fn::GetAtt":["SQSQueue" ,"Arn"]}
Principle:
AWS: "*"
Topics:
- { "Ref": "SNSTopic" }


SQSQueue:
Type: AWS::SQS::Queue
Properties:
QueueName: ${file(./env.yml):${opt:stage, self:provider.stage}.env.eeegPagesQueueName}
RedrivePolicy:
deadLetterTargetArn: {"Fn::GetAtt" : [ "SQSQueueDLQ", "Arn" ]}
maxReceiveCount: 2


SQSQueuePolicy:
Type: AWS::SQS::QueuePolicy
Properties:
PolicyDocument:
Id: allowSNSSourceAndLambdaTrigger
Statement:
-
Effect: Allow
Action:
- SQS:ReceiveMessage
- SQS:SendMessage
- SQS:ChangeMessageVisibility
- SQS:ListDeadLetterSourceQueues
- SQS:GetQueueUrl
# - lambda:CreateEventSourceMapping
# - lambda:ListEventSourceMappings
# - lambda:ListFunction
Resource: {"Ref": "SNSTopic"}
Queues:
- { "Ref": "SQSQueue" }


I have an SQS Policy statement that is working just fine.



  Your Environment Information ----------------------------
OS: Mac darwin
Node Version: 8.12.0
Serverless Version: 1.32.0






amazon-web-services amazon-sns serverless






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 26 '18 at 18:35









Robel Robel LingstuylRobel Robel Lingstuyl

17512




17512













  • it might be the wrong indentation you have there, check this article (the yaml part) and ident accordingly: docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/…

    – AlexK
    Nov 26 '18 at 20:31











  • Thanks @alexk Indentation is fine. I'm using Serverless and this was a subset of the whole doc.

    – Robel Robel Lingstuyl
    Nov 26 '18 at 21:47











  • Cool, glad you got your answer. I have encountered problem with copying files from Windows to Linux and indentation got messed up hence my guess

    – AlexK
    Nov 26 '18 at 21:49



















  • it might be the wrong indentation you have there, check this article (the yaml part) and ident accordingly: docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/…

    – AlexK
    Nov 26 '18 at 20:31











  • Thanks @alexk Indentation is fine. I'm using Serverless and this was a subset of the whole doc.

    – Robel Robel Lingstuyl
    Nov 26 '18 at 21:47











  • Cool, glad you got your answer. I have encountered problem with copying files from Windows to Linux and indentation got messed up hence my guess

    – AlexK
    Nov 26 '18 at 21:49

















it might be the wrong indentation you have there, check this article (the yaml part) and ident accordingly: docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/…

– AlexK
Nov 26 '18 at 20:31





it might be the wrong indentation you have there, check this article (the yaml part) and ident accordingly: docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/…

– AlexK
Nov 26 '18 at 20:31













Thanks @alexk Indentation is fine. I'm using Serverless and this was a subset of the whole doc.

– Robel Robel Lingstuyl
Nov 26 '18 at 21:47





Thanks @alexk Indentation is fine. I'm using Serverless and this was a subset of the whole doc.

– Robel Robel Lingstuyl
Nov 26 '18 at 21:47













Cool, glad you got your answer. I have encountered problem with copying files from Windows to Linux and indentation got messed up hence my guess

– AlexK
Nov 26 '18 at 21:49





Cool, glad you got your answer. I have encountered problem with copying files from Windows to Linux and indentation got messed up hence my guess

– AlexK
Nov 26 '18 at 21:49












1 Answer
1






active

oldest

votes


















0














Turns out you need spelling is important and also the AWS sub object was not needed.
Principal: "*"



Working Policy below:



SNSTopicPolicy:
Type: AWS::SNS::TopicPolicy
Properties:
PolicyDocument:
Statement:
- Sid: auraAllowSQSPublish
Effect: Allow
Principal: "*"
Action: "sns:Publish"
Resource: { "Ref": "SNSTopic" }
Topics:
- { "Ref": "SNSTopic" }





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%2f53487115%2fserverless-create-snspolicy-fails-with-invalid-parameter%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









    0














    Turns out you need spelling is important and also the AWS sub object was not needed.
    Principal: "*"



    Working Policy below:



    SNSTopicPolicy:
    Type: AWS::SNS::TopicPolicy
    Properties:
    PolicyDocument:
    Statement:
    - Sid: auraAllowSQSPublish
    Effect: Allow
    Principal: "*"
    Action: "sns:Publish"
    Resource: { "Ref": "SNSTopic" }
    Topics:
    - { "Ref": "SNSTopic" }





    share|improve this answer




























      0














      Turns out you need spelling is important and also the AWS sub object was not needed.
      Principal: "*"



      Working Policy below:



      SNSTopicPolicy:
      Type: AWS::SNS::TopicPolicy
      Properties:
      PolicyDocument:
      Statement:
      - Sid: auraAllowSQSPublish
      Effect: Allow
      Principal: "*"
      Action: "sns:Publish"
      Resource: { "Ref": "SNSTopic" }
      Topics:
      - { "Ref": "SNSTopic" }





      share|improve this answer


























        0












        0








        0







        Turns out you need spelling is important and also the AWS sub object was not needed.
        Principal: "*"



        Working Policy below:



        SNSTopicPolicy:
        Type: AWS::SNS::TopicPolicy
        Properties:
        PolicyDocument:
        Statement:
        - Sid: auraAllowSQSPublish
        Effect: Allow
        Principal: "*"
        Action: "sns:Publish"
        Resource: { "Ref": "SNSTopic" }
        Topics:
        - { "Ref": "SNSTopic" }





        share|improve this answer













        Turns out you need spelling is important and also the AWS sub object was not needed.
        Principal: "*"



        Working Policy below:



        SNSTopicPolicy:
        Type: AWS::SNS::TopicPolicy
        Properties:
        PolicyDocument:
        Statement:
        - Sid: auraAllowSQSPublish
        Effect: Allow
        Principal: "*"
        Action: "sns:Publish"
        Resource: { "Ref": "SNSTopic" }
        Topics:
        - { "Ref": "SNSTopic" }






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 26 '18 at 21:46









        Robel Robel LingstuylRobel Robel Lingstuyl

        17512




        17512
































            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%2f53487115%2fserverless-create-snspolicy-fails-with-invalid-parameter%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

            Contact image not getting when fetch all contact list from iPhone by CNContact

            count number of partitions of a set with n elements into k subsets

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks