title: Does S3 filtering allow wildcards for prefixes and suffixes in Lambda function triggering?
body: <p>I have the following bucket configuration in my CloudFormation template:</p>
  
  <pre><code>DummyBucket:
    Type: AWS::S3::Bucket
    DependsOn:
    - DummyBucketPermission
    - DummyImportFunction
    Properties:
      BucketName:
        ...
      BucketEncryption:
        ...
      NotificationConfiguration:
        LambdaConfigurations:
        - Event: 's3:ObjectCreated:*'
          Function:
            Fn::GetAtt: DummyFunction.Arn
          Filter:
            S3Key:
              Rules:
              - Name: prefix
                Value: queued/
              - Name: suffix
                Value: .csv
  </code></pre>
  
  <p>After I deploy my stack, I create a <code>queued</code> directory in that bucket and observation that uploading 'test1.csv' into <code>queued</code> triggers the notification, but creating another directory inside <code>queued</code> (e.g. <code>a</code>) and uploading 'test2.csv' to <code>queued/a</code> does not trigger it. Is there any way that CloudFormation allows the use of wildcards in prefixes and suffixes to support nested directories?</p>