- 最新
- 最多得票
- 最多評論
There are multiple ways to achieve this. But it really depends what kind of status you want to track.
For real timenotifications within a short duration, you can take advantage of Event notification from object upload and pair it with SNS/SQS/Lambda and use some sort of Database or a text/csv file to keep track of objects uploaded. This will require code.
If the tracking can wait for 24+ hours, then S3 inventory is a better choice. It's very easy to configure without any code.
Decouple the process by sending the S3 notification to a SQS queue. https://docs.aws.amazon.com/AmazonS3/latest/userguide/how-to-enable-disable-notification-intro.html
Then have your Lambda function poll the queue. https://docs.aws.amazon.com/lambda/latest/dg/with-sqs.html
You could also look at using the S3 inventory https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-inventory.html
I would say that even going with Lambda notification should be ok for you if the lambda is only saving to DynamoDB because it should be super fast. It's not so easy to reach the account limit. But it is possible, so you can notify SQS instead of Lambda and trigger Lambda from SQS but using batch. For standard SQS it can be maximum 10000 items in one batch, so you will call Lambda much less often.
相關內容
AWS 官方已更新 1 年前- AWS 官方已更新 2 年前
- AWS 官方已更新 9 個月前
- AWS 官方已更新 10 個月前