seeebiii / ses-email-forwarding Goto Github PK

I'm getting this error when I do a cdk deploy. I'm kind of new to the ckd and typescript so possibly I'm just making some beginner error

VitaminsStack failed: Error [ValidationError]: Template format error: Unrecognized resource types: [AWS::SES::ReceiptRuleSet, AWS::SES::ReceiptRule]
at Request.extractError (/opt/homebrew/Cellar/aws-cdk/2.64.0/libexec/lib/node_modules/aws-cdk/lib/index.js:31:33843)
at Request.callListeners (/opt/homebrew/Cellar/aws-cdk/2.64.0/libexec/lib/node_modules/aws-cdk/lib/index.js:31:76646)
at Request.emit (/opt/homebrew/Cellar/aws-cdk/2.64.0/libexec/lib/node_modules/aws-cdk/lib/index.js:31:76094)
at Request.emit (/opt/homebrew/Cellar/aws-cdk/2.64.0/libexec/lib/node_modules/aws-cdk/lib/index.js:31:182419)
at Request.transition (/opt/homebrew/Cellar/aws-cdk/2.64.0/libexec/lib/node_modules/aws-cdk/lib/index.js:31:175971)
at AcceptorStateMachine.runT

Great package @seeebiii Sebastian!

There's an issue with setting up a catch-all forwarder for an entire domain or subdomain.

Your emailMapping definition takes a "subdomain.domain.com" format, which is what's needed to create the forwarding rule in SES.

However, the aws-lambda-ses-forwarder package is expecting the input to be "@subdomain.domain.com", with the leading "@".

I was thinking that when you write the mapping to SSM, if the receiveEmail is not a valid e-mail, but rather a subdomain or domain, then you prepend "@" before saving in SSM so that aws-lambda-ses-forwarder can properly forward email from the entire (sub)domain.

EmailForwardingRuleSet/EmailForwardingRule-0/EmailForwardingFunction: Resource handler returned message: "The runtime parameter of nodejs12.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs18.x) while creating or updating functions. (Service: Lambda, Status Code: 400, Request ID: 124fd8f3-53b5-478e-a8e7-ed5075c5e7fe)" (RequestToken: eafdb84e-8fb3-0283-1223-881c1581b1f2, HandlerErrorCode: InvalidRequest)

==========

Can we get this bumped up?