You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Amazon API Gateway just announced support for writing Access Logs directly to Kinesis Data Firehose instead of CloudWatch Logs.
Buried in the CloudFormation documentation is this constraint:
DestinationArn
The Amazon Resource Name (ARN) of the CloudWatch Logs log group or Kinesis Data Firehose delivery stream to receive access logs. If you specify a Kinesis Data Firehose delivery stream, the stream name must begin with amazon-apigateway-.
The stream name prefix constraint is likely going to trip up customers who are letting CloudFormation name their Kinesis Data Firehose delivery stream since it won't have the required prefix unless their stack name begins with amazon-apigateway-.
Opening this issue to see if cfn-lint could help users by detecting this scenario and issuing a warning/error.
The text was updated successfully, but these errors were encountered:
PatMyron
changed the title
Error if API GW Access Logging points to Kinesis Data Firehose not prefixed with amazon-apigateway-
AWS::ApiGateway.AccessLogSetting.DestinationArn AllowedPatternRegex
Aug 26, 2020
Description of issue.
Amazon API Gateway just announced support for writing Access Logs directly to Kinesis Data Firehose instead of CloudWatch Logs.
Buried in the CloudFormation documentation is this constraint:
The stream name prefix constraint is likely going to trip up customers who are letting CloudFormation name their Kinesis Data Firehose delivery stream since it won't have the required prefix unless their stack name begins with amazon-apigateway-.
Opening this issue to see if cfn-lint could help users by detecting this scenario and issuing a warning/error.
The text was updated successfully, but these errors were encountered: