Presently sponsored by PureSec: 30-Day Free Trial. Secure Your Serverless Applications today with the leading Serverless Security solution. Serverless asset inventory, unparalleled real time threat visibility, risk management, security posture analysis and best-of-breed serverless runtime protection.
I needed to find out which process is listening on a port the other day and a quick search on SO showed me the way and all you need is to run:
netstat –aon | find /i "listening"
and you will get a list of the ports and the PID of the process listening on that port:
Sweet!
Yan Cui
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
Further reading
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong