Cloudformation-coverage-roadmap: AWS::SNS::Topic-TopicName-CloudFormation autogenerated name for FIFO topics

[grauj-aws]

1. Title

AWS::SNS::Topic-TopicName

2. Scope of request

• When creating a FIFO topic by using the AWS::SNS::Topic resource, if the TopicName property is not defined, CloudFormation will autogenerate a name for the resource
• However, the autogenerated name will not have the ".fifo" extension, causing the Topic creation to fail with an Invalid parameter: Topic Name message
• As noted on the SNS CreateTopic definition:
  > For a FIFO (first-in-first-out) topic, the name must end with the .fifo suffix.

3. Expected behavior

• It's expected that CloudFormation will generate valid names for the resources defined on the template, when those are not specified.
• On this case, CloudFormation should ensure that the autogenerated FIFO topic names have the ".fifo" sufix appended to them

4. Suggest specific test cases

• Issue can be reproduced with the following template definition:

Resources:
  Topic:
    Type: AWS::SNS::Topic
    Properties:
      ContentBasedDeduplication: false
      FifoTopic: true

5. Helpful Links to speed up research and evaluation

• AWS::SNS::Topic documentation
• SNS CreateTopic API action definition

6. Category

1. Integration (MQ, SQS, SNS,...)

[rrhodes]

Any updates or indication when this will be resolved? It's impacting customers using FIFO topics in the CDK too.

[yangmarc]

Hi @rrhodes we will start migrating SNS resources to self service. Once we are migrated, the issue should be resolved. The estimated timeline is the end of Q1. Thanks

[yangmarc]

SNS Resources are now live in Github. https://github.com/aws-cloudformation/aws-cloudformation-resource-providers-sns. The fix is addressed in repository. We are still in the process of migrating SNS resources to self service. In the meanwhile, you can download the code and deploy it in your own AWS account as a private registry. Cheers