DNS name configuration
DNS names are for example purpose only. There are no specific requirements for DNS names.
Example of domain names which need to be assigned to the servers.
| Domain Name (Example) | Record Type | Description |
|---|---|---|
| db.example.com | A or CNAME | DB Server |
| app.example.com | A or CNAME | APP Server |
| s3.example.com | additional A or CNAME record for APP server | APP Server *required to access S3 emulator URLs like this s3.example.com/bucket |
| apm.example.com | A or CNAME | APM Server |
| ocr.example.com | A or CNAME | OCR Server |
| automl-standalone.example.com | A or CNAME | AutoML standalone server (master + agent) |
| automl-master.example.com | A or CNAME | For installing AutoML in cluster mode. There might be multiple AutoML agent servers. DNS records should be created for all of them. |
| automl-agent.example.com | A or CNAME | |
| rpa.example.com | A or CNAME | RPA server |
| bi.example.com | A or CNAME | BI server (Analytics) |
The alternative way is as follows:
If you can't use DNS service, add the records into the hosts file on each server and end users' PC that will use the product:
- On Linux machines: edit the
/etc/hostsfile. - On Windows machines: edit the
C:\Windows\system32\drivers\etc\hostsfile.
Add the following records to the hosts file:
IP addresses below are for example purpose only. You should use your real IP addresses.
192.168.1.1 db.example.com
192.168.1.2 app.example.com
192.168.1.2 s3.example.com
192.168.1.3 apm.example.com
192.168.1.4 ocr.example.com
192.168.1.5 automl.example.com
192.168.1.6 rpa.example.com
192.168.1.7 bi.example.com