All Products
Search

This Product

    Object Storage Service:Cannot ping an OSS internal endpoint from an ECS instance

    Document Center

    Object Storage Service:Cannot ping an OSS internal endpoint from an ECS instance

    Last Updated:Mar 20, 2026

    Ping is blocked on OSS internal endpoints by design, for security reasons. A failed ping does not mean your Elastic Compute Service (ECS) instance cannot reach Object Storage Service (OSS). Use curl or telnet to verify connectivity instead.

    Verify connectivity

    Using curl

    Run the following command to send an HTTP HEAD request to an object via the internal endpoint:

    curl -I http://<bucket-name>.<oss-internal-endpoint>/<object-name>

    Replace the placeholders with your actual values:

    PlaceholderDescriptionExample
    <bucket-name>Name of the bucketmy-bucket
    <oss-internal-endpoint>Internal endpoint for the bucket's regionoss-cn-hangzhou-internal.aliyuncs.com
    <object-name>Name of the objectsample.txt

    A successful connection returns HTTP/1.1 200 OK:

    HTTP/1.1 200 OK
Server: AliyunOSS
...

    Using telnet

    Run the following command to test TCP connectivity to port 80:

    telnet <bucket-name>.<oss-internal-endpoint> 80

    A successful connection returns:

    Trying 10.x.x.x...
Connected to <bucket-name>.<oss-internal-endpoint>.
Escape character is '^]'.

    If curl or telnet also fails

    Check the following in order:

    1. Confirm the ECS instance and OSS bucket are in the same region. Internal endpoints are only reachable from within the same region.

    2. Confirm the internal endpoint is correct. Copy the endpoint directly from the OSS console to avoid typos. For a full list of internal endpoints by region, see Regions and endpoints.