Skip to content

eventbridge-sfn-terraform: Update AWS Provider to v6 #3069

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kakakakakku wants to merge 2 commits into
base: main
Choose a base branch
from
Open

eventbridge-sfn-terraform: Update AWS Provider to v6 #3069

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1fcc393
eventbridge-sfn-terraform: Update AWS Provider to v6
kakakakakku Apr 20, 2026
3733b50
eventbridge-sfn-terraform: Fix Step Function to Step Functions
kakakakakku Apr 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions eventbridge-sfn-terraform/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# EventBridge to Step Function
# EventBridge to Step Functions

This pattern demonstrates executing a Step Function using an EventBridge rule.
This pattern demonstrates executing a Step Functions using an EventBridge rule.

In this example, the EventBridge rule specified in `main.tf` filters the events based upon the criteria in the `aws_cloudwatch_event_rule` block. When matching events are sent to EventBridge that trigger the rule, they are delivered as a JSON event payload (see "Example event payload from EventBridge to SQS" in the README) to the Step Function as an Input.
In this example, the EventBridge rule specified in `main.tf` filters the events based upon the criteria in the `aws_cloudwatch_event_rule` block. When matching events are sent to EventBridge that trigger the rule, they are delivered as a JSON event payload (see "Example event payload from EventBridge to SQS" in the README) to the Step Functions as an Input.

Learn more about this pattern at Serverless Land Patterns: https://serverlessland.com/patterns/eventbridge-sfn

Expand Down Expand Up @@ -39,7 +39,7 @@ Important: this application uses various AWS services and there are costs associ

## How it works

The template creates a shell Step Function, with a CloudWatch log group for log reporting of all events, that triggers based upon the criteria in the `aws_cloudwatch_event_rule` block and branches based on the value.
The template creates a shell Step Functions, with a CloudWatch log group for log reporting of all events, that triggers based upon the criteria in the `aws_cloudwatch_event_rule` block and branches based on the value.

## Testing

Expand All @@ -51,16 +51,16 @@ The template creates a shell Step Function, with a CloudWatch log group for log
```bash
aws events put-events --entries file://event-B.json
```
1. Send an event for Path C to EventBridge, which should cause the Step Function to fail:
1. Send an event for Path C to EventBridge, which should cause the Step Functions to fail:
```bash
aws events put-events --entries file://event-Fail.json
```

Go to the Step Function created by this template to view the new execution that ran.
Go to the Step Functions created by this template to view the new execution that ran.

![](./images/stepfunctions_graph.png)

You can also go to the CloudWatch Logs stream in the Log Group displayed in the output of the terraform deployment to check the results of the three events that triggered the Step Function.
You can also go to the CloudWatch Logs stream in the Log Group displayed in the output of the terraform deployment to check the results of the three events that triggered the Step Functions.
## Cleanup

1. Change directory to the pattern directory:
Expand Down
16 changes: 8 additions & 8 deletions eventbridge-sfn-terraform/main.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 3.27"
version = "~> 6.0"
Copy link
Copy Markdown
Contributor

@parikhudit parikhudit May 26, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optional: jumping ~> 3.27 → ~> 6.0 skips v4 and v5. The Terraform v6 upgrade guide recommends stepping through the latest 5.x first. None of the resources used here seem to have v6 breaking changes, so for fresh deployments this works. However, please confirm in the PR description that you've run terraform init && terraform apply against ~> 6.0 end-to-end.
Thanks

}
}

Expand Down Expand Up @@ -52,7 +52,7 @@ resource "aws_iam_role" "StateMachineRole" {
POLICY2
}

# Create an IAM policy for Eventbridge to be able to start a Step Function execution
# Create an IAM policy for Eventbridge to be able to start a Step Functions execution
Copy link
Copy Markdown
Contributor Author

@kakakakakku kakakakakku Apr 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: Fix to correct service name😀
https://docs.aws.amazon.com/step-functions/latest/dg/welcome.html

Copy link
Copy Markdown
Contributor

@parikhudit parikhudit May 26, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Naming: Request you to refer the official Lambda durable functions docs. Same applies in hitl-lambda-durable-function-cdk/README.md and fix pre-existing nits for AWS Service names, including this one.

resource "aws_iam_policy" "EventBridgePolicy" {
policy = <<POLICY3
{
Expand All @@ -70,7 +70,7 @@ resource "aws_iam_policy" "EventBridgePolicy" {
POLICY3
}

# Create an IAM policy to enable Step Function State Machine to push logs to CloudWatch logs
# Create an IAM policy to enable Step Functions State Machine to push logs to CloudWatch logs
resource "aws_iam_policy" "StateMachineLogDeliveryPolicy" {
policy = <<POLICY4
{
Expand Down Expand Up @@ -106,12 +106,12 @@ resource "aws_iam_role_policy_attachment" "StateMachinePolicyAttachment" {
policy_arn = aws_iam_policy.StateMachineLogDeliveryPolicy.arn
}

# Create an Log group for the Step Function
# Create an Log group for the Step Functions
resource "aws_cloudwatch_log_group" "MyLogGroup" {
name_prefix = "/aws/vendedlogs/states/StateMachine-terraform-"
}

# Create a Step Function State Machine
# Create a Step Functions State Machine
resource "aws_sfn_state_machine" "sfn_state_machine" {
name = "eventbridge-state-machine-demo-${data.aws_caller_identity.current.account_id}"
role_arn = aws_iam_role.StateMachineRole.arn
Expand Down Expand Up @@ -169,7 +169,7 @@ resource "aws_cloudwatch_event_rule" "MyEventRule" {
PATTERN
}

# Set the Step Function as target to the Eventbridge rule
# Set the Step Functions as target to the Eventbridge rule
resource "aws_cloudwatch_event_target" "SFNTarget" {
rule = aws_cloudwatch_event_rule.MyEventRule.name
arn = aws_sfn_state_machine.sfn_state_machine.arn
Expand All @@ -184,5 +184,5 @@ output "CW-Logs-Stream-Name" {

output "StepFunction-Name" {
value = aws_sfn_state_machine.sfn_state_machine.name
description = "The Step Function Name"
}
description = "The Step Functions Name"
}