SSM ValidationException

[thorben-akent]

We are observing the following error when attempting a make bootstrap against an account on the standard aws partition. This is using LISA v5.3.0. We are unsure what SSM parameter CDK is attempting to access. The error fails to provide that detail.

Error fetching SSM parameter: ValidationException: Parameter name: can't be prefixed with "ssm" (case-insensitive). If formed as a path, it can consist of sub-paths divided by slash symbol; each sub-path can be formed as a mix of letters, numbers and the following 3 symbols .-_
    at de_ValidationExceptionRes (/builds/LISA/node_modules/@aws-sdk/client-ssm/dist-cjs/index.js:8954:21)
    at de_CommandError (/builds/LISA/node_modules/@aws-sdk/client-ssm/dist-cjs/index.js:7525:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /builds/LISA/node_modules/@smithy/middleware-serde/dist-cjs/index.js:36:20
    at async /builds/LISA/node_modules/@smithy/core/dist-cjs/index.js:193:18
    at async /builds/LISA/node_modules/@smithy/middleware-retry/dist-cjs/index.js:312:38
    at async /builds/LISA/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22
    at <anonymous> (/builds/LISA/bin/lisa.ts:101:29) {
  '$fault': 'client',
  '$metadata': {
    httpStatusCode: 400,
    requestId: '90d2fbfd-ab6a-41a1-873f-10b42c821a1b',
    extendedRequestId: undefined,
    cfId: undefined,
    attempts: 1,
    totalRetryDelay: 0
  },
  ReasonCode: undefined,
  __type: 'ValidationException'
}
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

ValidationException: Parameter name: can't be prefixed with "ssm" (case-insensitive). If formed as a path, it can consist of sub-paths divided by slash symbol; each sub-path can be formed as a mix of letters, numbers and the following 3 symbols .-_
    at de_ValidationExceptionRes (/builds/LISA/node_modules/@aws-sdk/client-ssm/dist-cjs/index.js:8954:21)
    at de_CommandError (/builds/LISA/node_modules/@aws-sdk/client-ssm/dist-cjs/index.js:7525:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /builds/LISA/node_modules/@smithy/middleware-serde/dist-cjs/index.js:36:20
    at async /builds/LISA/node_modules/@smithy/core/dist-cjs/index.js:193:18
    at async /builds/LISA/node_modules/@smithy/middleware-retry/dist-cjs/index.js:312:38
    at async /builds/LISA/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22
    at <anonymous> (/builds//LISA/bin/lisa.ts:101:29) {
  '$fault': 'client',
  '$metadata': {
    httpStatusCode: 400,
    requestId: '90d2fbfd-ab6a-41a1-873f-10b42c821a1b',
    extendedRequestId: undefined,
    cfId: undefined,
    attempts: 1,
    totalRetryDelay: 0
  },
  ReasonCode: undefined,
  __type: 'ValidationException'
}

Node.js v18.20.8
npm run deploy: Subprocess exited with error 1
make: *** [Makefile:131: bootstrap] Error 1

[estohlmann]

Hey there @thorben-akent - I was able to just bootstrap a new account. Not sure if you have some environment variables that need to be set or something to get this to work. Can you share with me your config-custom.yaml file? You can email it to me at evmann@amazon.com just curious if something isn't set like it should be.

Thank you,

Evan

[thorben-akent]

@estohlmann Thanks for reaching out. I've sent you a copy of our config and the full make bootstrap output.

[estohlmann]

Got it.. Looking through your config I think I identified a issue with your custom deploymentPrefix value not starting with a /

[thorben-akent]

Confirming that the deploymentPrefix value was the root cause of the issue.

Shout out to the AWS team for quickly engaging to assist and resolve the issue. Greatly appreciated.