[aws-cognito] Setting from in emailSettings on a Cognito User pool causes the construct to fail

[gregorypierce]

Specifying the from in the emailSettings for a user pool causes the construct to fail with "Cannot configure From email address for default email configuration (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException; Request ID: c3ab1c5c-d6e5-4ab9-8bac-e604fdc2b175; Proxy: null)"

Reproduction Steps

Create a cognito.UserPool and set the emailSettings property:

         emailSettings: {
             from: 'noreply@' + props.domainName,
             replyTo: 'support@' + props.domainName
         },

What did you expect to happen?

The Cognito system will be configured to deliver email messages with a from and reply to as specified

What actually happened?

The construct will fail with Cannot configure From email address for default email configuration (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException; Request ID: c3ab1c5c-d6e5-4ab9-8bac-e604fdc2b175; Proxy: null).

This isn't specified anywhere in the documentation that you cannot do this for the default email configuration.

Environment

• CLI Version :
• Framework Version: 1.58
• Node.js Version: 12.16.3
• OS : ANY
• Language (Version): ALL

Other

Change documentation to:

Cognito sends emails to users in the user pool, when particular actions take place, such as welcome emails, invitation emails, password resets, etc. The address from which these emails are sent can be configured on the user pool . Read more about email settings here.

---

This is 🐛 Bug Report

[nija-at]

This is an error from the Cognito service. The CDK simply passes this value down to the From CloudFormation attribute.

Searching for this error on google - https://www.google.com/search?q=%22Cannot+configure+From+email+address+for+default+email+configuration%22 - it seems that this attribute may be reserved when used with SES only. You may have to dig in a little deeper to confirm this or talk to AWS support around this.

As for the CDK, we have an issue tracking SES implementation - #6768

[JoshM1994]

For those who are looking for a quick solution, I implement the following:

        const userPoolCfn = userPool.node.defaultChild as CfnUserPool;
        userPoolCfn.emailConfiguration = {
            emailSendingAccount: 'DEVELOPER',
            sourceArn: `arn:aws:ses:${Aws.REGION}:${Aws.ACCOUNT_ID}:identity/${VERIFIED_EMAIL_IDENTIY}`,
        };