Lambda function fails to bundle node_modules in DynamoDB table management during deploy

[micaelgomes]

Environment information

System:
  OS: macOS 13.5.1
  CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
  Memory: 31.48 MB / 32.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 22.12.0 - ~/.nvm/versions/node/v22.12.0/bin/node
  Yarn: 1.22.22 - ~/.yarn/bin/yarn
  npm: 10.9.0 - ~/.nvm/versions/node/v22.12.0/bin/npm
  pnpm: 9.15.4 - ~/Library/pnpm/pnpm
NPM Packages:
  @aws-amplify/auth-construct: 1.5.1
  @aws-amplify/backend: 1.13.0
  @aws-amplify/backend-auth: 1.4.2
  @aws-amplify/backend-cli: 1.4.7
  @aws-amplify/backend-data: 1.4.0
  aws-amplify: 6.12.1
  aws-cdk: 2.176.0
  aws-cdk-lib: 2.176.0

Describe the bug

During deployment (both sandbox and app), the internal Lambda function responsible for DynamoDB table management is being deployed without its node_modules, causing module import failures. The deployment gets stuck during table creation and fails with the following error:

<*> undefined ERROR Uncaught Exception {"errorType":"Runtime.ImportModuleError","errorMessage":"Error: Cannot find module 'lodash.isequal'\nRequire stack:\n- <*> <*> <*>,"stack":["Runtime.ImportModuleError: Error: Cannot find module 'lodash.isequal'"...

The deployment process hangs at:

2025-01-16T01:32:43.380Z [INFO]: 98/12 Currently in progress: amplify-d2t830pi2dqir1-main-branch-9c399377b4, data7552DF31, amplifyDataAccountNestedStackAccountNestedStackResourceC2EA4038, AccountTable

I've attempted various solutions including:

• Updating esbuild to recommended versions (0.21.5, 0.23.1)
• Clean installs and redeployments
• Manual deletion of stacks after failed deployments

None of these attempts resolved the issue, and manual cleanup of stacks was required after each failed deployment.

Reproduction steps

1. Create a new Amplify Gen2 project
2. Define a data model using defineData:

const schema = a.schema({
  Account: a.model({
    id: a.string().required(),
    // ... other fields
  })
});

export const data = defineData({
  schema,
  authorizationModes: {
    defaultAuthorizationMode: "userPool"
  }
});

3. Run npx ampx sandbox
4. Observe deployment getting stuck at table creation step
5. Check CloudWatch logs to see the Lambda failing with module import error
6. Manual cleanup of stacks required due to failed deployment

[ykethan]

Hey,👋 thanks for raising this! I'm going to transfer this over to our data repository for better assistance 🙂

[AnilMaktala]

Hey @micaelgomes, Thank you for raising this issue. I’ve tried reproducing it using the schema below but wasn’t able to replicate the problem. To better understand the situation, could you confirm if the Account table includes any indexes, relationships, or identifiers? If possible, would you be able to share your Account model for further analysis?

const schema = a.schema({
  Todo: a
    .model({
      content: a.string().required(),
    })
    .authorization((allow) => [allow.guest()]),
});

export type Schema = ClientSchema<typeof schema>;

export const data = defineData({
  schema,
  authorizationModes: {
    defaultAuthorizationMode: "userPool",
  },
});