- Le plus récent
- Le plus de votes
- La plupart des commentaires
Apparently, your function is in a VPC. If it's really necessary to use a VPC, check the subnet; if it is public, for private it must go out to the internet via NAT Gateway, or you will need to use VPC Endpoints (there's a cost) to reach the necessary AWS services, such as ECR, S3, Redshift. It's also necessary to check the VPC security group rules for this function to see if they allow the necessary connections. Are you using ECR for your image? Is the function at least able to download the image?
Arhh I think I know whats happening.
Your Lambda function may not have access to the S3 or RedShift Endpoints. Can you confirm if your Lambda is connected to a VPC or not? If it is VPC connected, you will either need the Lambda function in a Private subnet with a route to a NAT gateway OR to have VPC Endpoints setup for each service the Lambda function needs to consume.
If its not in a VPC, then connectivity will be good for S3
The Lambda function wasn't connected to a VPC.
Since the Redshift is in a VPC, that's why the Lambda function is not working?
I'll work on the NAT Gateway and get back here. Thanks for the kind guidance!
If your Redshift is only accessible privately through the VPC, your Lambda function must be in the same VPC for the connection to occur. With that, follow the other tips mentioned above.
When the Lambda function is not in a VPC, it only gets a temporary EIP and works directly via the internet.
Gotcha! Thanks for the confirmation. I'll follow the steps you have proposed.
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
Can you share the error when crashing? Any log outputs?