Why transferring files from Droplet to Spaces is counting as Public Bandwitch?

I’m copying files from my droplet located in NYC3 region to my new Spaces bucket also located in NYC3 region. The total filesize is 18GB.

When I look on my droplet graphs page, it’s counting as public bandwitch. Is this right? I’m accessing the Spaces bucket using https://{bucketname} Is there any kind of “private address”?



Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

because spaces endpoints (currently) exist only within the public ip space i think it won’t matter whether you have a private ip or not because Spaces outbound is public only. i’d like to see private endpoints but have no idea if that’s planned. for what it’s worth, below may address the root concern you may have here.

there are no bandwidth charges to/from Spaces/Droplets so long as the the Spaces objects and Droplets exist within the same regional datacenter.


no answer yet (at the above link) as to whether or not both Spaces & Droplet must be owned by the same user account.

Do you have a private network adapter configured?