# US 11,310,108 B2 · Secure configuration of cloud computing nodes > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,310,108 B2 - Document ID: US11310108B2 - Status: Granted - Kind: B2 - Application number: 17/002,726 - Filed: 2020-08-25 - Published: 2020-12-10 - Granted: 2022-04-19 - Earliest claimed: 2020-08-25 - Assignees: Google Inc. - Applicants: Google LLC - Inventors: Nelson Araujo; Mohsen Vakilian; Stephen Francis Yegge - Web page: https://patentgrep.com/patent/US11310108B2 ## CPC - G06F 9/5072: {Grid computing} - H04L 41/0813: characterised by the conditions triggering a change of settings - H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)} - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04L 41/0894: Policy-based network configuration management - H04L 67/025: for remote control or remote monitoring of applications - H04L 67/125: involving control of end-device applications over a network - H04L 67/303: Terminal profiles - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Methods and systems for configuring nodes in a cloud computing network are described. One example method includes receiving, over a network, a configuration request from a particular node in the cloud computing network, the configuration request including node information for the particular node; verifying that the particular node is authorized for configuration based at least in part on the node information; in response to verifying that the particular node is authorized for configuration, identifying configuration actions to perform on the particular node based at least in part on the node information; and sending, over the network, a configuration command corresponding to one or more of the identified configuration actions to the particular node, wherein the particular node executes the configuration command upon receipt to perform the corresponding configuration actions. ## Claims ### Claim 1 A method comprising: receiving, at data processing hardware, a request from a user system to create and configure a node in a cloud computing network, the request comprising attributes associated with the node to be created and configured; verifying, by the data processing hardware, that the user system is authorized to create and configure the node; and in response to verifying that the user system is authorized to create and configure the node: creating, by the data processing hardware, the node; identifying, by the data processing hardware, configuration actions to perform on the created node based at least in part on the attributes associated with the created node; sending, by the data processing hardware, a configuration command corresponding to one or more of the identified configuration actions to the created node, wherein the created node executes the configuration command upon receipt of the configuration command to perform the corresponding configuration actions; receiving, at the data processing hardware, from the created node, reporting information related to the execution of the configuration command by the created node; determining, by the data processing hardware, whether the configuration command was executed successfully by the created node based on the reporting information; and when the configuration command was not executed successfully, notifying, by the data processing hardware, an administrative component associated with the created node that the created node was not configured successfully. ### Claim 2 (depends on 1) The method of claim 1, further comprising sending, by the data processing hardware, to the user system, acknowledgement that the created node was created. ### Claim 3 (depends on 1) The method of claim 1, wherein the request further comprises an identity of the user system. ### Claim 4 (depends on 1) The method of claim 1, wherein the attributes comprise a type of node instance. ### Claim 5 (depends on 1) The method of claim 1, wherein the request further comprises a unique identifier for identifying the request. ### Claim 6 (depends on 1) The method of claim 1, further comprising sending, by the data processing hardware, a configuration report corresponding to the configuration command from the created node, the configuration report including reporting information related to the execution of the configuration command by the created node. ### Claim 7 (depends on 6) The method of claim 6, wherein the configuration command is a first configuration command, the method further comprising: determining, by the data processing hardware, that the first configuration command was executed successfully by the created node based on the reporting information; and in response to determining that the first configuration command was executed successfully, sending, by the data processing hardware, a second configuration command corresponding to one or more additional configuration actions to the created node, wherein the one or more additional configuration actions are selected from the identified configuration actions and are different than the configuration actions corresponding to the first configuration command. ### Claim 8 (depends on 1) The method of claim 1, wherein verifying that the user system is authorized to create and configure the node comprises verifying that the attributes matches a security policy associated with the data processing hardware. ### Claim 9 (depends on 1) The method of claim 1, wherein the attributes includes an identity of the node to be created. ### Claim 10 (depends on 1) The method of claim 1, further comprising, in response to determining that the configuration command was not executed successfully, deleting, by the data processing hardware, the created node. ### Claim 11 A system comprising: data processing hardware; and memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising: receiving a request from a user system to create and configure a node in a cloud computing network, the request comprising attributes associated with the node to be created and configured; verifying that the user system is authorized to create and configure the node; and in response to verifying that the user system is authorized to create and configure the node: creating the node; identifying configuration actions to perform on the created node based at least in part on the attributes associated with the created node; sending a configuration command corresponding to one or more of the identified configuration actions to the created node, wherein the created node executes the configuration command upon receipt of the configuration command to perform the corresponding configuration actions; receiving, from the created node, reporting information related to the execution of the configuration command by the created node; determining whether the configuration command was executed successfully by the created node based on the reporting information; and when the configuration command was not executed successfully, notifying an administrative component associated with the created node that the created node was not configured successfully. ### Claim 12 (depends on 11) The system of claim 11, wherein the operations further comprise sending, to the user system, acknowledgement that the created node was created. ### Claim 13 (depends on 11) The system of claim 11, wherein the request further comprises an identity of the user system. ### Claim 14 (depends on 11) The system of claim 11, wherein the attributes comprise a type of node instance. ### Claim 15 (depends on 11) The system of claim 11, wherein the request further comprises a unique identifier for identifying the request. ### Claim 16 (depends on 11) The system of claim 11, wherein the operations further comprise sending a configuration report corresponding to the configuration command from the created node, the configuration report including reporting information related to the execution of the configuration command by the created node. ### Claim 17 (depends on 16) The system of claim 16, wherein the configuration command is a first configuration command, wherein the operations further comprise: determining that the first configuration command was executed successfully by the created node based on the reporting information; and in response to determining that the first configuration command was executed successfully, sending a second configuration command corresponding to one or more additional configuration actions to the created node, wherein the one or more additional configuration actions are selected from the identified configuration actions and are different than the configuration actions corresponding to the first configuration command. ### Claim 18 (depends on 11) The system of claim 11, wherein verifying that the user system is authorized to create and configure the node comprises verifying that the attributes matches a security policy associated with the data processing hardware. ### Claim 19 (depends on 11) The system of claim 11, wherein the attributes includes an identity of the node to be created. ### Claim 20 (depends on 11) The system of claim 11, wherein the operations further comprise, in response to determining that the configuration command was not executed successfully deleting the created node.