thdxr
10/30/2021, 4:10 PMSimon Reilly
11/02/2021, 9:05 AMAshishkumar Pandey
11/04/2021, 9:19 AMÖmer Toraman
11/04/2021, 2:29 PMarda
11/07/2021, 4:13 PMthdxr
11/08/2021, 7:03 PMthdxr
11/11/2021, 5:36 AMthdxr
11/11/2021, 8:53 PMPostPost.fromAuthor(author)Post.fromAuthorWithCommentsWithCommenterFirstName()Ömer Toraman
11/15/2021, 10:36 PM//////////////////////////////
//
//////////////////////////////Danny
11/16/2021, 5:00 AMOmi Chowdhury
11/16/2021, 5:47 PMAdrian Schweizer
11/16/2021, 9:22 PMmanitej
11/17/2021, 6:41 AMJP (junaway)
11/17/2021, 4:29 PMDaniel
11/17/2021, 6:43 PMSam Hulick
11/18/2021, 2:44 AMSam
11/18/2021, 9:49 AMmanitej
11/18/2021, 2:44 PMJP (junaway)
11/18/2021, 3:09 PMJP (junaway)
11/18/2021, 3:21 PMClayton
11/18/2021, 10:33 PMÖmer Toraman
11/19/2021, 7:04 AMErik Robertson
11/19/2021, 8:39 AMSam Hulick
11/20/2021, 3:28 AMÖmer Toraman
11/22/2021, 9:07 AMOmi Chowdhury
11/23/2021, 12:12 AMthdxr
11/23/2021, 2:31 AMmanitej
11/23/2021, 1:51 PMRoss Coundon
11/23/2021, 1:56 PMWhen you use Lambda outside VPC, it means a request to DynamoDB will go over the internet which might traverse over multiple ISPs. This leaves room where requests may get lost along the path, this is especially true if the issue is intermittent and error shows timeout exceptions.
It is actually better from a DynamoDB perspective to have your Lambda inside a VPC, this is because the network path becomes predictable, thus more stable. When you have your Lambda inside the VPC, you can make use of DynamoDB's VPC endpoint to access DynamoDB (Lambda -> Lambda ENI - > DDB VPCendpoint -> DDB service). Furthermore, this allows better monitoring, because you will be able to use VPC flow logs to see network traffic and determine if messages are being dropped. Since DNS uses UDP for DNS queries, the packets can get lost along the path (Lambda probably has a retry mechanism for retry DNS queries).thdxr
11/24/2021, 10:21 PM