Use an ECS instance that runs Ubuntu to configure a reverse proxy for access to OSS

Procedure

1. Create an ECS instance that runs Ubuntu. Make sure that the instance and the bucket you want to access are located within the same region.
   The Ubuntu 18.04 (64-bit) system is used in this example. For more information, see Create an ECS instance.
2. Log on to the ECS instance as the root user. Update the APT sources.

   root@test:~# apt-get update

3. Install NGINX.

   root@test:~# apt-get install nginx

   Note By default, the files of NGINX are installed in the following paths:

    /usr/sbin/nginx       Stores the NGINX executable. 
    /etc/nginx            Stores configuration files. 
    /usr/share/nginx      Stores static files. 
    /var/log/nginx        Stores log files.

4. Open the configuration file of NGINX.

   root@test:~# vi /etc/nginx/nginx.conf

5. Add the following content to the http context of the configuration file:

   server {
           listen 80;
           server_name 47.**.**.73; 
   
           location / {
               proxy_pass http://bucketname.oss-cn-beijing-internal.aliyuncs.com; 
               #proxy_set_header Host $host; 
        }  
   }

   • server_name: the IP address used to provide the reverse proxy service, which is the public IP address of the ECS instance.
   • proxy_pass: the endpoint for redirection.
     • When the ECS instance and the bucket that you want to access are located within the same region, specify the internal endpoint of the bucket. For more information about endpoints, see OSS domain names.
     • When the ECS instance and the bucket that you want to access are located in different regions, specify the public endpoint of the bucket.
     • For security reasons, when you access an image or web page object in a bucket by using the default domain name of the bucket in a browser, the object is downloaded. To preview the object in your browser, map a custom domain name to the bucket in which the object is stored and add the custom domain name to the value of proxy_pass. For more information about how to map a custom domain name to a bucket, see Map custom domain names.
   • proxy_set_header Host $host: If you add this parameter, the host value is replaced with the IP address of the ECS instance when NGINX sends a request to OSS. You must add this parameter in the following scenarios:
     • Signature errors occur.
     • The custom domain name that is mapped to the bucket is resolved to the public IP address of the ECS instance. You must preview image or web page objects in the bucket by using a browser. You can map the custom domain name to the bucket for which a reverse proxy is configured without adding a CNAME record for the custom domain name. In this case, you can set proxy_pass to the internal or public endpoint of the bucket. For more information about how to map a custom domain name to a bucket, see Map custom domain names.

   Notice

   • A demo environment is used in this topic as an example. For data security reasons, we recommend that you configure the https context. For more information, see Configure HTTPS for your custom domain name in OSS by using reverse proxy.
   • You can configure a reverse proxy for only one bucket if you use this configuration method.
6. Go to the directory in which the NGINX executable file is located. Start NGINX.

   root@test:~# cd /usr/sbin/
   root@test:~# ./nginx

7. Enable TCP port 80 of the ECS instance.
   By default, NGINX uses TCP port 80. Therefore, you must enable TCP port 80 when you configure a security group for the ECS instance. For more information, see Add security group rules.
8. Add the object path to the public IP address of the ECS instance to access OSS resources.

References