Help Center/ Huawei Cloud Astro Zero/ User Guide (Low-Code)/ Application Integration Development/ Using Connectors to Interconnect with Cloud Services/ Format of the Compatible Instance for Interconnecting with the Object Storage Proxy
Updated on 2025-08-15 GMT+08:00

Format of the Compatible Instance for Interconnecting with the Object Storage Proxy

When you perform operations on object instances of different storage types (OBS or MinIO), you need to configure storage proxy connectors for the object instances of different storage types to implement unified access management of the connector instances.

Billing

After connecting an application to the OBS-type object storage proxy connector, you need to pay for the OBS service separately. For details on the pricing, see Huawei Cloud Pricing. After an application is disabled, OBS is still billed based on the preset billing rules.

Creating an Object Storage Proxy

  1. Log in to the application designer by referring to Logging In to the Application Designer.
  2. In the navigation pane, choose Integrations.
  3. Click Connector Instance under Connector.
  4. In the navigation pane, choose Storage > Object Storage Proxy.
  5. On the right of the page, click + to set the parameters for interconnecting with the object storage proxy.

    Figure 1 Creating an Object Storage Proxy
    Table 1 Parameters for creating an object storage proxy connector

    Parameter

    Description

    Name

    Name of the new connector. The naming rules are as follows:

    • The value cannot exceed 64 characters, including the prefix namespace.

      The content before the name is the namespace. To avoid duplicate data names among different tenants in Astro Zero, a tenant needs to define a namespace when creating an application for the first time. A tenant can create only one namespace. After being created, the namespace cannot be modified.

    • Start with a letter and can contain only letters, digits, and underscores (_). Do not end with an underscore (_).

    Proxy Type

    Storage container type of the object instance. OBS and MinIO are supported.

    Proxy Name

    Select a connector from the drop-down list box.

    Bucket

    Name of the bucket for storing the object instances.

  6. Click Save.

Calling a Connector in a Flow

  1. Create an empty flow by referring to Creating a Blank Flow.
  2. On the flow design page, choose Connector > Storage, and drag the objectstorageproxy diagram element to the canvas.

    objectstorageproxy is preset in the system and is used to call the API of the storage proxy connector.

    Figure 2 Dragging the objectstorageproxy diagram element to the canvas

  3. Click the diagram element, click , and set basic information.

    Figure 3 Setting basic information
    Table 2 Parameter description

    Parameter

    Description

    Label

    Label of a diagram element displayed on the page.

    Name

    Unique ID of the diagram element in the system. The ID cannot be the same as that of other diagram elements. The naming requirements are as follows:

    • Enter up to 80 characters.
    • Start with a letter and can contain only letters, digits, and underscores (_). It cannot end with an underscore (_).

    Description

    Enter the description of the diagram element in the text box.

    Connector

    Select a connector from the drop-down list box.

  4. Click and set parameters.

    Figure 4 Configuring objectstorageproxy parameters
    Table 3 Configuration parameters

    Parameter

    Description

    Action

    Action preset by the system for the connector. Select an action based on service requirements.

    • Get_endpoint_objectstorageproxy: Obtain the address prefix of the object file to be uploaded.
    • view_object_objectstorageproxy: Check the storage objects.
    • put_object_objectstorageproxy: Store objects in the system to OBS buckets.

    In this example, get_endpoint_objectstorageproxy is selected.

    Input Parameters

    Customized parameters set when the connector is defined.

    • If Target is set to object, set the object name in Source.
    • If Target is set to data, configure object data in Source.
    • If Target is set to bucket, configure the bucket in Source.
    • If Target is set to acl, configure the access control permission for the object file in Source. For example, private, public-read, public-read-write, and default (same as the bucket permission).

    Output Parameters

    • Set Source to result and Target to receive the payment result. You must define a structure variable of an empty instance to receive the payment result.
    • Select error from the Source drop-down list box, and set Target to the error code when the calling fails.
    • Select endpoint from the Source drop-down list box. The Target drop-down list box is used to obtain the address prefix of the object file to be uploaded. You must define a variable of the text type to receive the object file.

  5. Connect the Start and objectstorage diagram elements.

    Figure 5 Connecting diagram elements

  6. Click the blank area of the flow designer, select , and set the flow output parameters.

    Use the output parameters of the objectstorageproxy diagram element as the output parameters of the entire flow.

    Figure 6 Setting output parameters

  7. Click to save the flow.
  8. Click to activate the flow.

    You do not need to set input parameters. If the following information is displayed, the address prefix of the uploaded object file is successfully obtained:

    {
      "interviewId": "002N000000T1Jl8Zzzpg",
      "outputs": {
        "variable0": "http://10.100.92.158:9000/mybucket/"
      }
    }