- Mais recentes
- Mais votos
- Mais comentários
Thanks for the quick replies! I originally didnt use a VPC but I was getting the same error which is why I tried the VPC approach.
If the VPC isn't required I'll remove it.
See below for the cloudwatch log snip, could this be an issue with the version of selenium or chrome webdriver I have used?
First, I do not see any reason to attach your function to a VPC. It does not seem you are actually accessing any private resources in your VPC.
If you do need the VPC for some reason, your function must be attached to a private subnet with a route to a NAT Gateway or to VPC endpoints to different AWS services you need to access (e.g., S3 in your case).
If Lambda is configured in a VPC, check the route table of the subnet where Lambda is configured to see if there is a route to the NAT Gateway.
Also verify that the security group's outbound rules allow it and that the network ACLs allow the necessary communications.
https://docs.aws.amazon.com/lambda/latest/dg/troubleshooting-networking.html
You may want to check if the Lambda function is configured with the correct security group and network ACL settings that allow outbound traffic.
Another thing to check is if your VPC has a NAT gateway or NAT instance set up for internet connectivity. Without a NAT, your Lambda function would not be able to communicate with resources outside of your VPC.
You can also check the AWS CloudWatch logs for your Lambda function to see if there are any additional error messages or clues as to why the network call failed.
Conteúdo relevante
- AWS OFICIALAtualizada há 6 meses
- AWS OFICIALAtualizada há 2 anos
- AWS OFICIALAtualizada há 6 meses
The error message "Chrome failed to start ~" appears in the log of the image.
This error can be fixed by adding the following options.