Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: AWS::Serverless::Queue #1571

Closed
timoschilling opened this issue Apr 23, 2020 · 0 comments
Closed

Proposal: AWS::Serverless::Queue #1571

timoschilling opened this issue Apr 23, 2020 · 0 comments
Labels
area/new-resource Label for new resources being asked/proposed maintainer/need-response type/feature

Comments

@timoschilling
Copy link
Contributor

timoschilling commented Apr 23, 2020

Description:

Setting up an SQS Queue is sometimes more complicated than it needs to be.
Setting up an Queue should be done in the same DRY way it works for Lambdas.

Before example:

  Queue:
    Type: AWS::SQS::Queue
    Properties:
      RedrivePolicy:
        deadLetterTargetArn: !GetAtt DeadLetterQueue.Arn
        maxReceiveCount: 5

  DeadLetterQueue:
    Type: AWS::SQS::Queue

  QueuePolicy:
    Type: AWS::SQS::QueuePolicy
    Properties:
      Queues:
        - !Ref Queue
      PolicyDocument:
        Version: 2012-10-17
        Statement:
          - Effect: Allow
            Principal:
              AWS: '*'
            Action: SQS:SendMessage
            Resource: !GetAtt Queue.Arn
            Condition:
              ArnEquals:
                aws:SourceArn:
                  - !Ref SnsArn
                  - !GetAtt SomeResource.Arn

After Example:

  Queue:
    Type: AWS::Serverless::Queue
    Properties:
      DeadLetterQueue: true
      Sources:
         - Arn: !Ref SnsArn
         - Arn: !GetAtt SomeResource.Arn
@jfuss jfuss added the area/new-resource Label for new resources being asked/proposed label Mar 30, 2022
@aws aws locked and limited conversation to collaborators Feb 7, 2024
@jfuss jfuss converted this issue into discussion #3530 Feb 7, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
area/new-resource Label for new resources being asked/proposed maintainer/need-response type/feature
Projects
None yet
Development

No branches or pull requests

4 participants