Terraform配置AWS EventBridge调度与API目标的疑问

核心逻辑澄清 #

先明确EventBridge的关键层级关系，和你手动操作的逻辑完全匹配：

• 单个Connection可以被多个API目标复用，不用每个目标单独创建Connection
• 每个Schedule规则只绑定对应1个API目标，避免同一规则关联多个Target

模块代码的潜在问题分析 #

你提到的模块大概率是把Targets设计成了规则的嵌套列表结构，比如：

variable "rules" {
  type = list(object({
    name                = string
    schedule_expression = string
    targets = list(object({
      name = string
      # API目标相关配置项
    }))
  }))
}

如果你的配置里把两个API目标都塞进了同一个规则的targets列表，就会导致该规则绑定两个Target，这就是你疑惑的根源。

正确的Terraform配置结构（贴合你的需求） #

1. 创建单个共享Connection #

resource "aws_cloudwatch_event_connection" "shared_api_conn" {
  name = "shared-api-connection"
  authorization {
    type = "API_KEY" # 替换成你实际用的授权类型，比如OAUTH_CLIENT_CREDENTIALS
    parameters = {
      api_key = "your-actual-api-key"
      # 补充其他授权参数
    }
  }
}

2. 创建两个独立的API目标 #

# 第一个API目标
resource "aws_cloudwatch_event_api_destination" "target_1" {
  name               = "api-target-1"
  connection_arn     = aws_cloudwatch_event_connection.shared_api_conn.arn
  invocation_endpoint = "https://your-api-domain.com/endpoint1"
  http_method        = "POST"
}

# 第二个API目标
resource "aws_cloudwatch_event_api_destination" "target_2" {
  name               = "api-target-2"
  connection_arn     = aws_cloudwatch_event_connection.shared_api_conn.arn
  invocation_endpoint = "https://your-api-domain.com/endpoint2"
  http_method        = "GET"
}

3. 两个Schedule规则分别绑定对应API目标 #

# 第一个调度规则，绑定第一个API目标
resource "aws_cloudwatch_event_rule" "schedule_1" {
  name                = "daily-12pm-trigger"
  schedule_expression = "cron(0 12 * * ? *)" # 每天12点执行
  description         = "Trigger first API target daily"
}

resource "aws_cloudwatch_event_target" "rule_1_target" {
  rule      = aws_cloudwatch_event_rule.schedule_1.name
  target_id = "api-target-1"
  arn       = aws_cloudwatch_event_api_destination.target_1.arn
}

# 第二个调度规则，绑定第二个API目标
resource "aws_cloudwatch_event_rule" "schedule_2" {
  name                = "daily-6pm-trigger"
  schedule_expression = "cron(0 18 * * ? *)" # 每天18点执行
  description         = "Trigger second API target daily"
}

resource "aws_cloudwatch_event_target" "rule_2_target" {
  rule      = aws_cloudwatch_event_rule.schedule_2.name
  target_id = "api-target-2"
  arn       = aws_cloudwatch_event_api_destination.target_2.arn
}

理解偏差纠正 #

1. Connection复用逻辑：你手动操作的思路完全正确，单个Connection可以关联多个API目标，Terraform里直接复用同一个connection_arn就行。
2. 规则与Target的绑定：每个规则对应一个独立的aws_cloudwatch_event_target资源，而不是在一个规则下配置多个Target列表项。如果用模块的话，要确保每个规则的targets数组只包含一个对应API目标的配置。

模块使用的调整方案 #

如果坚持用你参考的EventBridge模块，调整变量输入即可：

• 定义两个规则对象，每个规则的targets数组只放一个对应API目标的配置
• 确保模块内部是为每个规则的每个Target单独创建aws_cloudwatch_event_target资源

示例模块输入：

module "eventbridge" {
  source = "./your-module-path"

  rules = [
    {
      name                = "daily-12pm-trigger"
      schedule_expression = "cron(0 12 * * ? *)"
      targets = [
        {
          name                = "api-target-1"
          api_destination_arn = aws_cloudwatch_event_api_destination.target_1.arn
          # 补充其他Target参数
        }
      ]
    },
    {
      name                = "daily-6pm-trigger"
      schedule_expression = "cron(0 18 * * ? *)"
      targets = [
        {
          name                = "api-target-2"
          api_destination_arn = aws_cloudwatch_event_api_destination.target_2.arn
          # 补充其他Target参数
        }
      ]
    }
  ]

  # 其他模块必填参数...
}

这样模块就会为每个规则创建单独的Target，不会出现同一规则绑定两个Target的问题。

内容的提问来源于stack exchange，提问作者A l w a y s S u n n y