Abstract: Systems and methods are described for providing an application-level gateway to an on-demand network code execution system. An on-demand network code execution system may allow users to submit code to be executed in a serverless environment, and may provide an interface for executing the user-submitted code on demand. The interface may require that users authenticate, provide input in a particular format, or meet other criteria when sending a request to execute the code. An application-level gateway may thus provide an interface that implements these functions, thereby allowing computing devices to interact with the code as though it were running on a server (e.g., by using HTTP). The application-level gateway may also use on-demand code execution to provide load balancing for servers that are running the user-submitted code, and seamlessly provide access to code that runs on both server-based and serverless environments.

Abstract: Techniques for an identity-aware load balancer (ALB) are described. An identity-aware ALB can securely authenticate users when accessing web-based applications accessed through the ALB, or a node of the ALB. An application owner can configure an authentication action in the ALB. When a request for the application is received, the ALB inspects the request for a session cookie to determine whether the requesting user is logged-in. If the request includes a session cookie, the ALB can decrypt the session cookie and provide identity information with the request to the application. If no session cookie is included, or if the session cookie is expired, the ALB can authenticate the user with an identity provider specified in the authentication action. Integrating authentication into an ALB simplifies application development and maintenance, and improves security, since fewer changes to the application stack reduce the chances of errors being introduced.

Abstract: An example method for connection persistence across server farms in a network environment is provided and includes associating a first real server with a first server farm attached to a first virtual Internet Protocol address (VIP), associating a second real server with a second server farm attached to a second VIP, and linking the first real server with the second real server in a particular group. The first real server is configured to service a first connection from a client to the first VIP in a network environment, the second real server is configured to service a second connection from the client to the second VIP in the network environment, and the method further includes facilitating connection persistence of the first connection with the second connection across the first server farm and the second server farm.

Abstract: An example method for connection persistence across server farms in a network environment is provided and includes associating a first real server with a first server farm attached to a first virtual Internet Protocol address (VIP), associating a second real server with a second server farm attached to a second VIP, and linking the first real server with the second real server in a particular group. The first real server is configured to service a first connection from a client to the first VIP in a network environment, the second real server is configured to service a second connection from the client to the second VIP in the network environment, and the method further includes facilitating connection persistence of the first connection with the second connection across the first server farm and the second server farm.