Skip to content
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

[AWS::SES::ConfigurationSetEventDestination] - [BUG] - Updating EventDestination.Name makes no changes #2131

Open
cyounkins opened this issue Sep 11, 2024 · 1 comment
Labels

Comments

@cyounkins
Copy link

Name of the resource

AWS::SES::ConfigurationSetEventDestination

Resource Name

No response

Issue Description

Updating the EventDestination.Name property does not change

Expected Behavior

I expected the update to be rejected, the event destination to be modified, or to be re-created

Observed Behavior

No changes

Test Cases

  CloudwatchEvents:
    Type: AWS::SES::ConfigurationSetEventDestination
    Properties:
      ConfigurationSetName: !Ref SESConfigurationSet
      EventDestination:
        Name: !Sub ${SESConfigurationSet}-cloudwatch
        Enabled: true
        MatchingEventTypes:
          - send
          - reject
          - bounce
          - complaint
          - delivery
          - renderingFailure
          - deliveryDelay
          - subscription
        CloudWatchDestination:
          DimensionConfigurations:
            - DimensionName: ses:configuration-set
              DimensionValueSource: messageTag
              DefaultDimensionValue: default

Change Name to !Sub ${SESConfigurationSet}-cloudwatch2 and update. Observe no changes in console.

Other Details

No response

@cyounkins cyounkins added the bug label Sep 11, 2024
@harryaswan
Copy link

I just had this same issue.

A workaround is to change the resource's Logical ID to force the resource's replacement.
Part of the issue is that you cannot update the name of the EventDestination so changing the name requires a replacement, which it is not doing.

Worth noting also that documentation is also incorrect for this. It states Update requires: No interruption - but this should be Update requires: Replacement when it is replacing the resource correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants