Appsync Unified Repo [portable]

import { evaluateMappingTemplate } from '@aws-appsync/utils-tests'; import { readFileSync } from 'fs';

If you use the AppSync JS runtime, ensure all developers use the same Node.js version for local testing. Consider a Docker dev environment.

Let’s walk through setting up a minimal unified repo using AWS CDK.

The transforms AWS AppSync from a mystical, console-dependent service into a developer-friendly, auditable, and scalable asset.

For complex business logic (e.g., auth check -> database update -> send notification), use . Store each function as its own VTL file in resolvers/functions/ .

my-appsync-api/ ├── lib/ │ ├── appsync-stack.ts # Main CDK stack │ └── resolvers/ # All resolver logic │ ├── Query/ │ │ ├── getPost.req.vtl # Request mapping template │ │ └── getPost.res.vtl # Response mapping template │ ├── Mutation/ │ │ ├── updatePost.req.vtl │ │ ├── updatePost.res.vtl │ │ └── updatePost.js # (Optional) Lambda resolver code │ └── functions/ # Pipeline resolvers │ ├── auth.req.vtl │ └── enrich.req.vtl ├── graphql/ │ └── schema.graphql # The unified GraphQL schema ├── test/ │ └── appsync.test.ts # Jest tests for resolvers ├── cdk.json └── package.json