A method for configuring a cloud service, an electronic device, and a storage medium

Abstract

The application relates to the technical field of cloud services, and discloses a cloud service configuration method, an electronic device and a storage medium. The cloud service configuration method comprises the following steps: in response to an adding service request, service configuration items are displayed, the service configuration items comprise cloud product configuration items, contact configuration items and cloud service information configuration items; after information is input into the service configuration items, a cloud service is generated in response to a selection operation on a save option; and in response to an adding access credential request for the cloud service, permanent access credentials of the cloud service are generated. Through unified entry integration of three types of core information, namely, cloud products, contacts and cloud services, the problems that cloud services are mostly added in related technologies and need to be manually input in multiple steps across consoles are avoided, operation confusion caused by multiple module jumps is avoided, human input error rates are reduced, and the problem that configuration processes are scattered and not unified is solved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of cloud service technology, and in particular to a method for configuring cloud services, an electronic device, and a storage medium. Background Technology

[0002] Currently, there is a lack of corresponding permission policy configuration components to address the business needs of interaction between the console and IAM (Identity and Access Management) access control. When configuring cloud services for cloud products, there are many core technical problems, such as fragmented and inconsistent cloud service configuration processes, missing and non-standard information, lack of closed-loop operation paths, fragmented and difficult-to-retrieve information, as well as disconnect between access credentials and cloud services, confusion in the location of multiple credentials, and opaque permission control. Summary of the Invention

[0003] The purpose of this invention is to provide at least one method, electronic device, and storage medium for configuring cloud services, which can at least solve the technical problem of the fragmented and inconsistent cloud service configuration process in existing methods, and at least achieve the effects of efficiency and security in cloud asset management and configuration.

[0004] To address the aforementioned technical problems, at least one embodiment of this application provides a method for configuring cloud services, including: In response to a service add request, service configuration items are displayed, including cloud product configuration items, contact configuration items, and cloud service information configuration items. After inputting information into the service configuration item, a cloud service is generated in response to the selection of the save option; In response to a request to add access credentials for a cloud service, generate a permanent access credential for the cloud service.

[0005] At least one embodiment of this application also provides an electronic device, comprising: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method for configuring cloud services as described above.

[0006] At least one embodiment of this application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for configuring cloud services.

[0007] The cloud service configuration method provided in this application integrates the input of three core information categories—cloud products, contacts, and cloud services—through a unified entry point. This avoids the need for manual input across consoles and multiple steps in related technologies when adding cloud services, prevents operational confusion from multiple module jumps, reduces the human input error rate, and solves the problem of fragmented and inconsistent configuration processes. In existing technologies, configuration often leads to subsequent maintenance and troubleshooting obstacles due to missing contacts or non-standard product information. This method forces the completion of all three types of information before saving, ensuring the integrity and traceability of cloud service information, shortening the information location time for fault diagnosis, and solving the problems of missing information / non-standard format. In existing technologies, manually adding a single service requires multi-stage review and configuration. This method quickly generates valid cloud service information through one-click triggering and standardized input, compressing the configuration time for a single service from minutes to seconds, adapting to business scenarios with high frequency of adding cloud services, and solving the problems of cumbersome cloud service addition processes and low delivery efficiency. Therefore, this method effectively simplifies the cloud service configuration process, improves the standardization and maintainability of cloud service information, reduces operation and maintenance communication and troubleshooting costs, and adapts to the lightweight needs of small and medium-sized enterprises to add cloud services in batches.

[0008] In some optional embodiments, after generating the cloud service in response to a selection of a save option, the method further includes: In response to the selection of the return option, a list of cloud services is displayed. The list of cloud services includes configuration information of the generated cloud services. The configuration information includes cloud products, contacts, and cloud service information. The cloud service information includes service names and service identifiers.

[0009] In some optional embodiments, in addition to displaying the list of cloud services, the following are also included: In response to the selection of the add service option, a new add service request is generated.

[0010] In some optional embodiments, before generating the cloud service in response to a selection of a save option, the method further includes: After entering information into the service configuration item, in response to the selection operation for the added option, a new cloud service information configuration item is displayed, which is used to configure the next cloud service for the current cloud product.

[0011] In some optional embodiments, the cloud service list further includes operation options for the generated cloud services, the operation options including access credentials; after displaying the cloud service list, the method further includes: In response to the selection of the access credential option corresponding to the cloud service in the cloud service list, the generated permanent access credential for the cloud service is displayed.

[0012] In some optional embodiments, in response to a request to add access credentials for a cloud service, a permanent access credential for the cloud service is generated, including: If the number of generated permanent access credentials for the displayed cloud service has not reached the preset limit, a permanent access credential will be generated for the current cloud service in response to the selection of the option to add a new access credential for the current cloud service.

[0013] In some optional embodiments, the method for configuring cloud services further includes: In response to a service role configuration request, display a list of service roles; In response to a selection action for the role creation option, the service role configuration items are displayed; After inputting information into the service role configuration item, in response to the selection of the save option, the service role is generated and the service role list is displayed; In response to the selection of configuration policy options for a service role in the service role list, the policy list for that service role is displayed; In response to a selection action for a new policy option, the policy configuration items are displayed; After inputting information into the policy configuration item, the policy for the service role is generated in response to the selection of the save option.

[0014] In some optional embodiments, the method for configuring cloud services further includes: In response to an IAM role creation request, create an IAM role for the cloud service based on the generated cloud service and the created service role. Attached Figure Description

[0015] One or more embodiments are illustrated by way of example with reference to the accompanying drawings, and these illustrative descriptions do not constitute a limitation on the embodiments.

[0016] Figure 1 This is a schematic diagram of the Steps component in Ant Design, a related technology. Figure 2 This is a flowchart of a method for configuring cloud services provided in an embodiment of this application; Figure 3 This is a schematic diagram of an apparatus for configuring cloud services provided in an embodiment of this application; Figure 4 This is a schematic diagram of a component page provided in an embodiment of this application; Figure 5 This is a schematic diagram of a page for creating an IAM role provided in an embodiment of this application; Figure 6 This is a schematic diagram of a cloud service role created according to an embodiment of this application; Figure 7 This is a schematic diagram of the permission policy list of the role permission configuration page provided in an embodiment of this application; Figure 8 This is a schematic diagram of a cloud service display page provided in an embodiment of this application; Figure 9 This is a schematic diagram of the service configuration items provided in an embodiment of this application; Figure 10 This is a schematic diagram of a page for batch configuring cloud services for the same cloud product, provided by an embodiment of this application. Figure 11 This is a schematic diagram illustrating the list of cloud services provided in an embodiment of this application; Figure 12 This is a schematic diagram illustrating the new access credential option provided in an embodiment of this application; Figure 13 This is a schematic diagram showing that the "Add Access Credentials" button is invalid, as provided in an embodiment of this application. Figure 14 This is a schematic diagram of a service role configuration list provided in an embodiment of this application; Figure 15 This is a schematic diagram of a page for creating a service role provided in an embodiment of this application; Figure 16 This is a schematic diagram of the policy configuration page provided in an embodiment of this application; Figure 17 This is a schematic diagram showing the policy configuration items provided in an embodiment of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the various embodiments of this application will be described in detail below with reference to the accompanying drawings. However, those skilled in the art will understand that many technical details have been provided in the various embodiments of this application to help readers better understand this application. However, the technical solutions claimed in this application can be implemented even without these technical details and various changes and modifications based on the following embodiments. The division of the various embodiments below is for the convenience of description and should not constitute any limitation on the specific implementation of this application. The various embodiments can be combined with and referenced by each other without contradiction.

[0018] To facilitate understanding of the embodiments of this application, the relevant content regarding the interaction between the console and IAM access control will be introduced first.

[0019] Currently, there is a lack of corresponding permission policy configuration components to meet the business needs of interaction between the console and IAM access control. When configuring cloud services for cloud products, there are many core technical problems, such as fragmented and inconsistent cloud service configuration processes, missing and non-standard information, lack of closed-loop operation paths, fragmented and difficult-to-retrieve information, as well as disconnection between access credentials and cloud services, confusion in the location of multiple credentials, and opaque permission control.

[0020] In related technologies, Ant Design's Steps component, such as... Figure 1 As shown, however, it does not meet the interactive business requirements of console-IAM access control, and it is not easy to modify or expand.

[0021] To address the aforementioned technical problems of existing methods, this invention proposes a method for configuring cloud services, an electronic device, and a storage medium. The implementation details of this embodiment are described below. The following content is for ease of understanding and is not essential for implementing this solution.

[0022] Example 1: The method for configuring cloud services in this embodiment can be applied to electronic devices with communication, computing, and data storage capabilities. The specific process can be as follows: Figure 2 As shown, it includes: Step 101: In response to the add service request, display the service configuration items.

[0023] Specifically, service configuration items include cloud product configuration items, contact configuration items, and cloud service information configuration items. Service requests are used to configure cloud services for cloud products.

[0024] Step 102: After entering information into the service configuration items, cloud services are generated in response to the selection of the save option.

[0025] Specifically, after users enter the corresponding cloud product configuration information, contact configuration information, and cloud service information into the service configuration items, they can generate the cloud service by clicking the save option button.

[0026] Step 103: In response to the request to add access credentials for the cloud service, generate a permanent access credential for the cloud service.

[0027] Specifically, while generating cloud services, corresponding permanent access credentials can also be generated for them. Permanent credentials can be generated once and reused for a long time, eliminating the need to repeatedly complete the issuance, verification, and destruction process chain. This saves computing resources and network bandwidth consumed by repeatedly generating credentials and also reduces the operational load of the dynamic credential management system.

[0028] This method integrates the input of three core information categories—cloud products, contacts, and cloud services—through a unified entry point. This avoids the need for manual input across multiple consoles and steps required in many related technologies, preventing the confusion of switching between multiple modules, reducing human error rates, and solving the problem of fragmented and inconsistent configuration processes. Existing technologies often encounter obstacles in subsequent maintenance and troubleshooting due to missing contacts or non-standard product information. This method mandates that all three types of information be filled in before saving, ensuring the integrity and traceability of cloud service information, shortening the information location time for troubleshooting, and solving the problems of missing information / non-standard formatting. Existing technologies require multiple stages of review and configuration for manually adding a single service. This method quickly generates valid cloud service information through one-click triggering and standardized input, reducing the time for configuring a single service from minutes to seconds. It is suitable for business scenarios involving frequent addition of cloud services, solving the problems of cumbersome processes and low delivery efficiency in adding cloud services. Therefore, this method effectively simplifies the cloud service configuration process, improves the standardization and maintainability of cloud service information, reduces maintenance communication and troubleshooting costs, and is suitable for the lightweight needs of small and medium-sized enterprises adding cloud services in batches.

[0029] In some embodiments, after generating the cloud service in response to a selection of a save option, the method further includes: In response to the selection of return options, a list of cloud services is displayed.

[0030] Specifically, the cloud service list includes configuration information for the generated cloud services. The configuration information includes cloud products, contacts, and cloud service information. The cloud service information includes service names and service identifiers.

[0031] In the actual implementation, after saving and generating the cloud service, the user clicks the return option to display the list of cloud services.

[0032] In existing technologies, processes often lack a one-click return to the list after saving, requiring users to manually navigate through multiple levels of navigation, resulting in cumbersome operation paths and potential disruptions to the user's continuous service addition workflow. This embodiment addresses this by enabling a one-click return to the cloud service list through a selectable return option, resolving the issue of missing path loops after configuration. Existing cloud service lists typically only display service information; product and contact information requires navigating to a separate details page, leading to extremely low efficiency in cross-page information retrieval and hindering rapid overall verification. This embodiment integrates the input of three core types of information—cloud products, contacts, and cloud services—and mandates completion of all three types before saving, resolving the problem of fragmented cloud service information. With these three elements centrally displayed on the list page, global verification and rapid retrieval of target services can be achieved without clicking through details individually, significantly reducing information acquisition costs for operation and maintenance management and improving management efficiency.

[0033] In some embodiments, in addition to displaying the list of cloud services, the system may also include: In response to the selection of the add service option, a new add service request is generated.

[0034] In this embodiment, after saving, the user can return to the list with one click, and then generate a new service request by clicking the "Add Service" option. This forms a complete operation loop of "Add-View-Add Again", reducing unnecessary page jumps, shortening the overall time consumption of continuous configuration, and optimizing the operation path.

[0035] In some embodiments, prior to generating the cloud service in response to a selection of a save option, the method further includes: After entering information into the service configuration item, in response to the selection of the added option, a new cloud service information configuration item is displayed, which is used to configure the next cloud service for the current cloud product.

[0036] In practice, after entering information into the service configuration items, users can click the "Add" button to create multiple cloud services (e.g., 10) for the current cloud product, so that they can save the data by clicking the "Save" button after batch entry.

[0037] In this embodiment, when a user adds multiple cloud services consecutively, the existing process requires switching pages multiple times, interrupting the operation rhythm and increasing operation time and interaction burden. However, this application allows the user to select the add option after entering information into the service configuration item to display the new cloud service information configuration item, configuring the next cloud service for the current cloud product, realizing batch entry of multiple cloud services, and then saving them uniformly. This supports users to complete the addition of multiple cloud services in a continuous manner, improving the smoothness of operation, adapting to the continuous operation scenario of enterprises' high-frequency operation needs for centralized batch entry and updating of cloud service information, and solving the problem of poor continuity of batch configuration operation.

[0038] In some embodiments, the cloud service list further includes operation options for the generated cloud services, including access credentials; after displaying the cloud service list, the method further includes: In response to the selection of access credentials for a cloud service in the cloud service list, the generated permanent access credentials for the cloud service are displayed.

[0039] Specifically, permanent credentials can be generated once and reused long-term, eliminating the need for repeated issuance, verification, and destruction processes. This saves computing resources and network bandwidth consumed by repeatedly generating credentials and reduces the operational burden on the dynamic credential management system. From a labor cost perspective, there's no need for periodic key rotation and configuration updates, reducing repetitive work for maintenance personnel. From a storage cost perspective, the storage footprint of a single permanent credential is far lower than that of batch-generated temporary credentials, and expansion costs via cloud storage are extremely low. Even considering security hardening investments, the overall cost of this one-time configuration for long-term use is still significantly lower than the frequently updated temporary credential system, making it particularly suitable for stable, automated business scenarios.

[0040] Existing cloud service credentials are all temporary credentials. When a cloud service is bound to multiple temporary credentials, it is not possible to preview all credentials directly; users must navigate through the details page to find them, significantly reducing management efficiency. This embodiment, however, generates corresponding permanent credentials for the cloud service at the same time as it is generated. Furthermore, when returning to the cloud service list with one click, users can click on the generated permanent access credential option to view all permanent access credentials for the current cloud service, effectively solving the problem of confusing credential location in multi-credential scenarios.

[0041] Furthermore, under the existing decentralized management system, it is impossible to quickly confirm all the authorization credentials bound to a certain cloud service, which can easily lead to security risks such as expired credentials not being reclaimed and unauthorized credentials not being cleared. However, this embodiment effectively solves the problem of opaque access control by allowing users to select the access credential option corresponding to the cloud service when displaying the cloud service list, thereby displaying the generated permanent access credentials for that cloud service.

[0042] In some embodiments, in response to a request to add access credentials for a cloud service, a persistent access credential for the cloud service is generated, including: If the number of generated permanent access credentials for the displayed cloud service has not reached the preset limit, a permanent access credential will be generated for the current cloud service in response to the selection of the option to add a new access credential for the current cloud service.

[0043] In the actual implementation, the preset upper limit can be set according to actual needs, such as 2. That is, if there are less than 2 cloud services displayed, you can still select the option to add access credentials for the current cloud service (e.g., click the option to add access credentials). When the number of permanent access credentials generated reaches 2, the option to add access credentials becomes invalid and no more permanent access credentials can be generated.

[0044] In existing scenarios, access credentials are often scattered and stored in local files or separate credential systems, which are disconnected from the bound cloud service. Finding the corresponding credential requires cross-platform retrieval, which is prone to errors. However, this embodiment generates permanent credentials for the cloud service when it is generated, which effectively solves the problem of credential and cloud service information being disconnected.

[0045] This embodiment achieves the association and binding of cloud services and access credentials, eliminating the need for cross-platform redirection. The corresponding credentials can be viewed directly on the list page, significantly shortening the time for credential retrieval and location. It also supports unified preview of multiple credentials under the same cloud service, adapting to business scenarios with permanent access credentials, meeting differentiated authorization management needs, and quickly identifying expired, redundant, and invalid access credentials. The corresponding operations can be performed through the operation options on the display page of the generated permanent access credentials - edit, disable, or delete, promptly cleaning up expired authorizations, reducing the cloud resource security risks caused by credential leakage, and improving the transparency of overall credential management.

[0046] In some embodiments, the above-described method for configuring cloud services further includes: In response to a service role configuration request, display a list of service roles; In response to the selection action for the role creation option, the service role configuration items are displayed; the service role configuration items include the role name and remarks; After entering information into the service role configuration item, in response to the selection of the save option, the service role is generated and the list of service roles is displayed; In response to the selection of configuration policy options for a service role in the list of service roles, display the policy list for that service role; In response to the selection action for the new policy option, the policy configuration items are displayed, including the policy name, scope, and policy configuration method; After entering information into the policy configuration item, the policy for that service role is generated in response to the selection of the save option.

[0047] In practice, when configuring cloud services, service roles are also configured to generate service roles and their policies for selection when creating IAM roles.

[0048] In some embodiments, the above method for configuring cloud services further includes: In response to an IAM role creation request, create an IAM role for the cloud service based on the generated cloud service and the created service role.

[0049] In practice, when creating an IAM role, you can create an IAM role for the cloud service by selecting the pre-configured cloud service and service role.

[0050] The method in this embodiment, through step-by-step optimization design, sequentially solves several core technical problems in existing cloud service configuration processes, such as fragmented and inconsistent processes, missing and non-standardized information, lack of closed-loop operation paths, fragmented and difficult-to-retrieve information, as well as disconnection between access credentials and cloud services, chaotic location of multiple credentials, and opaque permission control. Through standardized information entry, a one-click return to the list operation loop, centralized display of the three key elements, and preview of credential and cloud service association, the method simplifies configuration operation processes, improves the integrity and traceability of cloud service information, shortens credential retrieval time, optimizes the smoothness of continuous operations, and helps to quickly clean up redundant and expired credentials, reducing the overall technical effects of cloud resource authorization security risks. This effectively improves the efficiency and security of cloud asset management and configuration for small and medium-sized teams.

[0051] Example 2: Another embodiment of this application relates to an apparatus for configuring cloud services. The implementation details of the apparatus for configuring cloud services in this embodiment are described below. The following implementation details are provided for ease of understanding and are not essential for implementing this solution. A schematic diagram of the apparatus for configuring cloud services in this embodiment can be seen as follows: Figure 3 As shown, it includes a service configuration module 310, a service generation module 320, and a credential generation module 330.

[0052] Service configuration module 310 is used to display service configuration items in response to a request to add a service.

[0053] Specifically, service configuration items include cloud product configuration items, contact configuration items, and cloud service information configuration items. Service requests are used to configure cloud services for cloud products.

[0054] The service generation module 320 is used to generate cloud services in response to the selection of the save option after inputting information into the service configuration items.

[0055] Specifically, after users enter the corresponding cloud product configuration information, contact configuration information, and cloud service information into the service configuration items, they can generate the cloud service by clicking the save option button.

[0056] The credential generation module 330 is used to generate a permanent access credential for the cloud service in response to a request to add access credentials for the cloud service.

[0057] Specifically, while generating cloud services, corresponding permanent access credentials can also be generated for them. Permanent credentials can be generated once and reused for a long time, eliminating the need to repeatedly complete the issuance, verification, and destruction process chain. This saves computing resources and network bandwidth consumed by repeatedly generating credentials and also reduces the operational load of the dynamic credential management system.

[0058] This device integrates the input of three core information categories—cloud products, contacts, and cloud services—through a unified entry point. This avoids the need for manual input across multiple consoles and steps required in many related technologies when adding cloud services, preventing operational confusion from multiple module jumps, reducing human error rates, and solving the problem of fragmented and inconsistent configuration processes. This device mandates that all three types of information be filled in before saving, ensuring the integrity and traceability of cloud service information, shortening the information location time for troubleshooting, and solving the problems of missing information / non-standard formatting. Through one-click triggering and standardized input, it quickly generates valid cloud service information, reducing the time required for single service configuration from minutes to seconds, adapting to business scenarios with high-frequency addition of cloud services, and solving the problems of cumbersome processes and low delivery efficiency in adding cloud services. Therefore, this device effectively simplifies the cloud service configuration operation process, improves the standardization and maintainability of cloud service information, reduces operation and maintenance communication and troubleshooting costs, and adapts to the lightweight needs of small and medium-sized enterprises for batch addition of cloud services.

[0059] In some embodiments, after generating cloud services in response to a selection operation of the save option, the service generation module 320 is further configured to: display a list of cloud services in response to a selection operation of the return option.

[0060] Specifically, the cloud service list includes configuration information for the generated cloud services. The configuration information includes cloud products, contacts, and cloud service information. The cloud service information includes service names and service identifiers.

[0061] In the actual implementation, after saving and generating the cloud service, the user clicks the return option to display the list of cloud services.

[0062] This embodiment enables one-click return to the cloud service list by selecting the return option, solving the problems of missing path closure after configuration and fragmented cloud service information; the three key elements are centrally displayed on the list page, allowing for global verification and quick retrieval of target services without clicking on details one by one, greatly reducing the information acquisition cost of operation and maintenance management and improving management efficiency.

[0063] In some embodiments, while displaying the list of cloud services, the service generation module 320 is also configured to: generate a new service addition request in response to the selection operation of the add service option.

[0064] In this embodiment, saving allows for a one-click return to the list, forming a complete operation loop of "add-view-add again," reducing unnecessary page jumps, shortening the overall time consumption of continuous configuration, and optimizing the operation path.

[0065] In some embodiments, before generating a cloud service in response to a selection operation for a save option, the service generation module 320 is further configured to: after inputting information into a service configuration item, in response to a selection operation for an add option, display a new cloud service information configuration item for configuring the next cloud service for the current cloud product.

[0066] In practice, after entering information into the service configuration items, users can click the "Add" button to create multiple cloud services, enabling batch entry and subsequent saving by clicking the "Save" button.

[0067] In this embodiment, when a user adds multiple cloud services consecutively, the existing process requires switching pages multiple times, interrupting the operation rhythm and increasing operation time and interaction burden. However, this application allows the user to select the add option after entering information into the service configuration item to display the new cloud service information configuration item, configuring the next cloud service for the current cloud product, realizing batch entry of multiple cloud services, and then saving them uniformly. This supports users to complete the addition of multiple cloud services in a continuous manner, improving the smoothness of operation, adapting to the continuous operation scenario of enterprises' high-frequency operation needs for centralized batch entry and updating of cloud service information, and solving the problem of poor continuity of batch configuration operation.

[0068] In some embodiments, the cloud service list further includes operation options for the generated cloud services, the operation options including access credentials; after displaying the cloud service list, the credential generation module 330 further includes: in response to the selection operation of the access credential option corresponding to the cloud service in the cloud service list, displaying the generated permanent access credentials of the cloud service.

[0069] Specifically, permanent credentials can be generated once and reused long-term, eliminating the need for repeated issuance, verification, and destruction processes. This saves computing resources and network bandwidth consumed by repeatedly generating credentials and reduces the operational burden on the dynamic credential management system. From a labor cost perspective, there's no need for periodic key rotation and configuration updates, reducing repetitive work for maintenance personnel. From a storage cost perspective, the storage footprint of a single permanent credential is far lower than that of batch-generated temporary credentials, and expansion costs via cloud storage are extremely low. Even considering security hardening investments, the overall cost of this one-time configuration for long-term use is still significantly lower than the frequently updated temporary credential system, making it particularly suitable for stable, automated business scenarios.

[0070] This embodiment generates corresponding permanent credentials for cloud services simultaneously. When returning to the cloud service list with one click, users can click the option for the generated access credential for the cloud service to view all generated permanent access credentials for the current cloud service, effectively solving the problem of confusing credential location in multi-credential scenarios. This embodiment also effectively solves the problem of opaque access control by allowing users to select the corresponding access credential option when displaying the cloud service list.

[0071] In some embodiments, in response to a request to add access credentials for a cloud service, a persistent access credential for the cloud service is generated, including: If the number of generated permanent access credentials for the displayed cloud service has not reached the preset limit, a permanent access credential will be generated for the current cloud service in response to the selection of the option to add a new access credential for the current cloud service.

[0072] In the actual implementation, the preset upper limit can be set according to actual needs, such as 2. That is, if there are less than 2 cloud services displayed, you can still select the option to add access credentials for the current cloud service (e.g., click the option to add access credentials). When the number of permanent access credentials generated reaches 2, the option to add access credentials becomes invalid and no more permanent access credentials can be generated.

[0073] In existing scenarios, access credentials are often scattered and stored in local files or separate credential systems, which are disconnected from the bound cloud service. Finding the corresponding credential requires cross-platform retrieval, which is prone to errors. However, this embodiment generates permanent credentials for the cloud service when it is generated, which effectively solves the problem of credential and cloud service information being disconnected.

[0074] This embodiment achieves the association and binding of cloud services and access credentials, eliminating the need for cross-platform redirection. The corresponding credentials can be viewed directly on the list page, significantly shortening the time for credential retrieval and location. It also supports unified preview of multiple credentials under the same cloud service, adapting to business scenarios with permanent access credentials, meeting differentiated authorization management needs, and quickly identifying expired, redundant, and invalid access credentials. The corresponding operations can be performed through the operation options on the display page of the generated permanent access credentials - edit, disable, or delete, promptly cleaning up expired authorizations, reducing the cloud resource security risks caused by credential leakage, and improving the transparency of overall credential management.

[0075] In some embodiments, the above-described apparatus for configuring cloud services further includes a service role configuration module, used for: In response to a service role configuration request, display a list of service roles; In response to the selection action for the role creation option, the service role configuration items are displayed; the service role configuration items include the role name and remarks; After entering information into the service role configuration item, in response to the selection of the save option, the service role is generated and the list of service roles is displayed; In response to the selection of configuration policy options for a service role in the list of service roles, display the policy list for that service role; In response to the selection action for the new policy option, the policy configuration items are displayed, including the policy name, scope, and policy configuration method; After entering information into the policy configuration item, the policy for that service role is generated in response to the selection of the save option.

[0076] In practice, when configuring cloud services, service roles are also configured to generate service roles and their policies for selection when creating IAM roles.

[0077] In some embodiments, the above method for configuring cloud services further includes: In response to an IAM role creation request, create an IAM role for the cloud service based on the generated cloud service and the created service role.

[0078] In practice, when creating an IAM role, you can create an IAM role for the cloud service by selecting the pre-configured cloud service and service role.

[0079] The device in this embodiment, through step-by-step optimization design, sequentially solves several core technical problems in existing cloud service configuration processes, such as fragmented and inconsistent processes, missing and non-standardized information, lack of closed-loop operation paths, fragmented and difficult-to-retrieve information, as well as disconnection between access credentials and cloud services, chaotic location of multiple credentials, and opaque permission control. Through standardized information entry, a one-click return to the list operation loop, centralized display of the three key elements, and preview of credential and cloud service association, it simplifies configuration operation processes, improves the integrity and traceability of cloud service information, shortens credential retrieval time, optimizes the smoothness of continuous operation, and helps quickly clean up redundant and expired credentials, reducing the overall technical effects of cloud resource authorization security risks. This effectively improves the efficiency and security of cloud asset management and configuration for small and medium-sized teams.

[0080] It is worth mentioning that all modules involved in this embodiment are logical modules. In practical applications, a logical unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. Furthermore, to highlight the innovative aspects of this application, this embodiment does not introduce units that are not closely related to solving the technical problems proposed in this application; however, this does not mean that other units are absent in this embodiment.

[0081] In some alternative embodiments, the apparatus of this embodiment can implement the methods described in the above embodiments.

[0082] Example 3: Based on the above embodiments, this embodiment provides specific application examples.

[0083] The method or apparatus described above can be implemented as a control component that satisfies the four processes of permission policy configuration: policy selection, cloud service corresponding to the policy, policy operation, and service resource configuration corresponding to the policy. The process control is dependent on each other and is autonomous and controllable. For example, the second step depends on the first step, the third step depends on the second step, and the last step has a default value that depends on the third step, etc. Each step operation is also different, and the interaction is also different. The control process of this component can be autonomously configured according to business logic.

[0084] The component's structure is implemented as follows: JSX code encapsulates interactive components according to business requirements, extracts the component's interactive logic to create the component, and external business data is passed in. This decouples and separates business information, making the component applicable to both process control and interactive requirements. It also supports multi-process parallel configuration and is user-controllable.

[0085] Based on the configuration, the component will define the process configuration and implement it with JSX + CSS front-end code.

[0086] Component page screenshot as follows Figure 4 As shown, after configuring cloud services, service roles, and policies, selections can be made when creating custom policies. The following section provides a detailed explanation of applications utilizing this component.

[0087] (1) Create an IAM role (cloud service) Specifically, this involves creating a cloud service role, obtaining the relevant permissions for the IAM role (cloud service role), controlling the login permissions of users' accounts under this role, supporting backend services to access cloud services using key methods, and verifying operation permissions within the policy specifications. The page for creating an IAM role is as follows... Figure 5 As shown, the main operation involves selecting a cloud service-level IAM role name. Specifically, the selected role is a cloud service, the role type is a service-associated role, and in the cloud service selection options, the configured cloud service—fuwu2—is chosen. An IAM role name—IAMzdtest_WCSconfigRole—is then created for fuwu2. The created cloud service role is shown below. Figure 6As shown, the IAM roles are displayed in a list format. The list displays the IAM role name, role type, remarks, creation time, and operations. Operations include permission configuration and deletion, which can be configured according to actual needs. Furthermore, related policy configurations can be viewed in the permission configuration items displayed in the list. However, policy configurations cannot be modified in the current IAM role list; only viewing functionality is provided. The policy configuration here refers to the configuration of cloud service roles. If changes are needed, they should be made on the relevant page of the cloud service role configuration. Further configuration is required in the following sections; only the following is provided here: Figure 7 The permission policy list displayed on the role permission configuration page shown does not support user modification of information such as the role carrier. It can only be modified in the background cloud service role and its policy configuration after configuring the cloud service.

[0088] (2) Cloud service configuration The list involves displaying cloud services, supports associating roles (and service roles), and generating permanent access credentials, such as... Figure 8 As shown, each cloud service includes the (cloud) product name, (cloud) service name, (cloud) service name (in English), service identifier, contact person, contact person's mobile phone number, and operation. The operation includes associated role, access credentials, editing, deletion, and operation log.

[0089] The cloud service configuration specifically includes: (2.1) Creating cloud services A single cloud product can be associated with multiple cloud services (including service name and service identifier), and after creation, they can be linked as follows: Figure 8 The list shown is displayed. In response to a service add request, service configuration items are displayed, such as... Figure 9 As shown, the service configuration items include cloud product configuration items, contact configuration items, and cloud service information configuration items. After the user enters information into the service configuration items, the cloud service is generated in response to the selection of the save option. After entering information into the service configuration items, the cloud service is generated in response to the selection of the save option. Figure 9 The "Add" option on the page shown displays new cloud service information configuration items, used to configure the next cloud service for the current cloud product. After clicking "Add," a maximum of 10 cloud service entries can be created. The page for batch configuring cloud services for the same cloud product is as follows. Figure 10 As shown, multiple cloud service entries can be added. Taking adding fuwu\fuwu2\fuwu3\fuwu5\fuwu6 as an example, the cloud service list is as follows: Figure 11 As shown.

[0090] (2.2) Generate access credentials for cloud services The access credentials generated by the cloud service serve as identifiers for IAM role access. The backend also verifies these identifiers to locate the corresponding service role and verify relevant permissions, thus restricting user access. These access credentials are the permanent access credentials mentioned in the previous embodiment. Since the cloud service list also includes operation options for generated cloud services, including access credentials, after displaying the cloud service list, users can select the corresponding access credential option for each cloud service to display the generated permanent access credentials. If the number of generated permanent access credentials displayed for a cloud service does not reach the preset limit, users can click... Figure 12 The "Add Access Credential" option shown generates a permanent access credential for the current cloud service. Each cloud service can have a maximum of two access credentials: when there are two access credentials, the "Add Access Credential" button becomes disabled. Figure 13 As shown.

[0091] (3) Service role configuration Service role configuration includes key modules such as role creation and role policy configuration, as shown in the list below. Figure 14 As shown, it includes the role name, notes, preset strategy, creator and operation, and the operation further includes editing information, configuring strategy, deletion and operation log.

[0092] Service role configuration, including: (3.1) Service Role Creation Service role creation includes role name and remarks. Specifically, the input of role name has preset specifications, such as the format: prefix _WCS******Role (supports uppercase and lowercase letters, numbers, and underscores). For example, the role associated with the cloud audit service (orange name) is CTS_WCSconfigRole.

[0093] The page for creating service roles is as follows: Figure 15 As shown, configuration items including character name, notes, and notes (in English) are filled in and saved by the user.

[0094] (3.2) Service role strategy configuration like Figure 16 The policy configuration page shows a list where you can view the policies configured for service roles and also create policies. There is no limit to the number of policies a role can contain. Selecting the "Configure Policy" option for a service role in the service role list will display the policy list for that service role. Further selecting the "Create New Policy" option will display the policy configuration items, including the policy name, scope, and configuration method. After the user enters information into the policy configuration items, the policy for that service role is saved and generated.

[0095] The policy configuration options display page is as follows Figure 17As shown. The policy creation or editing page allows you to configure policy permissions; once generated, you will have the desired permissions. Figure 16 The list displays the permissions for the corresponding policies for each service role. The policy configuration includes the name, scope, and corresponding identifier. The policy name is globally unique, and the scope can be global (global service) or a fixed cloud region (regional service), etc. Furthermore, the policies included in this service role can be dynamically added, modified, and deleted later, configured in the backend as needed, without affecting the frontend user.

[0096] Example 4: Another embodiment of this application relates to an electronic device, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the methods described in the above embodiments.

[0097] In this embodiment, the memory and processor are connected via a bus, which can include any number of interconnected buses and bridges, connecting various circuits of one or more processors and the memory together. The bus can also connect various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described in this embodiment. A bus interface provides an interface between the bus and the transceiver. The transceiver can be a single element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices over a transmission medium. Data processed by the processor is transmitted over the wireless medium via an antenna, which further receives data and transmits it to the processor.

[0098] The processor manages the bus and general processing, and also provides various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory is used to store data used by the processor during operation.

[0099] Example 5: Another embodiment of this application relates to a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the method embodiments described above.

[0100] That is, those skilled in the art will understand that all or part of the steps in the methods of the above embodiments can be implemented by a program instructing related hardware. This program is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0101] Those skilled in the art will understand that the above embodiments are specific embodiments for implementing this application, and in practical applications, various changes can be made to them in form and detail without departing from the spirit and scope of this application.

Claims

1. A method for configuring cloud services, characterized in that, include: In response to a service add request, service configuration items are displayed, including cloud product configuration items, contact configuration items, and cloud service information configuration items. After inputting information into the service configuration item, a cloud service is generated in response to the selection of the save option; In response to a request to add access credentials for a cloud service, generate a permanent access credential for the cloud service.

2. The method for configuring cloud services according to claim 1, characterized in that, After generating the cloud service in response to the selection of the save option, it also includes: In response to the selection of the return option, a list of cloud services is displayed. The list of cloud services includes configuration information of the generated cloud services. The configuration information includes cloud products, contacts, and cloud service information. The cloud service information includes service names and service identifiers.

3. The method for configuring cloud services according to claim 2, characterized in that, Along with the list of cloud services, it also includes: In response to the selection of the add service option, a new add service request is generated.

4. The method for configuring cloud services according to claim 2, characterized in that, Before generating the cloud service in response to the selection of save options, it also includes: After entering information into the service configuration item, in response to the selection operation for the added option, a new cloud service information configuration item is displayed, which is used to configure the next cloud service for the current cloud product.

5. The method for configuring cloud services according to claim 2, characterized in that, The cloud service list also includes operation options for generated cloud services, including access credentials; After displaying the list of cloud services, the method further includes: In response to the selection of the access credential option corresponding to the cloud service in the cloud service list, the generated permanent access credential for the cloud service is displayed.

6. The method for configuring cloud services according to claim 5, characterized in that, In response to a request to add access credentials for a cloud service, a persistent access credential for the cloud service is generated, including: If the number of generated permanent access credentials for the displayed cloud service has not reached the preset limit, a permanent access credential will be generated for the current cloud service in response to the selection of the option to add a new access credential for the current cloud service.

7. The method for configuring cloud services according to claim 1, characterized in that, Also includes: In response to a service role configuration request, display a list of service roles; In response to a selection action for the role creation option, the service role configuration items are displayed; After inputting information into the service role configuration item, in response to the selection of the save option, the service role is generated and the service role list is displayed; In response to the selection of configuration policy options for a service role in the service role list, the policy list for that service role is displayed; In response to a selection action for a new policy option, the policy configuration items are displayed; After inputting information into the policy configuration item, the policy for the service role is generated in response to the selection of the save option.

8. The method for configuring cloud services according to claim 7, characterized in that, Also includes: In response to an IAM role creation request, create an IAM role for the cloud service based on the generated cloud service and the created service role.

9. An electronic device, characterized in that, include: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform a method for configuring a cloud service as described in any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method for configuring cloud services as described in any one of claims 1 to 8.

Images