Unable to seed sandbox - getId export is missing

[amuresia]

Environment information

System:
  OS: macOS 26.4.1
  CPU: (8) arm64 Apple M1 Pro
  Memory: 165.55 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 24.15.0 - /Users/andrei.muresianu/.nvm/versions/node/v24.15.0/bin/node
  Yarn: 1.22.22 - /opt/homebrew/bin/yarn
  npm: 11.12.1 - /Users/andrei.muresianu/.nvm/versions/node/v24.15.0/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/auth-construct: 1.11.2
  @aws-amplify/backend: 1.23.0
  @aws-amplify/backend-ai: Not Found
  @aws-amplify/backend-auth: 1.9.4
  @aws-amplify/backend-cli: 1.8.3
  @aws-amplify/backend-data: 1.7.0
  @aws-amplify/backend-function: 1.18.1
  @aws-amplify/backend-output-schemas: 1.8.0
  @aws-amplify/backend-output-storage: 1.3.5
  @aws-amplify/backend-secret: 1.4.2
  @aws-amplify/backend-storage: 1.5.0
  @aws-amplify/cli-core: 2.2.5
  @aws-amplify/client-config: 1.10.2
  @aws-amplify/data-construct: 1.17.3
  @aws-amplify/data-schema: 1.26.0
  @aws-amplify/deployed-backend-client: 1.8.2
  @aws-amplify/form-generator: 1.2.7
  @aws-amplify/model-generator: 1.2.3
  @aws-amplify/platform-core: 1.11.1
  @aws-amplify/plugin-types: 1.12.1
  @aws-amplify/sandbox: 2.2.1
  @aws-amplify/schema-generator: 1.4.1
  @aws-cdk/toolkit-lib: 1.19.0
  aws-amplify: 6.18.0
  aws-cdk-lib: 2.259.0
  typescript: 6.0.3
CDK CLI Version: 2.1127.0 (build 425ccb0)
normal verbosity, no debugging
AWS environment variables:
  AWS_PROFILE = *****
  AWS_EC2_METADATA_DISABLED = true
No CDK environment variables

Describe the bug

Unable to run the seed command due to the missing getId export.

Reproduction steps

npx ampx sandbox seed
seed is running...

ampx sandbox seed

Seeds sandbox environment

Commands:
  ampx sandbox seed generate-policy  Generates policy for seeding

Options:
      --debug       Print debug logs to the console
                                                [boolean] [default: false]
      --identifier  An optional identifier to distinguish between differen
                    t sandboxes. Default is the name of the system user ex
                    ecuting the process                           [string]
      --profile     An AWS profile name.                          [string]
  -h, --help        Show help                                    [boolean]

[SeedingFailedError] Seed failed to complete
  ∟ Caused by: [SyntaxError] The requested module '@aws-amplify/core' does not provide an export named 'getId'
Resolution: Check the Caused by error and fix any issues in your seed script

It works if I add the following to my package.json

"overrides": {
    "@aws-amplify/seed": {
      "aws-amplify": "6.18.0"
    }
  },

[amuresia]

Summary

@aws-amplify/seed@1.1.3 declares an exact dependency on aws-amplify@6.14.4:

// node_modules/@aws-amplify/seed/package.json
"dependencies": {
  "aws-amplify": "6.14.4"
}

In any project that depends on a different aws-amplify version, this exact pin forces npm to install a duplicate nested copy, and the resulting version skew breaks ampx sandbox seed at module-load time.

Error

[SeedingFailedError] Seed failed to complete
  ∟ Caused by: [SyntaxError] The requested module '@aws-amplify/core' does not provide an export named 'getId'

Root cause

getId is an export that older @aws-amplify/core provided and that was removed in @aws-amplify/core@6.16.x. When a consumer uses a newer aws-amplify, the import graph ends up mixing the seed-pinned aws-amplify@6.14.4 (which expects getId from core) with the hoisted @aws-amplify/core@6.16.4 (which no longer exports it), producing the SyntaxError.

Package	aws-amplify	→ @aws-amplify/core	exports getId?
App / hoisted	6.18.0	6.16.4	❌
@aws-amplify/seed@1.1.3	6.14.4 (exact pin)	6.11.4	✅

Reproduction

1. In a project (npm workspaces), depend on aws-amplify@6.18.0 and @aws-amplify/seed@1.1.3.
2. Run npx ampx sandbox seed.
3. Observe the getId SyntaxError above.

Workaround

Forcing @aws-amplify/seed onto the app's aws-amplify version via npm overrides resolves it (dedupes onto a single, internally consistent version set):

"overrides": {
  "@aws-amplify/seed": { "aws-amplify": "6.18.0" }
}

This works, but every consumer on a newer aws-amplify has to maintain this pin manually.

Request

aws-amplify is effectively a peer of the host app — consumers bring their own version. Please either:

1. Declare aws-amplify as a peerDependency of @aws-amplify/seed (preferred — dedupes onto the app's version automatically), or
2. At minimum, widen the dependency to a range (e.g. ^6.14.4) so it can dedupe with the consumer's version.

Environment

• @aws-amplify/seed: 1.1.3
• aws-amplify (app): 6.18.0
• Node: v24.15.0
• npm: 11.12.1
• OS: macOS