Cannot access EODATA on NSIS Cloud

If you cannot access EODATA, first identify the access method you are using and then follow the troubleshooting guidance in the relevant article:

If the problem persists, use the checklist below to narrow down the cause.

Troubleshooting checklist

No. 1 Check that the virtual machine is attached to the EODATA network

Make sure that your virtual machine is connected to the network that provides access to EODATA. Depending on the cloud and configuration, this network may be called eodata or have a name that begins with eodata_.

No. 2 Check the IP configuration of the virtual machine

Verify that the virtual machine has received an IP address on the network used for EODATA access. If the network attachment exists but no suitable IP configuration is present, access to EODATA may fail.

No. 3 Check that the EODATA endpoint is reachable

Verify that the endpoint used by your access method can be reached from the virtual machine. If the endpoint is not reachable, the problem is likely related to networking, routing, DNS resolution, or the selected endpoint configuration.

No. 4 If you are using a mount-based method, restart or recreate the mount

If you access EODATA through a mounted directory, such as with S3FS or goofys, verify that the mount is still active. If needed, unmount it and mount it again, or restart the relevant mount service if your setup uses one.

No. 5 If you are using a credential-based method, verify credentials and endpoint settings

If you access EODATA using tools such as s3cmd or boto3, verify that:

  • the access and secret keys are correct

  • the endpoint is correct for the cloud and region you are using

  • the configuration does not force an incorrect bucket hostname or path style

  • the path, prefix, or key that you are trying to access really exists

No. 6 Check whether the problem is related to the selected path rather than to EODATA access itself

Sometimes access to EODATA works correctly, but the specific path, object key, or product used in a command no longer exists or is different from the example used in the article. If possible, first list the parent location and then copy an existing path from the output.

No. 7 Repeat the test with the article that matches your access method

Once you have checked the points above, return to the article that matches the method you are using and repeat the test with its verified example.

What To Do Next

If you are still unable to access EODATA, return to the article for the specific method you are using and review its prerequisites, endpoint settings, and examples again.

If the problem continues after that, collect the exact command, script, or error message that fails and use it for further troubleshooting.