Abstract: Implementation of cross provider security in accordance with the disclosures made herein enables users of a system (e.g., a cloud services brokerage platform) in a cloud environment provides for system-managed provisioning and management of keys to cloud resources thereby allowing the user to manage data security and enable secured access to their cloud resources. To this end, cross provider security management functionality in accordance with the disclosures made herein can include provisioning system-generated keys across different regions in a provider, provisioning cloud brokerage system-generated keys across different providers; and associating (i.e., managing) the keys from the system to a hardware security module. The keys can be managed by/though a variety of different resources (e.g., brokering system, VDC, user group concepts, etc).

Abstract: A fulfillment bridge orchestrates various types of fulfillment that fall generally into three categories of fulfillment: CSB platform based automated provisioning; external automated provisioning; and manual workflow provisioning. External automated provisioning is implemented through fulfillment agents. The fulfillment agents can implements self-registration for allowing the fulfillment bridge to understand the capabilities of the fulfillment agent. Examples of such capabilities include, but are not limited to, supported actions and input/output parameters. Adapters of the fulfillment bridge interface with the fulfillment agents and fulfillment scripts that are independently operated with respect to the CSB platform can be use to interface with the fulfillment adapters.

Abstract: A fulfillment bridge orchestrates various types of fulfillment that fall generally into three categories of fulfillment: CSB platform based automated provisioning; external automated provisioning; and manual workflow provisioning. External automated provisioning is implemented through fulfillment agents. The fulfillment agents can implements self-registration for allowing the fulfillment bridge to understand the capabilities of the fulfillment agent. Examples of such capabilities include, but are not limited to, supported actions and input/output parameters. Adapters of the fulfillment bridge interface with the fulfillment agents and fulfillment scripts that are independently operated with respect to the CSB platform can be use to interface with the fulfillment adapters.

Abstract: A non-transitory computer-readable storage medium has tangibly embodied thereon and accessible therefrom instructions interpretable by at least one data processing device. The instructions are configured for causing the at least one data processing device to perform a method comprising creating a resource group for providing cloud services, receiving a request to increase a quantity of the virtual machines of the resource group; and instantiating one or more additional virtual machines within the resource group in response to receiving the request. The resource group includes one or more virtual machines that all have virtual machine specifications of a particular configuration. Instantiating the one or more additional virtual machines includes providing each one of the one or more additional virtual machines with virtual machine specifications of the particular configuration.

Abstract: Implementation of cross provider security in accordance with the disclosures made herein enables users of a system (e.g., a cloud services brokerage platform) in a cloud environment provides for system-managed provisioning and management of keys to cloud resources thereby allowing the user to manage data security and enable secured access to their cloud resources. To this end, cross provider security management functionality in accordance with the disclosures made herein can include provisioning system-generated keys across different regions in a provider, provisioning cloud brokerage system-generated keys across different providers; and associating (i.e., managing) the keys from the system to a hardware security module. The keys can be managed by/though a variety of different resources (e.g., brokering system, VDC, user group concepts, etc).