diff --git a/docs/vpcep/api-ref/ALL_META.TXT.json b/docs/vpcep/api-ref/ALL_META.TXT.json
index 41e89929..d08302bd 100644
--- a/docs/vpcep/api-ref/ALL_META.TXT.json
+++ b/docs/vpcep/api-ref/ALL_META.TXT.json
@@ -1,341 +1,650 @@
[
+ {
+ "dockw":"API Reference"
+ },
{
"uri":"vpcep_05_0000.html",
+ "node_id":"vpcep_05_0000.xml",
"product_code":"vpcep",
"code":"1",
"des":"Public cloud APIs comply with the RESTful API design principles. REST-based web services are organized into resources. Each resource is identified by one or more Uniform ",
"doc_type":"api",
"kw":"API Usage Guidelines,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"API Usage Guidelines",
"githuburl":""
},
{
"uri":"vpcep_06_0000.html",
+ "node_id":"vpcep_06_0000.xml",
"product_code":"vpcep",
"code":"2",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"APIs",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"APIs",
"githuburl":""
},
{
"uri":"vpcep_06_0100.html",
+ "node_id":"vpcep_06_0100.xml",
"product_code":"vpcep",
"code":"3",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"Version Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Version Management",
"githuburl":""
},
{
"uri":"vpcep_06_0101.html",
+ "node_id":"vpcep_06_0101.xml",
"product_code":"vpcep",
"code":"4",
"des":"This API is used to query versions of VPCEP APIs.v2 cannot be used.GET /Example requestGET https://{endpoint}/GET https://{endpoint}/ParametersResponse parametersParamete",
"doc_type":"api",
"kw":"Querying Versions of VPCEP APIs,Version Management,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Versions of VPCEP APIs",
"githuburl":""
},
{
"uri":"vpcep_06_0102.html",
+ "node_id":"vpcep_06_0102.xml",
"product_code":"vpcep",
"code":"5",
"des":"This API is used to query the version of a specified VPCEP API.GET /{version}ParametersRequest parameterParameterMandatoryTypeDescriptionversionNoStringSpecifies the vers",
"doc_type":"api",
"kw":"Querying the Version of a Specified VPCEP API,Version Management,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying the Version of a Specified VPCEP API",
"githuburl":""
},
{
"uri":"vpcep_06_0200.html",
+ "node_id":"vpcep_06_0200.xml",
"product_code":"vpcep",
"code":"6",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"APIs for Managing VPC Endpoint Services",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"APIs for Managing VPC Endpoint Services",
"githuburl":""
},
{
"uri":"vpcep_06_0201.html",
+ "node_id":"vpcep_06_0201.xml",
"product_code":"vpcep",
"code":"7",
"des":"This API is used to create a VPC endpoint service. Other users can create a VPC endpoint to connect to the endpoint service.This API is asynchronous. If it is successfull",
"doc_type":"api",
"kw":"Creating a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Creating a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0202.html",
+ "node_id":"vpcep_06_0202.xml",
"product_code":"vpcep",
"code":"8",
"des":"This API is used to query details about a VPC endpoint service.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes parameters in this UR",
"doc_type":"api",
"kw":"Querying Details About a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Details About a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0203.html",
+ "node_id":"vpcep_06_0203.xml",
"product_code":"vpcep",
"code":"9",
"des":"This API is used to modify a VPC endpoint service.PUT /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}Table 1 describes parameters in this URI.URI paramet",
"doc_type":"api",
"kw":"Modifying a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Modifying a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0204.html",
+ "node_id":"vpcep_06_0204.xml",
"product_code":"vpcep",
"code":"10",
"des":"This API is used to delete a VPC endpoint service.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has be",
"doc_type":"api",
"kw":"Deleting a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Deleting a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0205.html",
+ "node_id":"vpcep_06_0205.xml",
"product_code":"vpcep",
"code":"11",
"des":"This API is used to query VPC endpoint services.GET /v1/{project_id}/vpc-endpoint-services?endpoint_service_name={endpoint_service_name}&id={id}&sort_key={sort_key}&sort_",
"doc_type":"api",
"kw":"Querying VPC Endpoint Services,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying VPC Endpoint Services",
"githuburl":""
},
{
"uri":"vpcep_06_0206.html",
+ "node_id":"vpcep_06_0206.xml",
"product_code":"vpcep",
"code":"12",
"des":"This API is used to query connections of a VPC endpoint service. marker_id is the unique ID of each connection.GET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_se",
"doc_type":"api",
"kw":"Querying Connections of a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Connections of a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0207.html",
+ "node_id":"vpcep_06_0207.xml",
"product_code":"vpcep",
"code":"13",
"des":"This API is used to accept or reject a VPC endpoint for a VPC endpoint service.POST /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/connections/actionTab",
"doc_type":"api",
"kw":"Accepting or Rejecting a VPC Endpoint,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Accepting or Rejecting a VPC Endpoint",
"githuburl":""
},
{
"uri":"vpcep_06_0208.html",
+ "node_id":"vpcep_06_0208.xml",
"product_code":"vpcep",
"code":"14",
- "des":"This API is used to query whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_id}/",
+ "des":"This API is used to query whitelist records of a VPC endpoint service.Your account ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_id}",
"doc_type":"api",
"kw":"Querying Whitelist Records of a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API Ref",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Whitelist Records of a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0209.html",
+ "node_id":"vpcep_06_0209.xml",
"product_code":"vpcep",
"code":"15",
- "des":"This API is used to batch add or delete whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.POST /v",
+ "des":"This API is used to batch add or delete whitelist records of a VPC endpoint service.Your account ID is in the whitelist of your own VPC endpoint service by default.POST /",
"doc_type":"api",
"kw":"Batch Adding or Deleting Whitelist Records,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Batch Adding or Deleting Whitelist Records",
"githuburl":""
},
{
"uri":"vpcep_06_0301.html",
+ "node_id":"vpcep_06_0301.xml",
"product_code":"vpcep",
"code":"16",
"des":"This API is used to query public VPC endpoint services. These services are created by operations people and can be visible to and assessed by all users.GET /v1/{project_i",
"doc_type":"api",
"kw":"Querying Public VPC Endpoint Services,APIs for Managing VPC Endpoint Services,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Public VPC Endpoint Services",
"githuburl":""
},
{
"uri":"vpcep_06_0302.html",
+ "node_id":"vpcep_06_0302.xml",
"product_code":"vpcep",
"code":"17",
"des":"This API is used to query basic information about a target VPC endpoint service. You can use this API to query the target VPC endpoint service to be accessed. This API ca",
"doc_type":"api",
"kw":"Querying Basic Information About a VPC Endpoint Service,APIs for Managing VPC Endpoint Services,API ",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Basic Information About a VPC Endpoint Service",
"githuburl":""
},
{
"uri":"vpcep_06_0300.html",
+ "node_id":"vpcep_06_0300.xml",
"product_code":"vpcep",
"code":"18",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"APIs for Managing VPC Endpoints",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"APIs for Managing VPC Endpoints",
"githuburl":""
},
{
"uri":"vpcep_06_0303.html",
+ "node_id":"vpcep_06_0303.xml",
"product_code":"vpcep",
"code":"19",
"des":"This API is used to create a VPC endpoint for accessing a VPC endpoint service.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indic",
"doc_type":"api",
"kw":"Creating a VPC Endpoint,APIs for Managing VPC Endpoints,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Creating a VPC Endpoint",
"githuburl":""
},
{
"uri":"vpcep_06_0304.html",
+ "node_id":"vpcep_06_0304.xml",
"product_code":"vpcep",
"code":"20",
"des":"This API is used to query details about a VPC endpoint.GET /v1/{project_id}/vpc-endpoints/{vpc_endpoint_id}Table 1 describes parameters in this URI.URI parametersParamete",
"doc_type":"api",
"kw":"Querying Details About a VPC Endpoint,APIs for Managing VPC Endpoints,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Details About a VPC Endpoint",
"githuburl":""
},
{
"uri":"vpcep_06_0305.html",
+ "node_id":"vpcep_06_0305.xml",
"product_code":"vpcep",
"code":"21",
"des":"This API is used to delete a VPC endpoint.This API is asynchronous. If it is successfully invoked, status code 200 is returned, indicating that the request has been succe",
"doc_type":"api",
"kw":"Deleting a VPC Endpoint,APIs for Managing VPC Endpoints,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Deleting a VPC Endpoint",
"githuburl":""
},
{
"uri":"vpcep_06_0306.html",
+ "node_id":"vpcep_06_0306.xml",
"product_code":"vpcep",
"code":"22",
"des":"This API is used to query VPC endpoints.GET /v1/{project_id}/vpc-endpoints?endpoint_service_name={endpoint_service_name}&vpc_id={vpc_id}&limit={limit}&offset={offset}&id=",
"doc_type":"api",
"kw":"Querying VPC Endpoints,APIs for Managing VPC Endpoints,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying VPC Endpoints",
"githuburl":""
},
{
"uri":"vpcep_06_0400.html",
+ "node_id":"vpcep_06_0400.xml",
"product_code":"vpcep",
"code":"23",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"Resource Quota",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Resource Quota",
"githuburl":""
},
{
"uri":"vpcep_06_0401.html",
+ "node_id":"vpcep_06_0401.xml",
"product_code":"vpcep",
"code":"24",
"des":"This API is used to query the quota of your resources, including VPC endpoint services and VPC endpoints.GET /v1/{project_id}/quotas?type={resource_type}Table 1 describes",
"doc_type":"api",
"kw":"Querying the Quota,Resource Quota,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying the Quota",
"githuburl":""
},
{
"uri":"vpcep_06_0500.html",
+ "node_id":"vpcep_06_0500.xml",
"product_code":"vpcep",
"code":"25",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
- "kw":"Tag Function",
- "title":"Tag Function",
+ "kw":"Tags",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
+ "title":"Tags",
"githuburl":""
},
{
"uri":"vpcep_06_0501.html",
+ "node_id":"vpcep_06_0501.xml",
"product_code":"vpcep",
"code":"26",
"des":"This API is used to query resources of a tenant by tag.POST /v1/{project_id}/{resource_type}/resource_instances/actionTable 1 describes parameters in this URI.URI parame",
"doc_type":"api",
- "kw":"Querying Resources by Tag,Tag Function,API Reference",
+ "kw":"Querying Resources by Tag,Tags,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Resources by Tag",
"githuburl":""
},
{
"uri":"vpcep_06_0502.html",
+ "node_id":"vpcep_06_0502.xml",
"product_code":"vpcep",
"code":"27",
"des":"This API is used to batch add tags to or delete tags from a specified VPC endpoint service or VPC endpoint.You can add up to 20 tags to a resource.POST /v1/{project_id}/",
"doc_type":"api",
- "kw":"Batch Adding Tags to or Deleting Tags from a Specified Resource,Tag Function,API Reference",
+ "kw":"Batch Adding Tags to or Deleting Tags from a Specified Resource,Tags,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Batch Adding Tags to or Deleting Tags from a Specified Resource",
"githuburl":""
},
{
"uri":"vpcep_06_0503.html",
+ "node_id":"vpcep_06_0503.xml",
"product_code":"vpcep",
"code":"28",
"des":"This API is used to obtain tags of resources of a tenant based on the tenant ID and resource type.GET /v1/{project_id}/{resource_type}/tagsTable 1 describes parameters i",
"doc_type":"api",
- "kw":"Querying Tags of a Tenant's Resource,Tag Function,API Reference",
+ "kw":"Querying Tags of a Tenant's Resource,Tags,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Querying Tags of a Tenant's Resource",
"githuburl":""
},
{
"uri":"vpcep_06_0504.html",
+ "node_id":"vpcep_06_0504.xml",
"product_code":"vpcep",
"code":"29",
"des":"The key should be Unicode characters and cannot be left blank. Only digits, letters, hyphens (-), underscores, and at signs (@) are allowed.The value should be Unicode ch",
"doc_type":"api",
- "kw":"Tag Character Set Specifications,Tag Function,API Reference",
+ "kw":"Tag Character Set Specifications,Tags,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Tag Character Set Specifications",
"githuburl":""
},
{
"uri":"vpcep_08_0000.html",
+ "node_id":"vpcep_08_0000.xml",
"product_code":"vpcep",
"code":"30",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"Appendix",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Appendix",
"githuburl":""
},
{
"uri":"vpcep_08_0001.html",
+ "node_id":"vpcep_08_0001.xml",
"product_code":"vpcep",
"code":"31",
"des":"NormalReturn values for successful requestsStatus CodeReturned ValueDescription200OKThe results of POST, GET, and PUT operations are returned as expected.204No ContentThe",
"doc_type":"api",
"kw":"Status Codes,Appendix,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Status Codes",
"githuburl":""
},
{
"uri":"vpcep_08_0002.html",
+ "node_id":"vpcep_08_0002.xml",
"product_code":"vpcep",
"code":"32",
"des":"If an error occurs during API calling, a customized error message will be returned. This section describes the meaning of each status code returned by VPCEP.An error code",
"doc_type":"api",
"kw":"Error Codes,Appendix,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Error Codes",
"githuburl":""
},
{
"uri":"vpcep_08_0003.html",
+ "node_id":"vpcep_08_0003.xml",
"product_code":"vpcep",
"code":"33",
"des":"A project ID is required for some URLs when an API is called. Therefore, you need to obtain a project ID in advance. Two methods are available:Obtain the Project ID by Ca",
"doc_type":"api",
"kw":"Obtaining a Project ID,Appendix,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Obtaining a Project ID",
"githuburl":""
},
{
"uri":"vpcep_00_0004.html",
+ "node_id":"vpcep_00_0004.xml",
"product_code":"vpcep",
"code":"34",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"api",
"kw":"Change History,API Reference",
+ "search_title":"",
+ "metedata":[
+ {
+ "documenttype":"api",
+ "prodname":"vpcep",
+ "opensource":"false;true"
+ }
+ ],
"title":"Change History",
"githuburl":""
}
diff --git a/docs/vpcep/api-ref/CLASS.TXT.json b/docs/vpcep/api-ref/CLASS.TXT.json
index 85b09982..c873fc51 100644
--- a/docs/vpcep/api-ref/CLASS.TXT.json
+++ b/docs/vpcep/api-ref/CLASS.TXT.json
@@ -117,7 +117,7 @@
"code":"13"
},
{
- "desc":"This API is used to query whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_id}/",
+ "desc":"This API is used to query whitelist records of a VPC endpoint service.Your account ID is in the whitelist of your own VPC endpoint service by default.GET /v1/{project_id}",
"product_code":"vpcep",
"title":"Querying Whitelist Records of a VPC Endpoint Service",
"uri":"vpcep_06_0208.html",
@@ -126,7 +126,7 @@
"code":"14"
},
{
- "desc":"This API is used to batch add or delete whitelist records of a VPC endpoint service.Your domain ID is in the whitelist of your own VPC endpoint service by default.POST /v",
+ "desc":"This API is used to batch add or delete whitelist records of a VPC endpoint service.Your account ID is in the whitelist of your own VPC endpoint service by default.POST /",
"product_code":"vpcep",
"title":"Batch Adding or Deleting Whitelist Records",
"uri":"vpcep_06_0209.html",
@@ -218,7 +218,7 @@
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"product_code":"vpcep",
- "title":"Tag Function",
+ "title":"Tags",
"uri":"vpcep_06_0500.html",
"doc_type":"api",
"p_code":"2",
diff --git a/docs/vpcep/api-ref/en-us_image_0000001508295281.png b/docs/vpcep/api-ref/en-us_image_0000001508295281.png
deleted file mode 100644
index ec3abb85..00000000
Binary files a/docs/vpcep/api-ref/en-us_image_0000001508295281.png and /dev/null differ
diff --git a/docs/vpcep/api-ref/en-us_image_0000002069236673.png b/docs/vpcep/api-ref/en-us_image_0000002069236673.png
new file mode 100644
index 00000000..a6d398c9
Binary files /dev/null and b/docs/vpcep/api-ref/en-us_image_0000002069236673.png differ
diff --git a/docs/vpcep/api-ref/vpcep_00_0004.html b/docs/vpcep/api-ref/vpcep_00_0004.html
index d0243f98..1bd3d161 100644
--- a/docs/vpcep/api-ref/vpcep_00_0004.html
+++ b/docs/vpcep/api-ref/vpcep_00_0004.html
@@ -8,34 +8,58 @@
-
2023-06-13
+ |
2024-11-05
+ |
+This issue incorporates the following changes:
+Updated the description of routetables in Table 2 in Querying Details About a VPC Endpoint. Added the note "If you do not specify this parameter, the route table ID of the VPC is returned in Gateway VPC endpoint service."
+ |
+
+2024-10-31
+ |
+This issue incorporates the following changes:
+- Updated the description of routetables in Table 2 and Table 5 in Creating a VPC Endpoint. Added the note "This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service."
- Updated the description of routetables in Table 3 in Querying VPC Endpoints. Added the note "This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service."
+ |
+
+2024-09-26
+ |
+This issue incorporates the following changes:
+
+ |
+
+2024-09-11
+ |
+This issue incorporates the following changes:
+
+ |
+
+2023-06-13
|
This issue incorporates the following changes:
-
+
|
2023-06-08
|
This issue incorporates the following changes:
-- Added a note in Function.
- Modified the descriptions of port_id and server_type in Table 2 and Table 5.
- Modified the descriptions of port_id and server_type in Table 2.
- Modified the descriptions of port_id and server_type in Table 2 and Table 4.
- Modified the descriptions of port_id and server_type in Table 3.
- Modified the description of dns_names in Table 4.
+- Added a note in Function.
- Modified the descriptions of port_id and server_type in Table 2 and Table 5.
- Modified the descriptions of port_id and server_type in Table 2.
- Modified the descriptions of port_id and server_type in Table 2 and Table 4.
- Modified the descriptions of port_id and server_type in Table 3.
- Modified the description of dns_names in Table 5.
|
2023-06-07
|
This issue incorporates the following changes:
-- Modified the description of port_id in Table 2 and Table 5.
- Modified the description of port_id in Table 2.
- Modified the description of port_id in Table 2 and Table 4.
- Modified the description of port_id in Table 3.
- Modified the descriptions of subnet_id, enable_dns, and dns_names in Table 2 and Table 4.
- Modified the descriptions of enable_dns, dns_names, and subnet_id in Table 2.
- Modified the descriptions of enable_dns, dns_names, and subnet_id in Table 3.
+- Modified the description of port_id in Table 2 and Table 5.
- Modified the description of port_id in Table 2.
- Modified the description of port_id in Table 2 and Table 4.
- Modified the description of port_id in Table 3.
- Modified the descriptions of subnet_id, enable_dns, and dns_names in Table 2 and Table 5.
- Modified the descriptions of enable_dns, dns_names, and subnet_id in Table 2.
- Modified the descriptions of enable_dns, dns_names, and subnet_id in Table 3.
|
2023-06-06
|
This issue incorporates the following changes:
-- Updated Example response in Querying Versions of VPCEP APIs.
- Modified the description of approval_enabled in Table 2 and Table 5.
- Modified the description of approval_enabled in Table 2.
- Modified the description of approval_enabled in Table 4.
- Modified the description of approval_enabled in Table 3.
- Added description to Table 3.
- Modified the type and description of routetables, and modified the descriptions of whitelist and enable_whitelist in Table 2. Added response parameters specification_name, endpoint_pool_id, and description to Table 4.
- Modified the descriptions of parameters whitelist, enable_whitelist, and routetables and added response parameters description, specification_name, and endpoint_pool_id to Table 2.
- Modified the description of parameters whitelist, enable_whitelist, and routetables in Response and added response parameters description, specification_name, and endpoint_pool_id to Response.
+- Updated Example response in Querying Versions of VPCEP APIs.
- Modified the description of approval_enabled in Table 2 and Table 5.
- Modified the description of approval_enabled in Table 2.
- Modified the description of approval_enabled in Table 4.
- Modified the description of approval_enabled in Table 3.
- Added description to Table 3.
- Modified the type and description of routetables, and modified the descriptions of whitelist and enable_whitelist in Table 2. Added response parameters specification_name, endpoint_pool_id, and description to Table 5.
- Modified the descriptions of parameters whitelist, enable_whitelist, and routetables, and added response parameters description, specification_name, and endpoint_pool_id to Table 2.
- Modified the description of parameters whitelist, enable_whitelist, and routetables in Response and added response parameters description, specification_name, and endpoint_pool_id to Response.
|
2023-05-25
|
This issue incorporates the following changes:
-
+
|
2023-04-26
@@ -53,7 +77,7 @@
|
2022-10-26
|
This issue incorporates the following changes:
-- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 2.
- Updated the description of parameters port_id, vip_port_id, server_type, status, and tcp_proxy in Table 5. Deleted cidr_type in Table 5.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 2.
- Updated the description of parameters port_id and tcp_proxy in Table 2.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 4.
- Updated the description of parameter sort_key in Table 2.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 3.
- Updated the description of sort_key in Table 2 and adjusted the position of Table 2.
- Updated the description of parameter status in Table 3.
- Added sort_key in URI.
- Updated the description of sort_key in Table 2 and adjusted the position of Table 2.
- Updated the description of parameter created_at in Table 3.
- Updated the description of parameter sort_key in Table 2.
- Updated the name and adjusted the position of Table 2.
- Updated the description of parameter status in Table 4.
- Updated the description of parameter sort_key in Table 2.
- Updated Example request in Querying Resources by Tag.
- Updated Example request in Batch Adding Tags to or Deleting Tags from a Specified Resource.
- Updated Example request in Querying Tags of a Tenant's Resource.
+- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 2.
- Updated the description of parameters port_id, vip_port_id, server_type, status, and tcp_proxy in Table 5. Deleted cidr_type in Table 5.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 2.
- Updated the description of parameters port_id and tcp_proxy in Table 2.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 4.
- Updated the description of parameter sort_key in Table 2.
- Updated the description of parameters port_id, server_type, and tcp_proxy in Table 3.
- Updated the description of sort_key in Table 2 and adjusted the position of Table 2.
- Updated the description of parameter status in Table 3.
- Added sort_key in URI.
- Updated the description of sort_key in Table 2 and adjusted the position of Table 2.
- Updated the description of parameter created_at in Table 3.
- Updated the description of parameter sort_key in Table 2.
- Updated the name and adjusted the position of Table 2.
- Updated the description of parameter status in Table 5.
- Updated the description of parameter sort_key in Table 2.
- Updated Example request in Querying Resources by Tag.
- Updated Example request in Batch Adding Tags to or Deleting Tags from a Specified Resource.
- Updated Example request in Querying Tags of a Tenant's Resource.
|
2021-02-05
diff --git a/docs/vpcep/api-ref/vpcep_06_0000.html b/docs/vpcep/api-ref/vpcep_06_0000.html
index 9cad289f..cbf40ee3 100644
--- a/docs/vpcep/api-ref/vpcep_06_0000.html
+++ b/docs/vpcep/api-ref/vpcep_06_0000.html
@@ -12,7 +12,7 @@
Resource Quota
-Tag Function
+Tags
diff --git a/docs/vpcep/api-ref/vpcep_06_0201.html b/docs/vpcep/api-ref/vpcep_06_0201.html
index 004f982e..70c6bcd2 100644
--- a/docs/vpcep/api-ref/vpcep_06_0201.html
+++ b/docs/vpcep/api-ref/vpcep_06_0201.html
@@ -30,11 +30,11 @@
Request- Parameter description
Table 2 Request parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -46,7 +46,7 @@
Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in universally unique identifier (UUID) format.
The values are as follows:
-- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field port_id in Querying Details of a Load Balancer and Viewing Details of a Load Balancer in the Elastic Load Balancing API Reference.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see port_id in the response in section Querying NICs of an ECS in the Elastic Cloud Server API Reference.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
+- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field port_id in Querying Details of a Load Balancer and Viewing Details of a Load Balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see port_id in the response in Querying NICs of an ECS in the Elastic Cloud Server API Reference.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
NOTE: - To create a VPC endpoint service, the CIDR block of the VPC where the VPC endpoint service is deployed cannot overlap with 198.19.128.0/17.
- The destination address of the custom route in the VPC route table cannot overlap with 198.19.128.0/17.
|
@@ -77,7 +77,7 @@
String
|
Specifies the ID of the VPC to which the backend resource of the VPC endpoint service belongs.
-For details, see response field id in Querying VPC Details in the Virtual Private Cloud API Reference.
+For details, see response field id in Querying VPC Details in Virtual Private Cloud API Reference.
|
approval_enabled
@@ -98,9 +98,9 @@
| String
|
Specifies the type of the VPC endpoint service. Only your private services can be configured into interface VPC endpoint services.
-There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+ There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
- You can view those VPC endpoint services that are configured by operations people and are visible and accessible to all users. For detailed steps, see Querying Public VPC Endpoint Services. Perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoint services of the gateway type and interface type.
+ You can view those VPC endpoint services that are configured by O&M personnel and are visible and accessible to all users. For detailed steps, see Querying Public VPC Endpoint Services. Perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoint services of the gateway type and interface type.
|
server_type
@@ -120,7 +120,7 @@
| Array of objects
|
Lists the port mappings opened to the VPC endpoint service. For details, see Table 3.
-Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, either server_port or protocol, or both server_port and protocol of each VPC endpoint service must be unique. A maximum of 200 port mappings can be created at a time.
+Duplicate port mappings are not allowed in the same VPC endpoint service. If multiple VPC endpoint services share the same port_id value, either server_port or protocol, or both server_port and protocol of each of these VPC endpoint services must be unique. A maximum of 200 port mappings can be created at a time.
|
tcp_proxy
@@ -149,6 +149,15 @@
A maximum of 20 tags can be added to each VPC endpoint service.
|
+description
+ |
+No
+ |
+String
+ |
+Supplementary information about the VPC endpoint service. The description can contain a maximum of 128 characters and cannot contain left angle brackets (<) or right angle brackets (>).
+ |
+
@@ -157,9 +166,9 @@
Mandatory
|
-Type
+ | Type
|
-Description
+ | Description
|
|
@@ -199,7 +208,7 @@
Table 4 Tags parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
@@ -255,9 +264,9 @@
Response
- Parameter description
Table 5 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -288,7 +297,7 @@
String
|
Specifies the type of the VPC endpoint service.
-There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+ There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoints of the gateway and interface types.
|
@@ -320,7 +329,7 @@
Boolean
|
Specifies whether connection approval is required.
-- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
|
status
@@ -383,6 +392,13 @@
| Lists the resource tags. For details, see Table 7.
|
+description
+ |
+String
+ |
+Supplementary information about the VPC endpoint service.
+ |
+
@@ -391,7 +407,7 @@
Type
|
-Description
+ | Description
|
@@ -461,6 +477,7 @@
"service_type":"interface",
"server_type":"VM",
"project_id":"6e9dfd51d1124e8d8498dce894923a0d",
+ "description": "",
"created_at":"2018-01-30T07:42:01Z",
"ports":
[
diff --git a/docs/vpcep/api-ref/vpcep_06_0202.html b/docs/vpcep/api-ref/vpcep_06_0202.html
index f9169cbd..b8ca77e8 100644
--- a/docs/vpcep/api-ref/vpcep_06_0202.html
+++ b/docs/vpcep/api-ref/vpcep_06_0202.html
@@ -38,11 +38,11 @@
Response
- Parameter description
-
Table 2 Response parametersParameter
+Table 2 Response parametersParameter
|
Type
|
-Description
+ | Description
|
@@ -95,7 +95,7 @@
Boolean
|
Specifies whether connection approval is required.
-- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
|
status
@@ -111,7 +111,7 @@
| String
|
Specifies the type of the VPC endpoint service.
-There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+ There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoints of the gateway and interface types.
|
@@ -191,7 +191,7 @@
Type
|
-Description
+ | Description
|
@@ -251,7 +251,7 @@
Table 5 Error parametersParameter
|
-Type
+ | Type
|
Description
|
@@ -287,6 +287,7 @@
"service_type":"interface",
"server_type":"VM",
"project_id":"6e9dfd51d1124e8d8498dce894923a0d",
+ "description": "",
"created_at":"2018-01-30T07:42:01Z",
"ports":
[
diff --git a/docs/vpcep/api-ref/vpcep_06_0203.html b/docs/vpcep/api-ref/vpcep_06_0203.html
index 5f854e57..15c2ead0 100644
--- a/docs/vpcep/api-ref/vpcep_06_0203.html
+++ b/docs/vpcep/api-ref/vpcep_06_0203.html
@@ -35,11 +35,11 @@
Request- Parameter description
Table 2 Request parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -80,7 +80,7 @@
String
|
Specifies the ID for identifying the backend resource of the VPC endpoint service. The ID is in UUID format. The values are as follows:
-- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field port_id in Querying Details of a Load Balancer and Viewing Details of a Load Balancer in the Elastic Load Balancing API Reference.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see port_id in the response in section Querying NICs of an ECS in the Elastic Cloud Server API Reference.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
+- If the backend resource is a load balancer, the value is the ID of the port bound to the private IP address of the load balancer. For details, see response field port_id in Querying Details of a Load Balancer and Viewing Details of a Load Balancer.
- If the backend resource is an ECS, the value is the NIC ID of the ECS where the VPC endpoint service is deployed. For details, see port_id in the response in Querying NICs of an ECS in the Elastic Cloud Server API Reference.
- If the backend resource is a virtual IP address, the value is the port ID of the physical server where virtual resources are created. (This value will be discarded. The LB type is recommended.)
- If the backend resource is a BMS, the value is the NIC ID of the BMS where the VPC endpoint service is deployed. (This value will be discarded. The LB type is recommended.)
|
tcp_proxy
@@ -116,9 +116,9 @@
| Mandatory
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -177,11 +177,11 @@
Response- Parameter description
-
Table 4 Response parametersParameter
+Table 4 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -234,7 +234,7 @@
Boolean
|
Specifies whether connection approval is required.
-- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
|
status
@@ -250,7 +250,7 @@
| String
|
Specifies the type of the VPC endpoint service.
-There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+ There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoints of the gateway and interface types.
|
@@ -322,7 +322,7 @@
Type
|
-Description
+ | Description
|
@@ -393,6 +393,7 @@
"service_type":"interface",
"server_type":"VM",
"project_id":"6e9dfd51d1124e8d8498dce894923a0d",
+ "description": "",
"created_at":"2018-01-30T07:42:01Z",
"ports":
[
diff --git a/docs/vpcep/api-ref/vpcep_06_0205.html b/docs/vpcep/api-ref/vpcep_06_0205.html
index 1fd17e63..7437e881 100644
--- a/docs/vpcep/api-ref/vpcep_06_0205.html
+++ b/docs/vpcep/api-ref/vpcep_06_0205.html
@@ -27,11 +27,11 @@
Table 2 Query parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -114,11 +114,11 @@
Response- Parameter description
-
Table 3 Response parametersParameter
+Table 3 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -190,7 +190,7 @@
Boolean
|
Specifies whether connection approval is required.
-- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
+- false: Connection approval is not required. The created VPC endpoint is in the accepted state.
- true: Connection approval is required. The created VPC endpoint is in the pendingAcceptance state until the owner of the associated VPC endpoint service approves the connection.
|
status
@@ -198,7 +198,7 @@
| String
|
Specifies the status of the VPC endpoint service.
-- creating: The VPC endpoint service is being created.
- available: The VPC endpoint service is connectable.
- failed: The VPC endpoint service failed to be created.
- deleting: The VPC endpoint service is being deleted.
+- creating: The VPC endpoint service is being created.
- available: The VPC endpoint service is connectable.
- failed: The VPC endpoint service failed to be created.
- deleting: The VPC endpoint service is being deleted.
|
service_type
@@ -206,7 +206,7 @@
| String
|
Specifies the type of the VPC endpoint service.
-There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+ There are two types of VPC endpoint services: interface and gateway. - Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoints of the gateway and interface types.
|
@@ -292,6 +292,13 @@
Specifies the ID of the cluster the VPC endpoint belongs to.
|
+description
+ |
+String
+ |
+Supplementary information about the VPC endpoint service.
+ |
+
@@ -300,7 +307,7 @@
|
Type
|
-Description
+ | Description
|
@@ -361,7 +368,7 @@
Table 7 Error parametersParameter
|
-Type
+ | Type
|
Description
|
@@ -411,6 +418,7 @@
],
"project_id":"6e9dfd51d1124e8d8498dce894923a0d",
"domain_id" : "5fc973eea581490997e82ea11a1df31f",
+ "description": "",
"created_at":"2018-01-30T07:42:01Z",
"updated_at":"2018-01-30T07:42:01Z"
}
diff --git a/docs/vpcep/api-ref/vpcep_06_0206.html b/docs/vpcep/api-ref/vpcep_06_0206.html
index ddaff75f..ef440eaf 100644
--- a/docs/vpcep/api-ref/vpcep_06_0206.html
+++ b/docs/vpcep/api-ref/vpcep_06_0206.html
@@ -215,7 +215,7 @@
Table 5 Error parametersParameter
|
-Type
+ | Type
|
Description
|
diff --git a/docs/vpcep/api-ref/vpcep_06_0207.html b/docs/vpcep/api-ref/vpcep_06_0207.html
index 8eed769b..9012f578 100644
--- a/docs/vpcep/api-ref/vpcep_06_0207.html
+++ b/docs/vpcep/api-ref/vpcep_06_0207.html
@@ -162,7 +162,7 @@
Table 5 Error parametersParameter
|
-Type
+ | Type
|
Description
|
diff --git a/docs/vpcep/api-ref/vpcep_06_0208.html b/docs/vpcep/api-ref/vpcep_06_0208.html
index b93ab6da..6e6f77c4 100644
--- a/docs/vpcep/api-ref/vpcep_06_0208.html
+++ b/docs/vpcep/api-ref/vpcep_06_0208.html
@@ -2,7 +2,7 @@
Querying Whitelist Records of a VPC Endpoint Service
FunctionThis API is used to query whitelist records of a VPC endpoint service.
- Your domain ID is in the whitelist of your own VPC endpoint service by default.
+ Your account ID is in the whitelist of your own VPC endpoint service by default.
URIGET /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/permissions?permission={permission}&sort_key={sort_key}&sort_dir={sort_dir}&limit={limit}&offset={offset}
@@ -36,11 +36,11 @@
Table 2 Query parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -50,8 +50,8 @@
String
|
-Specifies the authorized domain ID. The format is the iam:domain::domain_id.
-domain_id indicates the domain ID, for example, iam:domain::6e9dfd51d1124e8d8498dce894923a0d
+ | Specifies the authorized account ID. The format is the iam:domain::domain_id.
+domain_id indicates the account ID, for example, iam:domain::6e9dfd51d1124e8d8498dce894923a0d
Fuzzy search is supported.
|
@@ -105,11 +105,11 @@
Response- Parameter description
-
Table 3 Response parametersParameter
+Table 3 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -133,9 +133,9 @@
Table 4 permissions parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
diff --git a/docs/vpcep/api-ref/vpcep_06_0209.html b/docs/vpcep/api-ref/vpcep_06_0209.html
index 03555d89..45b4906e 100644
--- a/docs/vpcep/api-ref/vpcep_06_0209.html
+++ b/docs/vpcep/api-ref/vpcep_06_0209.html
@@ -2,7 +2,7 @@
Batch Adding or Deleting Whitelist Records
FunctionThis API is used to batch add or delete whitelist records of a VPC endpoint service.
- Your domain ID is in the whitelist of your own VPC endpoint service by default.
+ Your account ID is in the whitelist of your own VPC endpoint service by default.
URIPOST /v1/{project_id}/vpc-endpoint-services/{vpc_endpoint_service_id}/permissions/action
@@ -41,7 +41,7 @@
Type
|
- Description
+ | Description
|
@@ -54,7 +54,7 @@
Lists the whitelist records.
The record is in the iam:domain::domain_id format.
Fields are described as follows:
-- iam:domain:: is fixed.
- domain_id indicates the domain ID of the target user.
The value contains 1 to 64 characters, including letters, digits, and asterisks (*). If you enter an asterisk, this VPC endpoint service allows access from any VPC endpoints.
+- iam:domain:: is fixed.
- domain_id indicates the account ID of the target user.
The value contains 1 to 64 characters, including letters, digits, and asterisks (*). If you enter an asterisk, this VPC endpoint service allows access from any VPC endpoints.
Example: iam:domain::6e9dfd51d1124e8d8498dce894923a0dd
|
@@ -93,11 +93,11 @@
Response- Parameter description
-
Table 3 Response parameterParameter
+Table 3 Response parameterParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
diff --git a/docs/vpcep/api-ref/vpcep_06_0301.html b/docs/vpcep/api-ref/vpcep_06_0301.html
index 8a8fd62a..4846752b 100644
--- a/docs/vpcep/api-ref/vpcep_06_0301.html
+++ b/docs/vpcep/api-ref/vpcep_06_0301.html
@@ -164,7 +164,7 @@
String
|
-Specifies the type of the VPC endpoint service. The value can be: - Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+ Specifies the type of the VPC endpoint service. The value can be: - Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoints of the gateway and interface types.
|
diff --git a/docs/vpcep/api-ref/vpcep_06_0302.html b/docs/vpcep/api-ref/vpcep_06_0302.html
index e0ecc2de..d498c156 100644
--- a/docs/vpcep/api-ref/vpcep_06_0302.html
+++ b/docs/vpcep/api-ref/vpcep_06_0302.html
@@ -93,7 +93,7 @@
String
|
Specifies the type of the VPC endpoint service. Only your private services can be configured into interface VPC endpoint services.
-- Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+- Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoints of the gateway and interface types.
|
diff --git a/docs/vpcep/api-ref/vpcep_06_0303.html b/docs/vpcep/api-ref/vpcep_06_0303.html
index 8ce93902..da9a5ece 100644
--- a/docs/vpcep/api-ref/vpcep_06_0303.html
+++ b/docs/vpcep/api-ref/vpcep_06_0303.html
@@ -27,14 +27,14 @@
-Request- Parameter description
+
Request- Parameter description
Table 2 Request parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -69,7 +69,7 @@
String
|
Specifies the ID of the VPC where the VPC endpoint is to be created.
-For details, see response field id in Querying VPC Details in the Virtual Private Cloud API Reference.
+For details, see response field id in Querying VPC Details in Virtual Private Cloud API Reference.
|
enable_dns
@@ -103,7 +103,7 @@
|
Lists the IDs of route tables.
If you do not specify this parameter, the route table ID of the VPC is returned.
- NOTE: This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+ NOTE: This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
|
@@ -153,6 +153,28 @@
Specifies the name of the VPC endpoint specifications.
|
+policy_statement
+ |
+No
+ |
+Array of PolicyStatement objects
+ |
+Specifies the policy of the gateway VPC endpoint.
+This parameter is available only when you create a gateway VPC endpoint.
+Array length: 0–10
+Default value:
+{
+ "Action": [
+ "obs:*:*"
+ ],
+ "Resource": [
+ "obs:*:*:*:*/*",
+ "obs:*:*:*:*"
+ ],
+ "Effect": "Allow"
+}
+ |
+
description
|
No
@@ -168,7 +190,7 @@
Table 3 Tags parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
@@ -197,29 +219,83 @@
---|
-- Example request
POST https://{endpoint}/v1/{project_id}/vpc-endpoints
-{
-"subnet_id": "68bfbcc1-dff2-47e4-a9d4-332b9bc1b8de",
-"vpc_id": "84758cf5-9c62-43ae-a778-3dbd8370c0a4",
-"tags":[
- {
- "key":"test1",
- "value":"test1"
- }
- ],
-"endpoint_service_id":"e0c748b7-d982-47df-ba06-b9c8c7650c1a",
-"enable_dns":true
-}
+
+ Table 4 PolicyStatementParameter
+ |
+Mandatory
+ |
+Type
+ |
+Description
+ |
+
+
+Effect
+ |
+Yes
+ |
+String
+ |
+Specifies the policy effect, which can be Allow or Deny.
+ |
+
+Action
+ |
+Yes
+ |
+Array of strings
+ |
+Specifies OBS access permissions.
+ |
+
+Resource
+ |
+Yes
+ |
+Array of strings
+ |
+Specifies the OBS object.
+ |
+
+
+
-
+ - Example request
POST https://{endpoint}/v1/{project_id}/vpc-endpoints
+Creating an interface VPC endpoint
+{
+ "subnet_id": "61881173-3899-4981-a700-170253d469b6",
+ "endpoint_service_id": "2da0fe8f-5cb7-4d93-bb35-dc05334da1be",
+ "vpc_id": "d7b2bf07-1b4c-43fa-bd88-d80c6ebea140",
+ "tags": [
+ {
+ "key": "test2",
+ "value": "test2"
+ }
+ ]
+}
+Creating a gateway VPC endpoint
+{
+ "endpoint_service_id": "e4a21a61-f09e-41bc-b487-23d6204ae27b",
+ "vpc_id": "d7b2bf07-1b4c-43fa-bd88-d80c6ebea140",
+ "enable_dns": true,
+ "tags": [
+ {
+ "key": "test1",
+ "value": "test1"
+ }
+ ],
+ "routetables": [
+ "cd7fdf2b-d964-4a4a-a169-2af1112e7d02"
+ ]
+}
-Response- Parameter description
-
Table 4 Response parametersParameter
+Response- Parameter description
+
Table 5 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -235,7 +311,7 @@
String
|
Specifies the type of the VPC endpoint service that is associated with the VPC endpoint.
-- Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+- Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can view those VPC endpoint services that are configured by operations people and are visible and accessible to all users. For detailed steps, see Querying Public VPC Endpoint Services. Perform the operations in Creating a VPC Endpoint Service to create an interface VPC endpoint service.
|
@@ -251,8 +327,8 @@
Array of strings
|
-Specifies the domain status.
-- arrear_frozen: frozen due to arrears
- verify_frozen: frozen due to lack of real-name authentication
- police_frozen: frozen for legal management
- illegal_frozen: frozen due to abuse
- partner_frozen: frozen for partnership
- active: The domain is normal.
+ | Specifies the account status.
+- arrear_frozen: frozen due to arrears
- verify_frozen: frozen due to lack of real-name authentication
- police_frozen: frozen for legal management
- illegal_frozen: frozen due to abuse
- partner_frozen: frozen for partnership
- active: The account is normal.
|
endpoint_service_name
@@ -338,7 +414,7 @@
|
Array of objects
|
-Lists the resource tags. For details, see Table 5.
+ | Lists the resource tags. For details, see Table 6.
|
whitelist
@@ -356,7 +432,7 @@
| Boolean
|
Specifies whether access control is enabled.
-- true: Access control is enabled.
- false: Access control is disabled.
+- true: Access control is enabled.
- false: Access control is disabled.
If you do not specify this parameter, the whitelist is not enabled.
NOTE: This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.
@@ -368,7 +444,7 @@
|
Lists the IDs of route tables.
If you do not specify this parameter, the route table ID of the VPC is returned.
- NOTE: This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+ NOTE: This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
|
@@ -387,6 +463,25 @@
- enable: The endpoint will be enabled.
- disable: The endpoint will be disabled.
+policy_statement
+ |
+Array of PolicyStatement objects
+ |
+Specifies the policy of the gateway VPC endpoint.
+This parameter is available only when you create a gateway VPC endpoint.
+Default value:
+{
+ "Action": [
+ "obs:*:*"
+ ],
+ "Resource": [
+ "obs:*:*:*:*/*",
+ "obs:*:*:*:*"
+ ],
+ "Effect": "Allow"
+}
+ |
+
endpoint_pool_id
|
String
@@ -405,7 +500,7 @@
|
-Table 5 Tags parametersParameter
+Table 6 Tags parametersParameter
|
Type
|
@@ -430,39 +525,120 @@
---|
+
+Table 7 PolicyStatementParameter
+ |
+Mandatory
+ |
+Type
+ |
+Description
+ |
+
+
+Effect
+ |
+Yes
+ |
+String
+ |
+Specifies the policy effect, which can be Allow or Deny.
+ |
+
+Action
+ |
+Yes
+ |
+Array of strings
+ |
+Specifies OBS access permissions.
+ |
+
+Resource
+ |
+Yes
+ |
+Array of strings
+ |
+Specifies the OBS object.
+ |
+
+
+
+
-- Example response
{
- "id": "4189d3c2-8882-4871-a3c2-d380272eed83",
- "status": "creating",
- "service_type": "interface",
- "marker_id": 322312312312,
- "active_status":[
- "active"
- ],
- "vpc_id": "4189d3c2-8882-4871-a3c2-d380272eed83",
- "enable_dns": false,
- "endpoint_service_name": "test123",
- "endpoint_service_id": "test123",
- "project_id": "6e9dfd51d1124e8d8498dce894923a0d",
- "whitelist": [
- "127.0.0.1"
- ],
- "enable_whitelist": true,
- "specification_name":"default",
- "enable_status":"enable",
- "endpoint_pool_id":"501f4a3b-6f96-4309-97d1-e291b8ca5b96",
- "description":"demo",
- "created_at": "2018-01-30T07:42:01Z",
- "updated_at": "2018-01-30T07:42:01Z",
- "tags": [
- {
- "key": "test1",
- "value": "test1"
- }
- ]
+ - Example response
An interface VPC endpoint has been created.
+{
+ "id": "530d6f2f-d115-4df2-8c36-32d19f3c0bbc",
+ "status": "creating",
+ "tags": [
+ {
+ "key": "test2",
+ "value": "test2"
+ }
+ ],
+ "whitelist": [],
+ "marker_id": 201515772,
+ "active_status": [
+ "active"
+ ],
+ "vpc_id": "d7b2bf07-1b4c-43fa-bd88-d80c6ebea140",
+ "service_type": "interface",
+ "project_id": "0df25bbc*****62f88c00c2959df9a",
+ "subnet_id": "61881173-3899-4981-a700-170253d469b6",
+ "enable_dns": false,
+ "created_at": "2024-08-23T07:37:37Z",
+ "updated_at": "2024-08-23T07:37:37Z",
+ "endpoint_service_id": "2da0fe8f-5cb7-4d93-bb35-dc05334da1be",
+ "endpoint_service_name": "test123",
+ "enable_whitelist": false,
+ "specification_name": "default",
+ "enable_status": "enable",
+ "description": "",
+ "endpoint_pool_id": "0e796c11-6cf1-484a-9b8c-f837cb925287"
+}
+A gateway VPC endpoint has been created.
+{
+ "id": "093998ea-ebaa-440d-8c75-935178e4dd93",
+ "status": "creating",
+ "tags": [
+ {
+ "key": "test1",
+ "value": "test1"
+ }
+ ],
+ "marker_id": 201414431,
+ "active_status": [
+ "active"
+ ],
+ "vpc_id": "d7b2bf07-1b4c-43fa-bd88-d80c6ebea140",
+ "service_type": "gateway",
+ "project_id": "0df25bbc87****8c00c2959df9a",
+ "routetables": [
+ "cd7fdf2b-d964-4a4a-a169-2af1112e7d02"
+ ],
+ "created_at": "2024-08-23T07:23:22Z",
+ "updated_at": "2024-08-23T07:23:22Z",
+ "endpoint_service_id": "e4a21a61-f09e-41bc-b487-23d6204ae27b"
+ "endpoint_service_name": "test123",
+ "policy_statement": [
+ {
+ "Action": [
+ "obs:*:*"
+ ],
+ "Resource": [
+ "obs:*:*:*:*/*",
+ "obs:*:*:*:*"
+ ],
+ "Effect": "Allow"
+ }
+ ],
+ "specification_name": "default",
+ "enable_status": "enable",
+ "description": "",
+ "endpoint_pool_id": "d86778c4-ad4b-4abd-988e-8c2572047fe4"
}
-
diff --git a/docs/vpcep/api-ref/vpcep_06_0304.html b/docs/vpcep/api-ref/vpcep_06_0304.html
index 058e8216..712dca94 100644
--- a/docs/vpcep/api-ref/vpcep_06_0304.html
+++ b/docs/vpcep/api-ref/vpcep_06_0304.html
@@ -37,12 +37,12 @@
-Response- Parameter description
-
Table 2 Response parametersParameter
+Response- Parameter description
+
Table 2 Response parametersParameter
|
Type
|
-Description
+ | Description
|
@@ -58,7 +58,7 @@
String
|
Specifies the type of the VPC endpoint service that is associated with the VPC endpoint.
-- Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+- Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
|
status
@@ -73,8 +73,8 @@
|
Array of strings
|
-Specifies the domain status.
-- arrear_frozen: frozen due to arrears
- verify_frozen: frozen due to lack of real-name authentication
- police_frozen: frozen for legal management
- illegal_frozen: frozen due to abuse
- partner_frozen: frozen for partnership
- active: The domain is normal.
+ | Specifies the account status.
+- arrear_frozen: frozen due to arrears
- verify_frozen: frozen due to lack of real-name authentication
- police_frozen: frozen for legal management
- illegal_frozen: frozen due to abuse
- partner_frozen: frozen for partnership
- active: The account is normal.
|
endpoint_service_name
@@ -178,7 +178,7 @@
| Array of objects
|
Specifies the error message.
-This field is returned when the status of the VPC endpoint changes to failed. For details, see Table 4.
+This field is returned when the status of the VPC endpoint changes to failed. For details, see Table 5.
|
whitelist
@@ -196,7 +196,7 @@
| Boolean
|
Specifies whether access control is enabled.
-- true: Access control is enabled.
- false: Access control is disabled.
+- true: Access control is enabled.
- false: Access control is disabled.
If you do not specify this parameter, the whitelist is not enabled.
NOTE: This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.
@@ -207,9 +207,26 @@
| Array of strings
|
Lists the IDs of route tables.
-If you do not specify this parameter, the route table ID of the VPC is returned.
- NOTE: This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
-
+If you do not specify this parameter, the route table ID of the VPC is returned in Gateway VPC endpoint service.
+ |
+
+policy_statement
+ |
+Array of PolicyStatement objects
+ |
+Specifies the policy of the gateway VPC endpoint.
+This parameter is available only when you create a gateway VPC endpoint.
+Default value:
+{
+ "Action": [
+ "obs:*:*"
+ ],
+ "Resource": [
+ "obs:*:*:*:*/*",
+ "obs:*:*:*:*"
+ ],
+ "Effect": "Allow"
+}
|
description
@@ -271,26 +288,67 @@
|
-Table 4 Error parametersParameter
+Table 4 PolicyStatementParameter
|
-Type
+ | Mandatory
|
-Description
+ | Type
+ |
+Description
|
-error_code
+ | Effect
|
-String
+ | Yes
|
-Specifies the error code.
+ | String
+ |
+Specifies the policy effect, which can be Allow or Deny.
|
-error_message
+ | Action
|
-String
+ | Yes
|
-Specifies the error message.
+ | Array of strings
+ |
+Specifies OBS access permissions.
+ |
+
+Resource
+ |
+Yes
+ |
+Array of strings
+ |
+Specifies the OBS object.
+ |
+
+
+
+
+
+Table 5 Error parametersParameter
+ |
+Type
+ |
+Description
+ |
+
+
+error_code
+ |
+String
+ |
+Specifies the error code.
+ |
+
+error_message
+ |
+String
+ |
+Specifies the error message.
|
@@ -298,35 +356,72 @@
-- Example response
{
- "id": "4189d3c2-8882-4871-a3c2-d380272eed83",
- "status": "accepted",
- "service_type": "interface",
- "marker_id": 322312312312,
- "active_status":[
- "active"
- ],
- "vpc_id": "4189d3c2-8882-4871-a3c2-d380272eed83",
- "enable_dns": false,
- "endpoint_service_name": "test123",
- "endpoint_service_id": "test123",
- "project_id": "6e9dfd51d1124e8d8498dce894923a0d",
- "whitelist": [
- "127.0.0.1"
- ],
- "enable_whitelist": true,
- "specification_name":"default",
- "endpoint_pool_id":"501f4a3b-6f96-4309-97d1-e291b8ca5b96",
- "description":"demo",
- "created_at": "2018-01-30T07:42:01Z",
- "updated_at": "2018-01-30T07:42:01Z",
- "description" : "",
- "tags": [
- {
- "key": "test1",
- "value": "test1"
- }
- ]
+ - Example response
Querying details of an interface VPC endpoint
+{
+ "id": "530d6f2f-d115-4df2-8c36-32d19f3c0bbc",
+ "status": "accepted",
+ "ip": "192.168.14.23",
+ "tags": [
+ {
+ "key": "test2",
+ "value": "test2"
+ }
+ ],
+ "whitelist": [],
+ "marker_id": 201515772,
+ "active_status": [
+ "active"
+ ],
+ "vpc_id": "d7b2bf07-1b4c-43fa-bd88-d80c6ebea140",
+ "service_type": "interface",
+ "project_id": "0df25bbc878***2f88c00c2959df9a",
+ "subnet_id": "61881173-3899-4981-a700-170253d469b6",
+ "enable_dns": false,
+ "routetables": [],
+ "created_at": "2024-08-23T07:37:37Z",
+ "updated_at": "2024-08-23T07:37:39Z",
+ "endpoint_service_id": "2da0fe8f-5cb7-4d93-bb35-dc05334da1be",
+ "endpoint_service_name": "test456",
+ "enable_whitelist": false,
+ "specification_name": "default",
+ "enable_status": "enable",
+ "description": "",
+ "endpoint_pool_id": "0e796c11-6cf1-484a-9b8c-f837cb925287"
+}
+Querying details of a gateway VPC endpoint
+{
+ "id": "59a40a87-abe0-4c1f-8bf0-63700128cb39",
+ "status": "accepted",
+ "tags": [],
+ "marker_id": 201421455,
+ "active_status": [
+ "active"
+ ],
+ "vpc_id": "4cbf8757-86d1-459a-a7db-0fac9c1f679f",
+ "service_type": "gateway",
+ "project_id": "0df25bbc878***f88c00c2959df9a",
+ "routetables": [
+ "6416b1df-bbe8-4e51-8fa3-4d169b8cc3aa"
+ ],
+ "created_at": "2024-08-13T06:56:41Z",
+ "updated_at": "2024-08-13T06:56:47Z",
+ "endpoint_service_id": "e4a21a61-f09e-41bc-b487-23d6204ae27b",
+ "endpoint_service_name": "test123",
+ "policy_statement": [
+ {
+ "Action": [
+ "*"
+ ],
+ "Resource": [
+ "*"
+ ],
+ "Effect": "Allow"
+ }
+ ],
+ "specification_name": "default",
+ "enable_status": "enable",
+ "description": "",
+ "endpoint_pool_id": "d86778c4-ad4b-4abd-988e-8c2572047fe4"
}
Status CodesSee Status Codes.
diff --git a/docs/vpcep/api-ref/vpcep_06_0306.html b/docs/vpcep/api-ref/vpcep_06_0306.html
index 7cc1199a..86a24163 100644
--- a/docs/vpcep/api-ref/vpcep_06_0306.html
+++ b/docs/vpcep/api-ref/vpcep_06_0306.html
@@ -27,11 +27,11 @@
Table 2 Query parametersParameter
|
-Mandatory
+ | Mandatory
|
Type
|
-Description
+ | Description
|
@@ -113,11 +113,11 @@
Response- Parameter description
-
Table 3 Response parametersParameter
+Table 3 Response parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -141,9 +141,9 @@
Table 4 endpoint parametersParameter
|
-Type
+ | Type
|
-Description
+ | Description
|
@@ -159,7 +159,7 @@
String
|
Specifies the type of the VPC endpoint service that is associated with the VPC endpoint.
-- Gateway: VPC endpoint services of this type are configured by operations people. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by operations people and private services created by yourselves. You cannot configure these cloud services, but can use them.
+- Gateway: VPC endpoint services of this type are configured by O&M personnel. You can use them directly without the need to create one by yourselves.
- Interface: VPC endpoint services of this type include cloud services configured by O&M personnel and private services created by yourselves. You cannot configure these cloud services, but can use them.
You can perform the operations in Creating a VPC Endpoint to create VPC endpoints for accessing VPC endpoints of the gateway and interface types.
|
@@ -175,8 +175,8 @@
Array of strings
|
-Specifies the domain status.
-- arrear_frozen: frozen due to arrears
- verify_frozen: frozen due to lack of real-name authentication
- police_frozen: frozen for legal management
- illegal_frozen: frozen due to abuse
- partner_frozen: frozen for partnership
- active: The domain is normal.
+ | Specifies the account status.
+- arrear_frozen: frozen due to arrears
- verify_frozen: frozen due to lack of real-name authentication
- police_frozen: frozen for legal management
- illegal_frozen: frozen due to abuse
- partner_frozen: frozen for partnership
- active: The account is normal.
|
endpoint_service_name
@@ -280,7 +280,7 @@
| Array of objects
|
Specifies the error message.
-This field is returned when the status of the VPC endpoint changes to failed. For details, see Table 6.
+This field is returned when the status of the VPC endpoint changes to failed. For details, see Table 7.
|
whitelist
@@ -298,7 +298,7 @@
| Boolean
|
Specifies whether access control is enabled.
-- true: Access control is enabled.
- false: Access control is disabled.
+- true: Access control is enabled.
- false: Access control is disabled.
If you do not specify this parameter, the whitelist is not enabled.
NOTE: This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.
@@ -310,10 +310,29 @@
|
Lists the IDs of route tables.
If you do not specify this parameter, the route table ID of the VPC is returned.
- NOTE: This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
+ NOTE: This parameter is available only when you create a VPC endpoint for connecting to a gateway VPC endpoint service.
|
+policy_statement
+ |
+Array of PolicyStatement objects
+ |
+Specifies the policy of the gateway VPC endpoint.
+This parameter is available only when you create a gateway VPC endpoint.
+Default value:
+{
+ "Action": [
+ "obs:*:*"
+ ],
+ "Resource": [
+ "obs:*:*:*:*/*",
+ "obs:*:*:*:*"
+ ],
+ "Effect": "Allow"
+}
+ |
+
description
|
String
@@ -374,26 +393,67 @@
|
- Table 6 Error parametersParameter
+Table 6 PolicyStatementParameter
|
-Type
+ | Mandatory
|
-Description
+ | Type
+ |
+Description
|
-error_code
+ | Effect
|
-String
+ | Yes
|
-Specifies the error code.
+ | String
+ |
+Specifies the policy effect, which can be Allow or Deny.
|
-error_message
+ | Action
|
-String
+ | Yes
|
-Specifies the error message.
+ | Array of strings
+ |
+Specifies OBS access permissions.
+ |
+
+Resource
+ |
+Yes
+ |
+Array of strings
+ |
+Specifies the OBS object.
+ |
+
+
+
+
+
+Table 7 Error parametersParameter
+ |
+Type
+ |
+Description
+ |
+
+
+error_code
+ |
+String
+ |
+Specifies the error code.
+ |
+
+error_message
+ |
+String
+ |
+Specifies the error message.
|
@@ -401,75 +461,75 @@
-- Example response
{
-"endpoints":
- [
- {
- "id":"03184a04-95d5-4555-86c4-e767a371ff99",
- "status":"accepted",
- "ip":"192.168.0.232",
- "marker_id":16777337,
- "active_status":[
- "active"
- ],
- "vpc_id":"84758cf5-9c62-43ae-a778-3dbd8370c0a4",
- "service_type":"interface",
- "project_id":"295dacf46a4842fcbf7844dc2dc2489d",
- "subnet_id":"68bfbcc1-dff2-47e4-a9d4-332b9bc1b8de",
- "enable_dns":"true",
- "specification_name":"default",
- "endpoint_pool_id":"501f4a3b-6f96-4309-97d1-e291b8ca5b96",
- "dns_name":"test123",
- "created_at":"2018-10-18T06:49:46Z",
- "updated_at":"2018-10-18T06:49:50Z",
- "endpoint_service_id":"5133655d-0e28-4090-b669-13f87b355c78",
- "endpoint_service_name":"test123",
- "whitelist":["127.0.0.1"],
- "enable_whitelist":true,
- "description" : "",
- "tags":
- [
- {
- "key":"test1",
- "value":"test1"
- }
- ]
- },
- {
- "id":"43b0e3b0-eec9-49da-866b-6687b75f9fe5",
- "status":"accepted",
- "ip":"192.168.0.115",
- "marker_id":16777322,
- "active_status":[
- "active"
- ],
- "vpc_id":"e251b400-2963-4131-b38a-da81e32026ee",
- "service_type":"interface",
- "project_id":"295dacf46a4842fcbf7844dc2dc2489d",
- "subnet_id":"65528a22-59a1-4972-ba64-88984b3207cd",
- "enable_dns":"true",
- "specification_name":"default",
- "endpoint_pool_id":"ee38223b-aacb-46f0-ba7e-94fa62e35dde",
- "dns_name":"test123",
- "created_at":"2018-10-18T06:36:20Z",
- "updated_at":"2018-10-18T06:36:24Z",
- "endpoint_service_id":"5133655d-0e28-4090-b669-13f87b355c78",
- "endpoint_service_name":"test123",
- "whitelist":["127.0.0.1"],
- "enable_whitelist":true,
- "description" : "",
- "tags":
- [
- {
- "key":"test1",
- "value":"test1"
- }
- ]
- }
+ - Example response
{
+ "endpoints": [
+{
+ "id": "59a40a87-abe0-4c1f-8bf0-63700128cb39",
+ "status": "accepted",
+ "tags": [],
+ "marker_id": 201421455,
+ "active_status": [
+ "active"
],
- "total_count":2
+ "vpc_id": "4cbf8757-86d1-459a-a7db-0fac9c1f679f",
+ "service_type": "gateway",
+ "project_id": "0df25bbc878***f88c00c2959df9a",
+ "routetables": [
+ "6416b1df-bbe8-4e51-8fa3-4d169b8cc3aa"
+ ],
+ "created_at": "2024-08-13T06:56:41Z",
+ "updated_at": "2024-08-13T06:56:47Z",
+ "endpoint_service_id": "e4a21a61-f09e-41bc-b487-23d6204ae27b",
+ "endpoint_service_name": "test123",
+ "policy_statement": [
+ {
+ "Action": [
+ "*"
+ ],
+ "Resource": [
+ "*"
+ ],
+ "Effect": "Allow"
+ }
+ ],
+ "specification_name": "default",
+ "enable_status": "enable",
+ "description": "",
+ "endpoint_pool_id": "d86778c4-ad4b-4abd-988e-8c2572047fe4"
+},
+{
+ "id": "530d6f2f-d115-4df2-8c36-32d19f3c0bbc",
+ "status": "accepted",
+ "ip": "192.168.14.23",
+ "tags": [
+ {
+ "key": "test2",
+ "value": "test2"
+ }
+ ],
+ "whitelist": [],
+ "marker_id": 201515772,
+ "active_status": [
+ "active"
+ ],
+ "vpc_id": "d7b2bf07-1b4c-43fa-bd88-d80c6ebea140",
+ "service_type": "interface",
+ "project_id": "0df25bbc878***2f88c00c2959df9a",
+ "subnet_id": "61881173-3899-4981-a700-170253d469b6",
+ "enable_dns": false,
+ "created_at": "2024-08-23T07:37:37Z",
+ "updated_at": "2024-08-23T07:37:39Z",
+ "endpoint_service_id": "2da0fe8f-5cb7-4d93-bb35-dc05334da1be",
+ "endpoint_service_name": "test456",
+ "enable_whitelist": false,
+ "specification_name": "default",
+ "enable_status": "enable",
+ "description": "",
+ "endpoint_pool_id": "0e796c11-6cf1-484a-9b8c-f837cb925287"
+}
+],
+ "total_count": 2
}
-
diff --git a/docs/vpcep/api-ref/vpcep_06_0500.html b/docs/vpcep/api-ref/vpcep_06_0500.html
index c78b1651..ffa2013c 100644
--- a/docs/vpcep/api-ref/vpcep_06_0500.html
+++ b/docs/vpcep/api-ref/vpcep_06_0500.html
@@ -1,6 +1,6 @@
-Tag Function
+Tags
diff --git a/docs/vpcep/api-ref/vpcep_06_0501.html b/docs/vpcep/api-ref/vpcep_06_0501.html
index 88302c47..f2d4cb2a 100644
--- a/docs/vpcep/api-ref/vpcep_06_0501.html
+++ b/docs/vpcep/api-ref/vpcep_06_0501.html
@@ -414,7 +414,7 @@
diff --git a/docs/vpcep/api-ref/vpcep_06_0502.html b/docs/vpcep/api-ref/vpcep_06_0502.html
index fa010506..82054472 100644
--- a/docs/vpcep/api-ref/vpcep_06_0502.html
+++ b/docs/vpcep/api-ref/vpcep_06_0502.html
@@ -153,7 +153,7 @@
diff --git a/docs/vpcep/api-ref/vpcep_06_0503.html b/docs/vpcep/api-ref/vpcep_06_0503.html
index 2743b481..14a1276d 100644
--- a/docs/vpcep/api-ref/vpcep_06_0503.html
+++ b/docs/vpcep/api-ref/vpcep_06_0503.html
@@ -117,7 +117,7 @@
diff --git a/docs/vpcep/api-ref/vpcep_06_0504.html b/docs/vpcep/api-ref/vpcep_06_0504.html
index 67000dbd..30f2a267 100644
--- a/docs/vpcep/api-ref/vpcep_06_0504.html
+++ b/docs/vpcep/api-ref/vpcep_06_0504.html
@@ -8,7 +8,7 @@
diff --git a/docs/vpcep/api-ref/vpcep_08_0002.html b/docs/vpcep/api-ref/vpcep_08_0002.html
index be36545b..b0886961 100644
--- a/docs/vpcep/api-ref/vpcep_08_0002.html
+++ b/docs/vpcep/api-ref/vpcep_08_0002.html
@@ -12,7 +12,6 @@
"error_msg": "Parameter error."
}
-
Descriptions of Error Codes An error code returned by an API does not correspond to an error message.
diff --git a/docs/vpcep/api-ref/vpcep_08_0003.html b/docs/vpcep/api-ref/vpcep_08_0003.html
index 5536a459..2db31c96 100644
--- a/docs/vpcep/api-ref/vpcep_08_0003.html
+++ b/docs/vpcep/api-ref/vpcep_08_0003.html
@@ -1,11 +1,11 @@
Obtaining a Project ID
- ScenariosA project ID is required for some URLs when an API is called. Therefore, you need to obtain a project ID in advance. Two methods are available:
+ ScenariosA project ID is required for some URLs when an API is called. Therefore, you need to obtain a project ID in advance. Two methods are available:
Obtain the Project ID by Calling an APIYou can obtain the project ID by calling the IAM API used to query project information based on the specified criteria.
- The API used to obtain a project ID is GET https://{Endpoint}/v3/projects. {Endpoint} is the IAM endpoint and can be obtained from Regions and Endpoints.
+ The API used to obtain a project ID is GET https://{Endpoint}/v3/projects. {Endpoint} is the IAM endpoint and can be obtained from Regions and Endpoints.
The following is an example response. The value of id is the project ID.
{
"projects": [
@@ -32,7 +32,7 @@
}
Obtain a Project ID from the ConsoleA project ID needs to be specified in the URIs of some APIs. Therefore, you need to obtain the project ID before calling APIs. The following procedure describes how to obtain a project ID: - Log in to the management console.
- Click the username and select My Credentials from the drop-down list.
On the My Credentials page, view project IDs in the project list.
-Figure 1 Viewing project IDs
+Figure 1 Viewing project IDs
In multi-project scenarios, expand the region, and obtain your sub-project ID from the Project ID column.
|
---|
|
---|
|
---|
|
---|
|
---|
|
---|
|
| |
---|
|
---|
---|
---|
---|
|
---|
---|
|
---|