aws.sesv2.ConfigurationSet requires 'deliveryOptions.maxDeliverySeconds'

[michaeldop]

Describe what happened

aws.sesv2.ConfigurationSet is requiring 'deliveryOptions.maxDeliverySeconds' to be set even though it seems like an optional field. I receive this error

    error:   sdk-v2/provider2.go:515: sdk.helper_schema: creating AWS SESv2 (Simple Email V2) Configuration Set (default): operation error SESv2: CreateConfigurationSet, https response error StatusCode: 400, RequestID: 05656185-e3f2-41f8-825f-137c248bf950, BadRequestException: 1 validation error detected: Value at 'deliveryOptions.maxDeliverySeconds' failed to satisfy constraint: Member must have value greater than or equal to 300: [email protected]

I am not sure if this is an upstream issue or not because I do see it flagged as an optional field here and in the AWS documentation it isn't a required field

Sample program

  import * as aws from '@pulumi/aws';

  const configurationSet = new aws.sesv2.ConfigurationSet('default-config-set', {
    configurationSetName: 'default',
    deliveryOptions: {
      tlsPolicy: 'REQUIRE',
    },
    reputationOptions: {
      reputationMetricsEnabled: true,
    },
    sendingOptions: {
      sendingEnabled: true,
    },
    suppressionOptions: {
      suppressedReasons: ['BOUNCE', 'COMPLAINT'],
    },
  });

Log output

No response

Affected Resource(s)

aws.sesv2.ConfigurationSet

Output of pulumi about

❯ pulumi about
CLI          
Version      3.145.0
Go Version   go1.23.4
Go Compiler  gc

Plugins
KIND      NAME    VERSION
resource  aws     6.66.2
language  nodejs  3.145.0-dev.0

Host     
OS       darwin
Version  15.2
Arch     x86_64

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[t0yv0]

Thanks for logging this @michaeldop

This behavior is inherited from the upstream provider, I have filed an issue in hashicorp/terraform-provider-aws#40836 - please feel free to upvote it. The best way for Pulumi provider to get the fix is having this fixed upstream and flow into the Pulumi provider automatically.