Serverless: CloudFormation 配置错误

创建于 2016-06-06  ·  3评论  ·  资料来源: serverless/serverless

我找不到类似的问题,但是我安装的无服务器不想使用我的 AWS 帐户,而且它似乎是 CloudFormation 的问题。

值得注意的是,我在这台机器上有另一个无服务器项目,使用完全不同的 AWS 公司控制台的配置文件。 也许他们正在发生冲突。

这是完整的堆栈跟踪:

➜  Sites sls project create
Serverless: Initializing Serverless Project...
Serverless: Enter a name for this project:  (serverless-hyzha4) gamblor
Serverless: Enter a new stage name for this project:  (dev)
Serverless: For the "dev" stage, do you want to use an existing Amazon Web Services profile or create a new one?
  > Existing Profile
    Create A New Profile
Serverless: Select a profile for your project:
  > greenwald_web
Serverless: Creating stage "dev"...
Serverless: Select a new region for your stage:
  > us-east-1
    us-west-2
    eu-west-1
    eu-central-1
    ap-northeast-1
Serverless: Creating region "us-east-1" in stage "dev"...
Serverless: Deploying resources to stage "dev" in region "us-east-1" via Cloudformation (~3 minutes)...
/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:61
        fn = function () { throw arg; };
                           ^

ServerlessError: ServerlessError: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

The Canonical String for this request should have been
'POST
/

host:cloudformation.us-east-1.amazonaws.com
x-amz-content-sha256:a2a7598a25270c66b8240e6b6b79dba162c1cd4f0a4e55a8ae70bcfaa1742f28
x-amz-date:20160606T000717Z

host;x-amz-content-sha256;x-amz-date
a2a7598a25270c66b8240e6b6b79dba162c1cd4f0a4e55a8ae70bcfaa1742f28'

The String-to-Sign should have been
'AWS4-HMAC-SHA256
20160606T000717Z
20160606/us-east-1/cloudformation/aws4_request
162169136a49170309594344c3a2f48851a81a8a4aefd2a0f4eeb5caebd0639c'

    at new ServerlessError (/usr/local/lib/node_modules/serverless/lib/Error.js:17:11)
    at ResourcesDeploy.<anonymous> (/usr/local/lib/node_modules/serverless/lib/actions/ResourcesDeploy.js:242:25)
    at ResourcesDeploy.tryCatcher (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:502:31)
    at Promise._settlePromise (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:559:18)
    at Promise._settlePromise0 (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:604:10)
    at Promise._settlePromises (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:679:18)
    at Async._drainQueue (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:138:16)
    at Async._drainQueues (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:148:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/lib/node_modules/serverless/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)
无服务器版本

无服务器版本 0.5.5。

平台

OSX El Capitan

包/依赖项

也许aws-cli ? 第 1.10.35 节

最有用的评论

如果其他人遇到了这个问题,我通过生成一个新的密钥/秘密来解决它,然后创建一个新的 aws 配置文件

serverless config credentials --provider aws --key 1234 --secret 5678 --profile custom-profile

所有3条评论

关闭,因为我不再将此项目用于相关应用程序。

如果其他人遇到了这个问题,我通过生成一个新的密钥/秘密来解决它,然后创建一个新的 aws 配置文件

serverless config credentials --provider aws --key 1234 --secret 5678 --profile custom-profile

@brandonmp感谢分享。
我也必须生成一个新的密钥和秘密。

我有点困惑为什么旧的不起作用。
但那是 AWS 的支持票。

此页面是否有帮助?
0 / 5 - 0 等级