AWS API gateway

2.5.2 — 15^th July

Resolved Issue

Regression in accounts Input

Fixed a regression that impacted the accounts input when the agent was configured to monitor every API Gateway.

2.5.1 — 4^th July

Update

Support for Direct Log Group Names and Custom Access Log Format

This release introduces two new configuration options: log_groups and access_log_format, providing greater control over access logging.

• log_groups
  Allows you to directly specify a list of CloudWatch log group names where traffic logs should be captured. This option is practical when you want to use explicit log group names instead of associating logs with API Gateway stages.

• access_log_format
  Required when using the log_groups option. This setting defines the access log format used by API Gateway instances, allowing you to control the structure and content of access logs written to the specified log groups.

2.5.0 — 1^st July

Traceable’s AWS API gateway agent 2.5.0 provides the following:

Updates

Upgraded AWS SDK

The AWS JavaScript SDK has been upgraded to version 3 to ensure compatibility with the latest AWS features and libraries.

Runtime and AMI Update

The runtime has been updated to Node.js 22, and the default Amazon Machine Image (AMI) for EC2-based deployments is now Amazon Linux 2023 (AL2023).

Enhanced Access Log Parsing

Support has been added for parsing access log entries that use single-quoted JSON strings, improving compatibility with different customer log formats.

2.4.1 — 7^th April

Traceable’s AWS API gateway agent 2.4.1 provides the following:

Updates

• Upgraded Terraform provider to version 0.6.0:
  The Terraform provider used in AWS API Gateway integration has been updated to v0.6.0. This version includes:

  • Fixes for lingering provider processes that were not terminating cleanly.

  • Support for the single-quoted access_map format for better compatibility.

Resolved Issues

• Fixed missing ECS task tags in CloudFormation ECS deployments:
  Resolved an issue where ECS tasks responsible for CloudWatch log scraping were not inheriting tags passed via CloudFormation. While ECS task definitions and services were correctly tagged, the individual tasks were not, impacting customers' ability to track costs accurately.

• Fixed CloudFormation update failures due to invalid input:
  Updates to existing ECS-based deployments now handle malformed input (for example, invalid accounts JSON) more gracefully. Faulty inputs no longer block the entire stack update, helping reduce deployment friction and manual intervention in such scenarios.

2.4.0 — 26^th March

Traceable’s AWS API gateway agent 2.4.0 provides the following:

Update

• Added support for configurable cron interval in ECS log polling:
  You can now configure the time interval (in minutes) at which the cron job runs to pull CloudWatch logs. This setting is available in both Terraform and CloudFormation templates.

  • Terraform variable: cron_interval_mins

  • CloudFormation parameter: CronIntervalMins

  • Description: Time interval (in minutes) at which the cron job is triggered.

  • Default value: 5

  This enhancement allows greater flexibility, particularly in non-production environments where a higher interval can help reduce infrastructure costs.

2.3.3 — 12^th February

Traceable’s AWS API gateway agent 2.3.3 provides the following:

Resolved Issue

• Fixed Terraform template failure due to local-exec block:
  Updated the Terraform template to resolve a failure caused by the use of a local-exec provisioner when generating and executing the user data script. The previous implementation caused script execution errors and plugin crashes during deployment. The new version uses a more robust approach to inject and execute user data without relying on local-exec, improving reliability across environments.

2.3.2 — 7^th January

Resolved issue

• 2.3.2 release resolves an issue with the CloudFormation template for ECS deployment upgrades that caused the setup to be deleted during updates.