How to fix Error: Error creating EventBridge Rule: ResourceAlreadyExistsException in Terraform

TerraformINTERMEDIATEMEDIUM

This error occurs when Terraform attempts to create an EventBridge rule that already exists in AWS. This typically happens due to state drift, duplicate configurations, or rules created outside of Terraform. You can resolve this by importing the existing resource or ensuring unique rule names.

What this error means

The `ResourceAlreadyExistsException` error indicates that AWS EventBridge detected an attempt to create a rule with a name that already exists in the specified event bus. EventBridge enforces unique rule names within each event bus. This error can occur in several scenarios: 1. **State Drift**: The rule exists in AWS but Terraform doesn't know about it (the state file is out of sync) 2. **Manual Creation**: Someone created the rule through the AWS Console or CLI outside of Terraform 3. **Multiple Workspaces**: Different Terraform workspaces or teams deployed the same rule 4. **Duplicate Configuration**: The same rule is defined multiple times in your Terraform configuration 5. **Cross-deployment Conflict**: Another deployment or service created the rule before Terraform could EventBridge rules must have unique names within the same event bus. The error prevents accidental overwrites and ensures infrastructure consistency.

How to fix "Error: Error creating EventBridge Rule: ResourceAlreadyExistsException"

1Check if the rule exists in AWS EventBridge

First, verify that the rule actually exists in AWS. List all rules in the event bus to confirm:

bash

# List all EventBridge rules in the default event bus
aws events list-rules

# List rules in a specific event bus
aws events list-rules --event-bus-name "your-event-bus-name"

# Describe a specific rule to see its details
aws events describe-rule --name "your-rule-name"

If the rule exists in the output, you have state drift and need to import it into Terraform state.

2Import the existing rule into Terraform state

If the rule already exists in AWS but isn't in your Terraform state, import it using terraform import:

bash

# Import a rule from the default event bus
terraform import aws_cloudwatch_event_rule.my_rule my_rule_name

# Import a rule from a specific event bus (format: rule_name/event_bus_name)
terraform import aws_cloudwatch_event_rule.my_rule my_rule_name/my-event-bus

# For event buses, use the full event bus name
terraform import aws_cloudwatch_event_rule.partner_rule partner_rule_name/aws.partner/example.com/123456/default

After import, verify the rule is now in state:

bash

terraform state show aws_cloudwatch_event_rule.my_rule

3Remove duplicate resource definitions

Check your Terraform configuration for duplicate aws_cloudwatch_event_rule blocks with the same name. Remove or consolidate duplicates:

hcl

# BAD: Duplicate rule definitions
resource "aws_cloudwatch_event_rule" "my_rule_1" {
  name = "my-event-rule"
  # ...
}

resource "aws_cloudwatch_event_rule" "my_rule_2" {
  name = "my-event-rule"  # Same name - causes conflict!
  # ...
}

# GOOD: Single rule definition
resource "aws_cloudwatch_event_rule" "my_rule" {
  name = "my-event-rule"
  # ...
}

Use grep to find potential duplicates:

bash

# Search for rule name in all .tf files
grep -r "aws_cloudwatch_event_rule" .
grep -r "name.*=.*my-rule" .

4Use unique names with environment prefixes

Prevent naming conflicts across environments by using environment-specific prefixes:

hcl

variable "environment" {
  default = "prod"
}

resource "aws_cloudwatch_event_rule" "my_rule" {
  name = "${var.environment}-my-event-rule"
  # This creates unique names: prod-my-event-rule, staging-my-event-rule, etc.
}

Or use workspace names for multi-workspace deployments:

hcl

resource "aws_cloudwatch_event_rule" "my_rule" {
  name = "${terraform.workspace}-my-event-rule"
  # For 'default' workspace: default-my-event-rule
  # For 'prod' workspace: prod-my-event-rule
}

5Use name_prefix for auto-generated unique names

Instead of specifying a fixed rule name, use name_prefix to let AWS auto-generate unique names:

hcl

resource "aws_cloudwatch_event_rule" "my_rule" {
  name_prefix = "my-event-rule-"
  # AWS will create unique names like: my-event-rule-abc123def456
}

This approach eliminates naming conflicts entirely, as each rule gets a unique suffix. The tradeoff is that rule names become less predictable and harder to reference manually.

6Refresh Terraform state and retry

If you've resolved the underlying issue (imported the rule, removed duplicates), refresh your state and try again:

bash

# Refresh Terraform state to sync with current AWS resources
terraform refresh

# Run plan to see what would be created/changed
terraform plan

# Apply the changes
terraform apply

If you're confident the rule should be removed from AWS to make room for Terraform to manage it, you can delete it first:

bash

# Delete the rule via AWS CLI (WARNING: This is destructive!)
aws events delete-rule --name "my-rule-name"

# Then retry Terraform apply
terraform apply

Advanced notes

### EventBridge Rule Naming Constraints

EventBridge rule names must:
- Be 1-64 characters long
- Contain only alphanumeric characters, hyphens, and underscores
- Be unique within each event bus
- Not start or end with a hyphen

### Event Bus Considerations

When importing or creating rules, consider the event bus:

hcl

# Default event bus (implicit)
resource "aws_cloudwatch_event_rule" "default_bus_rule" {
  name = "my-rule"
  # Uses the default event bus in your AWS account
}

# Custom event bus (explicit)
resource "aws_cloudwatch_event_rule" "custom_bus_rule" {
  name           = "my-rule"
  event_bus_name = "my-custom-bus"
}

# Partner event bus
resource "aws_cloudwatch_event_rule" "partner_bus_rule" {
  name           = "my-rule"
  event_bus_name = "aws.partner/example.com/123456/default"
}

Rules on different event buses can have the same name without conflict. Import syntax must include the event bus name for non-default buses.

### Terraform State Drift Detection

To proactively detect state drift:

bash

# Show all managed EventBridge rules
terraform state list | grep aws_cloudwatch_event_rule

# Compare state with actual AWS resources
terraform plan

# View the state file directly (for debugging)
terraform state show aws_cloudwatch_event_rule.my_rule

### CI/CD and Multi-team Deployments

In shared environments with multiple teams:

1. Use separate Terraform workspaces for each environment/team
2. Implement rule naming conventions: {team}-{environment}-{purpose}
3. Use Terraform state locking to prevent concurrent modifications
4. Consider using Terraform Cloud/Enterprise for centralized state management

### Targets and Rule Cleanup

When deleting a rule with targets:

hcl

# Terraform will automatically remove associated targets
resource "aws_cloudwatch_event_rule" "my_rule" {
  name = "my-rule"
  # When destroyed, associated aws_cloudwatch_event_target resources are also removed
}

# Make sure targets depend on the rule
resource "aws_cloudwatch_event_target" "my_target" {
  rule      = aws_cloudwatch_event_rule.my_rule.name
  target_id = "my-target"
  # ... target configuration ...
}

How to fix Error: Error creating EventBridge Rule: ResourceAlreadyExistsException in Terraform

What this error means

Typical symptoms

Common causes

How to fix "Error: Error creating EventBridge Rule: ResourceAlreadyExistsException"

Advanced notes

Related errors

Official resources & further reading