diff --git a/docs/vpcep/umn/ALL_META.TXT.json b/docs/vpcep/umn/ALL_META.TXT.json new file mode 100644 index 000000000..7ab1fabc8 --- /dev/null +++ b/docs/vpcep/umn/ALL_META.TXT.json @@ -0,0 +1,532 @@ +[ + { + "uri":"en-us_topic_0131645193.html", + "product_code":"vpcep", + "code":"1", + "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":"usermanual", + "kw":"Service Overview", + "title":"Service Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0131645194.html", + "product_code":"vpcep", + "code":"2", + "des":"VPC Endpoint (VPCEP) is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services, including cloud services or your private ", + "doc_type":"usermanual", + "kw":"What Is VPC Endpoint?,Service Overview,User Guide", + "title":"What Is VPC Endpoint?", + "githuburl":"" + }, + { + "uri":"vpcep_01_0002.html", + "product_code":"vpcep", + "code":"3", + "des":"Excellent Performance: Each gateway supports up to 1 million concurrent connections in a variety of application scenarios.Immediately Ready for Use Upon Creation: VPC end", + "doc_type":"usermanual", + "kw":"Product Advantages,Service Overview,User Guide", + "title":"Product Advantages", + "githuburl":"" + }, + { + "uri":"en-us_topic_0131645196.html", + "product_code":"vpcep", + "code":"4", + "des":"VPCEP establishes a secure and private channel between a VPC endpoint (cloud resources in a VPC) and a VPC endpoint service in the same region.You can use VPCEP in differ", + "doc_type":"usermanual", + "kw":"Application Scenarios,Service Overview,User Guide", + "title":"Application Scenarios", + "githuburl":"" + }, + { + "uri":"vpcep_01_0005.html", + "product_code":"vpcep", + "code":"5", + "des":"Table 1 describes constraints on the VPCEP resource quota.When you create a VPC endpoint, ensure that the associated VPC endpoint service has been created and is in the s", + "doc_type":"usermanual", + "kw":"Constraints,Service Overview,User Guide", + "title":"Constraints", + "githuburl":"" + }, + { + "uri":"vpcep_01_0007.html", + "product_code":"vpcep", + "code":"6", + "des":"Table 1 shows the relationship between VPCEP and other cloud services.", + "doc_type":"usermanual", + "kw":"VPCEP and Other Services,Service Overview,User Guide", + "title":"VPCEP and Other Services", + "githuburl":"" + }, + { + "uri":"vpcep_01_0009.html", + "product_code":"vpcep", + "code":"7", + "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":"usermanual", + "kw":"Product Concepts", + "title":"Product Concepts", + "githuburl":"" + }, + { + "uri":"vpcep_01_0013.html", + "product_code":"vpcep", + "code":"8", + "des":"A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.There are two types of VPC endpoint services: gateway and inter", + "doc_type":"usermanual", + "kw":"VPC Endpoint Services,Product Concepts,User Guide", + "title":"VPC Endpoint Services", + "githuburl":"" + }, + { + "uri":"vpcep_01_0006.html", + "product_code":"vpcep", + "code":"9", + "des":"VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoi", + "doc_type":"usermanual", + "kw":"VPC Endpoints,Product Concepts,User Guide", + "title":"VPC Endpoints", + "githuburl":"" + }, + { + "uri":"vpcep_01_0010.html", + "product_code":"vpcep", + "code":"10", + "des":"The cloud system provides two types of user permissions by default, user management and resource management.User management refers to management of users, user groups, an", + "doc_type":"usermanual", + "kw":"User Permissions,Product Concepts,User Guide", + "title":"User Permissions", + "githuburl":"" + }, + { + "uri":"vpcep_01_0011.html", + "product_code":"vpcep", + "code":"11", + "des":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "doc_type":"usermanual", + "kw":"Region and AZ,Product Concepts,User Guide", + "title":"Region and AZ", + "githuburl":"" + }, + { + "uri":"vpcep_02_0000.html", + "product_code":"vpcep", + "code":"12", + "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":"usermanual", + "kw":"Getting Started", + "title":"Getting Started", + "githuburl":"" + }, + { + "uri":"vpcep_qs_0001.html", + "product_code":"vpcep", + "code":"13", + "des":"This section uses examples to describe how to use VPCEP.You can use VPCEP on the VPCEP console. For more information, see What Is VPC Endpoint?VPCEP is a perfect fit in d", + "doc_type":"usermanual", + "kw":"Operation Guide,Getting Started,User Guide", + "title":"Operation Guide", + "githuburl":"" + }, + { + "uri":"vpcep_02_0200.html", + "product_code":"vpcep", + "code":"14", + "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":"usermanual", + "kw":"Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain", + "title":"Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain", + "githuburl":"" + }, + { + "uri":"vpcep_02_02021.html", + "product_code":"vpcep", + "code":"15", + "des":"With VPCEP, you can access resources across VPCs in the same region.Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP", + "doc_type":"usermanual", + "kw":"Overview,Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"vpcep_02_02022.html", + "product_code":"vpcep", + "code":"16", + "des":"To enable communications across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.This section uses an elasti", + "doc_type":"usermanual", + "kw":"Step 1: Create a VPC Endpoint Service,Configuring a VPC Endpoint for Communications Across VPCs of t", + "title":"Step 1: Create a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_02_02023.html", + "product_code":"vpcep", + "code":"17", + "des":"After you create a VPC endpoint service, you also need to create a VPC endpoint to access the VPC endpoint service.This section describes how to create a VPC endpoint in ", + "doc_type":"usermanual", + "kw":"Step 2: Create a VPC Endpoint,Configuring a VPC Endpoint for Communications Across VPCs of the Same ", + "title":"Step 2: Create a VPC Endpoint", + "githuburl":"" + }, + { + "uri":"vpcep_02_0203.html", + "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":"usermanual", + "kw":"Configuring a VPC Endpoint for Communications Across VPCs of Different Domains", + "title":"Configuring a VPC Endpoint for Communications Across VPCs of Different Domains", + "githuburl":"" + }, + { + "uri":"vpcep_02_02031.html", + "product_code":"vpcep", + "code":"19", + "des":"With VPCEP, you can access resources across VPCs in the same region.Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP", + "doc_type":"usermanual", + "kw":"Overview,Configuring a VPC Endpoint for Communications Across VPCs of Different Domains,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"vpcep_02_02032.html", + "product_code":"vpcep", + "code":"20", + "des":"To enable communications across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.This section describes how ", + "doc_type":"usermanual", + "kw":"Step 1: Create a VPC Endpoint Service,Configuring a VPC Endpoint for Communications Across VPCs of D", + "title":"Step 1: Create a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_02_02034.html", + "product_code":"vpcep", + "code":"21", + "des":"Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.After a VPC endpoint service is created, you can add an aut", + "doc_type":"usermanual", + "kw":"Step 2: Add a Whitelist Record,Configuring a VPC Endpoint for Communications Across VPCs of Differen", + "title":"Step 2: Add a Whitelist Record", + "githuburl":"" + }, + { + "uri":"vpcep_02_02035.html", + "product_code":"vpcep", + "code":"22", + "des":"After you add the required whitelist record, you can create a VPC endpoint in VPC 1 to connect to the target VPC endpoint service.Select the same region and project as th", + "doc_type":"usermanual", + "kw":"Step 3: Create a VPC Endpoint,Configuring a VPC Endpoint for Communications Across VPCs of Different", + "title":"Step 3: Create a VPC Endpoint", + "githuburl":"" + }, + { + "uri":"vpcep_02_0300.html", + "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":"usermanual", + "kw":"Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address", + "title":"Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address", + "githuburl":"" + }, + { + "uri":"vpcep_02_0301.html", + "product_code":"vpcep", + "code":"24", + "des":"If you want to access a cloud service like OBS from an IDC, you can connect the IDC to your VPC using a VPN connection or a direct connection and then connect your VPC to", + "doc_type":"usermanual", + "kw":"Overview,Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"vpcep_02_0302.html", + "product_code":"vpcep", + "code":"25", + "des":"This section describes how to create a VPC endpoint for accessing a DNS server, in order to forward requests of resolving OBS domain names.The required VPC endpoint servi", + "doc_type":"usermanual", + "kw":"Step 1: Create a VPC Endpoint for Connecting to DNS,Configuring a VPC Endpoint for Accessing OBS Usi", + "title":"Step 1: Create a VPC Endpoint for Connecting to DNS", + "githuburl":"" + }, + { + "uri":"vpcep_02_0303.html", + "product_code":"vpcep", + "code":"26", + "des":"This section describes how to create a VPC endpoint to access OBS from an IDC.The required VPC endpoint service already exists.Log in to the management console.Click in ", + "doc_type":"usermanual", + "kw":"Step 2: Create a VPC Endpoint for Connecting to OBS,Configuring a VPC Endpoint for Accessing OBS Usi", + "title":"Step 2: Create a VPC Endpoint for Connecting to OBS", + "githuburl":"" + }, + { + "uri":"vpcep_02_0304.html", + "product_code":"vpcep", + "code":"27", + "des":"This section describes how to access OBS using a VPN connection or a direct connection.Your local data center has been connected to your VPC using a VPN or Direct Connect", + "doc_type":"usermanual", + "kw":"Step 3: Access OBS,Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address,User G", + "title":"Step 3: Access OBS", + "githuburl":"" + }, + { + "uri":"vpcep_02_0400.html", + "product_code":"vpcep", + "code":"28", + "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":"usermanual", + "kw":"Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address", + "title":"Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address", + "githuburl":"" + }, + { + "uri":"vpcep_02_0401.html", + "product_code":"vpcep", + "code":"29", + "des":"If you want to access OBS using its public address from an IDC, you can use a VPC endpoint to connect to the VPC endpoint service configured for OBS.This section describe", + "doc_type":"usermanual", + "kw":"Overview,Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address,User Guide", + "title":"Overview", + "githuburl":"" + }, + { + "uri":"vpcep_02_0402.html", + "product_code":"vpcep", + "code":"30", + "des":"This section describes how to create a VPC endpoint to access OBS from an IDC.The required VPC endpoint service already exists.Log in to the management console.Click in ", + "doc_type":"usermanual", + "kw":"Step 1: Create a VPC Endpoint for Connecting to OBS,Configuring a VPC Endpoint for Accessing OBS wit", + "title":"Step 1: Create a VPC Endpoint for Connecting to OBS", + "githuburl":"" + }, + { + "uri":"vpcep_02_0403.html", + "product_code":"vpcep", + "code":"31", + "des":"This section describes how to access OBS using a VPN connection or a direct connection.Your local data center has been connected to your VPC using a VPN or Direct Connect", + "doc_type":"usermanual", + "kw":"Step 2: Access OBS,Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address,User Gui", + "title":"Step 2: Access OBS", + "githuburl":"" + }, + { + "uri":"vpcep_03_0100.html", + "product_code":"vpcep", + "code":"32", + "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":"usermanual", + "kw":"VPC Endpoint Services", + "title":"VPC Endpoint Services", + "githuburl":"" + }, + { + "uri":"vpcep_03_0107.html", + "product_code":"vpcep", + "code":"33", + "des":"A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.There are two types of VPC endpoint services: gateway and inter", + "doc_type":"usermanual", + "kw":"VPC Endpoint Service Overview,VPC Endpoint Services,User Guide", + "title":"VPC Endpoint Service Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0131645182.html", + "product_code":"vpcep", + "code":"34", + "des":"There are two types of VPC endpoint services: gateway and interface.Gateway VPC endpoint services are created only for cloud services.Interface VPC endpoint services can ", + "doc_type":"usermanual", + "kw":"Creating a VPC Endpoint Service,VPC Endpoint Services,User Guide", + "title":"Creating a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_03_0102.html", + "product_code":"vpcep", + "code":"35", + "des":"This section describes how to query summary of a VPC endpoint service, including the name, ID, backend resource type, backend resource name, VPC, status, connection appro", + "doc_type":"usermanual", + "kw":"Viewing Summary of a VPC Endpoint Service,VPC Endpoint Services,User Guide", + "title":"Viewing Summary of a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_03_0103.html", + "product_code":"vpcep", + "code":"36", + "des":"This section describes how to delete a VPC endpoint service.Deleted VPC endpoint services cannot be recovered. Exercise caution when performing this operation.The VPC end", + "doc_type":"usermanual", + "kw":"Deleting a VPC Endpoint Service,VPC Endpoint Services,User Guide", + "title":"Deleting a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_03_0104.html", + "product_code":"vpcep", + "code":"37", + "des":"To connect a VPC endpoint to a VPC endpoint service that has connection approval enabled, obtain the approval from the owner of the endpoint service.This section describe", + "doc_type":"usermanual", + "kw":"Managing Connections of a VPC Endpoint Service,VPC Endpoint Services,User Guide", + "title":"Managing Connections of a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_03_0105.html", + "product_code":"vpcep", + "code":"38", + "des":"Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.After a VPC endpoint service is created, you can add an aut", + "doc_type":"usermanual", + "kw":"Managing Whitelist Records of a VPC Endpoint Service,VPC Endpoint Services,User Guide", + "title":"Managing Whitelist Records of a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_03_0106.html", + "product_code":"vpcep", + "code":"39", + "des":"After a VPC endpoint service is created, you can view the added port mappings.A port mapping defines the protocol and ports used for communications between a VPC endpoint", + "doc_type":"usermanual", + "kw":"Viewing Port Mappings of a VPC Endpoint Service,VPC Endpoint Services,User Guide", + "title":"Viewing Port Mappings of a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_03_0108.html", + "product_code":"vpcep", + "code":"40", + "des":"After a VPC endpoint service is created, you can view its tags, or add, edit, or delete a tag.A tag is a unique identifier of each VPC endpoint service, and it consists o", + "doc_type":"usermanual", + "kw":"Managing Tags of a VPC Endpoint Service,VPC Endpoint Services,User Guide", + "title":"Managing Tags of a VPC Endpoint Service", + "githuburl":"" + }, + { + "uri":"vpcep_03_0200.html", + "product_code":"vpcep", + "code":"41", + "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":"usermanual", + "kw":"VPC Endpoints", + "title":"VPC Endpoints", + "githuburl":"" + }, + { + "uri":"vpcep_03_0204.html", + "product_code":"vpcep", + "code":"42", + "des":"VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoi", + "doc_type":"usermanual", + "kw":"VPC Endpoint Overview,VPC Endpoints,User Guide", + "title":"VPC Endpoint Overview", + "githuburl":"" + }, + { + "uri":"en-us_topic_0131645189.html", + "product_code":"vpcep", + "code":"43", + "des":"VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoi", + "doc_type":"usermanual", + "kw":"Creating a VPC Endpoint,VPC Endpoints,User Guide", + "title":"Creating a VPC Endpoint", + "githuburl":"" + }, + { + "uri":"vpcep_03_0202.html", + "product_code":"vpcep", + "code":"44", + "des":"After a VPC endpoint is created, you can query its details and access it.Perform the following operations to query details about a VPC endpoint, including the ID, associa", + "doc_type":"usermanual", + "kw":"Querying and Accessing a VPC Endpoint,VPC Endpoints,User Guide", + "title":"Querying and Accessing a VPC Endpoint", + "githuburl":"" + }, + { + "uri":"vpcep_03_0203.html", + "product_code":"vpcep", + "code":"45", + "des":"This section describes how to delete a VPC endpoint.Deleted VPC endpoints cannot be recovered. Exercise caution when performing this operation.Log in to the management co", + "doc_type":"usermanual", + "kw":"Deleting a VPC Endpoint,VPC Endpoints,User Guide", + "title":"Deleting a VPC Endpoint", + "githuburl":"" + }, + { + "uri":"vpcep_03_0206.html", + "product_code":"vpcep", + "code":"46", + "des":"After a VPC endpoint is created, you can view its tags, or add, edit, or delete a tag.Each VPC endpoint has a unique tag, which consists of a tag key and a tag value. You", + "doc_type":"usermanual", + "kw":"Managing Tags of a VPC Endpoint,VPC Endpoints,User Guide", + "title":"Managing Tags of a VPC Endpoint", + "githuburl":"" + }, + { + "uri":"vpcep_04_0000.html", + "product_code":"vpcep", + "code":"47", + "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":"usermanual", + "kw":"FAQ", + "title":"FAQ", + "githuburl":"" + }, + { + "uri":"en-us_topic_0154804561.html", + "product_code":"vpcep", + "code":"48", + "des":"Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number and capacity of resources available ", + "doc_type":"usermanual", + "kw":"What Is a Quota?,FAQ,User Guide", + "title":"What Is a Quota?", + "githuburl":"" + }, + { + "uri":"en-us_topic_0138838187.html", + "product_code":"vpcep", + "code":"49", + "des":"Confirm that the security group of the ECS NIC is correctly configured.On the ECS details page, view the security group details.Check whether the security group permits I", + "doc_type":"usermanual", + "kw":"What Should I Do If the VPC Endpoint I Purchased Cannot Connect to a VPC Endpoint Service?,FAQ,User ", + "title":"What Should I Do If the VPC Endpoint I Purchased Cannot Connect to a VPC Endpoint Service?", + "githuburl":"" + }, + { + "uri":"vpcep_04_0004.html", + "product_code":"vpcep", + "code":"50", + "des":"Table 1 describes differences between VPC endpoints and VPC peering connections.VPC endpoints and VPC peering connections are two different resources. You can configure e", + "doc_type":"usermanual", + "kw":"What Are the Differences Between VPC Endpoints and VPC Peering Connections?,FAQ,User Guide", + "title":"What Are the Differences Between VPC Endpoints and VPC Peering Connections?", + "githuburl":"" + }, + { + "uri":"vpcep_04_0005.html", + "product_code":"vpcep", + "code":"51", + "des":"Table 1 describes statuses of a VPC endpoint service and their meanings.Statuses of a VPC endpoint serviceStatusDescriptionCreatingIndicates that the VPC endpoint service", + "doc_type":"usermanual", + "kw":"What Are Statuses of VPC Endpoint Services and VPC Endpoints?,FAQ,User Guide", + "title":"What Are Statuses of VPC Endpoint Services and VPC Endpoints?", + "githuburl":"" + }, + { + "uri":"vpcep_0_0002.html", + "product_code":"vpcep", + "code":"52", + "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":"usermanual", + "kw":"Change History,User Guide", + "title":"Change History", + "githuburl":"" + }, + { + "uri":"vpcep_0_0003.html", + "product_code":"vpcep", + "code":"53", + "des":"For details about the terms involved in this document, see Glossary.", + "doc_type":"usermanual", + "kw":"Glossary,User Guide", + "title":"Glossary", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/vpcep/umn/CLASS.TXT.json b/docs/vpcep/umn/CLASS.TXT.json new file mode 100644 index 000000000..56e7c23f8 --- /dev/null +++ b/docs/vpcep/umn/CLASS.TXT.json @@ -0,0 +1,479 @@ +[ + { + "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":"Service Overview", + "uri":"en-us_topic_0131645193.html", + "doc_type":"usermanual", + "p_code":"", + "code":"1" + }, + { + "desc":"VPC Endpoint (VPCEP) is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services, including cloud services or your private ", + "product_code":"vpcep", + "title":"What Is VPC Endpoint?", + "uri":"en-us_topic_0131645194.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"2" + }, + { + "desc":"Excellent Performance: Each gateway supports up to 1 million concurrent connections in a variety of application scenarios.Immediately Ready for Use Upon Creation: VPC end", + "product_code":"vpcep", + "title":"Product Advantages", + "uri":"vpcep_01_0002.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"3" + }, + { + "desc":"VPCEP establishes a secure and private channel between a VPC endpoint (cloud resources in a VPC) and a VPC endpoint service in the same region.You can use VPCEP in differ", + "product_code":"vpcep", + "title":"Application Scenarios", + "uri":"en-us_topic_0131645196.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"4" + }, + { + "desc":"Table 1 describes constraints on the VPCEP resource quota.When you create a VPC endpoint, ensure that the associated VPC endpoint service has been created and is in the s", + "product_code":"vpcep", + "title":"Constraints", + "uri":"vpcep_01_0005.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"5" + }, + { + "desc":"Table 1 shows the relationship between VPCEP and other cloud services.", + "product_code":"vpcep", + "title":"VPCEP and Other Services", + "uri":"vpcep_01_0007.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"6" + }, + { + "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":"Product Concepts", + "uri":"vpcep_01_0009.html", + "doc_type":"usermanual", + "p_code":"1", + "code":"7" + }, + { + "desc":"A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.There are two types of VPC endpoint services: gateway and inter", + "product_code":"vpcep", + "title":"VPC Endpoint Services", + "uri":"vpcep_01_0013.html", + "doc_type":"usermanual", + "p_code":"7", + "code":"8" + }, + { + "desc":"VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoi", + "product_code":"vpcep", + "title":"VPC Endpoints", + "uri":"vpcep_01_0006.html", + "doc_type":"usermanual", + "p_code":"7", + "code":"9" + }, + { + "desc":"The cloud system provides two types of user permissions by default, user management and resource management.User management refers to management of users, user groups, an", + "product_code":"vpcep", + "title":"User Permissions", + "uri":"vpcep_01_0010.html", + "doc_type":"usermanual", + "p_code":"7", + "code":"10" + }, + { + "desc":"A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.A region is a physical data center, which", + "product_code":"vpcep", + "title":"Region and AZ", + "uri":"vpcep_01_0011.html", + "doc_type":"usermanual", + "p_code":"7", + "code":"11" + }, + { + "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":"Getting Started", + "uri":"vpcep_02_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"12" + }, + { + "desc":"This section uses examples to describe how to use VPCEP.You can use VPCEP on the VPCEP console. For more information, see What Is VPC Endpoint?VPCEP is a perfect fit in d", + "product_code":"vpcep", + "title":"Operation Guide", + "uri":"vpcep_qs_0001.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"13" + }, + { + "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":"Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain", + "uri":"vpcep_02_0200.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"14" + }, + { + "desc":"With VPCEP, you can access resources across VPCs in the same region.Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP", + "product_code":"vpcep", + "title":"Overview", + "uri":"vpcep_02_02021.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"15" + }, + { + "desc":"To enable communications across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.This section uses an elasti", + "product_code":"vpcep", + "title":"Step 1: Create a VPC Endpoint Service", + "uri":"vpcep_02_02022.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"16" + }, + { + "desc":"After you create a VPC endpoint service, you also need to create a VPC endpoint to access the VPC endpoint service.This section describes how to create a VPC endpoint in ", + "product_code":"vpcep", + "title":"Step 2: Create a VPC Endpoint", + "uri":"vpcep_02_02023.html", + "doc_type":"usermanual", + "p_code":"14", + "code":"17" + }, + { + "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":"Configuring a VPC Endpoint for Communications Across VPCs of Different Domains", + "uri":"vpcep_02_0203.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"18" + }, + { + "desc":"With VPCEP, you can access resources across VPCs in the same region.Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP", + "product_code":"vpcep", + "title":"Overview", + "uri":"vpcep_02_02031.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"19" + }, + { + "desc":"To enable communications across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.This section describes how ", + "product_code":"vpcep", + "title":"Step 1: Create a VPC Endpoint Service", + "uri":"vpcep_02_02032.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"20" + }, + { + "desc":"Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.After a VPC endpoint service is created, you can add an aut", + "product_code":"vpcep", + "title":"Step 2: Add a Whitelist Record", + "uri":"vpcep_02_02034.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"21" + }, + { + "desc":"After you add the required whitelist record, you can create a VPC endpoint in VPC 1 to connect to the target VPC endpoint service.Select the same region and project as th", + "product_code":"vpcep", + "title":"Step 3: Create a VPC Endpoint", + "uri":"vpcep_02_02035.html", + "doc_type":"usermanual", + "p_code":"18", + "code":"22" + }, + { + "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":"Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address", + "uri":"vpcep_02_0300.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"23" + }, + { + "desc":"If you want to access a cloud service like OBS from an IDC, you can connect the IDC to your VPC using a VPN connection or a direct connection and then connect your VPC to", + "product_code":"vpcep", + "title":"Overview", + "uri":"vpcep_02_0301.html", + "doc_type":"usermanual", + "p_code":"23", + "code":"24" + }, + { + "desc":"This section describes how to create a VPC endpoint for accessing a DNS server, in order to forward requests of resolving OBS domain names.The required VPC endpoint servi", + "product_code":"vpcep", + "title":"Step 1: Create a VPC Endpoint for Connecting to DNS", + "uri":"vpcep_02_0302.html", + "doc_type":"usermanual", + "p_code":"23", + "code":"25" + }, + { + "desc":"This section describes how to create a VPC endpoint to access OBS from an IDC.The required VPC endpoint service already exists.Log in to the management console.Click in ", + "product_code":"vpcep", + "title":"Step 2: Create a VPC Endpoint for Connecting to OBS", + "uri":"vpcep_02_0303.html", + "doc_type":"usermanual", + "p_code":"23", + "code":"26" + }, + { + "desc":"This section describes how to access OBS using a VPN connection or a direct connection.Your local data center has been connected to your VPC using a VPN or Direct Connect", + "product_code":"vpcep", + "title":"Step 3: Access OBS", + "uri":"vpcep_02_0304.html", + "doc_type":"usermanual", + "p_code":"23", + "code":"27" + }, + { + "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":"Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address", + "uri":"vpcep_02_0400.html", + "doc_type":"usermanual", + "p_code":"12", + "code":"28" + }, + { + "desc":"If you want to access OBS using its public address from an IDC, you can use a VPC endpoint to connect to the VPC endpoint service configured for OBS.This section describe", + "product_code":"vpcep", + "title":"Overview", + "uri":"vpcep_02_0401.html", + "doc_type":"usermanual", + "p_code":"28", + "code":"29" + }, + { + "desc":"This section describes how to create a VPC endpoint to access OBS from an IDC.The required VPC endpoint service already exists.Log in to the management console.Click in ", + "product_code":"vpcep", + "title":"Step 1: Create a VPC Endpoint for Connecting to OBS", + "uri":"vpcep_02_0402.html", + "doc_type":"usermanual", + "p_code":"28", + "code":"30" + }, + { + "desc":"This section describes how to access OBS using a VPN connection or a direct connection.Your local data center has been connected to your VPC using a VPN or Direct Connect", + "product_code":"vpcep", + "title":"Step 2: Access OBS", + "uri":"vpcep_02_0403.html", + "doc_type":"usermanual", + "p_code":"28", + "code":"31" + }, + { + "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":"VPC Endpoint Services", + "uri":"vpcep_03_0100.html", + "doc_type":"usermanual", + "p_code":"", + "code":"32" + }, + { + "desc":"A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.There are two types of VPC endpoint services: gateway and inter", + "product_code":"vpcep", + "title":"VPC Endpoint Service Overview", + "uri":"vpcep_03_0107.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"33" + }, + { + "desc":"There are two types of VPC endpoint services: gateway and interface.Gateway VPC endpoint services are created only for cloud services.Interface VPC endpoint services can ", + "product_code":"vpcep", + "title":"Creating a VPC Endpoint Service", + "uri":"en-us_topic_0131645182.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"34" + }, + { + "desc":"This section describes how to query summary of a VPC endpoint service, including the name, ID, backend resource type, backend resource name, VPC, status, connection appro", + "product_code":"vpcep", + "title":"Viewing Summary of a VPC Endpoint Service", + "uri":"vpcep_03_0102.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"35" + }, + { + "desc":"This section describes how to delete a VPC endpoint service.Deleted VPC endpoint services cannot be recovered. Exercise caution when performing this operation.The VPC end", + "product_code":"vpcep", + "title":"Deleting a VPC Endpoint Service", + "uri":"vpcep_03_0103.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"36" + }, + { + "desc":"To connect a VPC endpoint to a VPC endpoint service that has connection approval enabled, obtain the approval from the owner of the endpoint service.This section describe", + "product_code":"vpcep", + "title":"Managing Connections of a VPC Endpoint Service", + "uri":"vpcep_03_0104.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"37" + }, + { + "desc":"Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.After a VPC endpoint service is created, you can add an aut", + "product_code":"vpcep", + "title":"Managing Whitelist Records of a VPC Endpoint Service", + "uri":"vpcep_03_0105.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"38" + }, + { + "desc":"After a VPC endpoint service is created, you can view the added port mappings.A port mapping defines the protocol and ports used for communications between a VPC endpoint", + "product_code":"vpcep", + "title":"Viewing Port Mappings of a VPC Endpoint Service", + "uri":"vpcep_03_0106.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"39" + }, + { + "desc":"After a VPC endpoint service is created, you can view its tags, or add, edit, or delete a tag.A tag is a unique identifier of each VPC endpoint service, and it consists o", + "product_code":"vpcep", + "title":"Managing Tags of a VPC Endpoint Service", + "uri":"vpcep_03_0108.html", + "doc_type":"usermanual", + "p_code":"32", + "code":"40" + }, + { + "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":"VPC Endpoints", + "uri":"vpcep_03_0200.html", + "doc_type":"usermanual", + "p_code":"", + "code":"41" + }, + { + "desc":"VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoi", + "product_code":"vpcep", + "title":"VPC Endpoint Overview", + "uri":"vpcep_03_0204.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"42" + }, + { + "desc":"VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoi", + "product_code":"vpcep", + "title":"Creating a VPC Endpoint", + "uri":"en-us_topic_0131645189.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"43" + }, + { + "desc":"After a VPC endpoint is created, you can query its details and access it.Perform the following operations to query details about a VPC endpoint, including the ID, associa", + "product_code":"vpcep", + "title":"Querying and Accessing a VPC Endpoint", + "uri":"vpcep_03_0202.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"44" + }, + { + "desc":"This section describes how to delete a VPC endpoint.Deleted VPC endpoints cannot be recovered. Exercise caution when performing this operation.Log in to the management co", + "product_code":"vpcep", + "title":"Deleting a VPC Endpoint", + "uri":"vpcep_03_0203.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"45" + }, + { + "desc":"After a VPC endpoint is created, you can view its tags, or add, edit, or delete a tag.Each VPC endpoint has a unique tag, which consists of a tag key and a tag value. You", + "product_code":"vpcep", + "title":"Managing Tags of a VPC Endpoint", + "uri":"vpcep_03_0206.html", + "doc_type":"usermanual", + "p_code":"41", + "code":"46" + }, + { + "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":"FAQ", + "uri":"vpcep_04_0000.html", + "doc_type":"usermanual", + "p_code":"", + "code":"47" + }, + { + "desc":"Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number and capacity of resources available ", + "product_code":"vpcep", + "title":"What Is a Quota?", + "uri":"en-us_topic_0154804561.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"48" + }, + { + "desc":"Confirm that the security group of the ECS NIC is correctly configured.On the ECS details page, view the security group details.Check whether the security group permits I", + "product_code":"vpcep", + "title":"What Should I Do If the VPC Endpoint I Purchased Cannot Connect to a VPC Endpoint Service?", + "uri":"en-us_topic_0138838187.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"49" + }, + { + "desc":"Table 1 describes differences between VPC endpoints and VPC peering connections.VPC endpoints and VPC peering connections are two different resources. You can configure e", + "product_code":"vpcep", + "title":"What Are the Differences Between VPC Endpoints and VPC Peering Connections?", + "uri":"vpcep_04_0004.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"50" + }, + { + "desc":"Table 1 describes statuses of a VPC endpoint service and their meanings.Statuses of a VPC endpoint serviceStatusDescriptionCreatingIndicates that the VPC endpoint service", + "product_code":"vpcep", + "title":"What Are Statuses of VPC Endpoint Services and VPC Endpoints?", + "uri":"vpcep_04_0005.html", + "doc_type":"usermanual", + "p_code":"47", + "code":"51" + }, + { + "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":"Change History", + "uri":"vpcep_0_0002.html", + "doc_type":"usermanual", + "p_code":"", + "code":"52" + }, + { + "desc":"For details about the terms involved in this document, see Glossary.", + "product_code":"vpcep", + "title":"Glossary", + "uri":"vpcep_0_0003.html", + "doc_type":"usermanual", + "p_code":"", + "code":"53" + } +] \ No newline at end of file diff --git a/docs/vpcep/umn/PARAMETERS.txt b/docs/vpcep/umn/PARAMETERS.txt new file mode 100644 index 000000000..6da8d5f07 --- /dev/null +++ b/docs/vpcep/umn/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/vpcep/umn/en-us_image_0000001072032207.png b/docs/vpcep/umn/en-us_image_0000001072032207.png new file mode 100644 index 000000000..4efaa1c1f Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001072032207.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001085936276.png b/docs/vpcep/umn/en-us_image_0000001085936276.png new file mode 100644 index 000000000..d954e44b7 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001085936276.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124210529.png b/docs/vpcep/umn/en-us_image_0000001124210529.png new file mode 100644 index 000000000..ce5493b18 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124210529.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124216445.png b/docs/vpcep/umn/en-us_image_0000001124216445.png new file mode 100644 index 000000000..ce5493b18 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124216445.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124226291.png b/docs/vpcep/umn/en-us_image_0000001124226291.png new file mode 100644 index 000000000..5050d8780 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124226291.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124311365.png b/docs/vpcep/umn/en-us_image_0000001124311365.png new file mode 100644 index 000000000..f520e39e4 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124311365.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124314193.png b/docs/vpcep/umn/en-us_image_0000001124314193.png new file mode 100644 index 000000000..cc7816e44 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124314193.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124315049.png b/docs/vpcep/umn/en-us_image_0000001124315049.png new file mode 100644 index 000000000..aea1e9778 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124315049.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124317045.png b/docs/vpcep/umn/en-us_image_0000001124317045.png new file mode 100644 index 000000000..ed80d7371 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124317045.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124393987.png b/docs/vpcep/umn/en-us_image_0000001124393987.png new file mode 100644 index 000000000..07b16f0b2 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124393987.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124397561.png b/docs/vpcep/umn/en-us_image_0000001124397561.png new file mode 100644 index 000000000..78df03a6e Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124397561.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124399267.png b/docs/vpcep/umn/en-us_image_0000001124399267.png new file mode 100644 index 000000000..d949b2e8a Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124399267.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124400069.png b/docs/vpcep/umn/en-us_image_0000001124400069.png new file mode 100644 index 000000000..07b16f0b2 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124400069.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124400993.png b/docs/vpcep/umn/en-us_image_0000001124400993.png new file mode 100644 index 000000000..3a028740f Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124400993.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124517799.png b/docs/vpcep/umn/en-us_image_0000001124517799.png new file mode 100644 index 000000000..659c5f998 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124517799.png differ diff --git a/docs/vpcep/umn/en-us_image_0000001124529567.png b/docs/vpcep/umn/en-us_image_0000001124529567.png new file mode 100644 index 000000000..5edff8d0e Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0000001124529567.png differ diff --git a/docs/vpcep/umn/en-us_image_0152727234.png b/docs/vpcep/umn/en-us_image_0152727234.png new file mode 100644 index 000000000..35e283157 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0152727234.png differ diff --git a/docs/vpcep/umn/en-us_image_0184026531.png b/docs/vpcep/umn/en-us_image_0184026531.png new file mode 100644 index 000000000..1303a51c2 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0184026531.png differ diff --git a/docs/vpcep/umn/en-us_image_0270653585.png b/docs/vpcep/umn/en-us_image_0270653585.png new file mode 100644 index 000000000..aa64792a3 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0270653585.png differ diff --git a/docs/vpcep/umn/en-us_image_0270653586.png b/docs/vpcep/umn/en-us_image_0270653586.png new file mode 100644 index 000000000..39779e941 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0270653586.png differ diff --git a/docs/vpcep/umn/en-us_image_0275513364.png b/docs/vpcep/umn/en-us_image_0275513364.png new file mode 100644 index 000000000..1909444d2 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0275513364.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945751.jpg b/docs/vpcep/umn/en-us_image_0289945751.jpg new file mode 100644 index 000000000..5c4c87931 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945751.jpg differ diff --git a/docs/vpcep/umn/en-us_image_0289945758.png b/docs/vpcep/umn/en-us_image_0289945758.png new file mode 100644 index 000000000..9519c6d78 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945758.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945778.png b/docs/vpcep/umn/en-us_image_0289945778.png new file mode 100644 index 000000000..fe39ed763 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945778.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945784.png b/docs/vpcep/umn/en-us_image_0289945784.png new file mode 100644 index 000000000..412d69a02 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945784.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945818.png b/docs/vpcep/umn/en-us_image_0289945818.png new file mode 100644 index 000000000..cbabe3a27 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945818.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945827.png b/docs/vpcep/umn/en-us_image_0289945827.png new file mode 100644 index 000000000..fe39ed763 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945827.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945877.png b/docs/vpcep/umn/en-us_image_0289945877.png new file mode 100644 index 000000000..f1403c1d1 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945877.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945896.png b/docs/vpcep/umn/en-us_image_0289945896.png new file mode 100644 index 000000000..50880420a Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945896.png differ diff --git a/docs/vpcep/umn/en-us_image_0289945902.jpg b/docs/vpcep/umn/en-us_image_0289945902.jpg new file mode 100644 index 000000000..b8048c33b Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945902.jpg differ diff --git a/docs/vpcep/umn/en-us_image_0289945946.png b/docs/vpcep/umn/en-us_image_0289945946.png new file mode 100644 index 000000000..14b914a4a Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0289945946.png differ diff --git a/docs/vpcep/umn/en-us_image_0298368446.png b/docs/vpcep/umn/en-us_image_0298368446.png new file mode 100644 index 000000000..62e922170 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298368446.png differ diff --git a/docs/vpcep/umn/en-us_image_0298376151.png b/docs/vpcep/umn/en-us_image_0298376151.png new file mode 100644 index 000000000..0782bfbdc Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298376151.png differ diff --git a/docs/vpcep/umn/en-us_image_0298539810.png b/docs/vpcep/umn/en-us_image_0298539810.png new file mode 100644 index 000000000..73f052cc6 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298539810.png differ diff --git a/docs/vpcep/umn/en-us_image_0298556321.png b/docs/vpcep/umn/en-us_image_0298556321.png new file mode 100644 index 000000000..dbf206290 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298556321.png differ diff --git a/docs/vpcep/umn/en-us_image_0298561817.png b/docs/vpcep/umn/en-us_image_0298561817.png new file mode 100644 index 000000000..9a42bb331 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298561817.png differ diff --git a/docs/vpcep/umn/en-us_image_0298570037.png b/docs/vpcep/umn/en-us_image_0298570037.png new file mode 100644 index 000000000..f866641ad Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298570037.png differ diff --git a/docs/vpcep/umn/en-us_image_0298571864.png b/docs/vpcep/umn/en-us_image_0298571864.png new file mode 100644 index 000000000..fed39c0a9 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298571864.png differ diff --git a/docs/vpcep/umn/en-us_image_0298583614.png b/docs/vpcep/umn/en-us_image_0298583614.png new file mode 100644 index 000000000..1eca888d3 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298583614.png differ diff --git a/docs/vpcep/umn/en-us_image_0298978917.png b/docs/vpcep/umn/en-us_image_0298978917.png new file mode 100644 index 000000000..e26e12831 Binary files /dev/null and b/docs/vpcep/umn/en-us_image_0298978917.png differ diff --git a/docs/vpcep/umn/en-us_topic_0131645182.html b/docs/vpcep/umn/en-us_topic_0131645182.html new file mode 100644 index 000000000..592047d40 --- /dev/null +++ b/docs/vpcep/umn/en-us_topic_0131645182.html @@ -0,0 +1,132 @@ + + +

Creating a VPC Endpoint Service

+

Scenarios

There are two types of VPC endpoint services: gateway and interface.
  • Gateway VPC endpoint services are created only for cloud services.
  • Interface VPC endpoint services can be created for both cloud services and your private services. All VPC endpoint services for cloud services are created by default while those for private services need to be created by users themselves.
+
+

This section describes how to configure a private service into an interface VPC endpoint service.

+
+

Constraints

+
+

Prerequisites

There are available backend resources in the same VPC.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  4. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services, and click Create VPC Endpoint Service.
    The Create VPC Endpoint Service page is displayed.
    Figure 1 Create VPC Endpoint Service
    +
    +
  5. Configure parameters by referring to Table 1. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint service is deployed.

    +

    Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Name

    +

    This parameter is optional.

    +

    Specifies the name of the VPC endpoint service.

    +

    The name can contain a maximum of 16 characters, including letters, digits, underscores (_), and hyphens (-).

    +
    • If you do not enter a name, the system automatically generates a name in the region.service_id format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f
    • If you enter a name, the system automatically generates a name in the region.Name.service_id format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0
    +

    VPC

    +

    Specifies the VPC where the VPC endpoint service is deployed.

    +

    Service Type

    +

    Specifies the type of the VPC endpoint service. The type can only be Interface.

    +

    Connection Approval

    +

    Specifies whether the connection between a VPC endpoint and a VPC endpoint service requires approval from the owner of the VPC endpoint service.

    +

    You can determine whether to enable or disable the connection approval.

    +

    If connection approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see Managing Connections of a VPC Endpoint Service.

    +

    Port Mapping

    +

    Specifies the protocol and ports used for communications between the VPC endpoint service and VPC endpoint. The protocol is TCP.

    +
    • Service Port: A service port is provided by the backend service bound to the endpoint service.
    • Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
    +

    The service and terminal port numbers range from 1 to 65535. A maximum of 50 port mappings can be added at a time.

    +
    NOTE:

    Accessing a VPC endpoint service from a VPC endpoint is to access the service port from the associated terminal port.

    +

    After a port mapping is added, it cannot be modified or deleted.

    +
    +

    Backend Resource Type

    +

    Specifies the type of the backend resource that provides services to be accessed.

    +

    The following backend resources are supported:

    +
    • Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
    • ECS: Backend resources of this type serve as servers.
    • BMS: Backend resources of this type serve as servers.
    +
    Example: Elastic load balancer
    NOTE:

    For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.

    +
    +
    +

    Load Balancer

    +

    When Backend Resource Type is set to Elastic load balancer, select the load balancer that provides services from the drop-down list.

    +
    NOTE:

    If an elastic load balancer is used as the backend resource, the source IP address received by the VPC endpoint service is not the real address of the client.

    +
    +

    ECS List

    +

    When Backend Resource Type is set to ECS, select the ECS that provides services from the ECS list.

    +

    BMS List

    +

    When Backend Resource Type is set to BMS, select the BMS that provides services from the BMS list.

    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint service tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint service.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoint services

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  6. Click Create Now.
  7. Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
    Figure 2 VPC endpoint service list
    +
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/en-us_topic_0131645189.html b/docs/vpcep/umn/en-us_topic_0131645189.html new file mode 100644 index 000000000..db998dbaf --- /dev/null +++ b/docs/vpcep/umn/en-us_topic_0131645189.html @@ -0,0 +1,179 @@ + + +

Creating a VPC Endpoint

+

Scenarios

VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.

+

You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoint service in another VPC of the same region.

+
A VPC endpoint comes with a VPC endpoint service. VPC endpoints vary depending on the type of the VPC endpoint services that they can access:
  • VPC endpoints for accessing interface VPC endpoint services are elastic network interfaces that have private IP addresses.
  • VPC endpoints for accessing gateway VPC endpoint services are gateways, with routes configured to distribute traffic to the associated VPC endpoint services.
+
+

You can create different types of VPC endpoints based the types of associated VPC endpoint services:

+ +
+

Creating a VPC Endpoint for Accessing Interface VPC Endpoint Services

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  4. On the displayed page, click Create VPC Endpoint.
  5. On the Create VPC Endpoint page, configure the parameters.
    Figure 1 Create VPC Endpoint (Service Category set to Cloud service)
    +
    Figure 2 Create VPC Endpoint (Service Category set to Find a service by name)
    +
    +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint is located. Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Service Category

    +

    There are two options as follows:

    +
    • Cloud services: Select this value if the target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.
    +

    Service List

    +

    This parameter is available only when you select Cloud services for Service Category.

    +

    The VPC endpoint service has been created by operations people and you can use it without having to perform the creation operation.

    +

    VPC Endpoint Service Name

    +

    This parameter is available only when you select Find a service by name for Service Category.

    +

    You can enter the VPC endpoint service name recorded in Viewing Summary of a VPC Endpoint Service and click Verify.

    +
    • If Service name found is displayed, proceed with subsequent operations.
    • If Service name not found is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the entered service name is correct.
    +

    Private Domain Name

    +

    If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when creating a VPC endpoint. After the VPC endpoint is created, you can access it using the domain name.

    +

    This parameter is only configured for interface VPC endpoints.

    +
    • For the gateway type, this parameter is unavailable.
    • For the interface type, this parameter is optional.
    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    Subnet

    +

    This parameter is available when you want to access an interface endpoint service.

    +

    Specifies the subnet where the VPC endpoint is located.

    +

    Private IP Address

    +

    This parameter is available when you want to access an interface endpoint service.

    +

    Specifies the private IP address of the VPC endpoint. You can select Automatic or Manual.

    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
    +
  6. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
    +
+
+

Creating a VPC Endpoint for Accessing Gateway VPC Endpoint Services

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  4. On the displayed page, click Create VPC Endpoint.
  5. On the Create VPC Endpoint page, configure the parameters.
    Figure 3 Create VPC Endpoint (Service Category set to Cloud service)
    +
    +
    + + + + + + + + + + + + + + + + + + + +
    Table 3 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint is located. Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Service Category

    +

    Specifies the type of services that are configured as gateway VPC endpoint services. Only cloud services are supported.

    +

    Select Cloud services.

    +

    Service List

    +

    This parameter is available only when you select Cloud services for Service Category.

    +

    In the VPC endpoint service list, select the VPC endpoint service whose type is gateway.

    +

    The VPC endpoint service has been created by operations people and you can use it without having to perform the creation operation.

    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.

    +

    Tag keys and values must meet requirements listed in Table 4.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 4 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
    +
  6. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
    +
+
+
+
+
+
Parent topic: VPC Endpoints
+
+
+ diff --git a/docs/vpcep/umn/en-us_topic_0131645193.html b/docs/vpcep/umn/en-us_topic_0131645193.html new file mode 100644 index 000000000..2e3d7f9a6 --- /dev/null +++ b/docs/vpcep/umn/en-us_topic_0131645193.html @@ -0,0 +1,21 @@ + + +

Service Overview

+
+
+ +
+ diff --git a/docs/vpcep/umn/en-us_topic_0131645194.html b/docs/vpcep/umn/en-us_topic_0131645194.html new file mode 100644 index 000000000..bef105b45 --- /dev/null +++ b/docs/vpcep/umn/en-us_topic_0131645194.html @@ -0,0 +1,26 @@ + + +

What Is VPC Endpoint?

+

VPC Endpoint (VPCEP) is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services, including cloud services or your private services. It allows you to plan networks flexibly without having to use EIPs.

+

Architecture

There are two types of resources: VPC endpoint services and VPC endpoints.

+ +
Figure 1 How VPCEP works
+

Figure 1 shows the process of establishing channels for network communications between:

+ +

For more information, see Application Scenarios.

+
+

Accessing VPCEP

A web-based console and HTTPS APIs are provided for you to access VPCEP.

+ +
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/vpcep/umn/en-us_topic_0131645196.html b/docs/vpcep/umn/en-us_topic_0131645196.html new file mode 100644 index 000000000..7f89594b5 --- /dev/null +++ b/docs/vpcep/umn/en-us_topic_0131645196.html @@ -0,0 +1,37 @@ + + +

Application Scenarios

+

VPCEP establishes a secure and private channel between a VPC endpoint (cloud resources in a VPC) and a VPC endpoint service in the same region.

+

You can use VPCEP in different scenarios.

+

High-Speed Access to Cloud Services

After you connect an IDC to a VPC using VPN or Direct Connect, you can use a VPC endpoint to connect the VPC to a cloud service or one of your private services, so that the IDC can access the cloud service or private service.

+
Figure 1 Access to cloud services
+

Figure 1 shows the process of connecting an IDC to VPC 1 over VPN or Direct Connect, for the purpose of:

+ +

For cloud migration, VPCEP has the following advantages:

+ + +

For details, see Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address.

+
+

Cross-VPC Connection

With VPCEP, resources in two different VPCs can communicate with each other despite of logic isolation between them as long as the two VPCs are in the same region.

+

VPC endpoints and VPC peering connections are different in security, communications methods, route configurations, and more.

+

For details, see What Are the Differences Between VPC Endpoints and VPC Peering Connections?.

+
+
Figure 2 Cross-VPC connection
+

An ECS in VPC 1 uses a VPC endpoint to access a load balancer in VPC 2 over a private network. Figure 2 shows the connection process.

+

VPCEP has the following advantages:

+ + +

For details, see the following sections:

+ +
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/vpcep/umn/en-us_topic_0138838187.html b/docs/vpcep/umn/en-us_topic_0138838187.html new file mode 100644 index 000000000..ab04c4ca9 --- /dev/null +++ b/docs/vpcep/umn/en-us_topic_0138838187.html @@ -0,0 +1,14 @@ + + +

What Should I Do If the VPC Endpoint I Purchased Cannot Connect to a VPC Endpoint Service?

+
  1. Confirm that the security group of the ECS NIC is correctly configured.
    • On the ECS details page, view the security group details.
    • Check whether the security group permits IP addresses in the 198.19.128.0/17 CIDR block in the inbound direction. If it does not, add inbound rules for this CIDR block based on service requirements.
    +
  2. Confirm that the firewall of the subnet used by the ECS NIC does not block traffic.

    If you can configure the firewall on the left part of the VPC console, confirm that the subnet of the associated VPC endpoint allows traffic to pass through.

    +

    For details about how to disable the firewall, see Enabling or Disabling a Firewall in the Virtual Private Cloud User Guide.

    +
+
+
+
+
Parent topic: FAQ
+
+
+ diff --git a/docs/vpcep/umn/en-us_topic_0154804561.html b/docs/vpcep/umn/en-us_topic_0154804561.html new file mode 100644 index 000000000..9b80ae0b0 --- /dev/null +++ b/docs/vpcep/umn/en-us_topic_0154804561.html @@ -0,0 +1,24 @@ + + +

What Is a Quota?

+

What Is a Quota?

Quotas are enforced for service resources on the platform to prevent unforeseen spikes in resource usage. Quotas can limit the number and capacity of resources available to users, for example, how many cloud resources you can create.

+

You can also increase the quota if the existing quota cannot meet your service requirements.

+
+

How Do I View My Quotas?

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. In the upper right corner of the page, click .

    The Service Quota page is displayed.

    +
  4. View the used and total quota of each type of resources on the displayed page.

    If a quota cannot meet service requirements, apply for a higher quota.

    +
+
+

How Do I Apply for a Higher Quota?

The system does not support online quota adjustment. If you need to adjust a quota, call the hotline or send an email to the customer service mailbox. Customer service personnel will timely process your request for quota adjustment and inform you of the real-time progress by making a call or sending an email.

+

Before dialing the hotline number or sending an email, make sure that the following information has been obtained:

+ +

Learn how to obtain the service hotline and email address.

+
+
+
+
+
Parent topic: FAQ
+
+
+ diff --git a/docs/vpcep/umn/public_sys-resources/ExpandCollapse.js b/docs/vpcep/umn/public_sys-resources/ExpandCollapse.js new file mode 100644 index 000000000..116ddaabf --- /dev/null +++ b/docs/vpcep/umn/public_sys-resources/ExpandCollapse.js @@ -0,0 +1 @@ +var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}}; \ No newline at end of file diff --git a/docs/vpcep/umn/public_sys-resources/caution_3.0-en-us.png b/docs/vpcep/umn/public_sys-resources/caution_3.0-en-us.png new file mode 100644 index 000000000..60f607621 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/caution_3.0-en-us.png differ diff --git a/docs/vpcep/umn/public_sys-resources/commonltr.css b/docs/vpcep/umn/public_sys-resources/commonltr.css new file mode 100644 index 000000000..c5480b0ab --- /dev/null +++ b/docs/vpcep/umn/public_sys-resources/commonltr.css @@ -0,0 +1 @@ +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/vpcep/umn/public_sys-resources/commonltr_print.css b/docs/vpcep/umn/public_sys-resources/commonltr_print.css new file mode 100644 index 000000000..a59823141 --- /dev/null +++ b/docs/vpcep/umn/public_sys-resources/commonltr_print.css @@ -0,0 +1 @@ +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/vpcep/umn/public_sys-resources/commonrtl.css b/docs/vpcep/umn/public_sys-resources/commonrtl.css new file mode 100644 index 000000000..f261da752 --- /dev/null +++ b/docs/vpcep/umn/public_sys-resources/commonrtl.css @@ -0,0 +1,2 @@ +/*! Copyright (c) Huawei Technologies Co., Ltd. 2020-2022. All rights reserved. */.msgph{font-family:Courier New}.unresolved{background-color:#87ceeb}.noTemplate{background-color:#ff0}.base{background-color:#fff}/*! Add space for top level topics */.nested0,.p{margin-top:1em}/*! div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid *//*! Default of italics to set apart figure captions */.figcap,.italic,.var{font-style:italic}.figdesc{font-style:normal}/*! Use @frame to create frames on figures */.figborder{padding-left:3px;padding-right:3px;margin-top:1em;border:2px solid Silver}.figsides{margin-top:1em;padding-left:3px;padding-right:3px;border-left:2px solid Silver;border-right:2px solid Silver}.figtop{border-top:2px solid Silver;margin-top:1em}.figbottom{border-bottom:2px solid Silver}.figtopbot{border-top:2px solid Silver;border-bottom:2px solid Silver;margin-top:1em}/*! Most link groups are created with
. Ensure they have space before and after. */.ullinks,ul.simple{list-style-type:none}.attention,.danger,.ddexpand,.dlexpand,.example,.fastpath,.important,.liexpand,.linklist,.note,.notice,.olchildlink,.relconcepts,.relinfo,.relref,.reltasks,.remember,.restriction,.section,.sliexpand,.stepexpand,.substepexpand,.tip,.ulchildlink,.warning{margin-top:1em;margin-bottom:1em}.linklistwithchild,.sublinklist{margin-top:1em;margin-right:1.5em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-right:20px}/*! Set heading sizes, getting smaller for deeper nesting */.topictitle1{font-size:1.34em;margin-top:0;margin-bottom:.1em}.topictitle2,.topictitle3,.topictitle4,.topictitle5,.topictitle6,.sectiontitle{font-size:1.17em}.topictitle2{margin-top:1pc;margin-bottom:.45em}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-weight:700}.topictitle4{margin-top:.83em;font-weight:700}.topictitle5{font-weight:700}.topictitle6{font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:0;color:#000;font-weight:700}/*! All note formats have the same default presentation */.attentiontitle,.bold,.cautiontitle,.dangertitle,.dlterm,.fastpathtitle,.firstcol,.importanttitle,.notelisttitle,.notetitle,.noticetitle,.parmname,.remembertitle,.restrictiontitle,.tiptitle,.uicontrol,.warningtitle{font-weight:700}.caution{font-weight:700;margin-bottom:1em}/*! Simple lists do not get a bullet *//*! Used on the first column of a table, when rowheader="firstcol" is used *//*! Various basic phrase styles */.boldItalic{font-weight:700;font-style:italic}.shortcut,.underlined{text-decoration:underline}/*! 2008-10-27 keyword采用跟随上下文的样式 +*//*! Default of bold for definition list terms *//*! Use CSS to expand lists with @compact="no" */.dltermexpand{font-weight:700;margin-top:1em}[compact="yes"]>li{margin-top:0}[compact="no"]>li{margin-top:.53em}/*! Align images based on @align on topic/image */div.imageleft,.text-align-left{text-align:left}div.imagecenter,.text-align-center{text-align:center}div.imageright,.text-align-right{text-align:right}div.imagejustify,.text-align-justify{text-align:justify}.cellrowborder{border-right:0;border-top:0;border-left:1px solid;border-bottom:1px solid}.row-nocellborder{border-left:hidden;border-right:0;border-top:0;border-bottom:1px solid}.cell-norowborder{border-top:0;border-bottom:hidden;border-right:0;border-left:1px solid}.nocellnorowborder{border:0;border-left:hidden;border-bottom:hidden}pre.codeblock,pre.screen{padding:5px;border:outset;background-color:#ccc;margin-top:2px;margin-bottom:2px;white-space:pre} \ No newline at end of file diff --git a/docs/vpcep/umn/public_sys-resources/danger_3.0-en-us.png b/docs/vpcep/umn/public_sys-resources/danger_3.0-en-us.png new file mode 100644 index 000000000..47a9c7235 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/danger_3.0-en-us.png differ diff --git a/docs/vpcep/umn/public_sys-resources/delta.gif b/docs/vpcep/umn/public_sys-resources/delta.gif new file mode 100644 index 000000000..0d1b1f674 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/delta.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/deltaend.gif b/docs/vpcep/umn/public_sys-resources/deltaend.gif new file mode 100644 index 000000000..cc7da0fc8 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/deltaend.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-arrowdn.gif b/docs/vpcep/umn/public_sys-resources/icon-arrowdn.gif new file mode 100644 index 000000000..379428032 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-arrowdn.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-arrowrt.gif b/docs/vpcep/umn/public_sys-resources/icon-arrowrt.gif new file mode 100644 index 000000000..6aaaa11c2 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-arrowrt.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-caution.gif b/docs/vpcep/umn/public_sys-resources/icon-caution.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-caution.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-danger.gif b/docs/vpcep/umn/public_sys-resources/icon-danger.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-danger.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-huawei.gif b/docs/vpcep/umn/public_sys-resources/icon-huawei.gif new file mode 100644 index 000000000..a31d60f89 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-huawei.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-note.gif b/docs/vpcep/umn/public_sys-resources/icon-note.gif new file mode 100644 index 000000000..31be2b039 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-note.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-notice.gif b/docs/vpcep/umn/public_sys-resources/icon-notice.gif new file mode 100644 index 000000000..409070650 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-notice.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-tip.gif b/docs/vpcep/umn/public_sys-resources/icon-tip.gif new file mode 100644 index 000000000..c47bae05c Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-tip.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/icon-warning.gif b/docs/vpcep/umn/public_sys-resources/icon-warning.gif new file mode 100644 index 000000000..079c79b26 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/icon-warning.gif differ diff --git a/docs/vpcep/umn/public_sys-resources/note_3.0-en-us.png b/docs/vpcep/umn/public_sys-resources/note_3.0-en-us.png new file mode 100644 index 000000000..57a0e1f53 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/note_3.0-en-us.png differ diff --git a/docs/vpcep/umn/public_sys-resources/notice_3.0-en-us.png b/docs/vpcep/umn/public_sys-resources/notice_3.0-en-us.png new file mode 100644 index 000000000..fa4b64990 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/notice_3.0-en-us.png differ diff --git a/docs/vpcep/umn/public_sys-resources/popup.js b/docs/vpcep/umn/public_sys-resources/popup.js new file mode 100644 index 000000000..a550862ed --- /dev/null +++ b/docs/vpcep/umn/public_sys-resources/popup.js @@ -0,0 +1 @@ +var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file diff --git a/docs/vpcep/umn/public_sys-resources/warning_3.0-en-us.png b/docs/vpcep/umn/public_sys-resources/warning_3.0-en-us.png new file mode 100644 index 000000000..def5c3565 Binary files /dev/null and b/docs/vpcep/umn/public_sys-resources/warning_3.0-en-us.png differ diff --git a/docs/vpcep/umn/vpcep_01_0002.html b/docs/vpcep/umn/vpcep_01_0002.html new file mode 100644 index 000000000..0852aa527 --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0002.html @@ -0,0 +1,11 @@ + + +

Product Advantages

+
  • Excellent Performance: Each gateway supports up to 1 million concurrent connections in a variety of application scenarios.
  • Immediately Ready for Use Upon Creation: VPC endpoints take effect a few seconds after they are created.
  • Easy to Use: You can use VPC endpoints to access resources over private networks, without having to use EIPs.
  • High Security: VPC endpoints enable you to access VPC endpoint services without exposing server information, minimizing security risks.
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/vpcep/umn/vpcep_01_0005.html b/docs/vpcep/umn/vpcep_01_0005.html new file mode 100644 index 000000000..5e550ed45 --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0005.html @@ -0,0 +1,38 @@ + + +

Constraints

+

Constraints on Resource Quotas

Table 1 describes constraints on the VPCEP resource quota.

+ +
+ + + + + + + + + + + + +
Table 1 VPCEP resource quotas

Resource

+

Quota

+

How to Increase Quota

+

VPC endpoint services per account

+

20

+

What Is a Quota?

+

VPC endpoints per account

+

50

+
+
+
+

Other Constraints

  • When you create a VPC endpoint, ensure that the associated VPC endpoint service has been created and is in the same region as the VPC endpoint.
  • One VPC endpoint can be used to connect to only one VPC endpoint service.
  • A VPC endpoint supports a maximum of 3,000 concurrent requests.
  • One VPC endpoint service can be connected by multiple VPC endpoints.
  • One VPC endpoint service corresponds to only one backend resource.
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/vpcep/umn/vpcep_01_0006.html b/docs/vpcep/umn/vpcep_01_0006.html new file mode 100644 index 000000000..b5ef9bf1b --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0006.html @@ -0,0 +1,14 @@ + + +

VPC Endpoints

+

VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.

+

You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoint service in another VPC of the same region.

+
A VPC endpoint comes with a VPC endpoint service. VPC endpoints vary depending on the type of the VPC endpoint services that they can access:
  • VPC endpoints for accessing interface VPC endpoint services are elastic network interfaces that have private IP addresses.
  • VPC endpoints for accessing gateway VPC endpoint services are gateways, with routes configured to distribute traffic to the associated VPC endpoint services.
+
+
+
+
+
Parent topic: Product Concepts
+
+
+ diff --git a/docs/vpcep/umn/vpcep_01_0007.html b/docs/vpcep/umn/vpcep_01_0007.html new file mode 100644 index 000000000..442322f45 --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0007.html @@ -0,0 +1,77 @@ + + +

VPCEP and Other Services

+

Table 1 shows the relationship between VPCEP and other cloud services.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Relationships with other services

Interactive Function

+

Service

+

Reference

+

Creating VPC endpoint services for resources in your VPC

+

VPC

+		 + +

Connecting an IDC to your VPC using a VPN connection and connecting your VPC to a cloud service through VPCEP

+

VPN

+

Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address

+

Connecting an IDC to your VPC using a direct connection and connecting your VPC to a cloud service through VPCEP

+

Direct Connect

+

When an enterprise needs to provide VPCEP for multiple users, IAM can be used to create users and control access of these domains to enterprise resources.

+

IAM

+

Permission Description

+

Configured as a gateway VPC endpoint service by default. You can create a VPC endpoint to access the VPC endpoint service.

+

OBS

+

Creating a VPC Endpoint

+

Configured as an interface VPC endpoint service by default. You can create VPC endpoints to access these endpoint services.

+

DNS

+

Creating a VPC Endpoint

+

Configuring a private service as a VPC endpoint service. You can create a VPC endpoint to access the VPC endpoint service.

+

ELB

+

Creating a VPC Endpoint Service

+

ECS

+

BMS

+
+
+
+
+
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/vpcep/umn/vpcep_01_0009.html b/docs/vpcep/umn/vpcep_01_0009.html new file mode 100644 index 000000000..2c23d4fdd --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0009.html @@ -0,0 +1,21 @@ + + +

Product Concepts

+
+
+ + +
+
Parent topic: Service Overview
+
+
+ diff --git a/docs/vpcep/umn/vpcep_01_0010.html b/docs/vpcep/umn/vpcep_01_0010.html new file mode 100644 index 000000000..a57c59e68 --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0010.html @@ -0,0 +1,13 @@ + + +

User Permissions

+
The cloud system provides two types of user permissions by default, user management and resource management.
  • User management refers to management of users, user groups, and user group permissions.
  • Resource management refers to access control over cloud service resources.
+
+

VPCEP provides two types of resources: VPC endpoint services and VPC endpoints, both of which are region-level resources. The required permissions must be added for users in the project.

+
+
+
+
Parent topic: Product Concepts
+
+
+ diff --git a/docs/vpcep/umn/vpcep_01_0011.html b/docs/vpcep/umn/vpcep_01_0011.html new file mode 100644 index 000000000..4cd8056b8 --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0011.html @@ -0,0 +1,22 @@ + + +

Region and AZ

+

Concept

A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.

+
  • A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
  • An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.
+

Figure 1 shows the relationship between regions and AZs.

+
Figure 1 Regions and AZs
+
+

Selecting a Region

Select a region closest to your target users for lower network latency and quick access.

+
+

Selecting an AZ

When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.

+
  • For high DR capability, deploy resources in different AZs within the same region.
  • For lower network latency, deploy resources in the same AZ.
+
+

Regions and Endpoints

Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.

+
+
+
+
+
Parent topic: Product Concepts
+
+
+ diff --git a/docs/vpcep/umn/vpcep_01_0013.html b/docs/vpcep/umn/vpcep_01_0013.html new file mode 100644 index 000000000..0577d8353 --- /dev/null +++ b/docs/vpcep/umn/vpcep_01_0013.html @@ -0,0 +1,116 @@ + + +

VPC Endpoint Services

+

A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.

+
There are two types of VPC endpoint services: gateway and interface.
  • Gateway VPC endpoint services are created only for cloud services.
  • Interface VPC endpoint services can be created for both cloud services and your private services. All VPC endpoint services for cloud services are created by default while those for private services need to be created by users themselves.
+
+

Gateway VPC Endpoint Services

Gateway endpoint services are configured from cloud services by the system. You do not have the permission to configure such services but can select them when creating a VPC endpoint.

+

Supported cloud services vary in different regions. For details, see the list of services that can be configured on the management console.

+
+ +
+ + + + + + + + + + + + + +
Table 1 Supported gateway VPC endpoint services

VPC Endpoint Service

+

Category

+

Type

+

Example

+

Description

+

OBS

+

Cloud service

+

Gateway

+
  • eu-de:

    com.t-systems.otc.eu-de.obs

    +
  • eu-nl:

    com.t-systems.otc.eu-nl.obs

    +

    com.t-systems.otc.eu-nl.obs-internet

    +
+
  • Select the endpoint service ending with obs if you want to access OBS using its private address.
  • Select the endpoint service ending with obs-internet if you want to access OBS using its private address.
+
+
+
+

Interface VPC Endpoint Services

Interface VPC endpoint services are mainly configured from:

+
  • Cloud services. You do not have the permission to configure such endpoint services, but can select them when creating a VPC endpoint.
  • Your private services
+

Supported cloud services vary in different regions. For details, see the list of services that can be configured on the management console.

+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Supported interface VPC endpoint services

VPC Endpoint Service

+

Category

+

Type

+

Example

+

Description

+

DNS

+

Cloud service

+

Interface

+
  • eu-de:

    com.t-systems.otc.eu-de.dns

    +
  • eu-nl:

    com.t-systems.otc.eu-nl.dns

    +
+

Select the endpoint service ending with dns if you want to access DNS over private networks.

+

Load balancer

+

Users' private service

+

Interface

+

None

+

Select a load balancer as the backend resource if your services receive high traffic and demand high reliability and disaster recovery (DR) performance.

+

ECS

+

Users' private service

+

Interface

+

None

+

VPC endpoint services work as servers.

+

BMS

+

Users' private service

+

Interface

+

None

+

VPC endpoint services work as servers.

+
NOTE:

Only region eu-de supports BMSs.

+
+
+
+
+
+
+
+
Parent topic: Product Concepts
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0000.html b/docs/vpcep/umn/vpcep_02_0000.html new file mode 100644 index 000000000..7f3b46dce --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0000.html @@ -0,0 +1,19 @@ + + +

Getting Started

+
+
+ +
+ diff --git a/docs/vpcep/umn/vpcep_02_0200.html b/docs/vpcep/umn/vpcep_02_0200.html new file mode 100644 index 000000000..d310a9d16 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0200.html @@ -0,0 +1,19 @@ + + +

Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain

+
+
+ + +
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_02021.html b/docs/vpcep/umn/vpcep_02_02021.html new file mode 100644 index 000000000..76a456615 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_02021.html @@ -0,0 +1,21 @@ + + +

Overview

+

Scenarios

With VPCEP, you can access resources across VPCs in the same region.

+

Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP addresses. After you create a VPC endpoint, you can use a private IP address to access resources across two VPCs despite of network isolation between them.

+

This section describes how cloud resources in VPCs of different domains in the same region can communicate with each other across VPCs.

+

VPC 1 and VPC 2 belong to different domains , respectively. You can take the ELB in VPC 2 as a VPC endpoint service and create a VPC endpoint in VPC 1 so that the ECS in VPC 1 can access the ELB in VPC 2 using the private IP address.

+
Figure 1 Cross-VPC communications
+
+
+
+

Configuration Process

Figure 2 shows how to enable communications between VPCs of the same domain using VPCEP.
Figure 2 Cross-VPC communications
+
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_02022.html b/docs/vpcep/umn/vpcep_02_02022.html new file mode 100644 index 000000000..76b1fb78b --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_02022.html @@ -0,0 +1,122 @@ + + +

Step 1: Create a VPC Endpoint Service

+

Scenarios

To enable communications across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.

+

This section uses an elastic load balancer as an example backend service to describe how to create a VPC endpoint service.

+
+

Prerequisites

There are available backend resources in the same VPC.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services, and click Create VPC Endpoint Service.

    The Create VPC Endpoint Service page is displayed.

    +

    +

    +
    Figure 1 Create VPC Endpoint Service
    +

    +
  2. Configure the required parameters. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint service is deployed.

    +

    Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Name

    +

    This parameter is optional.

    +

    Specifies the name of the VPC endpoint service.

    +

    The name can contain a maximum of 16 characters, including letters, digits, underscores (_), and hyphens (-).

    +
    • If you do not enter a name, the system automatically generates a name in the region.service_id format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f.
    • If you enter a name, the system automatically generates a name in the region.Name.service_id format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0.
    +

    VPC

    +

    Specifies the VPC where the VPC endpoint service is deployed.

    +

    Service Type

    +

    Specifies the type of the VPC endpoint service. The type can only be Interface.

    +

    Connection Approval

    +

    Specifies whether the connection between a VPC endpoint and a VPC endpoint service requires approval from the owner of the VPC endpoint service.

    +

    You can determine whether to enable or disable the connection approval.

    +

    If connection approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see step 7.

    +

    Port Mapping

    +

    Specifies the protocol and ports used for communications between the VPC endpoint service and VPC endpoint. The protocol is TCP.

    +
    • Service Port: A service port is provided by the backend service bound to the endpoint service.
    • Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
    +

    The service and terminal port numbers range from 1 to 65535. A maximum of 50 port mappings can be added at a time.

    +
    NOTE:

    Accessing a VPC endpoint service from a VPC endpoint is to access the service port from the associated terminal port.

    +

    After a port mapping is added, it cannot be modified or deleted.

    +
    +

    Backend Resource Type

    +

    Specifies the type of the backend resource that provides services to be accessed.

    +

    The following backend resources are supported:

    +
    • Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
    • ECS: Backend resources of this type serve as servers.
    • BMS: Backend resources of this type serve as servers.
    +
    Example: Elastic load balancer
    NOTE:

    For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.

    +
    +
    +

    Load Balancer

    +

    When Backend Resource Type is set to Elastic load balancer, select the load balancer that provides services from the drop-down list.

    +
    NOTE:

    If an elastic load balancer is used as the backend resource, the source IP address received by the VPC endpoint service is not the real address of the client.

    +
    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint service tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint service.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoint services

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  3. Click Create Now.
  4. Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
  5. In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view the details.
    Figure 2 Summary of the VPC endpoint service
    +

    +
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_02023.html b/docs/vpcep/umn/vpcep_02_02023.html new file mode 100644 index 000000000..20cfa2d0f --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_02023.html @@ -0,0 +1,110 @@ + + +

Step 2: Create a VPC Endpoint

+

Scenarios

After you create a VPC endpoint service, you also need to create a VPC endpoint to access the VPC endpoint service.

+

This section describes how to create a VPC endpoint in another VPC of your own for connecting to the VPC endpoint service.

+

Select the same region and project as those of the VPC endpoint service.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  4. On the VPC Endpoints page, click Create VPC Endpoint.
    The Create VPC Endpoint page is displayed.
    Figure 1 Create VPC Endpoint (Service Category set to Find a service by name)
    +
    +
  5. Set the required parameters. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint is located. This region is the same as that of the VPC endpoint service.

    +

    Service Category

    +

    There are two options: Cloud services or Find a service by name.

    +
    • Cloud services: The target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.
    +

    Example: Find a service by name

    +

    VPC Endpoint Service Name

    +

    This parameter is available only when you select Find a service by name for Service Category.

    +

    Enter the VPC endpoint service name recorded in step 8,, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f and click Verify.

    +
    • If Service name found is displayed, proceed with subsequent operations.
    • If Service name not found is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the entered service name is correct.
    +

    Private Domain Name

    +

    If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when creating a VPC endpoint. After the VPC endpoint is created, you can access it using the domain name.

    +
    • For the gateway type, this parameter is unavailable.
    • For the interface type, this parameter is optional.
    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    Subnet

    +

    Specifies the subnet where the VPC endpoint is located.

    +

    Private IP Address

    +

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    +

    Specifies the private IP address of the VPC endpoint. You can select Automatic or Manual.

    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  6. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
    +
  7. Manage the connection of the VPC endpoint.
    If the status of the VPC endpoint changes to Accepted, the VPC endpoint is connected to the required VPC endpoint service. If the status is Pending acceptance, connection approval is enabled for the endpoint service, ask the owner of the endpoint service to perform the following operations:
    1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
    2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
    3. On the displayed page, select the Connection Management tab.
      • If you allow a VPC endpoint to connect to this VPC endpoint service, locate the target VPC endpoint and click Accept in the Operation column.
      • If you refuse a VPC endpoint from connecting to this VPC endpoint service, click Reject in the Operation column.
      +
    4. Go back to the VPC endpoint list and check whether the status of the target VPC endpoint changes to Accepted. If yes, the VPC endpoint is connected to the VPC endpoint service.
    +
    +
  8. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
    After a VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name.
    Figure 2 Summary of the VPC endpoint
    +
    +

    You can use the private IP address or private domain name to access the VPC endpoint service.

    +
+
+

Configuration Verification

Log in to an ECS in VPC 1 remotely and access the VPC endpoint using its private IP address or private domain name.

+
Figure 3 Logging in to the ECS to access the VPC endpoint
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Communications Across VPCs of the Same Domain
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0203.html b/docs/vpcep/umn/vpcep_02_0203.html new file mode 100644 index 000000000..9e538b1c4 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0203.html @@ -0,0 +1,21 @@ + + +

Configuring a VPC Endpoint for Communications Across VPCs of Different Domains

+
+
+ + +
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_02031.html b/docs/vpcep/umn/vpcep_02_02031.html new file mode 100644 index 000000000..f667ad305 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_02031.html @@ -0,0 +1,21 @@ + + +

Overview

+

Scenarios

With VPCEP, you can access resources across VPCs in the same region.

+

Cloud resources in different VPCs are isolated from each other and cannot be accessed using private IP addresses. After you create a VPC endpoint, you can use a private IP address to access resources across two VPCs despite of network isolation between them.

+

This section describes how cloud resources in VPCs of different domains in the same region can communicate with each other across VPCs.

+

VPC 1 and VPC 2 belong to different domains. You can take the ELB in VPC 2 as a VPC endpoint service and create a VPC endpoint in VPC 1 so that the ECS in VPC 1 can access the ELB in VPC 2 using the private IP address.

+
Figure 1 Cross-VPC communications
+
+
+
+

Cross-VPC Communications

Figure 2 shows how to enable communications between two VPCs of different domains using VPCEP.

+
Figure 2 Cross-VPC communications flowchart
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Communications Across VPCs of Different Domains
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_02032.html b/docs/vpcep/umn/vpcep_02_02032.html new file mode 100644 index 000000000..1851fc13d --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_02032.html @@ -0,0 +1,122 @@ + + +

Step 1: Create a VPC Endpoint Service

+

Scenarios

To enable communications across two VPCs, you first need to configure a cloud resource (backend resource) in one VPC as a VPC endpoint service.

+

This section describes how to create a VPC endpoint service by selecting an elastic load balancer as an example backend service in VPC 2 using domain B.

+
+

Prerequisites

There are available backend resources in the same VPC.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services, and click Create VPC Endpoint Service.

    The Create VPC Endpoint Service page is displayed.

    +

    +

    +
    Figure 1 Create VPC Endpoint Service
    +

    +
  2. Configure the required parameters. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint service is deployed.

    +

    Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Name

    +

    This parameter is optional.

    +

    Specifies the name of the VPC endpoint service.

    +

    The name can contain a maximum of 16 characters, including letters, digits, underscores (_), and hyphens (-).

    +
    • If you do not enter a name, the system automatically generates a name in the region.service_id format, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f.
    • If you enter a name, the system automatically generates a name in the region.Name.service_id format, for example, eu-de.test.e9c186ca-99e4-4a88-9011-8898f1d680c0.
    +

    VPC

    +

    Specifies the VPC where the VPC endpoint service is deployed.

    +

    Service Type

    +

    Specifies the type of the VPC endpoint service. The type can only be Interface.

    +

    Connection Approval

    +

    Specifies whether the connection between a VPC endpoint and a VPC endpoint service requires approval from the owner of the VPC endpoint service.

    +

    You can determine whether to enable or disable the connection approval.

    +

    If connection approval is enabled, any VPC endpoint for connecting to the VPC endpoint service needs to be approved. For details, see step 7.

    +

    Port Mapping

    +

    Specifies the protocol and ports used for communications between the VPC endpoint service and VPC endpoint. The protocol is TCP.

    +
    • Service Port: A service port is provided by the backend service bound to the endpoint service.
    • Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
    +

    The service and terminal port numbers range from 1 to 65535. A maximum of 50 port mappings can be added at a time.

    +
    NOTE:

    Accessing a VPC endpoint service from a VPC endpoint is to access the service port from the associated terminal port.

    +

    After a port mapping is added, it cannot be modified or deleted.

    +
    +

    Backend Resource Type

    +

    Specifies the type of the backend resource that provides services to be accessed.

    +

    The following backend resources are supported:

    +
    • Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
    • ECS: Backend resources of this type serve as servers.
    • BMS: Backend resources of this type serve as servers.
    +
    Example: Elastic load balancer
    NOTE:

    For the security group associated with the backend resource configured for the VPC endpoint service, add an inbound rule, with the source IP address set to 198.19.128.0/17. For details, see Adding a Security Group Rule in the Virtual Private Cloud User Guide.

    +
    +
    +

    Load Balancer

    +

    When Backend Resource Type is set to Elastic load balancer, select the load balancer that provides services from the drop-down list.

    +
    NOTE:

    If an elastic load balancer is used as the backend resource, the source IP address received by the VPC endpoint service is not the real address of the client.

    +
    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint service tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint service.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoint services

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  3. Click Create Now.
  4. Click Back to VPC Endpoint Service List to view the newly-created VPC endpoint service.
  5. In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view the details.
    Figure 2 Summary of the VPC endpoint service
    +

    +
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Communications Across VPCs of Different Domains
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_02034.html b/docs/vpcep/umn/vpcep_02_02034.html new file mode 100644 index 000000000..1520f77d7 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_02034.html @@ -0,0 +1,28 @@ + + +

Step 2: Add a Whitelist Record

+

Scenarios

Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.

+

After a VPC endpoint service is created, you can add an authorized domain ID to or delete it from the whitelist of the endpoint service.

+

The following operations describe how to obtain your own domain ID and add it to the whitelist of an existing VPC endpoint service in another domain.

+
+

Prerequisites

The required VPC endpoint service already exists.

+
+

Obtain the ID of Your Own Domain

  1. Log in to the management console.
  2. Click My Credentials under the domain.
    Figure 1 My Credentials
    +

    +
    The My Credentials page is displayed. You can view and record the Domain ID.
    Figure 2 Domain ID
    +
    +
+
+

Add an Authorized Domain ID to the Whitelist of a VPC Endpoint Service

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. On the displayed page, select the Permission Management tab and click Add to Whitelist.
  4. Enter an authorized domain ID in the required format and click OK.
    Figure 3 Add to Whitelist
    +
    • Your domain is in the whitelist of your VPC endpoint service by default.
    • The authorized domain ID is in the iam:domain::domain_id format.

      domain_id indicates the ID of the authorized domain, for example, iam:domain::1564ec50ef2a47c791ea5536353ed4b9

      +
    • Adding * to the whitelist means that all users can access the VPC endpoint service.
    +
    +
  5. Click OK.
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Communications Across VPCs of Different Domains
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_02035.html b/docs/vpcep/umn/vpcep_02_02035.html new file mode 100644 index 000000000..ab5ac5afb --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_02035.html @@ -0,0 +1,106 @@ + + +

Step 3: Create a VPC Endpoint

+

Scenarios

After you add the required whitelist record, you can create a VPC endpoint in VPC 1 to connect to the target VPC endpoint service.

+

Select the same region and project as those of the VPC endpoint service.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  4. On the VPC Endpoints page, click Create VPC Endpoint.
    The Create VPC Endpoint page is displayed.
    Figure 1 Create VPC Endpoint (Service Category set to Find a service by name)
    +
    +
  5. Set the required parameters. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint is located. This region is the same as that of the VPC endpoint service.

    +

    Service Category

    +

    There are two options: Cloud services or Find a service by name.

    +
    • Cloud services: The target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.
    +

    Example: Find a service by name

    +

    VPC Endpoint Service Name

    +

    This parameter is available only when you select Find a service by name for Service Category.

    +

    Enter the VPC endpoint service name recorded in step 8,, for example, eu-de.69e93219-e3ad-43b9-8416-9d788319ac9f and click Verify.

    +
    • If Service name found is displayed, proceed with subsequent operations.
    • If Service name not found is displayed, check whether the region is the same as that of the connected VPC endpoint service or whether the entered service name is correct.
    +

    Private Domain Name

    +

    If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when creating a VPC endpoint. After the VPC endpoint is created, you can access it using the domain name.

    +
    • For the gateway type, this parameter is unavailable.
    • For the interface type, this parameter is optional.
    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    Subnet

    +

    Specifies the subnet where the VPC endpoint is located.

    +

    Private IP Address

    +

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    +

    Specifies the private IP address of the VPC endpoint. You can select Automatic or Manual.

    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  6. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
    +
  7. Manage the connection of the VPC endpoint.
    If the status of the VPC endpoint changes to Accepted, the VPC endpoint is connected to the required VPC endpoint service. If the status is Pending acceptance, connection approval is enabled for the endpoint service, ask the owner of the endpoint service to perform the following operations:
    1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
    2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
    3. On the displayed page, select the Connection Management tab.
      • If you allow a VPC endpoint to connect to this VPC endpoint service, locate the target VPC endpoint and click Accept in the Operation column.
      • If you refuse a VPC endpoint from connecting to this VPC endpoint service, click Reject in the Operation column.
      +
    4. Go back to the VPC endpoint list and check whether the status of the target VPC endpoint changes to Accepted. If yes, the VPC endpoint is connected to the VPC endpoint service.
    +
    +
  8. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
    After a VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name.
    Figure 2 Summary of the VPC endpoint
    +
    +

    You can use the private IP address or private domain name to access the VPC endpoint service.

    +
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Communications Across VPCs of Different Domains
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0300.html b/docs/vpcep/umn/vpcep_02_0300.html new file mode 100644 index 000000000..dd5c46af9 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0300.html @@ -0,0 +1,21 @@ + + +

Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address

+
+
+ + +
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0301.html b/docs/vpcep/umn/vpcep_02_0301.html new file mode 100644 index 000000000..76cf38cc2 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0301.html @@ -0,0 +1,23 @@ + + +

Overview

+

Scenarios

If you want to access a cloud service like OBS from an IDC, you can connect the IDC to your VPC using a VPN connection or a direct connection and then connect your VPC to a cloud service using a VPC endpoint.

+

This section describes how to configure a VPC endpoint to access OBS using its private address from an IDC.

+
Figure 1 Accessing OBS using its private address from an IDC
+

Figure 1 shows the process of connecting an IDC to a VPC over VPN or Direct Connect to access DNS and OBS using two VPC endpoints, respectively.

+

A VPC endpoint comes with a VPC endpoint service. Before you create a VPC endpoint, ensure that the VPC endpoint service that you want to access is available.

+

The following VPC endpoint services are required:

+
  • VPC endpoint service for DNS: resolves the OBS domain name at the IDC.

    eu-de: com.t-systems.otc.eu-de.dns

    +
  • VPC endpoint service for OBS: provides the OBS service for the IDC.

    eu-de: com.t-systems.otc.eu-de.obs

    +
+
+

Configuration Process

Figure 2 shows the process for configuring a VPC endpoint to access OBS using its private address from an IDC.

+
Figure 2 Configuration flowchart
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0302.html b/docs/vpcep/umn/vpcep_02_0302.html new file mode 100644 index 000000000..b2fa8dd82 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0302.html @@ -0,0 +1,107 @@ + + +

Step 1: Create a VPC Endpoint for Connecting to DNS

+

Scenarios

This section describes how to create a VPC endpoint for accessing a DNS server, in order to forward requests of resolving OBS domain names.

+
+

Prerequisites

The required VPC endpoint service already exists.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  1. On the VPC Endpoints page, click Create VPC Endpoint.
    The Create VPC Endpoint page is displayed.
    Figure 1 Create VPC Endpoint
    +
    +

    +
  2. Set the required parameters. +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint is located.

    +

    Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Service Category

    +

    There are two options: Cloud services or Find a service by name.

    +
    • Cloud services: Select this value if the target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.
    +

    Example: Cloud services

    +

    Service List

    +

    This parameter is available only when you select Cloud services for Service Category.

    +

    The VPC endpoint service has been created by operations people and you can use it without having to perform the creation operation.

    +

    Example: com.t-systems.otc.eu-de.dns

    +

    Private Domain Name

    +

    If you want to access a VPC endpoint using a domain name, select Create a Private Domain Name when creating a VPC endpoint. After the VPC endpoint is created, you can access it using the domain name.

    +

    This parameter can only be configured for VPC endpoints of the interface type, and its setting depends on the type of target VPC endpoint services:

    +
    • For the gateway type, this parameter is unavailable.
    • For the interface type, this parameter is optional.
    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    Subnet

    +

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    +

    Specifies the subnet where the VPC endpoint is located.

    +

    Private IP Address

    +

    This parameter is available only when you create a VPC endpoint for connecting to an interface VPC endpoint service.

    +

    Specifies the private IP address of the VPC endpoint. You can select Automatic or Manual.

    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  3. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
    +
  4. Click Back to VPC Endpoint List after the task is submitted.

    If the status of the VPC endpoint changes to Accepted, the VPC endpoint for connecting to com.t-systems.otc.eu-de.dns is created.

    +
  5. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
    After a VPC endpoint for accessing interface VPC endpoint services is created, a private IP address is generated together with a private domain name if you select Create a Private Domain Name during creation.
    Figure 2 Summary of the VPC endpoint
    +
    +
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0303.html b/docs/vpcep/umn/vpcep_02_0303.html new file mode 100644 index 000000000..e7dd5e9c1 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0303.html @@ -0,0 +1,88 @@ + + +

Step 2: Create a VPC Endpoint for Connecting to OBS

+

Scenarios

This section describes how to create a VPC endpoint to access OBS from an IDC.

+
+

Prerequisites

The required VPC endpoint service already exists.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  4. On the VPC Endpoints page, click Create VPC Endpoint.

    The Create VPC Endpoint page is displayed.

    +
    Figure 1 Create VPC Endpoint
    +
    +

    +
  5. Set the required parameters. +
    + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint is located.

    +

    Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Service Category

    +

    There are two options: Cloud services or Find a service by name.

    +
    • Cloud services: Select this value if the target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.
    +

    Example: Cloud services

    +

    Service List

    +

    This parameter is available only when you select Cloud services for Service Category.

    +

    The VPC endpoint service has been created by operations people and you can use it without having to perform the creation operation.

    +

    Example: com.t-systems.otc.eu-de.obs

    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    Tag

    +

    This parameter is optional.

    +

    Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  6. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
    +
  7. Click Back to VPC Endpoint List after the task is submitted.

    If the status of the VPC endpoint changes from Creating to Accepted, the VPC endpoint for connecting to com.t-systems.otc.eu-de.obs is created.

    +
  8. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
    Figure 2 Summary of the VPC endpoint
    +
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0304.html b/docs/vpcep/umn/vpcep_02_0304.html new file mode 100644 index 000000000..f25b2ac7d --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0304.html @@ -0,0 +1,45 @@ + + +

Step 3: Access OBS

+

Scenarios

This section describes how to access OBS using a VPN connection or a direct connection.

+
+

Prerequisites

Your local data center has been connected to your VPC using a VPN or Direct Connect connection.
  • The local subnet of the VPC that interconnects with your VPN contains the OBS CIDR block 100.125.0.0/16.

    For details about how to create a VPN connection, see Creating a VPN in the Virtual Private Network User Guide.

    +
  • The CIDR block of the virtual gateway associated with your direct connection contains the OBS CIDR block 100.125.0.0/16.

    For details about how to enable Direct Connect, see Getting Started in the Direct Connect User Guide.

    +
+
+
+

Procedure

  1. In the VPC endpoint list, locate the target VPC endpoint and click the ID of the endpoint to view its details.
    Figure 1 Summary of the VPC endpoint
    +
  2. Add DNS records on the DNS server at your local data center to forward requests for resolving OBS domain names to the VPC endpoint for accessing DNS.

    The methods of configuring DNS forwarding rules vary depending on operating systems. For details, see the DNS software operation documents.

    +

    This step uses the common DNS software Bind as an example to configure forwarding rules in the UNIX operating system as follows:

    +

    In file /etc/named.conf, add the DNS forwarder configuration and set forwarders to the private IP address of the VPC endpoint for accessing DNS.

    +

    options {

    +

    forward only;

    +

    forwarders{ xx.xx.xx.xx;};

    +

    };

    +
    • If no DNS server is available at your local data center, add the private IP address of the VPC endpoint in file /etc/resolv.conf.
    • xx.xx.xx.xx is the private IP address obtained in step 1.
    +
    +
  3. Configure a DNS route from your local data center to the VPN gateway or Direct Connect gateway.

    xx.xx.xx.xx indicates the private IP address of the VPC endpoint. To access DNS using a VPN connection or a direct connection, you need to ensure that traffic from your local data center to DNS is directed to the VPN gateway or Direct Connect gateway.

    +

    Configure a permanent route at your local data center and specify the IP address of the Direct Connect or VPN gateway as the next hop for accessing DNS.

    +

    route -p add xx.xx.xx.xx mask 255.255.255.255 xxx.xxx.xxx.xxx

    +
    • xx.xx.xx.xx is the private IP address obtained in step 1.
    • xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your local data center.
    +
    +
  4. Configure an OBS route from the local data center to the VPN or Direct Connect gateway.

    The CIDR block of the VPC endpoint for accessing OBS is 100.125.0.0/16. To access OBS using a VPN connection or direct connection, you need to ensure that traffic from your local data center to OBS is directed to the VPN gateway or Direct Connect gateway.

    +

    Configure a permanent route at your local data center and specify the Direct Connect or VPN gateway as the next hop for accessing OBS.

    +

    route -p add 100.125.0.0 mask 255.255.0.0 xxx.xxx.xxx.xxx

    +

    xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your local data center.

    +
    +
  5. At the local data center, run the following command to verify the connectivity with OBS:

    telnet bucket.endpoint

    +

    In the command:

    +
    • bucket: indicates the bucket name.
    • endpoint: indicates the endpoint information about OBS.
    +

    Example: telnet bucket.obs.eu-de.otc.t-systems.com

    +

    Obtain OBS endpoint information at Regions and Endpoints.

    +
    +
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Accessing OBS Using the OBS Private Address
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0400.html b/docs/vpcep/umn/vpcep_02_0400.html new file mode 100644 index 000000000..b9da0bcfe --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0400.html @@ -0,0 +1,19 @@ + + +

Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address

+
+
+ + +
+
Parent topic: Getting Started
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0401.html b/docs/vpcep/umn/vpcep_02_0401.html new file mode 100644 index 000000000..2ab2ee0f7 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0401.html @@ -0,0 +1,23 @@ + + +

Overview

+

Scenarios

If you want to access OBS using its public address from an IDC, you can use a VPC endpoint to connect to the VPC endpoint service configured for OBS.

+

This section describes how to create such a VPC endpoint to access OBS.

+

This scenario is supported only in region eu-nl.

+
+
Figure 1 Accessing OBS using its public address from an IDC
+

Figure 1 shows the process of connecting an IDC to a VPC over VPN or Direct Connect to access OBS using a VPC endpoint created in the VPC.

+

A VPC endpoint comes with a VPC endpoint service. Before you create a VPC endpoint, ensure that the VPC endpoint service that you want to access is available.

+

The following VPC endpoint services are required:

+

eu-nl: com.t-systems.otc.eu-nl.obs-internet

+
+

Configuration Process

Figure 2 shows the process for configuring a VPC endpoint to access OBS using its public address from an IDC.

+
Figure 2 Configuration flowchart
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0402.html b/docs/vpcep/umn/vpcep_02_0402.html new file mode 100644 index 000000000..6c4ce4f5d --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0402.html @@ -0,0 +1,87 @@ + + +

Step 1: Create a VPC Endpoint for Connecting to OBS

+

Scenarios

This section describes how to create a VPC endpoint to access OBS from an IDC.

+
+

Prerequisites

The required VPC endpoint service already exists.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  1. On the VPC Endpoints page, click Create VPC Endpoint.

    The Create VPC Endpoint page is displayed.

    +
    Figure 1 Create VPC Endpoint
    +
    +

    +
  2. Set the required parameters. +
    + + + + + + + + + + + + + + + + + + + +
    Table 1 Required parameters

    Parameter

    +

    Description

    +

    Region

    +

    Specifies the region where the VPC endpoint is located.

    +

    Resources in different regions cannot communicate with each other over internal networks. Select the nearest region for lower network latency and faster access to resources.

    +

    Service Category

    +

    There are two options: Cloud services or Find a service by name.

    +
    • Cloud services: Select this value if the target VPC endpoint service is a cloud service.
    • Find a service by name: Select this value if the target VPC endpoint service is a private service of your own.
    +

    Example: Cloud services

    +

    Service List

    +

    This parameter is available only when you select Cloud services for Service Category.

    +

    The VPC endpoint service has been created by operations people and you can use it without having to perform the creation operation.

    +

    Select com.t-systems.otc.eu-nl.obs-internet.

    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    Tag

    +

    (Optional) Specifies the VPC endpoint tag, which consists of a key and a value. You can add a maximum of 20 tags to each VPC endpoint.

    +

    Tag keys and values must meet requirements listed in Table 2.

    +
    NOTE:

    If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

    +

    For details about predefined tags, see Predefined Tag Overview.

    +
    +
    +
    + +
    + + + + + + + + + + +
    Table 2 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
  3. Confirm the specifications and click Create Now.
    • If all of the specifications are correct, click Submit.
    • If any of the specifications are incorrect, click Previous to return to the previous page and modify the parameters as needed, and click Submit.
    +
  4. Click Back to VPC Endpoint List after the task is submitted.

    If the status of the VPC endpoint changes from Creating to Accepted, the VPC endpoint for connecting to com.t-systems.otc.eu-nl.obs-internet is created.

    +
  5. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
    Figure 2 Summary of the VPC endpoint
    +
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address
+
+
+ diff --git a/docs/vpcep/umn/vpcep_02_0403.html b/docs/vpcep/umn/vpcep_02_0403.html new file mode 100644 index 000000000..af2fdd8a1 --- /dev/null +++ b/docs/vpcep/umn/vpcep_02_0403.html @@ -0,0 +1,24 @@ + + +

Step 2: Access OBS

+

Scenarios

This section describes how to access OBS using a VPN connection or a direct connection.

+
+

Prerequisites

Your local data center has been connected to your VPC using a VPN or Direct Connect connection.
  • The local subnet of your VPC that interconnects with your VPN connection contains the OBS CIDR block.

    For details about how to create a VPN connection, see Creating a VPN in the Virtual Private Network User Guide.

    +
  • The VPC subnet associated with the virtual gateway contains the OBS CIDR block.

    For details about how to enable Direct Connect, see Getting Started in the Direct Connect User Guide.

    +
+
+
+

Procedure

Configure an OBS route from the local data center to the VPN or Direct Connect gateway.

+

The CIDR block of the VPC endpoint for accessing OBS is a public CIDR block. To access OBS using a VPN connection or direct connection, ensure that traffic from your local data center to OBS is directed to the VPN gateway or Direct Connect gateway.

+

Configure a permanent route at your local data center and specify the Direct Connect or VPN gateway as the next hop for accessing OBS. The following is the example command for configuring such a route:

+

route -p add Public IP address xxx.xxx.xxx.xxx

+
  • Public IP address indicates the address for accessing OBS.
  • xxx.xxx.xxx.xxx indicates the IP address of the Direct Connect or VPN gateway created at your local data center.
+
+
+
+
+
+
Parent topic: Configuring a VPC Endpoint for Accessing OBS with the OBS Public Address
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0100.html b/docs/vpcep/umn/vpcep_03_0100.html new file mode 100644 index 000000000..96c968fa8 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0100.html @@ -0,0 +1,25 @@ + + +

VPC Endpoint Services

+
+
+ +
+ diff --git a/docs/vpcep/umn/vpcep_03_0102.html b/docs/vpcep/umn/vpcep_03_0102.html new file mode 100644 index 000000000..ab91d527b --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0102.html @@ -0,0 +1,166 @@ + + +

Viewing Summary of a VPC Endpoint Service

+

Scenarios

This section describes how to query summary of a VPC endpoint service, including the name, ID, backend resource type, backend resource name, VPC, status, connection approval, service type, and creation time.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  2. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.

    Locate the target VPC endpoint service by entering a filter in the search box in the upper right corner:

    +
    • Search by name or ID.
      1. Select Name or ID in the filter box.
      2. Enter a keyword in the search box.
      3. Click to start the search.

        VPC endpoint services containing the keyword are displayed in the list.

        +
      +
    • Search by preset tag.
      1. Click in Search by Tag.
        Figure 1 Searching by tag
        +
      2. Enter a tag and a value.

        Enter a key or value or select a key or value from the drop-down list.

        +

        You can use a maximum of 20 tags to search for a VPC endpoint service.

        +
      3. Click Search.

        The VPC endpoint service containing the specified tag is displayed in the list.

        +

        If you set multiple tags, VPC endpoint services containing all the specified tags will be displayed.

        +
      +
    +
  3. In the VPC endpoint service list, locate the target VPC endpoint service and click its name to view the details.
    Figure 2 Summary of the VPC endpoint service
    +

    Table 1 describes the parameters displayed on the VPC endpoint service details page.

    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Tab

    +

    Parameter

    +

    Description

    +

    Summary

    +

    Name

    +

    Specifies the name of the VPC endpoint service.

    +

    ID

    +

    Specifies the ID of the VPC endpoint service.

    +

    Backend Resource Type

    +

    Specifies the type of the backend resource that provides services.

    +

    Backend Resource Name

    +

    Specifies the name of the backend resource that provides services to be accessed.

    +

    VPC

    +

    Specifies the VPC where the VPC endpoint service is deployed.

    +

    Status

    +

    Specifies the status of the VPC endpoint service.

    +

    Connection Approval

    +

    Specifies whether connection approval is required.

    +

    Service Type

    +

    Specifies the type of the VPC endpoint service.

    +

    Creation

    +

    Specifies the creation time of the VPC endpoint service.

    +

    Connection Management

    +

    VPC Endpoint ID

    +

    Specifies the ID of the VPC endpoint.

    +

    Packet ID

    +

    Specifies the identifier of the VPC endpoint ID.

    +

    Status

    +

    Specifies the status of the VPC endpoint.

    +

    For details about statuses of VPC endpoint services and VPC endpoints, see What Are Statuses of VPC Endpoint Services and VPC Endpoints?

    +

    Owner

    +

    Specifies the domain ID of the VPC endpoint owner.

    +

    Creation

    +

    Specifies the creation time of the VPC endpoint.

    +

    Operation

    +

    Specifies whether to allow a VPC endpoint to connect to a VPC endpoint service. The option can be Accept or Reject.

    +

    Permission Management

    +

    Authorized Domain ID

    +

    Specifies the authorized domain ID for connecting to the VPC endpoint. The ID can also be *.

    +

    If you add an asterisk (*) to the whitelist, it means that all users can access the VPC endpoint service.

    +

    Operation

    +

    Specifies whether to delete an authorized domain from the whitelist.

    +

    Port Mapping

    +

    +

    Protocol

    +

    Specifies the protocol used for communications between the VPC endpoint service and VPC endpoint.

    +

    Service Port

    +

    Specifies the port provided by the backend service bound to the VPC endpoint service.

    +

    Terminal Port

    +

    Specifies the port provided by the VPC endpoint, allowing you to access the VPC endpoint service.

    +

    Tag

    +

    Key

    +

    Specifies the tag key of the VPC endpoint service.

    +

    Value

    +

    Specifies the tag value of the VPC endpoint service.

    +

    Operation

    +

    Specifies the operation to be performed on the VPC endpoint service tag, for example, you can select Edit or Delete.

    +
    +
    +
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0103.html b/docs/vpcep/umn/vpcep_03_0103.html new file mode 100644 index 000000000..dd057d39d --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0103.html @@ -0,0 +1,21 @@ + + +

Deleting a VPC Endpoint Service

+

Scenarios

This section describes how to delete a VPC endpoint service.

+

Deleted VPC endpoint services cannot be recovered. Exercise caution when performing this operation.

+
+
+

Constraints

  • The VPC endpoint services configured from your private services can be deleted, but those configured by the system cannot.
  • Any VPC endpoint service that has VPC endpoints in Accepted or Creating status cannot be deleted.

    For statuses of a VPC endpoint, see What Are Statuses of VPC Endpoint Services and VPC Endpoints?

    +

    +
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click Delete in the Operation column.
    Figure 1 Delete VPC Endpoint Service
    +
  3. Click Yes.
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0104.html b/docs/vpcep/umn/vpcep_03_0104.html new file mode 100644 index 000000000..371512f1c --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0104.html @@ -0,0 +1,19 @@ + + +

Managing Connections of a VPC Endpoint Service

+

Scenarios

To connect a VPC endpoint to a VPC endpoint service that has connection approval enabled, obtain the approval from the owner of the endpoint service.

+

This section describes how to accept or reject connection of a VPC endpoint.

+
+

Prerequisites

There is a VPC endpoint available for connecting to the target VPC endpoint service.

+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. Select the Connection Management tab.
    Figure 1 Connection Management
    +
  4. Accept or reject connection of a VPC endpoint in the list based on service requirements.
    • If you click Accept, the VPC endpoint can connect to the VPC endpoint service.
    • If you click Reject, the VPC endpoint cannot connect to the VPC endpoint service.
    +
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0105.html b/docs/vpcep/umn/vpcep_03_0105.html new file mode 100644 index 000000000..143b2ba08 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0105.html @@ -0,0 +1,24 @@ + + +

Managing Whitelist Records of a VPC Endpoint Service

+

Scenarios

Permission management controls the access of a VPC endpoint in one domain to a VPC endpoint service in another.

+

After a VPC endpoint service is created, you can add an authorized domain ID to or delete it from the whitelist of the endpoint service.

+
  • If the whitelist is empty, access from a VPC endpoint in another domain is not allowed.
  • If an authorized domain ID is already in the whitelist, you can use this domain to create a VPC endpoint for connecting to the VPC endpoint service.
  • If an authorized domain ID is not in the whitelist, you cannot use this domain to create a VPC endpoint for connecting to the VPC endpoint service.
+

This section describes how to add or delete a whitelist record for a VPC endpoint service.

+
+

Add a Whitelist Record

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. On the displayed page, select the Permission Management tab and click Add to Whitelist.
  4. Enter an authorized domain ID in the required format and click OK.
    Figure 1 Add to Whitelist
    +
    • Your domain is in the whitelist of your VPC endpoint service by default.
    • The authorized domain ID is in the iam:domain::domain_id format.

      domain_id indicates the ID of the authorized domain, for example, iam:domain::1564ec50ef2a47c791ea5536353ed4b9

      +
    • Adding * to the whitelist means that all users can access the VPC endpoint service.
    +
    +
+
+

Delete a Whitelist Record

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. On the displayed page, select the Permission Management tab, locate the target domain ID, and click Delete in the Operation column.

    To delete multiple whitelist records, select all the target domain IDs and click Delete in the upper left corner.

    +
  4. Click Yes.
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0106.html b/docs/vpcep/umn/vpcep_03_0106.html new file mode 100644 index 000000000..35e76ac18 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0106.html @@ -0,0 +1,18 @@ + + +

Viewing Port Mappings of a VPC Endpoint Service

+

Scenarios

After a VPC endpoint service is created, you can view the added port mappings.

+

A port mapping defines the protocol and ports used for communications between a VPC endpoint and a VPC endpoint service.

+
  • Protocol: A protocol both supported by the VPC endpoint and VPC endpoint service
  • Service Port: A service port is provided by the backend service bound to the endpoint service.
  • Terminal Port: A terminal port is provided by the VPC endpoint, allowing you to access the VPC endpoint service.
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. On the displayed page, select the Port Mapping tab.
    The port mapping configured for the VPC endpoint service is displayed.
    Figure 1 Port Mapping
    +
    +
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0107.html b/docs/vpcep/umn/vpcep_03_0107.html new file mode 100644 index 000000000..0fe24cdd5 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0107.html @@ -0,0 +1,78 @@ + + +

VPC Endpoint Service Overview

+

A VPC endpoint service is a cloud service or a private service that can be accessed through a VPC endpoint.

+
There are two types of VPC endpoint services: gateway and interface.
  • Gateway VPC endpoint services are created only for cloud services.
  • Interface VPC endpoint services can be created for both cloud services and your private services. All VPC endpoint services for cloud services are created by default while those for private services need to be created by users themselves.
+
+

Supported cloud services vary in different regions. For details, see the list of services that can be configured on the management console.

+
+

This section describes how to configure a VPC endpoint service (interface type) from your private service and how to manage it.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Management of VPC endpoint services

Operation

+

Description

+

Constraint

+

Creating a VPC Endpoint Service

+

Describes how to configure a private service as a VPC endpoint service.

+
  • VPC endpoint services are region-level resources. Select a region and project when you create such a service.
  • Each tenant can create a maximum of 20 VPC endpoint services.
  • The following private services can be configured into VPC endpoint services:
    • Elastic load balancer: Backend resources of this type suit services that receive high access traffic and demand high reliability and disaster recovery (DR) performance.
    • ECS: Backend resources of this type serve as servers.
    • BMS: Backend resources of this type serve as servers.
    +
  • One VPC endpoint service corresponds to only one backend resource.
+

Viewing Summary of a VPC Endpoint Service

+

Describes how to query details of a VPC endpoint service.

+

None

+

Deleting a VPC Endpoint Service

+

Describes how to delete a VPC endpoint service.

+
  • Deleted VPC endpoint services cannot be recovered. Exercise caution when performing this operation.
  • Only VPC endpoint services configured from users' private services can be deleted.
  • VPC endpoint services in the Accepted or Creating state cannot be deleted.
+

Managing Connections of a VPC Endpoint Service

+

Describes how to set connection approval of a VPC endpoint service to determine whether to allow a VPC endpoint to connect to the VPC endpoint service.

+

You can specify whether to allow a VPC endpoint to connect to a VPC endpoint service only when connection approval is enabled during VPC endpoint service creation.

+

Managing Whitelist Records of a VPC Endpoint Service

+

Describes how to manage whitelist records of a VPC endpoint service to control across-account access between a VPC endpoint and a VPC endpoint service.

+
  • The VPC endpoint must be in the same region as the VPC endpoint service.
  • Before you configure the whitelist for a VPC endpoint service, obtain the domain ID of the associated VPC endpoint.
+

Viewing Port Mappings of a VPC Endpoint Service

+

Describes how to view the port mapping between a VPC endpoint and a VPC endpoint service, including the supported protocol, service port, and terminal port.

+
  • Configuring a port mapping is required when you create a VPC endpoint service.
  • After a VPC endpoint service is created, you can view its port mappings but cannot modify them.
+

Managing Tags of a VPC Endpoint Service

+

Describes how to manage VPC endpoint service tags, including viewing, adding, editing, and deleting tags.

+

A maximum of 20 tags can be added to each VPC endpoint service.

+
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0108.html b/docs/vpcep/umn/vpcep_03_0108.html new file mode 100644 index 000000000..62d3b21d2 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0108.html @@ -0,0 +1,50 @@ + + +

Managing Tags of a VPC Endpoint Service

+

Scenarios

After a VPC endpoint service is created, you can view its tags, or add, edit, or delete a tag.

+

A tag is a unique identifier of each VPC endpoint service, and it consists of a tag key and a tag value. You can add a maximum of 20 tags to each VPC endpoint service.

+

If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

+

For details about predefined tags, see Predefined Tag Overview.

+
+
+

Add a Tag

Perform the following operations to add a tag for an existing VPC endpoint service:

+
  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. On the displayed page, select the Tags tab.
  4. Click Add Tag.
  5. In the displayed dialog box, enter a key and a value.
    Table 1 describes the required parameters. +
    + + + + + + + + + + +
    Table 1 Tag requirements for VPC endpoint services

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
    +
  6. Click OK.
+
+

Edit a Tag

Perform the following operations to edit a tag of a VPC endpoint service:

+
  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. On the displayed page, select the Tags tab.
  4. In the tag list, locate the target tag and click Edit in the Operation column.
  5. Enter a new value.

    You can only edit tags that have values.

    +
    +
  6. Click OK.
+
+

Delete a Tag

Perform the following operations to delete a tag of a VPC endpoint service:

+

Deleted tags cannot be recovered. Exercise caution when performing this operation.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoint Services.
  2. In the VPC endpoint service list, locate the target VPC endpoint service and click its name.
  3. On the displayed page, select the Tags tab.
  4. In the tag list, locate the target tag and click Delete in the Operation column.
  5. Click Yes.
+
+
+
+
+
Parent topic: VPC Endpoint Services
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0200.html b/docs/vpcep/umn/vpcep_03_0200.html new file mode 100644 index 000000000..46bcf2e30 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0200.html @@ -0,0 +1,19 @@ + + +

VPC Endpoints

+
+
+ +
+ diff --git a/docs/vpcep/umn/vpcep_03_0202.html b/docs/vpcep/umn/vpcep_03_0202.html new file mode 100644 index 000000000..8b70ef115 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0202.html @@ -0,0 +1,120 @@ + + +

Querying and Accessing a VPC Endpoint

+

Scenarios

After a VPC endpoint is created, you can query its details and access it.

+
+

Querying a VPC Endpoint

Perform the following operations to query details about a VPC endpoint, including the ID, associated VPC endpoint service name, VPC, and status.

+
  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.

    On the displayed page, locate the target VPC endpoint by entering a keyword in the search box in the upper right corner:

    +
    • Search by VPC endpoint service name or VPC endpoint ID.
      1. Select VPC endpoint service name or ID in the filter box.
      2. Enter a keyword in the search box.
      3. Click to start the search.

        VPC endpoints containing the keyword are displayed in the VPC endpoint list.

        +
      +
    • Search by preset tag.
      1. Click in Search by Tag.
        Figure 1 Searching by tag
        +
      2. Enter a tag and a value.

        Enter a key or value or select a key or value from the drop-down list.

        +

        You can use a maximum of 20 tags to search for a VPC endpoint.

        +
      3. Click Search.

        VPC endpoints containing the specified tag are displayed in the VPC endpoint list.

        +

        If you set multiple tags, VPC endpoints containing all the specified tags will be displayed.

        +
      +
    +
  2. In the VPC endpoint list, click the ID of the target VPC endpoint to view its details.
    After an interface VPC endpoint is created, a private IP address is assigned together with a private domain name if you select Create a Private Domain Name.
    Figure 2 Summary of the VPC endpoint
    +
    + +
    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    Table 1 Parameter description

    Tab

    +

    Parameter

    +

    Description

    +

    Summary

    +

    ID

    +

    Specifies the ID of the VPC endpoint.

    +

    VPC

    +

    Specifies the VPC where the VPC endpoint is deployed.

    +

    VPC Endpoint Service Name

    +

    Specifies the name of the VPC endpoint service that the VPC endpoint is used to access.

    +

    Private IP Address

    +

    Specifies the IP address for accessing the VPC endpoint.

    +

    Private Domain Name

    +

    Specifies the private domain name for accessing the VPC endpoint.

    +

    Status

    +

    Specifies the status of the VPC endpoint.

    +

    Type

    +

    Specifies the type of the VPC endpoint service that the VPC endpoint is used to access.

    +

    Created

    +

    Specifies the creation time of the VPC endpoint.

    +

    Tags

    +

    Key

    +

    Specifies the tag key of the VPC endpoint.

    +

    Value

    +

    Specifies the tag value of the VPC endpoint.

    +

    Operation

    +

    Specifies the operation to be performed on the VPC endpoint tag, for example, you can select Edit or Delete.

    +
    +
    +
+
+

Accessing a VPC Endpoint Using a Private IP Address

Perform the following operations to access a VPC endpoint using its private IP address:

+
  1. In the VPC that the VPC endpoint belongs to, log in to the backend resource, for example, an ECS.
  2. Select a command based on the backend resource type and run the command to access the VPC endpoint. The command format is as follows:

    Command Private IP address:Port number

    +

    The following is a command example:

    +

    curl Private IP address:Port number

    +
+
+

Accessing a VPC Endpoint (Using a Private Domain Name)

You can access a VPC endpoint using its private domain name if you select Create a Private Domain Name when creating the endpoint.

+

The system automatically creates a private zone for the generated domain name and adds A record set for the private zone to resolve the domain name into the private IP address of the VPC endpoint.

+

You can view the corresponding private zone and its resolution records on the DNS console. For more information, see Configuring a Private Zone.

+

Viewing the record set of the private domain name

+
  1. Log in to the management console.
  2. In the service list, choose Network > Domain Name Service.

    The DNS console is displayed.

    +
  3. In the navigation pane, choose Private Zones.

    The Private Zones page is displayed.

    +
  1. In the private zone list, click the name of the target private zone.

    The record set page is displayed.

    +
  2. In the record set list, locate the target A record set and view its information.
    When Status changes to Normal, the resolution takes effect.
    Figure 3 Record set of the private domain name
    +
    +
+

Accessing a VPC endpoint using a private domain name

+
  1. In the VPC that the VPC endpoint belongs to, log in to the backend resource, for example, an ECS.
  2. Select a command based on the backend resource type and run the command to access the VPC endpoint. The command format is as follows:

    Command Private domain name:Port number

    +

    The following is a command example:

    +

    curl Private domain name:Port number

    +
+
+
+
+
+
Parent topic: VPC Endpoints
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0203.html b/docs/vpcep/umn/vpcep_03_0203.html new file mode 100644 index 000000000..958e28ed3 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0203.html @@ -0,0 +1,17 @@ + + +

Deleting a VPC Endpoint

+

Scenarios

This section describes how to delete a VPC endpoint.

+

Deleted VPC endpoints cannot be recovered. Exercise caution when performing this operation.

+
+
+

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  3. Choose Service List > Networking > VPC Endpoint.
  4. In the navigation pane on the left, choose VPC Endpoint > VPC Endpoints.
  5. In the VPC endpoint list, locate the target VPC endpoint and click Delete in the Operation column.
    Figure 1 Delete VPC Endpoint
    +
  6. Click Yes.
+
+
+
+
+
Parent topic: VPC Endpoints
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0204.html b/docs/vpcep/umn/vpcep_03_0204.html new file mode 100644 index 000000000..dfb8efb1f --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0204.html @@ -0,0 +1,53 @@ + + +

VPC Endpoint Overview

+

VPC endpoints are secure and private channels for connecting VPCs to VPC endpoint services.

+

You can create a VPC endpoint to connect a resource in your VPC to a VPC endpoint service in another VPC of the same region.

+

This section describes how to create and manage a VPC endpoint.

+ +
+ + + + + + + + + + + + + + + + + + + + + +
Table 1 Management of VPC endpoints

Operation

+

Description

+

Constraint

+

Creating a VPC Endpoint

+

Describes how to create a VPC endpoint.

+
  • VPC endpoints are region-level resources. Select a region and project when you create such an endpoint.
  • Each tenant can create a maximum of 50 VPC endpoints.
  • When you create a VPC endpoint, ensure that the associated VPC endpoint service exists and is in the same region as the VPC endpoint.
+

Querying and Accessing a VPC Endpoint

+

Describes how to query summary of a VPC endpoint.

+

A VPC endpoint supports a maximum of 3,000 concurrent requests.

+

Deleting a VPC Endpoint

+

Describes how to delete a VPC endpoint.

+

Deleted VPC endpoints cannot be recovered. Exercise caution when performing this operation.

+

Managing Tags of a VPC Endpoint

+

Describes how to manage VPC endpoint tags, including viewing, adding, editing, and deleting tags.

+

A maximum of 20 tags can be added to each VPC endpoint.

+
+
+
+
+
+
Parent topic: VPC Endpoints
+
+
+ diff --git a/docs/vpcep/umn/vpcep_03_0206.html b/docs/vpcep/umn/vpcep_03_0206.html new file mode 100644 index 000000000..33bc97982 --- /dev/null +++ b/docs/vpcep/umn/vpcep_03_0206.html @@ -0,0 +1,50 @@ + + +

Managing Tags of a VPC Endpoint

+

Scenarios

After a VPC endpoint is created, you can view its tags, or add, edit, or delete a tag.

+

Each VPC endpoint has a unique tag, which consists of a tag key and a tag value. You can add a maximum of 20 tags to each VPC endpoint.

+

If a predefined tag has been created on TMS, you can directly select the corresponding tag key and value.

+

For details about predefined tags, see Predefined Tag Overview.

+
+
+

Add a Tag

Perform the following operations to add a tag for an existing VPC endpoint:

+
  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the VPC endpoint list, locate the target VPC endpoint and click its ID.
  1. On the displayed page, select the Tags tab.
  2. Click Add Tag.
  3. In the displayed dialog box, enter a key and a value.
    Table 1 describes the required parameters. +
    + + + + + + + + + + +
    Table 1 Tag requirements for VPC endpoints

    Parameter

    +

    Requirement

    +

    Tag key

    +
    • Cannot be left blank.
    • Must be unique for each resource.
    • Can contain a maximum of 36 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +

    Tag value

    +
    • Cannot be left blank.
    • Can contain a maximum of 43 Unicode characters.
    • Can contain only letters, digits, hyphens (-), and underscores (_).
    +
    +
    +
    +
  4. Click OK.
+
+

Edit a Tag

Perform the following operations to edit a tag of a VPC endpoint:

+
  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the VPC endpoint list, locate the target VPC endpoint and click its ID.
  1. On the displayed page, select the Tags tab.
  2. In the tag list, locate the target tag and click Edit in the Operation column.
  3. Enter a new value.

    You can only edit tags that have values.

    +
    +
  4. Click OK.
+
+

Delete a Tag

Perform the following operations to delete a tag of a VPC endpoint:

+

Deleted tags cannot be recovered. Exercise caution when performing this operation.

+
+
  1. Log in to the management console.
  2. Click in the upper left corner and select the required region and project.
  1. Choose Service List > Networking > VPC Endpoint.
  1. In the VPC endpoint list, locate the target VPC endpoint and click its ID.
  1. On the displayed page, select the Tags tab.
  1. In the tag list, locate the target tag and click Delete in the Operation column.
  2. Click Yes.
+
+
+
+
+
Parent topic: VPC Endpoints
+
+
+ diff --git a/docs/vpcep/umn/vpcep_04_0000.html b/docs/vpcep/umn/vpcep_04_0000.html new file mode 100644 index 000000000..c8bd20dfb --- /dev/null +++ b/docs/vpcep/umn/vpcep_04_0000.html @@ -0,0 +1,17 @@ + + +

FAQ

+
+
+ +
+ diff --git a/docs/vpcep/umn/vpcep_04_0004.html b/docs/vpcep/umn/vpcep_04_0004.html new file mode 100644 index 000000000..fb919fb2b --- /dev/null +++ b/docs/vpcep/umn/vpcep_04_0004.html @@ -0,0 +1,64 @@ + + +

What Are the Differences Between VPC Endpoints and VPC Peering Connections?

+

Table 1 describes differences between VPC endpoints and VPC peering connections.

+

VPC endpoints and VPC peering connections are two different resources. You can configure either of them based on your connectivity needs.

+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 Differences

Category

+

VPC Peering Connection

+

VPC Endpoint

+

Security

+

All resources in a VPC, such as ECSs and load balancers, can be accessed.

+

Allows access to a specific service or application. Only the ECSs and load balancers in the VPC for which VPC endpoint services are created can be accessed.

+

CIDR block overlap

+

Not supported

+

If two VPCs have overlapping subnets, the VPC peering connection will not work.

+

Supported

+

If you use a VPC endpoint to connect two VPCs, you do not have to worry about overlapping subnets.

+

Communications mode

+

VPCs connected through a peering connection can communicate with each other.

+

Requests can only be initiated from a VPC endpoint to a VPC endpoint service, but not the other way around.

+

Route configuration

+

If a peering connection is established between two VPCs, add routes to the VPCs so that they can communicate with each other.

+

For two VPCs that are connected through a VPC endpoint, the route has been configured, and you do not need to configure it again.

+

Access using VPN/Direct Connect

+

Supported

+

You can create a VPC Peering connection to connect your local data center to a cloud service using a VPN connection or a direct connection.

+

Supported

+

You can create a VPC endpoint to connect your local data center to a cloud service using a VPN connection or a direct connection over an internal network.

+
+
+
+
+
+
Parent topic: FAQ
+
+
+ diff --git a/docs/vpcep/umn/vpcep_04_0005.html b/docs/vpcep/umn/vpcep_04_0005.html new file mode 100644 index 000000000..8a59d698d --- /dev/null +++ b/docs/vpcep/umn/vpcep_04_0005.html @@ -0,0 +1,87 @@ + + +

What Are Statuses of VPC Endpoint Services and VPC Endpoints?

+
Table 1 describes statuses of a VPC endpoint service and their meanings. +
+ + + + + + + + + + + + + + + + + + + +
Table 1 Statuses of a VPC endpoint service

Status

+

Description

+

Creating

+

Indicates that the VPC endpoint service is being created.

+

Available

+

Indicates that the VPC endpoint service is created and can accept a VPC endpoint.

+

Failed

+

Indicates that the VPC endpoint service fails to be created.

+

Deleting

+

Indicates that the VPC endpoint service is being deleted.

+

Deleted

+

Indicates that the VPC endpoint service has been deleted.

+
+
+
+
Table 2 describes statuses of a VPC endpoint and their meanings. +
+ + + + + + + + + + + + + + + + + + + + + + +
Table 2 Statuses of a VPC endpoint

Status

+

Description

+

Pending acceptance

+

Indicates that the VPC endpoint is pending acceptance of the owner of the associated VPC endpoint service.

+

Creating

+

Indicates that the VPC endpoint is connecting to the associated VPC endpoint service.

+

Accepted

+

Indicates that the VPC endpoint is accepted by the associated VPC endpoint service.

+

Rejected

+

Indicates that the VPC endpoint is rejected by the associated VPC endpoint service.

+

Failed

+

Indicates that the VPC endpoint fails to connect to the associated VPC endpoint service.

+

Deleting

+

Indicates that the VPC endpoint is being deleted.

+
+
+
+
+
+
+
Parent topic: FAQ
+
+
+ diff --git a/docs/vpcep/umn/vpcep_0_0002.html b/docs/vpcep/umn/vpcep_0_0002.html new file mode 100644 index 000000000..d73cd08c7 --- /dev/null +++ b/docs/vpcep/umn/vpcep_0_0002.html @@ -0,0 +1,33 @@ + + +

Change History

+
+
+ + + + + + + + + + + + + +

Released On

+

Description

+

2021-02-01

+

This release incorporates the following changes:

+ +

2020-11-02

+

This release incorporates the following changes:

+

Modified the format description of whitelist records in Step 2: Add a Whitelist Record and Managing Whitelist Records of a VPC Endpoint Service.

+

2020-07-15

+

This issue is the first official release.

+
+
+
+ diff --git a/docs/vpcep/umn/vpcep_0_0003.html b/docs/vpcep/umn/vpcep_0_0003.html new file mode 100644 index 000000000..8bbf4164f --- /dev/null +++ b/docs/vpcep/umn/vpcep_0_0003.html @@ -0,0 +1,7 @@ + + +

Glossary

+

For details about the terms involved in this document, see Glossary.

+
+
+ diff --git a/docs/vpcep/umn/vpcep_qs_0001.html b/docs/vpcep/umn/vpcep_qs_0001.html new file mode 100644 index 000000000..0ae043635 --- /dev/null +++ b/docs/vpcep/umn/vpcep_qs_0001.html @@ -0,0 +1,36 @@ + + +

Operation Guide

+

This section uses examples to describe how to use VPCEP.

+

You can use VPCEP on the VPCEP console. For more information, see What Is VPC Endpoint?

+

Application Scenarios

VPCEP is a perfect fit in different scenarios. For details, see Table 1.

+ +
+ + + + + + + + + + +
Table 1 Application scenarios

Scenario

+

Description

+

Communications between cloud resources across VPCs in the same region

+

You can create a VPC endpoint service and a VPC endpoint to access cloud services across VPCs. For details, see the following sections:

+ +

Access to cloud resources from an on-premises data center

+

VPCEP allows you to access cloud resources from your local data center. For details, see the following sections:

+ +
+
+
+
+
+
+
Parent topic: Getting Started
+
+
+