You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
relevant costs for EOTDL dataset/model hosting and delivery (free + premium):
Base Load: machines for EOTDL API + supporting services.
Free Tier: fixed machine pool for free users.
Premium Tier: autoscaling pool (larger/GPU-enabled) for premium users.
NFS Storage: elastic storage for user home filesystems.
Object Storage:
For large datasets/models: storage costs for data; no network cost if staged to workspace hub, but network egress applies for user downloads.
For cached extracted datasets/models: storage costs only, mounted on workspace hub (no network costs).
differences in regard to pricing and included quotas between OTC eu_nl (CDSE scientific prices) and OTC eu_de (regular)
Network -100% applies to direct S3 access as well as outbound traffic from machines, so there is (should be) no egress costs! Note: https://documentation.dataspace.copernicus.eu/Quotas.html (eu_nl!) specifies a monthly transfer limit for direct S3 access (throttled but not charged beyond limit), seems that that applies to outbound traffic from machines as well (on EOTDL datasets/models are accessed via EOTDL API and not direct S3!)
The text was updated successfully, but these errors were encountered:
relevant costs for EOTDL dataset/model hosting and delivery (free + premium):
differences in regard to pricing and included quotas between OTC eu_nl (CDSE scientific prices) and OTC eu_de (regular)
Network -100% applies to direct S3 access as well as outbound traffic from machines, so there is (should be) no egress costs! Note: https://documentation.dataspace.copernicus.eu/Quotas.html (eu_nl!) specifies a monthly transfer limit for direct S3 access (throttled but not charged beyond limit), seems that that applies to outbound traffic from machines as well (on EOTDL datasets/models are accessed via EOTDL API and not direct S3!)
The text was updated successfully, but these errors were encountered: