Skip to main content
Amazon API Gateway emits two log streams: execution logs (request handling, integration latency, errors) and access logs (request/response details with custom format strings). Support differs by API type: CloudWatch Log Forwarder — enable execution and access logging on each API stage and the Bronto forwarder Lambda subscribes to the CloudWatch Log Groups and streams events into Bronto.

​
Alternatives

  • Amazon Data Firehose — for high-volume access logs.
    • REST APIs: set the stage’s access log destination directly to a Firehose stream. The stream name must start with amazon-apigateway-. A stage sends access logs to CloudWatch Logs or Firehose, not both; execution logs stay in CloudWatch Logs.
    • HTTP and WebSocket APIs: access logs go to CloudWatch Logs only. Add a subscription filter on the access-log group targeting a Firehose stream.
    Choose the JSON access-log format so Bronto flattens fields automatically — a CLF/CSV/XML format is stored raw and requires a custom parser. See Record formats.
See Ingesting AWS Data into Bronto for the full service-to-method mapping.

​
References