remove maximum=1 for cloudwatch destination

[david-wells-1]

Fixes #6689
Fixes #5620

Changes proposed in this pull request:

• Change 1
• Change 2

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSAvailabilityZones'

...

[bflad]

Hi @david-wells-1 👋 Thanks for submitting this! Could you please also update the existing acceptance testing to include multiple CloudWatch destinations to prevent regressions in the future? e.g. copy pasting this test configuration with a slight update:

https://github.com/terraform-providers/terraform-provider-aws/blob/e5c1c5158a413e6d95a912d93093b47e0cc5b3ca/aws/resource_aws_ses_event_destination_test.go#L201

[david-wells-1]

@bflad - additional test added as requested for the ses_destination_event

[bflad]

LGTM, thanks @david-wells-1! 🚀

This Terraform resource is very strange and does not have a Read implementation. While it doesn't look like the SES API has not changed in this regard from my brief searching, I was able to confirm via the acceptance testing with debug SDK logging that multiple destinations were appropriately set and that the SES API accepted this configuration.

--- PASS: TestAccAWSSESEventDestination_basic (93.89s)

[david-wells-1]

Thanks @bflad

[bflad]

This has been released in version 1.51.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!