@lambda-kata/cdk 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,169 @@
+# @lambda-kata/cdk
+
+AWS CDK integration for Lambda Kata - Transform Node.js Lambda functions to run via the Lambda Kata runtime.
+
+## Installation
+
+```bash
+npm install @lambda-kata/cdk
+```
+
+## Quick Start
+
+```typescript
+import { kata } from '@lambda-kata/cdk';
+import { NodejsFunction } from 'aws-cdk-lib/aws-lambda-nodejs';
+import { Stack, StackProps } from 'aws-cdk-lib';
+import { Construct } from 'constructs';
+
+export class MyStack extends Stack {
+  constructor(scope: Construct, id: string, props?: StackProps) {
+    super(scope, id, props);
+
+    const myFunction = new NodejsFunction(this, 'MyFunction', {
+      entry: 'src/handler.ts',
+    });
+
+    // Transform to use Lambda Kata runtime
+    kata(myFunction);
+  }
+}
+```
+
+## How It Works
+
+The `kata()` wrapper transforms your Node.js Lambda function to run via the Lambda Kata runtime:
+
+1. **Runtime Change**: Switches from Node.js to Python 3.12
+2. **Handler Update**: Sets handler to `lambdakata.optimized_handler.lambda_handler`
+3. **Layer Attachment**: Attaches the customer-specific Lambda Kata Layer
+4. **Config Layer**: Creates a config layer with handler path at `/opt/.kata/original_handler.json`
+
+Your original JavaScript/TypeScript code remains unchanged - the Lambda Kata runtime executes it through an embedded Node.js engine.
+
+## Custom Handler Resolution
+
+Lambda Kata supports two ways to customize how handlers are resolved:
+
+### Option 1: Inline Handler Resolver (Recommended)
+
+Write the resolver function directly in your CDK code:
+
+```typescript
+kata(myFunction, {
+  handlerResolver: (bundle, ctx) => {
+    const handlerName = ctx.originalHandler.split('.').pop() as string;
+    return (bundle as Record<string, Function>)[handlerName];
+  },
+});
+```
+
+The function is:
+1. Serialized to a temporary TypeScript file
+2. Compiled with esbuild
+3. Included in the config layer as `/opt/.kata/middleware.js`
+
+**Use cases:**
+- Handler wrapping with logging/metrics
+- Environment-based handler selection
+- Multi-handler routing
+
+**Example with logging wrapper:**
+
+```typescript
+kata(myFunction, {
+  handlerResolver: (bundle, ctx) => {
+    const handlerName = ctx.originalHandler.split('.').pop() as string;
+    const originalHandler = (bundle as Record<string, Function>)[handlerName];
+
+    // Wrap with logging
+    return async (event: unknown, lambdaCtx: unknown) => {
+      console.log('Invocation started', { handler: handlerName });
+      const start = Date.now();
+      try {
+        const result = await originalHandler(event, lambdaCtx);
+        console.log('Invocation completed', { durationMs: Date.now() - start });
+        return result;
+      } catch (error) {
+        console.error('Invocation failed', { error });
+        throw error;
+      }
+    };
+  },
+});
+```
+
+### Option 2: Middleware File
+
+For complex middleware logic, use a separate TypeScript file:
+
+```typescript
+kata(myFunction, {
+  middlewarePath: path.join(__dirname, 'middleware.ts'),
+});
+```
+
+See [Middleware Example](./examples/middleware-example/README.md) for details.
+
+## Handler Resolver Function Signature
+
+```typescript
+type HandlerResolver = (
+  bundle: unknown,
+  context: { originalHandler: string }
+) => Function;
+```
+
+| Parameter | Description |
+|-----------|-------------|
+| `bundle` | The loaded JavaScript bundle (result of `require()`) |
+| `context.originalHandler` | The original handler path (e.g., `"index.handler"`) |
+| **Returns** | The handler function to invoke |
+
+**Important:** The function must be pure (no closures over external CDK variables) because it's serialized via `.toString()`.
+
+## API Reference
+
+### `kata(lambda, options?)`
+
+Transforms a Node.js Lambda function to use Lambda Kata runtime.
+
+**Parameters:**
+
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `lambda` | `NodejsFunction \| Function` | The Lambda function to transform |
+| `options` | `KataWrapperOptions` | Optional configuration |
+
+**Options:**
+
+| Option | Type | Description |
+|--------|------|-------------|
+| `unlicensedBehavior` | `'warn' \| 'fail'` | Behavior when account is not licensed. Default: `'warn'` |
+| `bundlePath` | `string` | Custom path to JavaScript bundle |
+| `middlewarePath` | `string` | Path to middleware TypeScript/JavaScript file |
+| `handlerResolver` | `Function` | Inline handler resolver function |
+
+**Note:** `middlewarePath` and `handlerResolver` are mutually exclusive.
+
+## Requirements
+
+- AWS CDK v2
+- Node.js 18+
+- Valid AWS Marketplace subscription for Lambda Kata
+
+## Examples
+
+See the [examples](./examples) directory:
+
+- [Basic Usage](./examples/example-stack.ts) - Simple kata() transformation
+- [Middleware Example](./examples/middleware-example) - Custom handler resolution with middleware file
+- [Config Layer Example](./examples/config-layer-example) - Handler path configuration
+
+## Contributing
+
+**Security:** Report vulnerabilities privately to [raman@worktif.com](mailto:raman@worktif.com)
+
+## License
+
+Apache-2.0

package/lib/account-resolver.d.ts

@@ -0,0 +1,103 @@
+/**
+ * Account ID Resolution for Lambda Kata CDK Integration
+ *
+ * This module provides functionality to determine the target AWS account ID
+ * during CDK synthesis/deploy time. The account ID is required for validating
+ * AWS Marketplace entitlements.
+ *
+ * Resolution strategies (in order of precedence):
+ * 1. CDK context value (explicit configuration)
+ * 2. Stack account (if not a token/unresolved)
+ * 3. STS GetCallerIdentity (fallback for runtime resolution)
+ *
+ * @module account-resolver
+ */
+import { Construct } from 'constructs';
+import { STSClient } from '@aws-sdk/client-sts';
+/**
+ * Error thrown when account ID cannot be resolved through any strategy.
+ */
+export declare class AccountResolutionError extends Error {
+    constructor(message: string);
+}
+/**
+ * Result of account ID resolution, including the source of the resolution.
+ */
+export interface AccountResolutionResult {
+    /**
+     * The resolved AWS account ID (12-digit string)
+     */
+    accountId: string;
+    /**
+     * The source/strategy that successfully resolved the account ID
+     */
+    source: 'context' | 'stack' | 'sts';
+}
+/**
+ * Options for account ID resolution.
+ */
+export interface AccountResolverOptions {
+    /**
+     * Custom STS client for testing or custom configuration.
+     * If not provided, a default client will be created.
+     */
+    stsClient?: STSClient;
+    /**
+     * Whether to skip the STS fallback (useful for testing).
+     * Default: false
+     */
+    skipStsFallback?: boolean;
+}
+/**
+ * Resolves the target AWS account ID for entitlement checking.
+ *
+ * This function attempts to determine the AWS account ID using multiple
+ * strategies in order of precedence:
+ *
+ * 1. **CDK Context**: Checks for `aws:cdk:account` context value
+ * 2. **Stack Account**: Uses the Stack's account if it's not a token
+ * 3. **STS Fallback**: Calls STS GetCallerIdentity as a last resort
+ *
+ * @param scope - The CDK construct scope to resolve the account for
+ * @param options - Optional configuration for resolution behavior
+ * @returns Promise resolving to the AWS account ID (12-digit string)
+ * @throws AccountResolutionError if account cannot be resolved through any strategy
+ *
+ * @example
+ * ```typescript
+ * const accountId = await resolveAccountId(this);
+ * console.log(`Deploying to account: ${accountId}`);
+ * ```
+ *
+ * @remarks
+ * Validates: Requirements 3.1
+ * - WHEN `cdk deploy` is executed, THE kata_Wrapper SHALL determine the target AWS account ID
+ */
+export declare function resolveAccountId(scope: Construct, options?: AccountResolverOptions): Promise<string>;
+/**
+ * Resolves the target AWS account ID with information about the resolution source.
+ *
+ * This is an extended version of `resolveAccountId` that also returns
+ * information about which strategy was used to resolve the account ID.
+ *
+ * @param scope - The CDK construct scope to resolve the account for
+ * @param options - Optional configuration for resolution behavior
+ * @returns Promise resolving to the account ID and resolution source
+ * @throws AccountResolutionError if account cannot be resolved through any strategy
+ *
+ * @example
+ * ```typescript
+ * const { accountId, source } = await resolveAccountIdWithSource(this);
+ * console.log(`Account ${accountId} resolved via ${source}`);
+ * ```
+ */
+export declare function resolveAccountIdWithSource(scope: Construct, options?: AccountResolverOptions): Promise<AccountResolutionResult>;
+/**
+ * Validates that a string is a valid AWS account ID format.
+ *
+ * AWS account IDs are exactly 12 digits.
+ *
+ * @param accountId - The string to validate
+ * @returns true if the string is a valid 12-digit account ID
+ */
+export declare function isValidAccountIdFormat(accountId: string): boolean;

package/lib/config-layer.d.ts

@@ -0,0 +1,168 @@
+/**
+ * Config Layer Generator for Lambda Kata CDK Integration
+ *
+ * This module provides functionality to create a Lambda Layer containing
+ * the kata configuration. The configuration includes the original Node.js
+ * handler path, which the Lambda Kata runtime reads during initialization.
+ *
+ * The config layer replaces the JS_HANDLER_PATH environment variable approach,
+ * providing cleaner separation between runtime configuration and environment variables.
+ *
+ * @module config-layer
+ */
+import { Construct } from 'constructs';
+import { LayerVersion } from 'aws-cdk-lib/aws-lambda';
+/**
+ * Configuration for the kata config layer.
+ *
+ * @example
+ * ```typescript
+ * const props: KataConfigLayerProps = {
+ *   originalHandler: 'bundle.handler'
+ * };
+ * ```
+ *
+ * @example
+ * ```typescript
+ * // With custom bundle path and middleware
+ * const props: KataConfigLayerProps = {
+ *   originalHandler: 'index.handler',
+ *   bundlePath: '/var/task/index.js',
+ *   middlewarePath: './middleware.ts'
+ * };
+ * ```
+ */
+export interface KataConfigLayerProps {
+    /**
+     * The original Node.js handler path (e.g., "bundle.handler").
+     *
+     * This value will be stored in the config layer and read by the
+     * Lambda Kata runtime during initialization.
+     *
+     * Format: "<module>.<function>" or "<path/module>.<function>"
+     * Examples: "bundle.handler", "src/index.handler", "dist/main.handler"
+     */
+    originalHandler: string;
+    /**
+     * Path to the JavaScript bundle.
+     *
+     * When specified, the Lambda Kata runtime will load the bundle from this path
+     * instead of the default location. This allows using custom project layouts
+     * where the bundle is located in a different directory.
+     *
+     * If not specified, defaults to /opt/js_runtime/bundle.js
+     *
+     * @example "/var/task/index.js"
+     * @example "/var/task/dist/bundle.js"
+     *
+     * @remarks
+     * Validates: Requirement 4.1
+     */
+    bundlePath?: string;
+    /**
+     * Path to the middleware TypeScript/JavaScript source file.
+     *
+     * When specified, the middleware file will be compiled with esbuild and
+     * included in the config layer at /opt/.kata/middleware.js. The middleware
+     * module must export a function with signature: (bundle, context) => handler
+     *
+     * The context parameter includes:
+     * - originalHandler: The handler path (e.g., "index.handler")
+     *
+     * @example "./middleware.ts"
+     * @example "./src/custom-resolver.js"
+     *
+     * @remarks
+     * Validates: Requirement 5.1
+     */
+    middlewarePath?: string;
+    /**
+     * Inline handler resolver function.
+     *
+     * When specified, this function will be serialized to a temporary TypeScript file,
+     * compiled with esbuild, and included in the config layer at /opt/.kata/middleware.js.
+     *
+     * The function receives the loaded bundle and context with originalHandler,
+     * and must return the handler function.
+     *
+     * Note: The function must be pure (no closures over external variables)
+     * because it will be serialized via .toString()
+     *
+     * Cannot be used together with middlewarePath.
+     *
+     * @example
+     * ```typescript
+     * handlerResolver: (bundle, ctx) => {
+     *   const handlerName = ctx.originalHandler.split('.').pop();
+     *   return bundle[handlerName];
+     * }
+     * ```
+     */
+    handlerResolver?: (bundle: unknown, context: {
+        originalHandler: string;
+    }) => Function;
+}
+/**
+ * The path where the config file will be located in the Lambda Layer.
+ * When the layer is attached to a Lambda, this file will be at /opt/.kata/original_handler.json
+ */
+export declare const CONFIG_DIR_NAME = ".kata";
+/**
+ * The name of the config file within the .kata directory.
+ */
+export declare const CONFIG_FILE_NAME = "original_handler.json";
+/**
+ * The key used in the JSON config file to store the handler path.
+ */
+export declare const HANDLER_CONFIG_KEY = "original_js_handler";
+/**
+ * The name of the compiled middleware file within the .kata directory.
+ */
+export declare const MIDDLEWARE_FILE_NAME = "middleware.js";
+/**
+ * Creates a Lambda Layer containing the kata configuration.
+ *
+ * The layer contains a single JSON file at /opt/.kata/original_handler.json
+ * with the original handler path. This file is read by the Lambda Kata
+ * runtime during initialization to determine which JavaScript handler to invoke.
+ *
+ * @param scope - The CDK construct scope
+ * @param id - The unique identifier for this layer within the scope
+ * @param props - Configuration properties including the original handler path
+ * @returns A LayerVersion construct containing the configuration
+ *
+ * @example
+ * ```typescript
+ * import { createKataConfigLayer } from './config-layer';
+ *
+ * const configLayer = createKataConfigLayer(this, 'KataConfigLayer', {
+ *   originalHandler: 'bundle.handler'
+ * });
+ *
+ * myFunction.addLayers(configLayer);
+ * ```
+ *
+ * @remarks
+ * Validates: Requirements 1.1, 1.2, 1.3, 3.1, 3.2, 3.5
+ */
+export declare function createKataConfigLayer(scope: Construct, id: string, props: KataConfigLayerProps): LayerVersion;
+/**
+ * Generates the JSON configuration content for the config layer.
+ *
+ * This function creates a properly formatted JSON string containing
+ * the original handler path. The output is formatted with 2-space
+ * indentation for readability.
+ *
+ * @param originalHandler - The original Node.js handler path
+ * @returns The JSON configuration content as a string
+ *
+ * @example
+ * ```typescript
+ * const content = generateConfigContent('bundle.handler');
+ * // Returns: '{\n  "original_js_handler": "bundle.handler"\n}'
+ * ```
+ *
+ * @remarks
+ * Validates: Requirements 1.2, 3.2
+ */
+export declare function generateConfigContent(originalHandler: string): string;

package/lib/index.d.ts

@@ -0,0 +1,25 @@
+/**
+ * @lambda-kata/cdk - AWS CDK integration for Lambda Kata
+ *
+ * This package provides CDK constructs to transform Node.js Lambda functions
+ * to run via the Lambda Kata runtime.
+ *
+ * @example
+ * ```typescript
+ * import { kata } from '@lambda-kata/cdk';
+ * import { NodejsFunction } from 'aws-cdk-lib/aws-lambda-nodejs';
+ *
+ * const myFunction = new NodejsFunction(this, 'MyFunction', {
+ *   entry: 'src/handler.ts',
+ * });
+ *
+ * // Transform to use Lambda Kata runtime
+ * kata(myFunction);
+ * ```
+ */
+export { KataProps, LicensingResponse, TransformationConfig } from './types';
+export { LicensingService, HttpLicensingService, createLicensingService, isValidAccountId, } from './licensing';
+export { MockLicensingService, createMockLicensingService, } from './mock-licensing';
+export { resolveAccountId, resolveAccountIdWithSource, isValidAccountIdFormat, AccountResolutionError, AccountResolutionResult, AccountResolverOptions, } from './account-resolver';
+export { kata, kataWithAccountId, applyTransformation, handleUnlicensed, isKataTransformed, getKataPromise, KataWrapperOptions, KataResult, } from './kata-wrapper';
+export { createKataConfigLayer, generateConfigContent, KataConfigLayerProps, CONFIG_DIR_NAME, CONFIG_FILE_NAME, HANDLER_CONFIG_KEY, } from './config-layer';