Specify Destination ARN for API Gateway Custom Access Logs?

Serverless Framework
,
1

We deploy multiple serverless services to a shared api gateway—we would like custom access logging to be turned on, as so:

logs:
  restApi:
    accessLogging: true
    format: 'requestId: $context.requestId'
    executionLogging: true
    level: INFO
    fullExecutionData: true

However, the Access Log Destination ARN changes every time a service is deployed (generated from the service name), whereas we would like to point the entire gateway to one shared log group. Can this ARN be fixed as part of this configuration like the format or log level can be?

1 Like
2

I’m facing this same issue. If I change the APIGW Access Log Destination ARN to a Kinesis Firehose or custom CloudWatch LogGroup, it gets reverted anytime we do a deploy regardless of whether we’re modifying the logging settings or not.