-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Add Kinesis streams as Lambda event sources #3897
Comments
+1 |
My current workaroud is to use local-exec. eg.
|
+1 and thanks for the workaround @nick-nz! |
I have submitted the above referenced issue (#4089) as the event mapping workaround here seems to not work if IAM access exists between the role and the Lambda function. It bails saying that the mapping is a duplicate, and upon inspection on the console, the mapping is there, albeit disabled with an error. |
Correction to the above, it might be a stale mapping due to the need for a workaround. Check out the issue for more details. |
Submitted PR to add |
#4093 has now been merged, so I'll go ahead and close this issue. It will be in the 0.6.8 release of Terraform. Thanks for bringing this up @nick-nz, and implementing it @vancluever! |
Awesome. Thanks @vancluever! |
…scaling_group-az-vpc-diffs docs/resource/aws_autoscaling_group: Clarify usage of availability_zones
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. |
Feature request to be able to do this in Terraform:
Instructions for doing this via the AWS CLI are in step 3.2 of the docs here: http://docs.aws.amazon.com/lambda/latest/dg/wt-kinesis-configure-kinesis.html
The text was updated successfully, but these errors were encountered: