0

I'm setting up a storage bucket transfer from GC to an external S3-compatible service (Digital Ocean), as specified here. Everything seems to be ready (i.e., pool, active agent, and a transfer job calculating size for almost 2 hours!?), but I am curious about the endpoint used as a sink by the agent installed using the default process specified here.

Both the documentation listed here talk about how to specify the KEY and SECRET, but not the endpoint. What is it? Why can't I clearly say where (endpoint) a data transfer should go, as I do for the KEY and SECRET? Am I missing something here?

Nigini
  • 454
  • 1
  • 5
  • 16
  • Investigating other transfer options I've found the `gsutil` approach (https://stackoverflow.com/questions/62005171/) which led me to learn about the `.boto` configuration file (https://cloud.google.com/storage/docs/boto-gsutil), which has the `s3_host` option. It has worked using `gsutil`, so I imagine that something similar needs to be added to the GSC Transfer agent. – Nigini Nov 22 '22 at 01:10
  • mentioned in this [document](https://docs.digitalocean.com/reference/api/spaces-api/#:~:text=endpoint%3A%20'https%3A%2F%2Fnyc3.,the%20control%20panel%2C%20under%20Settings.) you can find your endpoint in the control panel, under Settings – Sathi Aiswarya Dec 13 '22 at 08:45

1 Answers1

0

The endpoint needs to be provided when creating an actual transfer job using an agent for which you specified the KEY and SECRET.

mwol
  • 99
  • 7