@aws/nx-plugin-mcp 1.0.0-rc.0 → 1.0.0-rc.10

package/docs/guides/typescript-project.mdx

@@ -11,7 +11,7 @@ import NxCommands from '@components/nx-commands.astro';
 import PackageManagerShortCommand from '@components/package-manager-short-command.astro';
 import Link from '@components/link.astro';
 
-The TypeScript project generator can be used to create a modern [TypeScript](https://www.typescriptlang.org/) library or application configured with best practices such as [ECMAScript Modules (ESM)](https://www.typescriptlang.org/docs/handbook/modules/reference.html), TypeScript [project references](https://www.typescriptlang.org/docs/handbook/project-references.html), [Vitest](https://vitest.dev/) for running tests and [ESLint](https://eslint.org/) for static analysis.
+The TypeScript project generator can be used to create a modern [TypeScript](https://www.typescriptlang.org/) library or application configured with best practices such as [ECMAScript Modules (ESM)](https://www.typescriptlang.org/docs/handbook/modules/reference.html), TypeScript [project references](https://www.typescriptlang.org/docs/handbook/project-references.html), [Vitest](https://vitest.dev/) for running tests and [Biome](https://biomejs.dev/) for linting and formatting.
 
 ## Usage
 
@@ -38,7 +38,6 @@ The generator will create the following project structure in the `<directory>/<n
   - tsconfig.lib.json TypeScript configuration for your library (your runtime or packaged source)
   - tsconfig.spec.json TypeScript configuration for your tests
   - vitest.config.mts Configuration for Vitest
-  - eslint.config.mjs Configuration for ESLint
 
 </FileTree>
 
@@ -198,7 +197,7 @@ If you're building an AWS Lambda function, check out the <Link path="/guides/ts-
 
 If you are publishing your TypeScript project to NPM, you must create a `package.json` file for it.
 
-This must declare the dependencies that your project references. Since at build time your project will resolve dependencies installed via the workspace root `package.json`, it's recommended to configure the [Nx Dependency Checks ESLint Plugin](https://nx.dev/nx-api/eslint-plugin/documents/dependency-checks) to ensure that your published project's `package.json` includes all dependencies you use in your project.
+This must declare the dependencies that your project references. Since at build time your project will resolve dependencies installed via the workspace root `package.json`, Biome's `noUndeclaredDependencies` rule will warn you if your project imports a package that isn't listed in its `package.json`.
 
 ### Building
 
@@ -269,11 +268,7 @@ If you are a VSCode user, we recommend installing the [Vitest Runner for VSCode
 
 ## Linting
 
-TypeScript projects use [ESLint](https://eslint.org/) for linting, along with [Prettier](https://prettier.io/) for formatting.
-
-We recommend configuring ESLint in the workspace root `eslint.config.mjs` file, as changes to this will apply to all TypeScript projects in your workspace and ensure consistency.
-
-Likewise, you can configure Prettier in the root `.prettierrc` file.
+TypeScript projects use [Biome](https://biomejs.dev/) for linting and formatting. Biome is configured in the workspace root `biome.json` file — changes to this apply to all TypeScript projects in your workspace and ensure consistency.
 
 ### Running the Linter
 
@@ -283,7 +278,7 @@ To invoke the linter to check your project, you can run the `lint` target.
 
 ### Fixing Lint Issues
 
-The majority of linting or formatting issues can be fixed automatically. You can tell ESLint to fix lint issues by running with the `--configuration=fix` argument.
+The majority of linting or formatting issues can be fixed automatically by running with the `--configuration=fix` argument.
 
 <NxCommands commands={["lint <project-name> --configuration=fix"]} />
 
@@ -303,7 +298,7 @@ To avoid linting issues slowing you down during development (particularly if you
 
 <NxCommands commands={["run-many --target build --configuration=skip-lint"]} />
 
-This will still run ESLint as part of the build, but the lint target will always be considered successful.
+This skips the lint target entirely during build.
 
 :::tip[Shorthand Command]
 This has a shorthand command from the root of your workspace:

package/docs/guides/workspace.mdx

@@ -29,6 +29,12 @@ When you create a new workspace with `@aws/nx-plugin`, the preset generator sets
   - aws-nx-plugin.config.mts Nx Plugin for AWS configuration
   - .git-secrets/ Vendored git-secrets bash script for credential scanning
   - .husky/ Git hooks
+  - .mcp.json Nx Plugin for AWS MCP server configuration for Claude Code
+  - .cursor/mcp.json ...and for Cursor
+  - .kiro/settings/mcp.json ...and for Kiro
+  - .gemini/settings.json ...and for Gemini CLI
+  - .vscode/mcp.json ...and for GitHub Copilot
+  - .codex/config.toml ...and for OpenAI Codex
 </FileTree>
 
 ## Nx
@@ -128,7 +134,7 @@ This will run the chosen target as well as the targets it depends on.
 
 ### Linting
 
-New workspaces are configured with [ESLint](https://eslint.org/) for static analysis and [Prettier](https://prettier.io/) for code formatting. Running `lint` applies both to all projects.
+New workspaces are configured with [Biome](https://biomejs.dev/) for static analysis and code formatting. Running `lint` checks all projects for issues, and `lint --configuration=fix` auto-fixes them.
 
 ### Git Secrets
 
@@ -167,7 +173,7 @@ import { AwsNxPluginConfig } from '@aws/nx-plugin';
 
 export default {
   iac: {
-    provider: 'CDK', // or 'Terraform'
+    provider: 'cdk', // or 'terraform'
   },
   containers: {
     engine: 'docker', // or 'finch'
@@ -175,7 +181,7 @@ export default {
 } satisfies AwsNxPluginConfig;
 ```
 
-- **`iac.provider`** — the default infrastructure-as-code provider (`CDK` or `Terraform`) used by generators that emit infrastructure (e.g. `ts#infra`, `ts#trpc-api`, `py#fast-api`). Generators that accept an `--iacProvider` flag default to `Inherit`, which reads this value.
+- **`iac.provider`** — the default infrastructure-as-code provider (`cdk` or `terraform`) used by generators that emit infrastructure (e.g. `ts#infra`, `ts#api`, `py#api`). Generators that accept an `--iac` flag default to `inherit`, which reads this value.
 - **`containers.engine`** — the container CLI (`docker` or `finch`) baked into generated build/push/login commands. CDK image-asset builds also pick this up via the `CDK_DOCKER` environment variable. See the <Link path="guides/docker-bundling">Docker bundling guide</Link> for details.
 
 You can edit either setting at any time — subsequent generator runs will pick up the new value.

package/docs/snippets/agent/architecture.mdx

@@ -3,8 +3,8 @@ title: Agent Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 
-<Tabs syncKey="computeType">
-<TabItem label="Bedrock AgentCore Runtime" _filter={{ computeType: 'BedrockAgentCoreRuntime' }}>
+<Tabs syncKey="infra">
+<TabItem label="Bedrock AgentCore Runtime" _filter={{ infra: 'agentcore' }}>
 
 When deployed to [Bedrock AgentCore Runtime](https://aws.amazon.com/bedrock/agentcore/), the agent is built into a container image, pushed to Amazon ECR and run in AgentCore Runtime. Clients invoke the AgentCore Runtime data plane endpoint, which forwards requests to your agent. The agent calls Amazon Bedrock for model inference and may invoke tools, MCP servers, or downstream APIs.
 
@@ -44,9 +44,9 @@ agentcore -> bedrock: InvokeModel
 agentcore -> cw
 ```
 </TabItem>
-<TabItem label="None (local only)" _filter={{ computeType: 'None' }}>
+<TabItem label="None (local only)" _filter={{ infra: 'none' }}>
 
-With `computeType: None`, no AWS infrastructure is generated. The agent runs as a local process and calls Amazon Bedrock for model inference.
+With `infra: none`, no AWS infrastructure is generated. The agent runs as a local process and calls Amazon Bedrock for model inference.
 
 ```d2 inline=true
 direction: right

package/docs/snippets/agent/bedrock-deployment.mdx

@@ -6,7 +6,7 @@ import Infrastructure from '@components/infrastructure.astro';
 
 ### Infrastructure as Code
 
-If you selected `BedrockAgentCoreRuntime` for `computeType`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your Agent to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
+If you selected `agentcore` for `infra`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your Agent to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
 
 <Infrastructure>
 <Fragment slot="cdk">

package/docs/snippets/api/api-architecture.mdx

@@ -6,7 +6,7 @@ import { Tabs, TabItem } from '@astrojs/starlight/components';
 The deployed application has the following architecture:
 
 <Tabs syncKey="http-rest">
-<TabItem label="REST API" _filter={{ computeType: 'ServerlessApiGatewayRestApi' }}>
+<TabItem label="REST API" _filter={{ infra: 'rest-lambda' }}>
 ```d2 inline=true
 direction: right
 
@@ -51,7 +51,7 @@ lambda -> xray
 
 REST APIs include an [AWS WAFv2](https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html) Web ACL in front of the API Gateway stage with the AWS managed default ruleset enabled.
 </TabItem>
-<TabItem label="HTTP API" _filter={{ computeType: 'ServerlessApiGatewayHttpApi' }}>
+<TabItem label="HTTP API" _filter={{ infra: 'http-lambda' }}>
 ```d2 inline=true
 direction: right
 

package/docs/snippets/api/type-safe-api-integrations.mdx

@@ -306,7 +306,7 @@ Edit `packages/common/terraform/src/app/apis/my-api/my-api.tf`:
 3. **Create specific integrations and routes** for each operation, reusing the same ZIP bundle:
 
 <Tabs syncKey="http-rest">
-<TabItem label="HTTP API" _filter={{ computeType: 'ServerlessApiGatewayHttpApi' }}>
+<TabItem label="HTTP API" _filter={{ infra: 'http-lambda' }}>
 
 ```diff
 # packages/common/terraform/src/app/apis/my-api/my-api.tf
@@ -429,7 +429,7 @@ Edit `packages/common/terraform/src/app/apis/my-api/my-api.tf`:
 + }
 ```
 </TabItem>
-<TabItem label="REST API" _filter={{ computeType: 'ServerlessApiGatewayRestApi' }}>
+<TabItem label="REST API" _filter={{ infra: 'rest-lambda' }}>
 
 ```diff
 # packages/common/terraform/src/app/apis/my-api/my-api.tf

package/docs/snippets/connection/dynamodb-local-development.mdx

@@ -0,0 +1,7 @@
+---
+title: DynamoDB Local Development
+---
+
+The `connection` generator configures your project's `serve-local` target to depend on the DynamoDB project's `serve-local` target. DynamoDB Local will start automatically alongside your project when running `serve-local`.
+
+The `SERVE_LOCAL=true` environment variable is set automatically, so `getDynamoDBClient()` and `resolveTableName()` connect to the local DynamoDB Local instance instead of AWS.

package/docs/snippets/connection/lambda-dynamodb-access.mdx

@@ -0,0 +1,80 @@
+---
+title: Lambda DynamoDB Access
+---
+import Infrastructure from '@components/infrastructure.astro';
+
+To allow Lambda functions to access the DynamoDB table, grant the necessary permissions in your infrastructure.
+
+<Infrastructure>
+<Fragment slot="cdk">
+
+Call `grantReadWriteData` on the table construct. This grants both the DynamoDB and KMS permissions required by the Lambda execution role:
+
+```ts title="packages/infra/src/stacks/application-stack.ts"
+import { MyTable } from ':my-scope/common-constructs';
+
+const table = new MyTable(this, 'Table');
+
+const api = new Api(this, 'Api', {
+  integrations: Api.defaultIntegrations(this).build(),
+});
+
+Object.entries(api.integrations).forEach(([, integration]) => {
+  table.grantReadWriteData(integration.handler);
+});
+```
+
+:::note
+This example grants every handler in your API access. If only some handlers need access, configure them individually.
+:::
+</Fragment>
+<Fragment slot="terraform">
+
+Grant the Lambda execution role permission to access the DynamoDB table and its KMS encryption key:
+
+```hcl title="packages/infra/src/main.tf"
+module "my_table" {
+  source = "../../common/terraform/src/app/dynamodb/my-table"
+}
+
+resource "aws_iam_role_policy" "dynamodb_access" {
+  role = module.my_api.lambda_role_name
+
+  policy = jsonencode({
+    Version = "2012-10-17"
+    Statement = [
+      {
+        Effect = "Allow"
+        Action = [
+          "dynamodb:GetItem",
+          "dynamodb:PutItem",
+          "dynamodb:UpdateItem",
+          "dynamodb:DeleteItem",
+          "dynamodb:Query",
+          "dynamodb:Scan",
+          "dynamodb:BatchGetItem",
+          "dynamodb:BatchWriteItem",
+        ]
+        Resource = [
+          module.my_table.table_arn,
+          "${module.my_table.table_arn}/index/*",
+        ]
+      },
+      {
+        Effect = "Allow"
+        Action = [
+          "kms:Encrypt",
+          "kms:Decrypt",
+          "kms:ReEncrypt*",
+          "kms:GenerateDataKey*",
+          "kms:DescribeKey"
+        ]
+        Resource = [module.my_table.kms_key_arn]
+      },
+    ]
+  })
+}
+```
+
+</Fragment>
+</Infrastructure>

package/docs/snippets/lambda-function/deploying-your-function.mdx

@@ -30,7 +30,7 @@ This sets up:
 This function can then be used as a target for any lambda [event source](https://docs.powertools.aws.dev/lambda/typescript/latest/utilities/parser/):
 
 :::note[Event Source Matching]
-Ensure the event source matches the selected `eventSource` option to ensure the event is properly handled within your handler function.
+Ensure the event source matches the selected `event` option to ensure the event is properly handled within your handler function.
 :::
 
 The example below demonstrates the CDK code for invoking your lambda function on a schedule using EventBridge:
@@ -112,7 +112,7 @@ resource "aws_lambda_permission" "allow_eventbridge" {
 ```
 
 :::note[Event Source Matching]
-Ensure the event source matches the selected `eventSource` option to ensure the event is properly handled within your handler function.
+Ensure the event source matches the selected `event` option to ensure the event is properly handled within your handler function.
 :::
 </Fragment>
 </Infrastructure>

package/docs/snippets/mcp/architecture.mdx

@@ -3,8 +3,8 @@ title: MCP Server Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
 
-<Tabs syncKey="computeType">
-<TabItem label="Bedrock AgentCore Runtime" _filter={{ computeType: 'BedrockAgentCoreRuntime' }}>
+<Tabs syncKey="infra">
+<TabItem label="Bedrock AgentCore Runtime" _filter={{ infra: 'agentcore' }}>
 
 When deployed to [Bedrock AgentCore Runtime](https://aws.amazon.com/bedrock/agentcore/), the MCP server is built into a container image, pushed to Amazon ECR, and run in AgentCore Runtime. AI assistants invoke the AgentCore Runtime data plane endpoint, which forwards `tools/*` and `resources/*` calls to your server over the [streamable HTTP transport](https://modelcontextprotocol.io/specification/draft/basic/transports#streamable-http).
 
@@ -36,9 +36,9 @@ ecr -> agentcore: Container\nimage
 agentcore -> cw
 ```
 </TabItem>
-<TabItem label="None (local only)" _filter={{ computeType: 'None' }}>
+<TabItem label="None (local only)" _filter={{ infra: 'none' }}>
 
-With `computeType: None`, no AWS infrastructure is generated. The MCP server is configured for local STDIO and HTTP transports only, and is consumed by AI assistants running on the same machine.
+With `infra: none`, no AWS infrastructure is generated. The MCP server is configured for local STDIO and HTTP transports only, and is consumed by AI assistants running on the same machine.
 
 ```d2 inline=true
 direction: right

package/docs/snippets/mcp/bedrock-deployment.mdx

@@ -6,7 +6,7 @@ import Infrastructure from '@components/infrastructure.astro';
 
 ### Infrastructure as Code
 
-If you selected `BedrockAgentCoreRuntime` for `computeType`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your MCP server to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
+If you selected `agentcore` for `infra`, the relevant CDK or Terraform infrastructure is generated which you can use to deploy your MCP server to [Amazon Bedrock AgentCore Runtime](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/agents-tools-runtime.html).
 
 <Infrastructure>
 <Fragment slot="cdk">

package/docs/snippets/mcp/config.mdx

@@ -6,7 +6,7 @@ title: MCP Server Configuration
   "mcpServers": {
     "nx-plugin-for-aws": {
       "command": "npx",
-      "args": ["-y", "@aws/nx-plugin-mcp"]
+      "args": ["-y", "@aws/nx-plugin-mcp@next"]
     }
   }
 }

package/docs/snippets/required-prerequisites.mdx

@@ -4,7 +4,7 @@ title: Required Prerequisites
 - [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
 - [Node >= 22](https://nodejs.org/en/download) (We recommend using something like [NVM](https://github.com/nvm-sh/nvm) to manage your node versions)
   - verify by running `node --version`
-- [PNPM >= 10](https://pnpm.io/installation#using-npm) (you can also use [Yarn >= 4](https://yarnpkg.com/getting-started/install), [Bun >= 1](https://bun.sh/docs/installation), or [NPM >= 10](https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager) if you prefer)
+- [PNPM >= 11](https://pnpm.io/installation#using-npm) (you can also use [Yarn >= 4](https://yarnpkg.com/getting-started/install), [Bun >= 1](https://bun.sh/docs/installation), or [NPM >= 10](https://nodejs.org/en/learn/getting-started/an-introduction-to-the-npm-package-manager) if you prefer)
   - verify by running `pnpm --version`, `yarn --version`, `bun --version` or `npm --version`
 - [UV >= 0.5.29](https://docs.astral.sh/uv/getting-started/installation/)
   1. install Python 3.14 by running: `uv python install 3.14.0`

package/generators.json

@@ -100,7 +100,8 @@
       "factory": "./src/py/mcp-server/generator",
       "schema": "./src/py/mcp-server/schema.json",
       "description": "Generate a Python Model Context Protocol (MCP) server for providing context to Large Language Models",
-      "metric": "g24"
+      "metric": "g24",
+      "guidePages": ["py-mcp-server"]
     },
     "py#project": {
       "factory": "./src/py/project/generator",
@@ -113,7 +114,8 @@
       "factory": "./src/py/agent/generator",
       "schema": "./src/py/agent/schema.json",
       "description": "Add an AI Agent to a Python project",
-      "metric": "g25"
+      "metric": "g25",
+      "guidePages": ["py-agent"]
     },
     "py#agent#mcp-connection": {
       "factory": "./src/py/agent/mcp-connection/generator",
@@ -182,7 +184,8 @@
       "factory": "./src/ts/mcp-server/generator",
       "schema": "./src/ts/mcp-server/schema.json",
       "description": "Generate a TypeScript Model Context Protocol (MCP) server for providing context to Large Language Models",
-      "metric": "g18"
+      "metric": "g18",
+      "guidePages": ["ts-mcp-server"]
     },
     "ts#nx-generator": {
       "factory": "./src/ts/nx-generator/generator",
@@ -252,7 +255,8 @@
       "factory": "./src/ts/agent/generator",
       "schema": "./src/ts/agent/schema.json",
       "description": "Add an AI Agent to a TypeScript project",
-      "metric": "g30"
+      "metric": "g30",
+      "guidePages": ["ts-agent"]
     },
     "ts#agent#mcp-connection": {
       "factory": "./src/ts/agent/mcp-connection/generator",
@@ -315,7 +319,8 @@
       "factory": "./src/ts/rdb/generator",
       "schema": "./src/ts/rdb/schema.json",
       "description": "Create a relational database project",
-      "metric": "g38"
+      "metric": "g38",
+      "guidePages": ["ts-rdb"]
     },
     "ts#rdb#smithy-connection": {
       "factory": "./src/ts/rdb/smithy-connection/generator",
@@ -344,6 +349,40 @@
       "description": "Connect a ts#mcp-server to a ts#rdb project",
       "metric": "g42",
       "hidden": true
+    },
+    "ts#dynamodb": {
+      "factory": "./src/ts/dynamodb/generator",
+      "schema": "./src/ts/dynamodb/schema.json",
+      "description": "Create a DynamoDB project",
+      "metric": "g43"
+    },
+    "ts#dynamodb#trpc-connection": {
+      "factory": "./src/ts/dynamodb/trpc-connection/generator",
+      "schema": "./src/ts/dynamodb/trpc-connection/schema.json",
+      "description": "Connect a ts#trpc-api project to a ts#dynamodb project",
+      "metric": "g44",
+      "hidden": true
+    },
+    "ts#dynamodb#smithy-connection": {
+      "factory": "./src/ts/dynamodb/smithy-connection/generator",
+      "schema": "./src/ts/dynamodb/smithy-connection/schema.json",
+      "description": "Connect a Smithy backend to a ts#dynamodb project",
+      "metric": "g45",
+      "hidden": true
+    },
+    "ts#dynamodb#agent-connection": {
+      "factory": "./src/ts/dynamodb/agent-connection/generator",
+      "schema": "./src/ts/dynamodb/agent-connection/schema.json",
+      "description": "Connect a ts#agent to a ts#dynamodb project",
+      "metric": "g46",
+      "hidden": true
+    },
+    "ts#dynamodb#mcp-server-connection": {
+      "factory": "./src/ts/dynamodb/mcp-server-connection/generator",
+      "schema": "./src/ts/dynamodb/mcp-server-connection/schema.json",
+      "description": "Connect a ts#mcp-server to a ts#dynamodb project",
+      "metric": "g47",
+      "hidden": true
     }
   }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aws/nx-plugin-mcp",
-  "version": "1.0.0-rc.0",
+  "version": "1.0.0-rc.10",
   "repository": {
     "type": "git",
     "url": "https://github.com/awslabs/nx-plugin-for-aws.git",

package/src/infra/app/schema.json

@@ -27,7 +27,7 @@
       "description": "The sub directory the project is placed in. By default this is the project name.",
       "x-prompt": "Which sub directory do you want to create the project in? (By default this is the project name)"
     },
-    "enableStageConfig": {
+    "stageConfig": {
       "description": "Enable centralized stage configuration (credentials, account, region) for multi-environment CDK deployments.",
       "type": "boolean",
       "default": false,

package/src/license/schema.json

@@ -17,6 +17,12 @@
       "description": "The copyright holder, included in the LICENSE file and source file headers by default.",
       "default": "Amazon.com, Inc. or its affiliates",
       "x-priority": "important"
+    },
+    "dependencyCheck": {
+      "type": "boolean",
+      "description": "Configure a license-check target that fails when dependencies declare licenses outside the configured allowlist.",
+      "default": true,
+      "x-priority": "important"
     }
   },
   "required": []

package/src/preset/schema.json

@@ -10,11 +10,11 @@
       "description": "Whether to add the ts plugin.",
       "default": true
     },
-    "iacProvider": {
+    "iac": {
       "type": "string",
       "description": "The preferred IaC provider.",
-      "enum": ["CDK", "Terraform"],
-      "default": "CDK",
+      "enum": ["cdk", "terraform"],
+      "default": "cdk",
       "x-priority": "important",
       "x-prompt": "Which provider would you like to manage your infrastructure?"
     },
@@ -23,7 +23,12 @@
       "description": "Whether to configure git-secrets to prevent committing AWS credentials.",
       "default": true
     },
-    "containerEngine": {
+    "mcp": {
+      "type": "boolean",
+      "description": "Whether to configure the Nx Plugin for AWS MCP server for use by coding agents.",
+      "default": true
+    },
+    "containers": {
       "type": "string",
       "description": "The container engine to use for build/push/login. 'infer' picks docker if installed, otherwise finch (falling back to docker when neither is installed).",
       "enum": ["infer", "docker", "finch"],

package/src/py/agent/schema.json

@@ -15,7 +15,7 @@
       "x-prompt": "Select the Python project to add the Agent to",
       "x-dropdown": "projects"
     },
-    "sdk": {
+    "framework": {
       "type": "string",
       "description": "The agent SDK to use.",
       "x-prompt": "Which agent SDK would you like to use?",
@@ -23,14 +23,6 @@
       "default": "strands",
       "x-priority": "important"
     },
-    "computeType": {
-      "type": "string",
-      "description": "The type of compute to host your Agent.",
-      "x-prompt": "How would you like to host your Agent server?",
-      "enum": ["BedrockAgentCoreRuntime", "None"],
-      "default": "BedrockAgentCoreRuntime",
-      "x-priority": "important"
-    },
     "name": {
       "type": "string",
       "description": "The name of your Agent (default: agent)",
@@ -38,9 +30,9 @@
     },
     "auth": {
       "type": "string",
-      "description": "The method used to authenticate with your Agent. Only applicable when computeType is set (ignored when computeType is None).",
-      "default": "IAM",
-      "enum": ["IAM", "Cognito"],
+      "description": "The method used to authenticate with your Agent. Only applicable when infra is set (ignored when infra is none).",
+      "default": "iam",
+      "enum": ["iam", "cognito"],
       "x-prompt": "How would you like to authenticate with your Agent?",
       "x-priority": "important"
     },
@@ -48,17 +40,25 @@
       "type": "string",
       "description": "The server protocol for your Agent. HTTP exposes a FastAPI HTTP server. A2A exposes an Agent-to-Agent protocol server. AG-UI exposes an Agent-User Interaction protocol server for direct frontend integration.",
       "x-prompt": "Which protocol would you like to use for your Agent?",
-      "enum": ["HTTP", "A2A", "AG-UI"],
-      "default": "HTTP",
+      "enum": ["http", "a2a", "ag-ui"],
+      "default": "http",
       "x-priority": "important"
     },
-    "iacProvider": {
+    "iac": {
       "type": "string",
       "description": "The preferred IaC provider. By default this is inherited from your initial selection.",
-      "enum": ["Inherit", "CDK", "Terraform"],
+      "enum": ["inherit", "cdk", "terraform"],
       "x-priority": "important",
-      "default": "Inherit",
-      "x-prompt": "Which provider would you like to manage your infrastructure? (default: Inherit)"
+      "default": "inherit",
+      "x-prompt": "Which provider would you like to manage your infrastructure? (default: inherit)"
+    },
+    "infra": {
+      "type": "string",
+      "description": "The type of infrastructure to host your Agent.",
+      "x-prompt": "How would you like to host your Agent server?",
+      "enum": ["agentcore", "none"],
+      "default": "agentcore",
+      "x-priority": "important"
     }
   },
   "required": ["project"]

package/src/py/api/schema.json

@@ -33,14 +33,6 @@
       },
       "x-priority": "important"
     },
-    "computeType": {
-      "type": "string",
-      "description": "The type of compute to use to deploy this API. Choose between ServerlessApiGatewayRestApi (default) or ServerlessApiGatewayHttpApi.",
-      "default": "ServerlessApiGatewayRestApi",
-      "enum": ["ServerlessApiGatewayRestApi", "ServerlessApiGatewayHttpApi"],
-      "x-prompt": "What compute type would you like to deploy your API with?",
-      "x-priority": "important"
-    },
     "integrationPattern": {
       "type": "string",
       "description": "How API Gateway integrations are generated for the API. Choose between isolated (default) and shared.",
@@ -65,9 +57,9 @@
     },
     "auth": {
       "type": "string",
-      "description": "The method used to authenticate with your API. Choose between IAM (default), Cognito or Custom.",
-      "default": "IAM",
-      "enum": ["IAM", "Cognito", "Custom"],
+      "description": "The method used to authenticate with your API. Choose between iam (default), cognito or custom.",
+      "default": "iam",
+      "enum": ["iam", "cognito", "custom"],
       "x-prompt": "How would you like users to authenticate with your API?",
       "x-priority": "important"
     },
@@ -83,17 +75,25 @@
       "description": "The sub directory the project is placed in. By default this is the project name.",
       "x-prompt": "Which sub directory do you want to create the project in? (By default this is the project name)"
     },
-    "iacProvider": {
+    "iac": {
       "type": "string",
       "description": "The preferred IaC provider. By default this is inherited from your initial selection.",
-      "enum": ["Inherit", "CDK", "Terraform"],
+      "enum": ["inherit", "cdk", "terraform"],
       "x-priority": "important",
-      "default": "Inherit",
-      "x-prompt": "Which provider would you like to manage your infrastructure? (default: Inherit)"
+      "default": "inherit",
+      "x-prompt": "Which provider would you like to manage your infrastructure? (default: inherit)"
     },
     "moduleName": {
       "type": "string",
       "description": "Python module name"
+    },
+    "infra": {
+      "type": "string",
+      "description": "The type of infrastructure to use to deploy this API.",
+      "default": "rest-lambda",
+      "enum": ["rest-lambda", "http-lambda", "none"],
+      "x-prompt": "What infrastructure would you like to deploy your API with?",
+      "x-priority": "important"
     }
   },
   "required": ["name"]