Invalid method setting path

[ozbillwang]

Add the plugin in my exist serverless.yml

plugins:
  - serverless-aws-alias

provider:
  name: aws
  runtime: nodejs6.10
  aliasStage:
    loggingLevel: "INFO"
    dataTraceEnabled: true

But got below error , when deploy:

Serverless: Checking Stack update progress...
........^@...................
Serverless: Operation failed!

  Serverless Error ---------------------------------------

  An error occurred: ApiGatewayStage - Invalid method setting path: /profile/ANY/logging/loglevel. Must be one of: [/deploymentId, /description, /cacheClusterEnabled, /cacheClusterSize, /clientCertificateId, /accesslogging, /accesslogging/destination, /accesslogging/format, /{resourcePath}/{httpMethod}/metrics/enabled, /{resourcePath}/{httpMethod}/logging/dataTrace, /{resourcePath}/{httpMethod}/logging/loglevel, /{resourcePath}/{httpMethod}/throttling/burstLimit/{resourcePath}/{httpMethod}/throttling/rateLimit/{resourcePath}/{httpMethod}/caching/ttlInSeconds, /{resourcePath}/{httpMethod}/caching/enabled, /{resourcePath}/{httpMethod}/caching/dataEncrypted, /{resourcePath}/{httpMethod}/caching/requireAuthorizationForCacheControl, /{resourcePath}/{httpMethod}/caching/unauthorizedCacheControlHeaderStrategy, /*/*/metrics/enabled, /*/*/logging/dataTrace, /*/*/logging/loglevel, /*/*/throttling/burstLimit /*/*/throttling/rateLimit /*/*/caching/ttlInSeconds, /*/*/caching/enabled, /*/*/caching/dataEncrypted, /*/*/caching/requireAuthorizationForCa.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Forums:        forum.serverless.com
     Chat:          gitter.im/serverless/serverless

  Your Environment Information -----------------------------
     OS:                     linux
     Node Version:           6.11.3
     Serverless Version:     1.24.1

[HyperBrain]

@ozbillwang Thanks for the report.

This might be an issue with the ANY method for endpoint proxies supporting any HTTP method.
All other parts of the settings path /profile/ANY/logging/loglevel match the pattern /{resourcePath}/{httpMethod}/logging/loglevel mentioned in the error text.

Maybe AWS expects that the plugin translates ANY to the complete set of allowed methods that are covered by ANY.

Can you do a double check and specify the setting on function level, for just a function that does not have ANY endpoints and see if it then works? If yes, the ANY support has to be fixed in the plugin.

[ozbillwang]

yes, the problem is gone, after rename any to other method.

Then I got this error:

An error occurred: ApiGatewayStage - CloudWatch Logs role ARN must be set in account settings to enable logging.

I added a role with this permission:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "logs:*"
            ],
            "Effect": "Allow",
            "Resource": "*"
        }
    ]
}

and

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "",
      "Effect": "Allow",
      "Principal": {
        "Service": "apigateway.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

I still got same error. So what role should I create, and can you show some codes for me?

[HyperBrain]

@ozbillwang You have to create a role as mentioned here: https://aws.amazon.com/premiumsupport/knowledge-center/api-gateway-cloudwatch-logs/
with the AmazonAPIGatewayPushToCloudWatchLogs policy attached.

And then in the API Gateway console at the bottom there is "Settings". Enter the role you created and it should work. The role configuration in API Gateway is an account setting and applies to all APIs.
This will enable the general use of the API logging and afterwards the deploy should go through.

If there is already a role assigned to API Gateway, you should look that up in IAM and just add the missing policy.

[HyperBrain]

... and thank you for the test. Then this bug has to be fixed to allow and support the any special method.

[ozbillwang]

@HyperBrain

After added the role manually from API Gateway console -> setting, it works now. Thanks a lot

So my code to add role directly in serverless.yml doesn't work with cloudwatch logs

provider:
  name: aws
  runtime: nodejs6.10
  role: arn:aws:iam::12345678:role/serverless-lambda-role

[HyperBrain]

I think you do not need the role in your serverless.yml or do you not want to use the role that is generated by Serverless?

[ozbillwang]

Sure. I just realised the role serverless-lambda-role is a global role which need be setup separately and manually and will be applied to all api gateways.

In my first thinking, I'd like to manage this role in serverless.yml. So I can define the options for different gateways.

[HyperBrain]

@ozbillwang Can you check with the attached PR, if ANY is supported correctly now?

[ozbillwang]

Thanks @HyperBrain

How to install this un-released version?

[HyperBrain]

Just use "serverless-aws-alias": "github:HyperBrain/serverless-aws-alias#support-any-in-stage-config" in your package.json. It will then install the branch directly from GitHub.