RosettaHealth (formally Nitor Group) is migrating services from the current datacenter into AWS. This requires RosettaHealth customers to update production endpoints depending upon your interface into RosettaHealth. This article goes through the scenarios with specific requirements to point to the new AWS endpoints.
If you connect to our HISPDirect API endpoints via REST calls:
You have 2 options:
- You can still use api.direct.hispdirect.com:443 if you use SNI - Server Name Indication. SNI is required to resolve the multiple TLS certificates on the new server.
- If you don't have SNI, you can continue to use api.direct.hispdirect.com, but only on port 442. NOTE: this is an odd port and may require firewall rule changes on your end.
If you have delegated a DNS domain to RosettaHealth (e.g. direct.YourDomain.com):
Our DNS servers are moving to new IP addresses. If you have delegated DNS to specific RosettaHealth IPs, you must do the following:
- Change your DNS delegation to point to ns1.direct.hispdirect.com and ns2.direct.hispdirect.com instead of IP addresses. This can be done anytime before the actual migration, and is recommended
If you have whitelisted RosettaHealth in your Firewall:
If you have firewall rules to whitelist RosettaHealth endpoints (API, DNS, IHE, etc), you will need to change or add rules to allow the following public IP addresses:
Note: it's highly recommended that these changes be made now, so that the migration is seamless when we change our DNS entries.
If you have questions or concerns, please submit a ticket to email@example.com, with your questions and we'll help you with the migration configurations.