Appsync Unified Repo May 2026

// Query.getPost.js import util from '@aws-appsync/utils'; export function request(ctx) return operation: 'GetItem', key: util.dynamodb.toMapValues( id: ctx.args.id ), ;

Use paths filters to trigger the pipeline only when relevant files change. However, for AppSync, even a change to a single resolver .js file changes the API behavior, so always run the full integration test suite. The Secret Sauce: Generated Types for Everything The unification shines when you add code generation . From Schema to Data Sources Use @graphql-codegen/cli to generate TypeScript types for your Lambda resolvers : appsync unified repo

export const handler = async (event: AppSyncResolverEvent<QueryGetPostArgs>): Promise<Post> => const id = event.arguments; // Your logic here... ; // Query

These resolvers are deployed as part of the AppSync API definition. In a unified repo, they live right next to the schema, making it obvious which resolver belongs to which field. 2. Lambda Data Sources (Packages/data-sources/) For complex business logic, use Lambda. In your CDK code: From Schema to Data Sources Use @graphql-codegen/cli to

Enter the .

const api = new GraphqlApi(this, 'UnifiedApi', name: 'UnifiedRepoApi', schema: Schema.fromAsset(path.join(__dirname, 'schema.graphql')), authorizationConfig: defaultAuthorization: ... , );