Set Visibility timeout of the SQS with reference to the timeout of the function about serverless-application-model

[ConnorRobertson]

Hello, @conao3
This issue was brought up here.
Essentially, the way to workaround this is to not use SqsSubscription: true and instead create your own AWS::SQS::Queue if you want custom options.

Here is an example,

Resources:
  Topic:
    Type: AWS::SNS::Topic

  MyFunctionTopicEventQueue:
    Type: AWS::SQS::Queue
    Properties:
      VisibilityTimeout: 60

  MyFunction:
    Type: AWS::Serverless::Function
    Properties:
      CodeUri: s3://bucket/key
      Handler: app.lambda_handler
      Runtime: python3.9
      Timeout: 60
      Events:
        TopicEvent:
          Type: SNS
          Properties:
            Topic: !Ref Topic
            SqsSubscription:
              QueueArn: 
                Fn::GetAtt: 
                  - MyFunctionTopicEventQueue
                  - "Arn"
              QueueUrl: !Ref MyFunctionTopicEventQueue

The reason that the SQS VisibilityTimeout: cannot be automatically set to the Function timeout automatically is that this is a breaking change to some customers potentially. If you read the thread below the comment I linked, then more detail is given about why we cannot implement that fix.