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

Feature request: SQS trigger lambda function #18354

Closed
asimtech12 opened this issue Jun 29, 2018 · 3 comments
Closed

Feature request: SQS trigger lambda function #18354

asimtech12 opened this issue Jun 29, 2018 · 3 comments

Comments

@asimtech12
Copy link

AWS have recently released feature where a lambda function can be triggered by SQS message,
We are using terraform in our project for IaC and this feature would simplify our solution.
manually we can use SQS message to trigger lambda using AWS console ::

aws console-->lambda function-->(left pane add trigger)SQS --> select your SQS queue(to listen for updates on)-->add-->save

Thanks
Asim

Terraform Version

terraform version = 1.16.0

References

AWS reference document
https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-lambda-function-trigger.html

https://aws.amazon.com/blogs/aws/aws-lambda-adds-amazon-simple-queue-service-to-supported-event-sources/

@drkreddy
Copy link

This is really an interesting release from AWS, for which we were waiting for long time. We are using Terraform in our project. We are in need of this feature to configure SQS as trigger point for Lambda.

Thanks
Ravindra

@asimtech12 asimtech12 changed the title SQS trigger lambda function Feature request: SQS trigger lambda function Jun 29, 2018
@ghost
Copy link

ghost commented Jun 29, 2018

This issue has been automatically migrated to hashicorp/terraform-provider-aws#5030 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#5030.

@ghost ghost closed this as completed Jun 29, 2018
@ghost
Copy link

ghost commented Apr 4, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 4, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants