Skip to content
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.

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

EventBridge with schedule rule and Step Functions target #73

Closed
yushkevicham opened this issue Dec 16, 2022 · 6 comments · Fixed by #76
Closed

EventBridge with schedule rule and Step Functions target #73

yushkevicham opened this issue Dec 16, 2022 · 6 comments · Fixed by #76

Comments

@yushkevicham
Copy link

module "eventbridge". version = "1.17.0"
Hey. I want to apply EventBridge with schedule rule and Step Functions target for multiple environments. How can I customize the IAM role name to access state machines? I'm running into a error: error creating IAM Policy default-sfn: EntityAlreadyExists: A policy called default-sfn already exists. Duplicate names are not allowed.

@kostasns
Copy link

Hello,

you can provide role_name variable in module to set desired name for your role

role_name = local.create_role ? coalesce(var.role_name, var.bus_name, "*") : null

@yushkevicham
Copy link
Author

Hello,

you can provide role_name variable in module to set desired name for your role

role_name = local.create_role ? coalesce(var.role_name, var.bus_name, "*") : null

Thanks, I already figured it out. Initially confused by the description: Name of IAM role to use for Lambda Function

@yushkevicham
Copy link
Author

Let me ask one more question. How can I change the name of an eventbridge rule from a default "crons-rule" to another. tags = {
Name = "Bla-bla-bla" } doesn't work.

@kostasns
Copy link

Use the name "Bla-bla-bla" instead of "crons"

"Name" = var.append_rule_postfix ? "${replace(index, "_", "-")}-rule" : index

@antonbabenko
Copy link
Member

This issue has been resolved in version 1.17.1 🎉

Copy link

github-actions bot commented Mar 9, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants