Abstract: In accordance with input received via a programmatic interface, a level of isolation at which a software container is to be executed is determined. Based on the level of isolation, a category of virtual machines of a virtualized computing service is selected for executing the software containers. The selected category differs from other categories in at least the number of devices emulated for virtual machines of the categories. The software container is run within a virtual machine of the selected category.

Abstract: The present application relates to providing a mechanism for specifying multiple network interfaces to be configured for on-demand compute capacity and for obtaining the credentials needed to configure the multiple network interfaces. For example, a container orchestration service may specify, in its code execution request to a serverless container management service, that multiple network interfaces are needed for the requested compute capacity. In response, the serverless container management service can identify the multiple network interfaces, determine the credential to be used to configure each of the multiple network interfaces, and attach the multiple network interfaces to the compute capacity acquired on behalf of the container orchestration service. During execution, the code running inside the compute capacity can utilize the multiple network interfaces as specified by the owner of the code.

Abstract: Provided is a system for managing the resource limit associated with a user, where the resource limit indicates the amount of compute resources the user is allowed to use. As the user requests and obtains additional resources from a pool of resources, the user's resource usage is increased to reflect the additional resources being used by the user. As the resources used by the user are released, to ensure that the pool of resources has sufficient capacity to handle additional resource requests, the replenishment status of the pool is further checked, and if the replenishment status satisfies a condition for updating the user's resource usage, the user's resource usage is decreased to reflect the resources that are no longer in use by the user. The released resources are torn down and re-provisioned back into the pool of resources.

Abstract: The present application relates to executing a containerized application in a nested manner on two separate container orchestration services. For example, a user may submit a request to a container orchestration service to execute a containerized application, and in response, instead of identifying one of the existing compute instances belonging to the user and executing the containerized application on the identified compute instance, the container orchestration service may generate and submit a request to a serverless container management service that can not only acquire compute resources on behalf of the container orchestration service but also manage the compute resources such that the container orchestration service (or the original requesting user) does not need to manage scaling, monitoring, patching, and security of the compute resources.

Abstract: Techniques for instantiating container instances from a pool of available container instances are described herein. An instance type is determined from a container description such that the instance type satisfies the resource parameters in the container description. An instance of the instance type is selected from a pool of running container instances, the instance is provisioned, and a container is instantiated on the instance.

Abstract: Techniques for instantiating container instances from a pool of available container instances are described herein. An instance type is determined from a container description such that the instance type satisfies the resource parameters in the container description. An instance of the instance type is selected from a pool of running container instances, the instance is provisioned, and a container is instantiated on the instance.