ps.lookup doesn't work on AWS Lambda
See original GitHub issueYou’re using ps.loopup() from the ps-node package. However ps l doesn’t seem to work on AWS Lambda. Is it really needed here?
I ran a few tests here:

Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Using Parameter Store parameters in AWS Lambda functions
Learn how to use the AWS Parameters and Secrets Lambda Extension with Parameter Store.
Read more >Troubleshoot Lambda permissions issues - Amazon AWS
I have several permissions issues associated with my AWS Lambda function. What troubleshooting steps should I take?
Read more >Troubleshooting AWS IoT Greengrass
Search the following symptoms and errors to find information to help troubleshoot issues with an AWS IoT Greengrass core. Issues. Error: The configuration...
Read more >How do I troubleshoot Lambda function failures? - AWS
To troubleshoot Lambda function failures, first determine what's causing the error by using one or more of the AWS services and features ...
Read more >Troubleshoot networking issues in Lambda
Network connectivity errors can result from issues with your VPC's routing configuration, security group rules, AWS Identity and Access Management (IAM) role ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@adieuadieu I was also getting numerous headless_shell zombies. Using the --no-zygote flag solved the issue for me.
Looking forward to getting the rework! We need you 😃 https://news.ycombinator.com/item?id=14105489