Abstract: A computer-implemented method, system and computer program product for providing secure access to devices enabled for connectivity using access control are disclosed. The computer-implemented method for providing secure access to devices enabled for connectivity comprises dynamically associating each of the one or more devices to at least one user account; assigning an IP address to each of the one or more devices enabled for connectivity; dynamically generating at least one access-control list (ACL) for each of the one or more devices associated with the at least one user account; and restricting access only to the at least one user account via ACL generated for the one or more devices.

Abstract: A computer-implemented system and method for automated secure device registration and provisioning of one or more devices enabled for connectivity over cellular network are disclosed. The computer-implemented method for automated secure device registration and provisioning of one or more devices enabled for connectivity over cellular network includes receiving subscriber identity module (SIM) information for at least one SIM; enabling the SIM for restricted connectivity; authenticating the one or more devices using a pre-shared key for each of the one or more devices; obtaining device information from the device; associating at least one of the one or more devices with the at least one SIM; provisioning the authenticated one or more devices; and enabling the one or more devices for general connectivity over cellular network.

Abstract: In a software product installed in a given computing environment, wherein the software product when installed is configured to operate in accordance with a licensing model having a first licensing functionality, a method receives an instruction to modify the licensing model to enable the software product to operate in accordance with a second licensing functionality. The method then automatically modifies the licensing model to enable the software product to operate in accordance with the second licensing functionality.

Abstract: Systems, methods, and computer program products are disclosed for upgrading a container node in a cloud environment. The system includes a processor coupled to a memory and a network interface. The processor is configured to obtain a version identifier associated with a cloud-based server instance and one or more container nodes operable in a cloud environment. The processor is further configured to identify the one or more container nodes associated with the cloud-based server instance. The processor is further configured to upgrade the one or more container nodes by instantiating one or more replacement container nodes having a pre-determined upgrade configuration associated with a new version identifier. The processor is further configured to associate the new version identifier with the cloud-based server instance and the one or more replacement container nodes.

Abstract: In a software product installed in a given computing environment, wherein the software product when installed is configured to operate in accordance with a licensing model having a first licensing functionality, a method receives an instruction to modify the licensing model to enable the software product to operate in accordance with a second licensing functionality. The method then automatically modifies the licensing model to enable the software product to operate in accordance with the second licensing functionality.

Abstract: A computer-implemented method, system and computer program product for providing secure access to devices enabled for connectivity using access control are disclosed. The computer-implemented method for providing secure access to devices enabled for connectivity comprises dynamically associating each of the one or more devices to at least one user account; assigning an IP address to each of the one or more devices enabled for connectivity; dynamically generating at least one access-control list (ACL) for each of the one or more devices associated with the at least one user account; and restricting access only to the at least one user account via ACL generated for the one or more devices.

Abstract: An apparatus in one embodiment comprises at least one processing platform comprising a plurality of processing devices. The at least one processing platform is configured to provide a plurality of applications with centralized access to a plurality of message oriented middleware (MOM) servers via a connectivity layer, to establish a connection between a given one of the plurality of applications and a given one of the plurality of MOM servers via the connectivity layer, and to exchange data between the given one of the plurality of applications and the given one of the plurality of MOM servers via the connectivity layer.

Abstract: An apparatus in one embodiment comprises at least one processing platform comprising a plurality of processing devices. The at least one processing platform is configured to provide a plurality of applications with centralized access to a plurality of message oriented middleware (MOM) servers via a connectivity layer, to establish a connection between a given one of the plurality of applications and a given one of the plurality of MOM servers via the connectivity layer, and to exchange data between the given one of the plurality of applications and the given one of the plurality of MOM servers via the connectivity layer.

Abstract: A device can receive a request to deploy, on the device, a container associated with a tenant. The request can include information identifying one or more parameters related to the container. The device can configure, for the container, an Internet protocol (IP) address that includes information identifying the tenant with which the container is associated. The IP address can permit the container to be reachable from outside of the device. The device can configure an interface for the container to isolate the container from another container deployed on the device. The other container can be associated with another tenant. The tenant and the other tenant can be different. The device can configure a set of rules related to traffic associated with the container. The device can perform an action related to the container after deploying the container with the IP address, the interface, and the set of rules.

Abstract: A device can receive a request to deploy, on the device, a container associated with a tenant. The request can include information identifying one or more parameters related to the container. The device can configure, for the container, an Internet protocol (IP) address that includes information identifying the tenant with which the container is associated. The IP address can permit the container to be reachable from outside of the device. The device can configure an interface for the container to isolate the container from another container deployed on the device. The other container can be associated with another tenant. The tenant and the other tenant can be different. The device can configure a set of rules related to traffic associated with the container. The device can perform an action related to the container after deploying the container with the IP address, the interface, and the set of rules.

Abstract: Technologies are disclosed herein for automated software release lifecycle management. In particular, a software release management network service is disclosed that provides functionality for allowing a software developer to automate aspects of a software release pipeline. A software release pipeline can have multiple stages, each of which can have multiple actions. The actions can include internal actions that utilize network services internal to a service provider network. The actions can also include external actions that utilize network services that are external to a service provider network. The internal and external actions can perform various release-related functions, such as obtaining source code, building the source code, deploying built program code, and for performing tests. Stage gates and/or action gates can also be defined for conditional execution of the next stage or action in a software release pipeline, respectively. A gate bypass can also be specified to override stage or action gates.