(aws-cognito): SES region validity check is out of date

[straygar]

What is the problem?

It appears that there is a list of SES supported regions in code, and this list has become out of date.

Reproduction Steps

1. Create a UserPool in eu-north-1 with an SES email config:

new UserPool(this, 'UserPool', {
  email: UserPoolEmail.withSES({
    fromEmail: 'test@example.com',
  }),
});

2. Synthesize the stack

What did you expect to happen?

The template synthesizes as expected, as SES is available in eu-north-1

What actually happened?

The following error is produced:

Your stack is in eu-north-1, which is not a SES Region. Please provide a valid value for 'sesRegion'

CDK CLI Version

1.134.0

Framework Version

No response

Node.js Version

v14.18.1

OS

MacOS

Language

Typescript

Language Version

No response

Other information

Maybe we could remove this check entirely, and let it fail when deploying the CFN stack, if the SES region does not exist, to keep things more maintainable?

[corymhall]

@straygar SES by itself is available in eu-north-1, but the Cognito-SES integration is only available in 3 regions (us-east-1, us-west-2, and eu-west-1). See the docs here.

[ebenedetti-futuring]

@corymhall
I have the same problem. From the AWS interface I can select the eu-north-1 region and my cognito is in the eu-north-1 region. With cdk it gives me this error. If i choose another region, for example the eu-west-1, it let me do the deploy, but after i recive an error saying that i can't use the eu-west-1 region for ses with cognito in the eu-north-1.

[straygar]

@corymhall Those docs must be outdated then. Overriding EmailConfiguration.SourceArn via escape hatches to point to SES's eu-north-1 region works fine for sending confirmation emails.

[corymhall]

@straygar ah yeah looks like the docs are not up to date. Thanks for reporting this!

I think your suggestion is probably the way to go, just remove the check altogether and allow CloudFormation to fail if it is not configured correctly.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.