@aws/nx-plugin-mcp 1.0.0-rc.98 → 1.0.1

package/docs/guides/react-website-auth.mdx

@@ -10,6 +10,7 @@ import GeneratorParameters from '@components/generator-parameters.astro';
 import NxCommands from '@components/nx-commands.astro';
 import Infrastructure from '@components/infrastructure.astro';
 import Snippet from '@components/snippet.astro';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 The React Website Authentication generator adds authentication to your React website using [Amazon Cognito](https://aws.amazon.com/cognito/).
 
@@ -71,38 +72,7 @@ You will also find the following infrastructure code generated based on your sel
 
 This generator adds an Amazon Cognito user pool (for sign-in) and an identity pool (for federating signed-in users to scoped IAM credentials) to the existing static-website architecture:
 
-```d2 inline=true
-direction: right
-
-browser: Web Browser {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-waf: WAF {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/waf.svg
-}
-
-cognito: Cognito\n(User + Identity Pool) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cognito.svg
-}
-
-iam: Scoped IAM\nCredentials {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/iam.svg
-}
-
-backend: Authenticated\nAWS Resources {
-  shape: rectangle
-}
-
-browser -> waf: Sign in
-waf -> cognito
-cognito -> iam
-browser -> backend: IAM/Cognito
-```
+<ArchitectureDiagram name="my-website" />
 
 #### Threat protection
 
@@ -255,7 +225,7 @@ In order to grant authenticated users access to perform certain actions, such as
 
 <Infrastructure>
 <Fragment slot="cdk">
-```ts title="packages/infra/src/stacks/application-stack.ts" {12}
+```ts title="packages/infra/src/stacks/application-stack.ts" {14}
 import { Stack, StackProps } from 'aws-cdk-lib';
 import { Construct } from 'constructs';
 import { MyWebsite, UserIdentity, MyApi } from '@my-scope/common-constructs';

package/docs/guides/react-website.mdx

@@ -17,6 +17,7 @@ import PackageManagerShortCommand from '@components/package-manager-short-comman
 import Infrastructure from '@components/infrastructure.astro';
 import Snippet from '@components/snippet.astro';
 import OptionFilter from '@components/option-filter.astro';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 This generator creates a new [React](https://react.dev/) website with [shadcn/ui](https://ui.shadcn.com/) configured by default, along with the AWS CDK or Terraform infrastructure to deploy your website to the cloud as a static website hosted in [S3](https://aws.amazon.com/s3/), served by [CloudFront](https://aws.amazon.com/cloudfront/) and protected by [WAF](https://aws.amazon.com/waf/).
 
@@ -106,35 +107,9 @@ The generator creates infrastructure as code for deploying your website based on
 
 #### Architecture
 
-The deployed website has the following architecture:
+The deployed website has the following architecture: your built assets in an S3 bucket, served by a CloudFront distribution with an AWS WAFv2 Web ACL in front of it.
 
-```d2 inline=true
-direction: right
-
-browser: Web Browser {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-waf: WAF {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/waf.svg
-}
-
-cloudfront: CloudFront {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudfront.svg
-}
-
-s3: Static Assets\n(S3) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/s3.svg
-}
-
-browser -> waf
-waf -> cloudfront
-cloudfront -> s3
-```
+<ArchitectureDiagram />
 
 ## Implementing your Website
 

package/docs/guides/runtime-config.mdx

@@ -5,6 +5,7 @@ description: How runtime configuration connects your generated projects using AW
 import { Tabs, TabItem, Steps } from '@astrojs/starlight/components';
 import Infrastructure from '@components/infrastructure.astro';
 import Link from '@components/link.astro';
+import EmbeddedGraph from '@components/embedded-graph.astro';
 
 Runtime configuration is the mechanism used by Nx Plugin for AWS to pass deploy-time values between generated projects and components so they can connect to one another. For example, when you generate an API, its URL is automatically registered in the runtime configuration so that a connected website can discover it.
 
@@ -26,40 +27,7 @@ The `connection` namespace is also deployed as a `runtime-config.json` file to y
 
 You can define as many additional namespaces as you like, providing a convenient alternative to environment variables for passing deploy-time values to your Lambda functions or other compute resources.
 
-```d2
-direction: down
-
-iac: "Infrastructure as code\nRuntimeConfig.set(...)"
-
-appconfig: "AWS AppConfig" {
-  shape: cylinder
-  connection: "connection namespace"
-  agentcore: "agentcore namespace"
-  custom: "custom namespaces"
-}
-
-s3: "website S3 bucket" {
-  shape: cylinder
-  rcj: runtime-config.json {
-    shape: page
-  }
-}
-
-website: React website
-
-server: Lambda / agent
-
-iac -> appconfig.connection
-iac -> appconfig.agentcore
-iac -> appconfig.custom
-
-appconfig.connection -> s3.rcj: deployed
-s3.rcj -> website: fetched at load
-
-appconfig.connection -> server
-appconfig.agentcore -> server: Powertools getAppConfig
-appconfig.custom -> server
-```
+<EmbeddedGraph diagram="runtime-config" />
 
 ## Infrastructure
 

package/docs/guides/terraform-project.mdx

@@ -89,7 +89,7 @@ Application projects include full deployment capabilities with remote state mana
 
 You can start writing your Terraform infrastructure inside `src/main.tf`, for example:
 
-```diff title="src/main.tf" {16-19}
+```diff title="src/main.tf"
 -locals {
 -  account_id = data.aws_caller_identity.current.account_id
 -  aws_region = data.aws_region.current.id

package/docs/guides/ts-dynamodb.mdx

@@ -11,6 +11,7 @@ import Link from '@components/link.astro';
 import RunGenerator from '@components/run-generator.astro';
 import GeneratorParameters from '@components/generator-parameters.astro';
 import Snippet from '@components/snippet.astro';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 This generator creates a new TypeScript DynamoDB project backed by [Amazon DynamoDB](https://aws.amazon.com/dynamodb/), using [ElectroDB](https://electrodb.dev/) for type-safe entity modelling. It generates the application code and infrastructure needed to provision and manage a DynamoDB table using AWS CDK or Terraform, with single-table design support and built-in local development via DynamoDB Local.
 
@@ -53,6 +54,12 @@ The local development scripts are shared across all DynamoDB projects (both Type
 
 <Snippet name="dynamodb/infrastructure" />
 
+#### Architecture
+
+The deployed project provisions the table itself, which any project it is connected to reads and writes:
+
+<ArchitectureDiagram />
+
 ## Local Development
 
 ### Starting Local DynamoDB

package/docs/guides/ts-smithy-api.mdx

@@ -20,6 +20,7 @@ import Snippet from '@components/snippet.astro';
 import OptionFilter from '@components/option-filter.astro';
 import InstallCommand from '@components/install-command.astro';
 import { TS_VERSIONS } from '../../../../../../packages/nx-plugin/src/utils/versions';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 [Smithy](https://smithy.io/) is a protocol-agnostic interface definition language for authoring APIs in a model driven fashion.
 
@@ -126,47 +127,7 @@ This project is generated using the <Link path="/guides/terraform-project">`terr
 
 The deployed Smithy API has the following architecture, with an [AWS WAFv2](https://docs.aws.amazon.com/waf/latest/developerguide/waf-chapter.html) Web ACL in front of the API Gateway stage:
 
-```d2 inline=true
-direction: right
-
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-waf: WAF {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/waf.svg
-}
-
-apigw: API Gateway\n(REST API) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/api-gateway.svg
-}
-
-lambda: Lambda\n(Smithy Server SDK) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: top-right
-}
-
-xray: X-Ray\n(Traces) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/xray.svg
-  near: bottom-right
-}
-
-client -> waf
-waf -> apigw
-apigw -> lambda
-lambda -> cw
-lambda -> xray
-```
+<ArchitectureDiagram options={{ infra: 'rest-lambda' }} />
 
 ## Implementing your Smithy API
 
@@ -315,7 +276,7 @@ You must construct the context yourself in both `handler.ts` (the Lambda functio
 
 The generator configures structured logging using AWS Lambda Powertools with automatic context injection via Middy middleware.
 
-```typescript {3}
+```typescript {4}
 // handler.ts
 export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
   .use(captureLambdaHandler(tracer))
@@ -326,7 +287,7 @@ export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
 
 You can reference the logger from your operation implementations via the context:
 
-```typescript {5}
+```typescript {6}
 // operations/echo.ts
 import { ServiceContext } from '../context.js';
 import { Echo as EchoOperation } from '../generated/ssdk/index.js';
@@ -341,7 +302,7 @@ export const Echo: EchoOperation<ServiceContext> = async (input, ctx) => {
 
 AWS X-Ray tracing is configured automatically via the `captureLambdaHandler` middleware.
 
-```typescript {2}
+```typescript {3}
 // handler.ts
 export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
   .use(captureLambdaHandler(tracer))
@@ -352,7 +313,7 @@ export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
 
 You can add custom subsegments to your traces in your operations:
 
-```typescript {6, 10, 13}
+```typescript {7, 11, 14}
 // operations/echo.ts
 import { ServiceContext } from '../context.js';
 import { Echo as EchoOperation } from '../generated/ssdk/index.js';
@@ -375,7 +336,7 @@ export const Echo: EchoOperation<ServiceContext> = async (input, ctx) => {
 
 CloudWatch metrics are collected automatically for each request via the `logMetrics` middleware.
 
-```typescript {4}
+```typescript {5}
 // handler.ts
 export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
   .use(captureLambdaHandler(tracer))
@@ -386,7 +347,7 @@ export const handler = middy<APIGatewayProxyEvent, APIGatewayProxyResult>()
 
 You can add custom metrics in your operations:
 
-```typescript {6}
+```typescript {7}
 // operations/echo.ts
 import { MetricUnit } from '@aws-lambda-powertools/metrics';
 import { ServiceContext } from '../context.js';

package/docs/guides/typescript-project.mdx

@@ -228,9 +228,9 @@ npm has no catalog feature, so versions are declared directly in each `package.j
 
 ##### Opting out of catalogs
 
-Catalogs are enabled by default. To turn them off, create your workspace with `--catalog false`:
+Catalogs are enabled by default. To turn them off, create your workspace with `--catalog=false`:
 
-<CreateNxWorkspaceCommand workspace="my-project" extraArgs="--catalog false" />
+<CreateNxWorkspaceCommand workspace="my-project" values={{ catalog: false }} />
 
 Or set it in `aws-nx-plugin.config.mts` at any time:
 

package/docs/guides/workspace.mdx

@@ -27,6 +27,7 @@ When you create a new workspace with `@aws/nx-plugin`, the preset generator sets
   - package.json Root package.json for your monorepo
   - nx.json Nx configuration (common targets, sync generators, caching)
   - tsconfig.base.json Root TypeScript configuration
+  - biome.json Biome configuration for linting and formatting
   - aws-nx-plugin.config.mts Nx Plugin for AWS configuration
   - .git-secrets/ Vendored git-secrets bash script for credential scanning
   - .gitallowed Patterns git-secrets treats as false positives
@@ -72,7 +73,7 @@ For details on how TypeScript and Python projects are set up, refer to the <Link
 
 ### Caching
 
-Nx caches the output of previously executed targets and replays them when the inputs haven't changed. This dramatically speeds up builds, tests, and linting — especially in CI. If you encounter stale or unexpected behaviour, reset the cache with:
+Nx caches the output of previously executed targets and replays them when the inputs haven't changed. This dramatically speeds up builds, tests, and linting. If you encounter stale or unexpected behaviour, reset the cache with:
 
 <NxCommands commands={['reset']} />
 
@@ -88,15 +89,7 @@ New workspaces set `parallel` in `nx.json`, which controls how many tasks Nx run
 }
 ```
 
-Lower it if you're building on a machine with fewer cores or limited memory:
-
-```json title="nx.json"
-{
-  "parallel": 3
-}
-```
-
-You can also override it per-invocation:
+Lower it if you're building on a machine with fewer cores or limited memory. You can also override it per-invocation:
 
 <NxCommands commands={['run-many --target build --parallel=4']} />
 
@@ -166,6 +159,10 @@ This will run the chosen target as well as the targets it depends on.
 
 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.
 
+### MCP Configuration
+
+The plugin's <Link path="get_started/building-with-ai">MCP server</Link> is configured as a project level MCP server for Claude Code, Cursor, Kiro, Gemini CLI, GitHub Copilot and OpenAI Codex, so your coding assistant can discover and run the plugin's generators without any setup. The configuration is committed with your workspace, giving everyone on your team the same setup. Remove any configurations for coding assistants you and your team do not use.
+
 ### Git Secrets
 
 Workspaces are set up with [git-secrets](https://github.com/awslabs/git-secrets) pre-commit hooks that scan staged files for AWS credential patterns before each commit. This prevents accidentally committing access keys, secret keys, and other sensitive values.

package/docs/snippets/agent/architecture.mdx

@@ -2,71 +2,28 @@
 title: Agent Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
 <Tabs syncKey="infra">
-<TabItem label="Bedrock AgentCore Runtime" _filter={{ infra: 'agentcore' }}>
+<TabItem label="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.
+When deployed to [Bedrock AgentCore Runtime](https://aws.amazon.com/bedrock/agentcore/), your agent's code is packaged as a zip and run in the AgentCore managed 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.
 
-```d2 inline=true
-direction: right
+<ArchitectureDiagram options={{ infra: 'agentcore' }} />
 
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-ecr: ECR {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/ecr.svg
-}
-
-agentcore: Strands Agent\n(AgentCore Runtime) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/bedrock-agentcore-runtime.svg
-}
+</TabItem>
+<TabItem label="AgentCore Runtime (container)" _filter={{ infra: 'agentcore-ecr' }}>
 
-bedrock: Bedrock\n(Model Inference) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/bedrock.svg
-  near: top-right
-}
+With `infra: agentcore-ecr`, the agent is built into a container image, pushed to Amazon ECR and run in AgentCore Runtime. This gives you OS-level control over the runtime environment, at the cost of a longer build and deploy cycle than the zip packaging above.
 
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: bottom-right
-}
+<ArchitectureDiagram options={{ infra: 'agentcore-ecr' }} />
 
-client -> agentcore
-ecr -> agentcore: Container\nimage
-agentcore -> bedrock: InvokeModel
-agentcore -> cw
-```
 </TabItem>
 <TabItem label="None (local only)" _filter={{ infra: 'none' }}>
 
 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
-
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-agent: Strands Agent\n(local process) {
-  shape: rectangle
-}
-
-bedrock: Bedrock\n(Model Inference) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/bedrock.svg
-}
+<ArchitectureDiagram options={{ infra: 'none' }} />
 
-client -> agent
-agent -> bedrock: InvokeModel
-```
 </TabItem>
 </Tabs>

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

@@ -111,7 +111,7 @@ export class ExampleStack extends Stack {
 ```
 </Fragment>
 <Fragment slot="terraform">
-```terraform {9-10}
+```terraform {10-11}
 module "asset_bucket" {
   source = "../../common/terraform/src/core/asset-bucket"
 }

package/docs/snippets/agent/runtime-arn.mdx

@@ -26,7 +26,7 @@ export class ExampleStack extends Stack {
 ```
 </Fragment>
 <Fragment slot="terraform">
-```terraform {9-10}
+```terraform {10-12}
 # Agent
 module "my_project_agent" {
   # Relative path to the generated module in the common/terraform project

package/docs/snippets/api/access-logging.mdx

@@ -16,7 +16,7 @@ The account role is managed by the `ApiGatewayAccount` construct, a stack-scoped
 
 The access log format is set by the `RestApi` construct your API extends. To customise it, pass `deployOptions` through to `super` in the generated `packages/common/constructs/src/app/apis/my-api.ts`, keeping the `tracingEnabled` the construct already sets:
 
-```ts {5-8} title="packages/common/constructs/src/app/apis/my-api.ts"
+```ts {4-7} title="packages/common/constructs/src/app/apis/my-api.ts"
 super(scope, id, {
   apiName: 'MyApi',
   // ...

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

@@ -2,91 +2,20 @@
 title: API Architecture
 ---
 import { Tabs, TabItem } from '@astrojs/starlight/components';
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
-The deployed application has the following architecture:
+The deployed application has the following architecture: an API Gateway API in front of a Lambda function running your handler.
 
 <Tabs syncKey="http-rest">
 <TabItem label="REST API" _filter={{ infra: 'rest-lambda' }}>
-```d2 inline=true
-direction: right
 
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-waf: WAF {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/waf.svg
-}
-
-apigw: API Gateway\n(REST API) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/api-gateway.svg
-}
-
-lambda: Lambda {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: top-right
-}
-
-xray: X-Ray\n(Traces) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/xray.svg
-  near: bottom-right
-}
-
-client -> waf
-waf -> apigw
-apigw -> lambda
-lambda -> cw
-lambda -> xray
-```
+<ArchitectureDiagram options={{ infra: 'rest-lambda' }} />
 
 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={{ infra: 'http-lambda' }}>
-```d2 inline=true
-direction: right
-
-client: Client {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/client.svg
-}
-
-apigw: API Gateway\n(HTTP API) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/api-gateway.svg
-}
-
-lambda: Lambda {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: top-right
-}
-
-xray: X-Ray\n(Traces) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/xray.svg
-  near: bottom-right
-}
 
-client -> apigw
-apigw -> lambda
-lambda -> cw
-lambda -> xray
-```
+<ArchitectureDiagram options={{ infra: 'http-lambda' }} />
 
 HTTP APIs do not support WAF directly — if you need WAF protection, choose REST API instead or front the HTTP API with a CloudFront distribution.
 </TabItem>

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

@@ -5,7 +5,6 @@ import { Steps } from '@astrojs/starlight/components';
 import Infrastructure from '@components/infrastructure.astro';
 import Drawer from '@components/drawer.astro';
 import OptionFilter from '@components/option-filter.astro';
-import RunGenerator from '@components/run-generator.astro';
 
 The REST/HTTP API CDK constructs are configured to provide a type-safe interface for defining integrations for each of your operations.
 
@@ -405,7 +404,7 @@ Generated APIs support two integration patterns:
 <Fragment slot="cdk">
 The integration pattern can be changed at any time in CDK by updating your API construct. For example, setting `pattern` to `'shared'` creates a single function instead of one per integration:
 
-```ts {6}
+```ts {7}
 // packages/common/constructs/src/app/apis/my-api.ts
 export class MyApi<...> extends ... {
 
@@ -424,8 +423,7 @@ Unlike CDK, the integration pattern is baked into the generated module. To chang
 
 <Steps>
   1. Delete the previously generated API module in `packages/common/terraform/src/app/apis`
-  2. Re-run the API generator with the other integration pattern:
-      <RunGenerator generator="ts#api" requiredParameters={{ integrationPattern: 'shared' }} />
+  2. Re-run the generator that created your API with the other integration pattern (eg `--integrationPattern=shared`)
 </Steps>
 
 With the `isolated` pattern, the module reads the operations from a generated file:

package/docs/snippets/lambda-function/architecture.mdx

@@ -1,36 +1,10 @@
 ---
 title: Lambda Function Architecture
 ---
+import ArchitectureDiagram from '@components/architecture-diagram.astro';
 
-The deployed function has the following architecture:
+The deployed function has the following architecture, with its logs, metrics and traces going to CloudWatch and X-Ray:
 
-```d2 inline=true
-direction: right
-
-source: Event Source\n(SNS, SQS, ...) {
-  shape: rectangle
-}
-
-lambda: Lambda {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/lambda.svg
-}
-
-cw: CloudWatch\n(Logs, Metrics) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/cloudwatch.svg
-  near: top-right
-}
-
-xray: X-Ray\n(Traces) {
-  shape: image
-  icon: /nx-plugin-for-aws/icons/aws/xray.svg
-  near: bottom-right
-}
-
-source -> lambda
-lambda -> cw
-lambda -> xray
-```
+<ArchitectureDiagram name="my-function" />
 
 The generator vends the function itself; you wire the event source up in your stack to invoke it (for example, an API Gateway integration, an EventBridge rule, an S3 notification or an SQS event source mapping).