Open vignesh-tpg opened 1 month ago
Hey @vignesh-tpg, the security token is invalid
error usually means the credentials are expired or misconfigured. Please check the AWS profile specified in your Serverless config (e.g., provider.profile
) or try running the command with --aws-profile
to ensure the correct one is used.
Issue description
The SSM Parameters though accessible via AWS CLI were not accessible using serverless version 3.38.0. There are no issues with AWS Credentials and it was verified. Variables are referred like this in application - serverless.js.
custom: { SUBNETID1: '${ssm:/platform/vpc/default-network/subnet/private1/id}', SUBNETID2: '${ssm:/platform/vpc/default-network/subnet/private2/id}', }
Above usage led to this error Cannot resolve serverless.js: Variables resolution errored with:
Context