AWS SSO doesn't seem to work with SERVERLESS_LICENSE_KEY about serverless

[czubocha]

Hey @kdybicz, thanks for sharing more details. I believe I know where the problem is. We’ll release the fix shortly and I’ll keep you updated.

[kdybicz]

We use the AWS SSO with AWS_PROFILE which might be not supported by SLS. When using AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY it works nicely. This makes our CI/CD work, but it breaks in the local dev environment.

[austencollins]

@kdybicz Thanks for reporting. We'll look into this.

[kdybicz]

I was curious to see if 4.1.6 fixes things, but unfortunately that's not the case. I was trying to validate it with:

profile: ${env:AWS_PROFILE,'development'}

but I'm still getting:

▶ yarn serverless package
yarn run v1.22.19
$ /Users/kamil/project/node_modules/.bin/serverless package


✖ Failed to resolve variable '/development/project/some/key' with resolver 'ssm' and provider 'aws': ParameterNotFound: UnknownError
Error: Failed to resolve variable '/development/project/some/key' with resolver 'ssm' and provider 'aws': ParameterNotFound: UnknownError
    at #resolveKey (file:///Users/kamil/.serverless/releases/4.1.6/package/dist/sf-core.js:1085:43511)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async _ResolverManager.resolve (file:///Users/kamil/.serverless/releases/4.1.6/package/dist/sf-core.js:1085:48418)
    at async #handlePlaceholderNode (file:///Users/kamil/.serverless/releases/4.1.6/package/dist/sf-core.js:1085:47272)
    at async file:///Users/kamil/.serverless/releases/4.1.6/package/dist/sf-core.js:1085:45407
    at async processNodeAndHandleCompletion (file:///Users/kamil/.serverless/releases/4.1.6/package/dist/sf-core.js:1085:38403)

but... when I set the env inline:

▶ AWS_PROFILE=development yarn serverless package
yarn run v1.22.19
$ /Users/kamil/project/node_modules/.bin/serverless package

Packaging "project" for stage "development" (eu-west-1)

✔ Service packaged (2s)

✨  Done in 8.09s.

The same happens when I set it in the .env. I've also noticed that the inline takes precedence over what's in .env - though it might be worth noting.

[czubocha]

Hi @kdybicz, we included a fix for resolving the AWS profile in the latest release, feel free to try this out now.