- What We Offer
- Your Processing Environment
- Example of tool usage
- Processing EO Data and Serving www services
- Processing and Storing EO
- Embedding OGC WMS Services into Your website
- GPU Use Case
- Using the EO Browser
- EO Data Finder API Manual
- Use of SNAP and QGIS on a CREODIAS Virtual Machine
- Use of WMS Configurator
- DNS as a Service - user documentation
- Use of Sinergise Sentinel Hub on the CREODIAS EO Data Hub
- Load Balancer as a Service
- Jupyter Hub
- Use of CREODIAS Finder for ordering data
- ESRI ArcGIS on CREODIAS
- se of SNAP and QGIS on a CREODIAS Virtual Machine
- Use of CEMS data through CREODIAS
- Searching, processing and analysis of Sentinel-5P data on CREODIAS
- Legal Matters
- Pricing Plans
- Public Reporting Dashboards
- Sentinel Hub Documentation
- Integration Guides
- OGC API
- Custom Processing Scripts
How can I access my VMs using names instead of IP addresses?
The VM-s are seen simultaneously in several networks, at least in your „private” LAN and in public Internet. By default the public addresses (floating-ip, 185.48.x.x) have no associated names. You may assign such names from your DNS domain or you may request a name from us (as an additional service). The names provided by us have the following format: computer_name.users.creodias.eu, where "computer_name" is chosen by you.
If you need the name just to access the machine from your office workstation, the simplest way is to add its address and friendly name to /etc/hosts.
The VM-s in a given project share common „private” network – by default it is 192.168.0.x. You may create additional private networks with any addresses you like. However, they will not be equipped with DNS. If the machines are expected to recognize other by their names, either /etc/hosts need to be created and copied to all machines, or private DNS may be run on one of them. Moreover, although the addresses are dynamically assigned they are constant – they do not change from the moment of creation to deletion of the machine.