AWS Lambda is a service that provides a way for developers to quickly write services without worrying about the underlying infrastructure. However, upon trying to use it for a real-world HTTP-based microservices project, Ambassador Labs found some uncool things that make Lambda not yet ready for the prime time. These issues include Lambda being a building block rather than a tool, poor documentation, and inadequate error handling. The root of the problem is that AWS provides building blocks like Lambda and API Gateway, leaving it up to developers to connect them manually. This manual process can be tedious and prone to errors, especially when dealing with versioned endpoints or HTTPS. To overcome these issues, various tools are being developed, such as Terraform, Serverless, and Zappa, which aim to automate the process of setting up Lambda and API Gateway. Despite its promise, AWS Lambda is not yet ready for production use due to its limitations in handling errors, providing clear documentation, and offering a seamless user experience.