If you have content that is submitted over a public network it is usually received at an 'ingest' server that is behind a firewall in a DMZ and is outside the Internal Network firewall, as seen in the diagram above. In this case the data is automatically forwarded from the 'ingest' server in the DMZ to the Aspera Server in the Internal Network, where the files are stored or additional processing takes place. For example, when an external customer submits content to an Aspera Server in a DMZ via Connect Client, that content is moved from the DMZ to the Internal Server with Aspera AspForward.
If you have content that is submitted internally to a distribution Aspera Server located in a DMZ by a contributor using Aspera Client on the Internet Network you can use the Content Distribution automation tool. When they content is received is it automatically forwarded from the distribution server to the intended external destination over the public network, as seen in the diagram above. For example, when an internal network user submits content to an Aspera Server in a DMZ via Connect Client, that content is distributed from the DMZ to external destinations with Aspera AspForward.
Enterprise networks often implement multistage DMZ and firewalls to enhance security and keep access levels separated. In these cases content submitted to an Aspera Server in a DMZ behind a firewall is automatically forwarded to an Internal DMZ when appropriate. The Aspera Servers in the Internal DMZ forward the data to the servers in the Internal Network. A diagram of a typical setup is above.
In most cases the files in the DMZ or Internal DMZ are automatically moved within the same server to a different directory before those files are automatically forwarded or pulled or any other tasks are performed on them. The move or copy of the files within the DMZ can maintain the directory structure. Multistage forwarding can be applied to both Ingest and Distribution.
For example, an external customer may submit content to an Aspera Server that is located in the External DMZ via Connect Client; that content is then moved from the External DMZ to the Internal DMZ with AspForward, and finally it is moved from the Internal DMZ to a server in the Internal Network with AspForward.
Advanced Forwarding Configuration
In several enterprises, multiple customers and partners submit content to a an Aspera Server in a DMZ and behind a firewall, and it forwards the content to multiple Aspera Servers in the Internal Network. The user data of the initial transfer is preserved throughout the process and is available to be used in post-processing actions to determine proper handling. An example of this scenario is seen below. For example, if an external customer submits content to an Aspera Server that is in a DMZ via Connect Client, the content is moved from the DMZ to the Internal Network using AspForward, which can preserve user credentials.