Amazon came close to serverless efforts with EB (Elastic Beanstalk). EB allows developers to upload code directly to the machines through the AWS GUI as compressed packages much like AWS Lambda does. However, unlike Lambda, EB allows developers to configure autoscaling, permits sysadmins and devs to log into the EC2 machines that Elastic Beanstalk sits on and make alterations, and grants access to load balancer with defined endpoints.nnAWS Lambda sits on ECS; thus, there are no EC2 machines in question. Since the underlying infrastructure is inaccessible and scale is not configurable (read: auto-scaling), sysadmins has no job. The containers once orchestrated on Amazon Elastic Container Registry (ECR) can’t be modified. Although load balancer endpoints are missing, you can still access them via Amazon API Gateway. Another advantage ECS brings to AWS Lambda is AWS Fargate. The time when you had to manage servers or clusters just for the sake of running your containers is gone. Fargate scales and manages the infrastructure required to run your containers.