shared-service-network-configurations

Shared Service Network Configurations

There is a single point of entry into the MDPS system, and it is "mdps.mcp.nasa.gov".

Delegating responsibility to a subdomain

Follow the steps on this aws tutorial to delegate responsibilities of a subdomain.

We only delegate shared service subdomains so that venue services remain inaccessible through direct connections- all connections to UIs and APIs within a venue must go through the shared service routes (that is mdps.mcp.nasa.gov/project/venue/processing)

Following the above tutorial, we delegate responsibility for the test.mdps.mcp.nasa.gov and dev.mdps.mcps.nasa.gov to the private hosted zones in unity-test and unity-dev, respectfully.

Within each shared service venue, there are two more subdomains- www and api. The route UI and API traffic to the appropriate endpoints within a venue. Below is a diagram of what this looks like at the shared service level:

Delegation of subdomains for shared services.

Certificates

In each private hosted zone, we should request a wildcard certificate good for any subdomain within that zone. For dev.mdps.mcp.nasa.gov, we have a wildcard certificate *.dev.mdps.mcp.nasa.gov which can be used within a hosted zone to create urls for various services. The only reserved subdomains for a given domain are api and www, which are used to route API and UI based traffic.