#terraform-aws-modules (2023-11)
Terraform Modules
Discussions related to https://github.com/terraform-aws-modules
Archive: https://archive.sweetops.com/terraform-aws-modules/
2023-11-01
2023-11-02
2023-11-03
2023-11-04
2023-11-05
2023-11-06
2023-11-08
2023-11-14
Hello, I’m using terraform-aws-cloudwatch-events module to trigger a lambda function. My rule is well created, with the lambda in the target but…The Lambda is not associated with eventbridge event.
It’s exactly the same behavior described on this issue but all the proposed solutions don’t work for me.
Have you ever encountered this problem?
Even I observed the same issue. If you see event rule target you can see lambda function. However, in the lambda console it does not shows as source.
I tried creating a target of eventbridge rule with aws cli: same result. When the event is triggered, the lambda is not.
I had to add permission on the lambda side to “link” the target of eventbridge rule to the lambda
aws lambda add-permission \
--function-name YOUR_FUNCTION_NAME \
--statement-id MY_TARGET_ID (set in eventbridge rule target) \
--action 'lambda:InvokeFunction' \
--principal events.amazonaws.com \
--source-arn arn:aws:events:YOUR_REGION:YOUR_ACCOUNT_ID:rule/YOUR_RULE_NAME
2023-11-15
anyone able to review this small PR? https://github.com/cloudposse/terraform-aws-rds-cluster/pull/181
what
Add missing config to aws_rds_cluster.secondary
why
Error: creating RDS Cluster (<redacted>) Instance (<redacted>): InvalidDBClusterStateFault: Set the Serverless v2 scaling configuration on the parent DB cluster before creating a Serverless v2 DB instance.
│ status code: 400, request id:
Tested on my cluster and confirmed to work when a serverless configuration is provided.
Anyone able to re-check this for me? I believe the test should now pass
what
Add missing config to aws_rds_cluster.secondary
why
Error: creating RDS Cluster (<redacted>) Instance (<redacted>): InvalidDBClusterStateFault: Set the Serverless v2 scaling configuration on the parent DB cluster before creating a Serverless v2 DB instance.
│ status code: 400, request id:
Tested on my cluster and confirmed to work when a serverless configuration is provided.
merged! thanks for the contribution!
no worries! thanks