2 個答案
- 最新
- 最多得票
- 最多評論
2
This is what you need .... https://aws.amazon.com/pt/blogs/compute/introducing-amazon-eventbridge-scheduler/
已回答 1 年前
0
What are you scaling concerns with cloudwatch? Have you also considered EventBridge or Step Functions to create a workflow? Also why have you discontinued sqs?
已回答 1 年前
discounted SQS on its own, because there's no time/schedule attribute, all tasks are just FIFO... previously thought that cloudwatch events (where each future job is a scheduled task) would become expensive (millions of jobs). Now thinking that the recurring schedule of jobs is the item i create (likely in eventbridge), and that handles the creation of individual jobs/lambda calls
相關內容
- AWS 官方已更新 2 年前
yep, looks like thats it. We're giving it a run now. Thanks for your help