This topic describes how to delete and export website configurations in batch.
Delete website configurations
If your website no longer needs anti-DDoS protection, you can delete the website. Before you perform this operation, you must update the DNS records and ensure that the DNS record values are not any of the following: the Anti-DDoS Proxy instance IP, the CNAME assigned by Anti-DDoS Proxy, or the CNAME assigned by security traffic manager. If you do not update the DNS records before you delete the website, services may be interrupted.
The domain names and port forwarding configurations are automatically deleted one month after all Anti-DDoS Proxy instances under your Alibaba Cloud account are released. If you have multiple Anti-DDoS Proxy instances, the domain names and port forwarding configurations are automatically deleted one month after the last instance is released.
Log on to the Website Config page in the Anti-DDoS Proxy console.
In the top navigation bar, select the region of your instance.
Anti-DDoS Proxy (Chinese Mainland): Choose the Chinese Mainland region.
Anti-DDoS Proxy (Outside Chinese Mainland): Choose the Outside Chinese Mainland region.
On the Website Config page, find the target website configuration and click Delete in the Actions column.
In the dialog box that appears, confirm and click Delete.
NoteIf you want to delete multiple website configurations, you can select them and click Batch Delete below the website list.
Export website configurations in batch
You can export all website configurations from Anti-DDoS Proxy in XML format and download them. The format of the exported website configurations is the same as that used for batch import and modification of website configurations.
Log on to the Website Config page in the Anti-DDoS Proxy console.
In the top navigation bar, select the region of your instance.
Anti-DDoS Proxy (Chinese Mainland): Choose the Chinese Mainland region.
Anti-DDoS Proxy (Outside Chinese Mainland): Choose the Outside Chinese Mainland region.
Below the website list, click Batch Export to submit an export task, and click OK.
Click Tasks in the upper-right corner of the page to check the export progress.
After the export task is complete, in the Tasks panel, click Download in the Actions column to download the file.
NoteIf the current task status is Pending, wait for the export task to complete.
After downloading the file, you can use a text editor to open the downloaded .xml file and view the website configurations.
NoteIf you use Anti-DDoS Proxy (Chinese Mainland), the name of the export file starts with DDoSCoo_. For Anti-DDoS Proxy (Outside Chinese Mainland), the name of the export file starts with DDoSDip_. The file formats for both exports are the same.
(Optional) In the Tasks panel, find the task that you no longer need and click Delete in the Actions column.
Appendix: Website configurations in an XML file
You can import, modify, or export multiple website configurations at a time by using an XML file.
Parameters
The website configurations in an XML file start with the <DomainList> tag, end with the </DomainList> tag, and include the parameters for multiple websites between two tags. Each website's configurations start with the <DomainConfig> tag and end with the </DomainConfig> tag, with the parameters for each website included between these tags. The parameters are illustrated in the following table.
An additional tag pair <DomainConfig>......</DomainConfig> is required for each additional website configuration.
Parameter | Description |
| The domain name that you want to add to an instance. You can enter only one domain name in a tag pair. |
| The protocol type of the domain name. Separate multiple protocol types with commas (,). In this example, the protocol types of the domain name are HTTP and HTTPS. |
| The instances to which you want to add the domain name. Note Each instance has a unique ID. Include the instance IDs in the <InstanceList> tag pair. Separate multiple instance IDs with commas (,). |
| The information about the origin server. The configurations include the following parameters:
Note To add the domain name of an origin server to an instance, you can use either the IP address or the domain name of the origin server. |
Example
<DomainList>
<DomainConfig>
<Domain>example.aliyundoc.com</Domain>
<ProtocolConfig>
<ProtocolList>http,https</ProtocolList>
</ProtocolConfig>
<InstanceConfig>
<InstanceList>ddoscoo-cn-zvp2eibz****</InstanceList>
</InstanceConfig>
<RealServerConfig>
<ServerType>0</ServerType>
<ServerList>192.0.XX.XX</ServerList>
</RealServerConfig>
</DomainConfig>
<DomainConfig>
<Domain>demo.aliyundoc.com</Domain>
<ProtocolConfig>
<ProtocolList>http,websocket,websockets</ProtocolList>
</ProtocolConfig>
<InstanceConfig>
<InstanceList>ddoscoo-cn-7pp2e74f****, ddoscoo-cn-2r42e12c****</InstanceList>
</InstanceConfig>
<RealServerConfig>
<ServerType>1</ServerType>
<ServerList>learn.aliyundoc.com</ServerList>
</RealServerConfig>
</DomainConfig>
</DomainList>In this example, the following website configurations are added:
Website A: The domain name is example.aliyundoc.com. The protocols are HTTP and HTTPS. The instance to which the domain name is added is ddoscoo-cn-zvp2eibz****. The IP address of the origin server is 192.0.XX.XX.
Website B: The domain name is demo.aliyundoc.com. The protocols are HTTP, WebSocket, and WebSockets. The instances to which the domain name is added are ddoscoo-cn-7pp2e74f**** and ddoscoo-cn-2r42e12c****. The domain name of the origin server is learn.aliyundoc.com.