@mavogel/awscdk-rootmail 0.0.17 → 0.0.18

package/.jsii

@@ -3518,7 +3518,7 @@
   },
   "name": "@mavogel/awscdk-rootmail",
   "readme": {
-    "markdown": "# awscdk-rootmail\n\nA single rootmail box for all your AWS accounts. The cdk implementation and **adaption** of the [superwerker](https://superwerker.cloud/) rootmail feature. See [here](docs/adrs/rootmail.md) for a detailed Architectural Decision Record ([ADR](https://adr.github.io/))\n\n- [TL;DR](#tldr)\n- [Usage](#usage)\n  - [Dependencies](#dependencies)\n  - [Deploy](#deploy)\n    - [CDK](#cdk)\n    - [Cloudformation](#cloudformation)\n- [Solution design: Version 1 - Domain in the same AWS account](#solution-design-version-1---domain-in-the-same-aws-account)\n- [Solution design: Version 2 - external DNS provider](#solution-design-version-2---external-dns-provider)\n- [Uninstall](#uninstall)\n- [Known issues](#known-issues)\n- [Related projects](#related-projects)\n\n## TL;DR\nEach AWS account needs one unique email address (the so-called \"AWS account root user email address\").\n\nAccess to these email addresses must be adequately secured since they provide privileged access to AWS accounts, such as account deletion procedures.\n\nThis is why you only need 1 mailing list for the AWS Management (formerly *root*) account,\nwe recommend the following pattern `aws-roots+<uuid>@mycompany.test`\n\n> [!NOTE]\n> Maximum **64** characters are allowed for the whole address.\n\nAnd as you own the domain `mycompany.test` you can add a subdomain, e.g. `aws`, for which all EMails will then be received with this solution within this particular AWS Management account.\n\n## Usage\n### Dependencies\nAdministrative access to an AWS account and the following tools:\n```sh\nbrew install aws-cli node@18 esbuild\n```\n\n<details>\n  <summary>... or a longer listing</summary>\n\n- Access to a development environment.  It is recommended to use AWS Cloud9 to avoid having to set up the tools needed to deploy the solution.  See [Getting started with AWS Cloud9](https://aws.amazon.com/cloud9/getting-started/).\n- Using Cloud9, all of the following have already been configured for you.  If you choose not to use Cloud9, you will need to install the following.\n    - AWS CLI. See [Installing, updating and uninstalling the AWS CLI version 2](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html)\n    - Set up the AWS CLI with IAM access credentials. See [Configuring the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html)\n    - Node.js version 10.13.0 or later\n    - AWS CDK version 2.90.0 or later. For installation instructions see [Getting Started with the AWS CDK](https://docs.aws.amazon.com/cdk/latest/guide/getting_started.html#getting_started_install)\n    - Docker version 20.10.x or later **OR** [esbuild](https://esbuild.github.io/)\n</details>\n\n### Deploy\nYou can chose via embedding the construct in your cdk-app or use is directly via Cloudformation.\n#### CDK\n1. To start a new project we recommend using [projen](https://projen.io/).\n   1. Create a new projen project\n   ```sh\n   npx projen new awscdk-app-ts\n   ```\n   2. Add `@mavogel/awscdk-rootmail` as a dependency to your project in the `.projenrc.ts` file\n   3. Run `npm run projen` to install it\n2. In you `main.ts` file add the following\n```ts\nimport {\n    App,\n    Stack,\n    aws_route53 as r53\n} from 'aws-cdk-lib';\nimport { Rootmail, SESReceiveStack } from '@mavogel/awscdk-rootmail';\nimport { Construct } from 'constructs';\n\nexport class MyStack extends Stack {\n  constructor(scope: Construct, id: string, props: StackProps = {}) {\n    super(scope, id, props);\n\n    const domain = 'mycompany.test'\n\n    const hostedZone = r53.HostedZone.fromLookup(this, 'rootmail-parent-hosted-zone', {\n      domainName: domain,\n    });\n\n    const rootmail = new Rootmail(this, 'rootmail-stack', {\n      // 1. a domain you own, registered via Route53 in the SAME account\n      domain: domain;\n      // 2. so the subdomain will be aws.mycompany.test and\n      //    wired / delegated  automatically\n      autowireDNSParentHostedZoneID: hostedZone.hostedZoneId,\n      env: {\n      // 3. or any other region SES is available\n        region: 'eu-west-1',\n      },\n    });\n  }\n}\n```\n2. run on your commandline\n```sh\nnpm run deploy\n```\n1. No need to do anything, the NS records are **automatically** propagated as the parent Hosted Zone is in the same account!\n2. The `hosted-zone-dkim-propagation-provider.is-complete-handler` Lambda function checks every 10 seconds if the DNS for the subdomain is propagated. Details are in the Cloudwatch log group.\n\n#### Cloudformation\nor use it directly a Cloudformation template `yaml` from the URL [here](https://mvc-test4-bucket-eu-west-1.s3.eu-west-1.amazonaws.com/rootmail/0.0.13-DEVELOPMENT/rootmailStack.template.yaml).\n\n\n<details>\n  <summary>... click to expand</summary>\n\nand fill out the parameters\n![cloudformation-template](docs/img/cloudformation-tpl-min.png)\n\n</details>\n\n## Solution design: Version 1 - Domain in the same AWS account\n![rootmail-solution-diagram-v1](docs/img/awscdk-rootmail-v1-min.png)\n\n1. You own a domain, e.g., `mycompany.test`, registered via `Route53` in the **same** AWS account.\n2. The stack creates a `Route53` public Hosted Zone for the subdomain, e.g., `aws.mycompany.test`. It also automatically adds the `TXT` and `CNAME` records for verifying the domain towards SES **and** adds the NS server entries automatically to the main domain `mycompany.test`.\n3. When the subdomain `aws.mycompany.test` is successfully propagated, the stack creates a verified Domain in AWS SES and adds a recipient rule for `root@aws.mycompany.test`. On a successful propagation you will get a mail as follows to the root Email address of the account you are installing the stack 👇\n![domain-verification](docs/img/3-domain-verification-min.png)\n4. Now, any mail going to `root+<any-string>@aws.mycompany.test` will be processed by OpsSanta 🎅🏽 Lambda function and also stored in the rootmail S3 bucket 🪣.\n5. The OpsSanta function verifies the verdicts (DKIM etc.) of the sender, also skips AWS Account welcome EMails, and processes all other EMails. If it is a password reset link EMail it stores the link in the parameter store (and does *not* create an OpsItem for now). For all other mails, which are not skipped an OpsItem is created to have a central location for all items.\n> [!NOTE]\n> You can also connect your Jira to the OpsCenter.\n6. The bucket where all mail to `root@aws.mycompany.test` are stored.\n7. The [SSM parameter store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html) for the password reset links.\n![ssm-pw-reset-link](docs/img/4-ssm-pw-reset-link-min.png)\n8. The OpsItem which is created. It is open and shall be further processed either in the OpsCenter or any other issue tracker.\n![opts-item](docs/img/4-opts-items-min.png)\n\n> [!NOTE]\n> SES support alias, so mail to `root+random-string@aws.mycompany.test` will also be catched and forwarded.\n\n## Solution design: Version 2 - external DNS provider\n<details>\n  <summary>open for details</summary>\n\n![rootmail-solution-diagram-v2](docs/img/awscdk-rootmail-v2-min.png)\n\n```ts\nconst rootmail = new Rootmail(this, 'rootmail-stack', {\n  // 1. a domain you own, registered via Route53 in the same account\n  domain: 'mycompany.test';\n  // 2. '' is the default, so you can also remove it\n  // autowireDNSParentHostedZoneID: '',\n  env: {\n  // 3. or any other region SES is available\n    region: 'eu-west-1',\n  },\n});\n```\n\n1. You own a domain, e.g., `mycompany.test`. It can be at any registrar such as `godaddy`, also `Route53` itself in another AWS account.\n2. The stack creates a `Route53` public Hosted Zone for the subdomain, e.g., `aws.mycompany.test`. It also automatically adds the TXT and CNAME records (for DKIM etc.) for verifying the domain towards SES. **NOTE:** You must now add the NS server entries into the Domain provider which owns the main domain `mycompany.test`.\n3. items 3-7 are the same as in `v1`\n\n\n> [!NOTE]\n> After running `npm run deploy` you need to do the following steps manually:\n\n1. watch out for the hosted zone  `aws.mycompany.test` to be created\n![subdomain-hosted-zone](docs/img/1-use-ns-from-hz-min.png) By default you have **2 hours** to wire the DNS!\n2. Then create the NS record in your domain `mycompany.test` for the subdomain `aws.mycompany.test`. Here for Route53 in AWS:\n![create-ns-records](docs/img/2-create-ns-records-min.png)\n3. You can test it yourself via\n```sh\ndig +short NS 8.8.8.8 aws.mycompany.test\n# should return something like\nns-1111.your-dns-provider-10.org.\nns-2222.your-dns-provider-21.co.uk.\nns-33.your-dns-provider-04.com.\nns-444.your-dns-provider-12.net.\n```\nand also by sending an EMail, e.g. from Gmail to `root@aws.mycompany.test`\n\n</details>\n\n## Uninstall\n1. Delete the stack, the custom resources will delete most resources\n2. And by design you need to manually delete the S3 Bucket containing the mails. This is to prevent accidental deletion of the mails. You can find the bucket name in the stack output.\n![s3-bucket](docs/img/4-s3-bucket-min.png)\n3. Furthermore, the cloudwatch log groups are not deleted, since they might contain valuable information. You can delete them manually.\n![log-groups](docs/img/5-log-groups-min.png)\n## Known issues\n- [jsii/2071](https://github.com/aws/jsii/issues/2071): so adding  `compilerOptions.\"esModuleInterop\": true,` in `tsconfig.json` is not possible. See aws-cdk usage with[typescript](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/#Usage_with_TypeScript). So we needed to change import from `import AWS from 'aws-sdk';` -> `import * as AWS from 'aws-sdk';` to be able to compile.\n\n## Related projects\n- [aws-account-factory-email](https://github.com/aws-samples/aws-account-factory-email): a similar approach with SES, however you need to manually configure it upfront and also it about delivering root mails for a specific account to a specific mailing list and mainly decouples the real email address from the one of the AWS account. The main difference is that we do not *hide* or decouple the email address, but more make those as unique and unguessable/bruteforable as possible (with `uuids`)."
+    "markdown": "# awscdk-rootmail\n\nA single rootmail box for all your AWS accounts. The cdk implementation and **adaption** of the [superwerker](https://superwerker.cloud/) rootmail feature. See [here](docs/adrs/rootmail.md) for a detailed Architectural Decision Record ([ADR](https://adr.github.io/))\n\n- [TL;DR](#tldr)\n- [Usage](#usage)\n  - [Dependencies](#dependencies)\n  - [Deploy](#deploy)\n    - [CDK](#cdk)\n    - [Cloudformation](#cloudformation)\n- [Solution design: Version 1 - Domain in the same AWS account](#solution-design-version-1---domain-in-the-same-aws-account)\n- [Solution design: Version 2 - external DNS provider](#solution-design-version-2---external-dns-provider)\n- [Uninstall](#uninstall)\n- [Known issues](#known-issues)\n- [Related projects](#related-projects)\n\n## TL;DR\nEach AWS account needs one unique email address (the so-called \"AWS account root user email address\").\n\nAccess to these email addresses must be adequately secured since they provide privileged access to AWS accounts, such as account deletion procedures.\n\nThis is why you only need 1 mailing list for the AWS Management (formerly *root*) account,\nwe recommend the following pattern `aws-roots+<uuid>@mycompany.test`\n\n> [!NOTE]\n> Maximum **64** characters are allowed for the whole address.\n\nAnd as you own the domain `mycompany.test` you can add a subdomain, e.g. `aws`, for which all EMails will then be received with this solution within this particular AWS Management account.\n\n## Usage\n### Dependencies\nAdministrative access to an AWS account and the following tools:\n```sh\nbrew install aws-cli node@18 esbuild\n```\n\n<details>\n  <summary>... or a longer listing</summary>\n\n- Access to a development environment.  It is recommended to use AWS Cloud9 to avoid having to set up the tools needed to deploy the solution.  See [Getting started with AWS Cloud9](https://aws.amazon.com/cloud9/getting-started/).\n- Using Cloud9, all of the following have already been configured for you.  If you choose not to use Cloud9, you will need to install the following.\n    - AWS CLI. See [Installing, updating and uninstalling the AWS CLI version 2](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html)\n    - Set up the AWS CLI with IAM access credentials. See [Configuring the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html)\n    - Node.js version 10.13.0 or later\n    - AWS CDK version 2.90.0 or later. For installation instructions see [Getting Started with the AWS CDK](https://docs.aws.amazon.com/cdk/latest/guide/getting_started.html#getting_started_install)\n    - Docker version 20.10.x or later **OR** [esbuild](https://esbuild.github.io/)\n</details>\n\n### Deploy\nYou can chose via embedding the construct in your cdk-app or use is directly via Cloudformation.\n#### CDK\n1. To start a new project we recommend using [projen](https://projen.io/).\n   1. Create a new projen project\n   ```sh\n   npx projen new awscdk-app-ts\n   ```\n   2. Add `@mavogel/awscdk-rootmail` as a dependency to your project in the `.projenrc.ts` file\n   3. Run `npm run projen` to install it\n2. In you `main.ts` file add the following code\n```ts\nimport {\n    App,\n    Stack,\n    aws_route53 as r53\n} from 'aws-cdk-lib';\nimport { Rootmail } from '@mavogel/awscdk-rootmail';\nimport { Construct } from 'constructs';\n\nexport class MyStack extends Stack {\n  constructor(scope: Construct, id: string, props: StackProps = {}) {\n    super(scope, id, props);\n\n    const domain = 'mycompany.test'\n\n    const hostedZone = r53.HostedZone.fromLookup(this, 'rootmail-parent-hosted-zone', {\n      domainName: domain,\n    });\n\n    const rootmail = new Rootmail(this, 'rootmail-stack', {\n      // 1. a domain you own, registered via Route53 in the SAME account\n      domain: domain;\n      // 2. so the subdomain will be aws.mycompany.test and\n      //    wired / delegated  automatically\n      autowireDNSParentHostedZoneID: hostedZone.hostedZoneId,\n      env: {\n      // 3. or any other region SES is available\n        region: 'eu-west-1',\n      },\n    });\n  }\n}\n```\n2. run on your commandline\n```sh\nnpm run deploy\n```\n1. No need to do anything, the NS records are **automatically** propagated as the parent Hosted Zone is in the same account!\n2. The `hosted-zone-dkim-propagation-provider.is-complete-handler` Lambda function checks every 10 seconds if the DNS for the subdomain is propagated. Details are in the Cloudwatch log group.\n\n### CDK with your own receiver function\nYou might also want to pass in you own function on what to do when an EMail is received\n\nfile `functions/custom-ses-receive-function.ts` which gets the 2 environment variables populated\n- `EMAIL_BUCKET`\n- `EMAIL_BUCKET_ARN`\n\nas well as `s3:GetObject` on the `RootMail/*` objects in the created Rootmail `S3` bucket.\n\n```ts\nimport { S3 } from '@aws-sdk/client-s3';\nimport { ParsedMail, simpleParser } from 'mailparser';\n// populated by default\nconst emailBucket = process.env.EMAIL_BUCKET;\nconst emailBucketArn = process.env.EMAIL_BUCKET_ARN;\nconst s3 = new S3();\n\n// SESEventRecordsToLambda\n// from https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-lambda-event.html\nexport const handler = async (event: SESEventRecordsToLambda) => {\n    for (const record of event.Records) {\n\n        const id = record.ses.mail.messageId;\n        const key = `RootMail/${id}`;\n        const response = await s3.getObject({ Bucket: emailBucket as string, Key: key });\n\n        const msg: ParsedMail = await simpleParser(response.Body as unknown as Buffer);\n\n        let title = msg.subject;\n        console.log(`Title: ${title} from emailBucketArn: ${emailBucketArn}`);\n        // use the content of the email body\n        const body = msg.html;\n        // add your custom code here ...\n\n        // dummy example: list s3 buckets\n        const buckets = await s3.listBuckets({});\n        if (!buckets.Buckets) {\n            console.log('No buckets found');\n            return;\n        }\n        console.log('Buckets:');\n        for (const bucket of buckets.Buckets || []) {\n            console.log(bucket.Name);\n        }\n    }\n\n};\n```\n\n```ts\nconst customSesReceiveFunction = new NodejsFunction(stackUnderTest, 'custom-ses-receive-function', {\n  functionName: PhysicalName.GENERATE_IF_NEEDED,\n  entry: path.join(__dirname, 'functions', 'custom-ses-receive-function.ts'),\n  runtime: lambda.Runtime.NODEJS_18_X,\n  logRetention: 1,\n  timeout: Duration.seconds(30),\n});\n\n// Note: any additional permissions you need to add to the function yourself!\ncustomSesReceiveFunction.addToRolePolicy(new iam.PolicyStatement({\n  actions: [\n    's3:List*',\n  ],\n  resources: ['*'],\n}))\n```\n\n#### Cloudformation\nor use it directly a Cloudformation template `yaml` from the URL [here](https://mvc-test4-bucket-eu-west-1.s3.eu-west-1.amazonaws.com/rootmail/0.0.13-DEVELOPMENT/rootmailStack.template.yaml).\n\n\n<details>\n  <summary>... click to expand</summary>\n\nand fill out the parameters\n![cloudformation-template](docs/img/cloudformation-tpl-min.png)\n\n</details>\n\n## Solution design: Version 1 - Domain in the same AWS account\n![rootmail-solution-diagram-v1](docs/img/awscdk-rootmail-v1-min.png)\n\n1. You own a domain, e.g., `mycompany.test`, registered via `Route53` in the **same** AWS account.\n2. The stack creates a `Route53` public Hosted Zone for the subdomain, e.g., `aws.mycompany.test`. It also automatically adds the `TXT` and `CNAME` records for verifying the domain towards SES **and** adds the NS server entries automatically to the main domain `mycompany.test`.\n3. When the subdomain `aws.mycompany.test` is successfully propagated, the stack creates a verified Domain in AWS SES and adds a recipient rule for `root@aws.mycompany.test`. On a successful propagation you will get a mail as follows to the root Email address of the account you are installing the stack 👇\n![domain-verification](docs/img/3-domain-verification-min.png)\n4. Now, any mail going to `root+<any-string>@aws.mycompany.test` will be processed by OpsSanta 🎅🏽 Lambda function and also stored in the rootmail S3 bucket 🪣.\n5. The OpsSanta function verifies the verdicts (DKIM etc.) of the sender, also skips AWS Account welcome EMails, and processes all other EMails. If it is a password reset link EMail it stores the link in the parameter store (and does *not* create an OpsItem for now). For all other mails, which are not skipped an OpsItem is created to have a central location for all items.\n> [!NOTE]\n> You can also connect your Jira to the OpsCenter.\n6. The bucket where all mail to `root@aws.mycompany.test` are stored.\n7. The [SSM parameter store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html) for the password reset links.\n![ssm-pw-reset-link](docs/img/4-ssm-pw-reset-link-min.png)\n8. The OpsItem which is created. It is open and shall be further processed either in the OpsCenter or any other issue tracker.\n![opts-item](docs/img/4-opts-items-min.png)\n\n> [!NOTE]\n> SES support alias, so mail to `root+random-string@aws.mycompany.test` will also be catched and forwarded.\n\n## Solution design: Version 2 - external DNS provider\n<details>\n  <summary>open for details</summary>\n\n![rootmail-solution-diagram-v2](docs/img/awscdk-rootmail-v2-min.png)\n\n```ts\nconst rootmail = new Rootmail(this, 'rootmail-stack', {\n  // 1. a domain you own, registered via Route53 in the same account\n  domain: 'mycompany.test';\n  // 2. '' is the default, so you can also remove it\n  // autowireDNSParentHostedZoneID: '',\n  env: {\n  // 3. or any other region SES is available\n    region: 'eu-west-1',\n  },\n});\n```\n\n1. You own a domain, e.g., `mycompany.test`. It can be at any registrar such as `godaddy`, also `Route53` itself in another AWS account.\n2. The stack creates a `Route53` public Hosted Zone for the subdomain, e.g., `aws.mycompany.test`. It also automatically adds the TXT and CNAME records (for DKIM etc.) for verifying the domain towards SES. **NOTE:** You must now add the NS server entries into the Domain provider which owns the main domain `mycompany.test`.\n3. items 3-7 are the same as in `v1`\n\n\n> [!NOTE]\n> After running `npm run deploy` you need to do the following steps manually:\n\n1. watch out for the hosted zone  `aws.mycompany.test` to be created\n![subdomain-hosted-zone](docs/img/1-use-ns-from-hz-min.png) By default you have **2 hours** to wire the DNS!\n2. Then create the NS record in your domain `mycompany.test` for the subdomain `aws.mycompany.test`. Here for Route53 in AWS:\n![create-ns-records](docs/img/2-create-ns-records-min.png)\n3. You can test it yourself via\n```sh\ndig +short NS 8.8.8.8 aws.mycompany.test\n# should return something like\nns-1111.your-dns-provider-10.org.\nns-2222.your-dns-provider-21.co.uk.\nns-33.your-dns-provider-04.com.\nns-444.your-dns-provider-12.net.\n```\nand also by sending an EMail, e.g. from Gmail to `root@aws.mycompany.test`\n\n</details>\n\n## Uninstall\n1. Delete the stack, the custom resources will delete most resources\n2. And by design you need to manually delete the S3 Bucket containing the mails. This is to prevent accidental deletion of the mails. You can find the bucket name in the stack output.\n![s3-bucket](docs/img/4-s3-bucket-min.png)\n3. Furthermore, the cloudwatch log groups are not deleted, since they might contain valuable information. You can delete them manually.\n![log-groups](docs/img/5-log-groups-min.png)\n## Known issues\n- [jsii/2071](https://github.com/aws/jsii/issues/2071): so adding  `compilerOptions.\"esModuleInterop\": true,` in `tsconfig.json` is not possible. See aws-cdk usage with[typescript](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/#Usage_with_TypeScript). So we needed to change import from `import AWS from 'aws-sdk';` -> `import * as AWS from 'aws-sdk';` to be able to compile.\n\n## Related projects\n- [aws-account-factory-email](https://github.com/aws-samples/aws-account-factory-email): a similar approach with SES, however you need to manually configure it upfront and also it about delivering root mails for a specific account to a specific mailing list and mainly decouples the real email address from the one of the AWS account. The main difference is that we do not *hide* or decouple the email address, but more make those as unique and unguessable/bruteforable as possible (with `uuids`)."
   },
   "repository": {
     "type": "git",
@@ -3544,7 +3544,7 @@
         },
         "locationInModule": {
           "filename": "src/rootmail.ts",
-          "line": 59
+          "line": 65
         },
         "parameters": [
           {
@@ -3570,7 +3570,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "src/rootmail.ts",
-        "line": 55
+        "line": 61
       },
       "name": "Rootmail",
       "properties": [
@@ -3581,7 +3581,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/rootmail.ts",
-            "line": 57
+            "line": 63
           },
           "name": "emailBucket",
           "type": {
@@ -3595,7 +3595,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/rootmail.ts",
-            "line": 56
+            "line": 62
           },
           "name": "hostedZoneParameterName",
           "type": {
@@ -3615,7 +3615,7 @@
       "kind": "interface",
       "locationInModule": {
         "filename": "src/rootmail.ts",
-        "line": 19
+        "line": 20
       },
       "name": "RootmailProps",
       "properties": [
@@ -3628,13 +3628,30 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/rootmail.ts",
-            "line": 23
+            "line": 24
           },
           "name": "domain",
           "type": {
             "primitive": "string"
           }
         },
+        {
+          "abstract": true,
+          "docs": {
+            "stability": "stable",
+            "summary": "The custom SES receive function to use."
+          },
+          "immutable": true,
+          "locationInModule": {
+            "filename": "src/rootmail.ts",
+            "line": 51
+          },
+          "name": "customSesReceiveFunction",
+          "optional": true,
+          "type": {
+            "fqn": "aws-cdk-lib.aws_lambda.Function"
+          }
+        },
         {
           "abstract": true,
           "docs": {
@@ -3646,7 +3663,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/rootmail.ts",
-            "line": 52
+            "line": 58
           },
           "name": "setDestroyPolicyToAllResources",
           "optional": true,
@@ -3664,7 +3681,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/rootmail.ts",
-            "line": 30
+            "line": 31
           },
           "name": "subdomain",
           "optional": true,
@@ -3682,7 +3699,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/rootmail.ts",
-            "line": 37
+            "line": 38
           },
           "name": "totalTimeToWireDNS",
           "optional": true,
@@ -3700,7 +3717,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/rootmail.ts",
-            "line": 45
+            "line": 46
           },
           "name": "wireDNSToHostedZoneID",
           "optional": true,
@@ -3724,7 +3741,7 @@
         },
         "locationInModule": {
           "filename": "src/ses-receive.ts",
-          "line": 43
+          "line": 48
         },
         "parameters": [
           {
@@ -3750,7 +3767,7 @@
       "kind": "class",
       "locationInModule": {
         "filename": "src/ses-receive.ts",
-        "line": 42
+        "line": 47
       },
       "name": "SESReceive",
       "symbolId": "src/ses-receive:SESReceive"
@@ -3817,6 +3834,23 @@
             "primitive": "string"
           }
         },
+        {
+          "abstract": true,
+          "docs": {
+            "stability": "stable",
+            "summary": "The custom SES receive function to use."
+          },
+          "immutable": true,
+          "locationInModule": {
+            "filename": "src/ses-receive.ts",
+            "line": 39
+          },
+          "name": "customSesReceiveFunction",
+          "optional": true,
+          "type": {
+            "fqn": "aws-cdk-lib.aws_lambda.Function"
+          }
+        },
         {
           "abstract": true,
           "docs": {
@@ -3827,7 +3861,7 @@
           "immutable": true,
           "locationInModule": {
             "filename": "src/ses-receive.ts",
-            "line": 39
+            "line": 44
           },
           "name": "setDestroyPolicyToAllResources",
           "optional": true,
@@ -3839,6 +3873,6 @@
       "symbolId": "src/ses-receive:SESReceiveProps"
     }
   },
-  "version": "0.0.17",
-  "fingerprint": "mnzksQYDH7lvN38jvIFfJRuz/XHt/dIH4b6Q8t41jjw="
+  "version": "0.0.18",
+  "fingerprint": "ZCmksEjMthIJoEbvZEHdNGJF5TwNn18SUkvmUmRDt2k="
 }

package/API.md

@@ -56,14 +56,14 @@ You can chose via embedding the construct in your cdk-app or use is directly via
    ```
    2. Add `@mavogel/awscdk-rootmail` as a dependency to your project in the `.projenrc.ts` file
    3. Run `npm run projen` to install it
-2. In you `main.ts` file add the following
+2. In you `main.ts` file add the following code
 ```ts
 import {
     App,
     Stack,
     aws_route53 as r53
 } from 'aws-cdk-lib';
-import { Rootmail, SESReceiveStack } from '@mavogel/awscdk-rootmail';
+import { Rootmail } from '@mavogel/awscdk-rootmail';
 import { Construct } from 'constructs';
 
 export class MyStack extends Stack {
@@ -97,6 +97,73 @@ npm run deploy
 1. No need to do anything, the NS records are **automatically** propagated as the parent Hosted Zone is in the same account!
 2. The `hosted-zone-dkim-propagation-provider.is-complete-handler` Lambda function checks every 10 seconds if the DNS for the subdomain is propagated. Details are in the Cloudwatch log group.
 
+### CDK with your own receiver function
+You might also want to pass in you own function on what to do when an EMail is received
+
+file `functions/custom-ses-receive-function.ts` which gets the 2 environment variables populated
+- `EMAIL_BUCKET`
+- `EMAIL_BUCKET_ARN`
+
+as well as `s3:GetObject` on the `RootMail/*` objects in the created Rootmail `S3` bucket.
+
+```ts
+import { S3 } from '@aws-sdk/client-s3';
+import { ParsedMail, simpleParser } from 'mailparser';
+// populated by default
+const emailBucket = process.env.EMAIL_BUCKET;
+const emailBucketArn = process.env.EMAIL_BUCKET_ARN;
+const s3 = new S3();
+
+// SESEventRecordsToLambda
+// from https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-lambda-event.html
+export const handler = async (event: SESEventRecordsToLambda) => {
+    for (const record of event.Records) {
+
+        const id = record.ses.mail.messageId;
+        const key = `RootMail/${id}`;
+        const response = await s3.getObject({ Bucket: emailBucket as string, Key: key });
+
+        const msg: ParsedMail = await simpleParser(response.Body as unknown as Buffer);
+
+        let title = msg.subject;
+        console.log(`Title: ${title} from emailBucketArn: ${emailBucketArn}`);
+        // use the content of the email body
+        const body = msg.html;
+        // add your custom code here ...
+
+        // dummy example: list s3 buckets
+        const buckets = await s3.listBuckets({});
+        if (!buckets.Buckets) {
+            console.log('No buckets found');
+            return;
+        }
+        console.log('Buckets:');
+        for (const bucket of buckets.Buckets || []) {
+            console.log(bucket.Name);
+        }
+    }
+
+};
+```
+
+```ts
+const customSesReceiveFunction = new NodejsFunction(stackUnderTest, 'custom-ses-receive-function', {
+  functionName: PhysicalName.GENERATE_IF_NEEDED,
+  entry: path.join(__dirname, 'functions', 'custom-ses-receive-function.ts'),
+  runtime: lambda.Runtime.NODEJS_18_X,
+  logRetention: 1,
+  timeout: Duration.seconds(30),
+});
+
+// Note: any additional permissions you need to add to the function yourself!
+customSesReceiveFunction.addToRolePolicy(new iam.PolicyStatement({
+  actions: [
+    's3:List*',
+  ],
+  resources: ['*'],
+}))
+```
+
 #### Cloudformation
 or use it directly a Cloudformation template `yaml` from the URL [here](https://mvc-test4-bucket-eu-west-1.s3.eu-west-1.amazonaws.com/rootmail/0.0.13-DEVELOPMENT/rootmailStack.template.yaml).
 
@@ -425,6 +492,7 @@ const rootmailProps: RootmailProps = { ... }
 | **Name** | **Type** | **Description** |
 | --- | --- | --- |
 | <code><a href="#@mavogel/awscdk-rootmail.RootmailProps.property.domain">domain</a></code> | <code>string</code> | Domain used for root mail feature. |
+| <code><a href="#@mavogel/awscdk-rootmail.RootmailProps.property.customSesReceiveFunction">customSesReceiveFunction</a></code> | <code>aws-cdk-lib.aws_lambda.Function</code> | The custom SES receive function to use. |
 | <code><a href="#@mavogel/awscdk-rootmail.RootmailProps.property.setDestroyPolicyToAllResources">setDestroyPolicyToAllResources</a></code> | <code>boolean</code> | Whether to set all removal policies to DESTROY. |
 | <code><a href="#@mavogel/awscdk-rootmail.RootmailProps.property.subdomain">subdomain</a></code> | <code>string</code> | Subdomain used for root mail feature. |
 | <code><a href="#@mavogel/awscdk-rootmail.RootmailProps.property.totalTimeToWireDNS">totalTimeToWireDNS</a></code> | <code>aws-cdk-lib.Duration</code> | The total time to wait for the DNS records to be available/wired. |
@@ -444,6 +512,18 @@ Domain used for root mail feature.
 
 ---
 
+##### `customSesReceiveFunction`<sup>Optional</sup> <a name="customSesReceiveFunction" id="@mavogel/awscdk-rootmail.RootmailProps.property.customSesReceiveFunction"></a>
+
+```typescript
+public readonly customSesReceiveFunction: Function;
+```
+
+- *Type:* aws-cdk-lib.aws_lambda.Function
+
+The custom SES receive function to use.
+
+---
+
 ##### `setDestroyPolicyToAllResources`<sup>Optional</sup> <a name="setDestroyPolicyToAllResources" id="@mavogel/awscdk-rootmail.RootmailProps.property.setDestroyPolicyToAllResources"></a>
 
 ```typescript
@@ -515,6 +595,7 @@ const sESReceiveProps: SESReceiveProps = { ... }
 | <code><a href="#@mavogel/awscdk-rootmail.SESReceiveProps.property.domain">domain</a></code> | <code>string</code> | Domain used for root mail feature. |
 | <code><a href="#@mavogel/awscdk-rootmail.SESReceiveProps.property.emailbucket">emailbucket</a></code> | <code>aws-cdk-lib.aws_s3.Bucket</code> | S3 bucket to store received emails. |
 | <code><a href="#@mavogel/awscdk-rootmail.SESReceiveProps.property.subdomain">subdomain</a></code> | <code>string</code> | Subdomain used for root mail feature. |
+| <code><a href="#@mavogel/awscdk-rootmail.SESReceiveProps.property.customSesReceiveFunction">customSesReceiveFunction</a></code> | <code>aws-cdk-lib.aws_lambda.Function</code> | The custom SES receive function to use. |
 | <code><a href="#@mavogel/awscdk-rootmail.SESReceiveProps.property.setDestroyPolicyToAllResources">setDestroyPolicyToAllResources</a></code> | <code>boolean</code> | Whether to set all removal policies to DESTROY. |
 
 ---
@@ -555,6 +636,18 @@ Subdomain used for root mail feature.
 
 ---
 
+##### `customSesReceiveFunction`<sup>Optional</sup> <a name="customSesReceiveFunction" id="@mavogel/awscdk-rootmail.SESReceiveProps.property.customSesReceiveFunction"></a>
+
+```typescript
+public readonly customSesReceiveFunction: Function;
+```
+
+- *Type:* aws-cdk-lib.aws_lambda.Function
+
+The custom SES receive function to use.
+
+---
+
 ##### `setDestroyPolicyToAllResources`<sup>Optional</sup> <a name="setDestroyPolicyToAllResources" id="@mavogel/awscdk-rootmail.SESReceiveProps.property.setDestroyPolicyToAllResources"></a>
 
 ```typescript

package/README.md

@@ -56,14 +56,14 @@ You can chose via embedding the construct in your cdk-app or use is directly via
    ```
    2. Add `@mavogel/awscdk-rootmail` as a dependency to your project in the `.projenrc.ts` file
    3. Run `npm run projen` to install it
-2. In you `main.ts` file add the following
+2. In you `main.ts` file add the following code
 ```ts
 import { 
     App, 
     Stack, 
     aws_route53 as r53 
 } from 'aws-cdk-lib';
-import { Rootmail, SESReceiveStack } from '@mavogel/awscdk-rootmail';
+import { Rootmail } from '@mavogel/awscdk-rootmail';
 import { Construct } from 'constructs';
 
 export class MyStack extends Stack {
@@ -97,6 +97,73 @@ npm run deploy
 1. No need to do anything, the NS records are **automatically** propagated as the parent Hosted Zone is in the same account!
 2. The `hosted-zone-dkim-propagation-provider.is-complete-handler` Lambda function checks every 10 seconds if the DNS for the subdomain is propagated. Details are in the Cloudwatch log group.
 
+### CDK with your own receiver function
+You might also want to pass in you own function on what to do when an EMail is received
+
+file `functions/custom-ses-receive-function.ts` which gets the 2 environment variables populated
+- `EMAIL_BUCKET`
+- `EMAIL_BUCKET_ARN`
+
+as well as `s3:GetObject` on the `RootMail/*` objects in the created Rootmail `S3` bucket. 
+
+```ts
+import { S3 } from '@aws-sdk/client-s3';
+import { ParsedMail, simpleParser } from 'mailparser';
+// populated by default
+const emailBucket = process.env.EMAIL_BUCKET;
+const emailBucketArn = process.env.EMAIL_BUCKET_ARN;
+const s3 = new S3();
+
+// SESEventRecordsToLambda
+// from https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-lambda-event.html
+export const handler = async (event: SESEventRecordsToLambda) => {
+    for (const record of event.Records) {
+        
+        const id = record.ses.mail.messageId;
+        const key = `RootMail/${id}`;
+        const response = await s3.getObject({ Bucket: emailBucket as string, Key: key });
+        
+        const msg: ParsedMail = await simpleParser(response.Body as unknown as Buffer);
+        
+        let title = msg.subject;
+        console.log(`Title: ${title} from emailBucketArn: ${emailBucketArn}`);
+        // use the content of the email body 
+        const body = msg.html;
+        // add your custom code here ...
+
+        // dummy example: list s3 buckets
+        const buckets = await s3.listBuckets({});
+        if (!buckets.Buckets) {
+            console.log('No buckets found');
+            return;
+        }
+        console.log('Buckets:');
+        for (const bucket of buckets.Buckets || []) {
+            console.log(bucket.Name);
+        }
+    }
+
+};
+```
+
+```ts
+const customSesReceiveFunction = new NodejsFunction(stackUnderTest, 'custom-ses-receive-function', {
+  functionName: PhysicalName.GENERATE_IF_NEEDED,
+  entry: path.join(__dirname, 'functions', 'custom-ses-receive-function.ts'),
+  runtime: lambda.Runtime.NODEJS_18_X,
+  logRetention: 1,
+  timeout: Duration.seconds(30),
+});
+
+// Note: any additional permissions you need to add to the function yourself!
+customSesReceiveFunction.addToRolePolicy(new iam.PolicyStatement({
+  actions: [
+    's3:List*',
+  ],
+  resources: ['*'],
+}))
+```
+
 #### Cloudformation
 or use it directly a Cloudformation template `yaml` from the URL [here](https://mvc-test4-bucket-eu-west-1.s3.eu-west-1.amazonaws.com/rootmail/0.0.13-DEVELOPMENT/rootmailStack.template.yaml).
 

package/integ-tests/functions/custom-ses-receive-function.ts

@@ -0,0 +1,92 @@
+import { S3 } from '@aws-sdk/client-s3';
+import { ParsedMail, simpleParser } from 'mailparser';
+// from https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-lambda-event.html
+export interface EventRecord {
+    eventSource: string;
+    eventVersion: string;
+    ses: Ses;
+}
+
+export interface Ses {
+    mail: Mail;
+    receipt: Receipt;
+}
+
+export interface Mail {
+    timestamp: string;
+    source: string;
+    messageId: string;
+    destination: string[];
+    headersTruncated: boolean;
+    headers: Header[];
+    commonHeaders: CommonHeaders;
+}
+
+export interface Header {
+    name: string;
+    value: string;
+}
+
+export interface CommonHeaders {
+    returnPath: string;
+    from: string[];
+    date: string;
+    to: string[];
+    messageId: string;
+    subject: string;
+}
+
+export interface Receipt {
+    timestamp: string;
+    processingTimeMillis: number;
+    recipients: string[];
+    spamVerdict: Verdict;
+    virusVerdict: Verdict;
+    spfVerdict: Verdict;
+    dkimVerdict: Verdict;
+    dmarcVerdict: Verdict;
+    action: Action;
+}
+
+export interface Verdict {
+    status: string;
+}
+
+export interface Action {
+    type: string;
+    functionArn: string;
+    invocationType: string;
+}
+
+export interface SESEventRecordsToLambda {
+    Records: EventRecord[];
+}
+
+const emailBucket = process.env.EMAIL_BUCKET;
+const emailBucketArn = process.env.EMAIL_BUCKET_ARN;
+const s3 = new S3();
+
+export const handler = async (event: SESEventRecordsToLambda) => {
+    for (const record of event.Records) {
+        
+        const id = record.ses.mail.messageId;
+        const key = `RootMail/${id}`;
+        const response = await s3.getObject({ Bucket: emailBucket as string, Key: key });
+        
+        const msg: ParsedMail = await simpleParser(response.Body as unknown as Buffer);
+        
+        let title = msg.subject;
+        console.log(`Title: ${title} from emailBucketArn: ${emailBucketArn}`);
+    }
+
+    // test custom permission to list s3 buckets
+    const buckets = await s3.listBuckets({});
+    if (!buckets.Buckets) {
+        console.log('No buckets found');
+        return;
+    }
+    console.log('Buckets:');
+    for (const bucket of buckets.Buckets || []) {
+        console.log(bucket.Name);
+    }
+};