Configuring AS2
To create an AS2-enabled server, you must also specify the following components:
-
Agreements – Bilateral trading partner agreements, or partnerships, define the relationship between the two parties that are exchanging messages (files). To define an agreement, Transfer Family combines server, local profile, partner profile, and certificate information. Transfer Family AS2-inbound processes use agreements.
-
Certificates – Public key (X.509) certificates are used in AS2 communication for message encryption and verification. Certificates are also used for connector endpoints.
-
Local profiles and partner profiles – A local profile defines the local (AS2-enabled Transfer Family server) organization or "party." Similarly, a partner profile defines the remote partner organization, external to Transfer Family.
While not required for all AS2-enabled servers, for outbound transfers, you need a connector. A connector captures the parameters for an outbound connection. The connector is required for sending files to a customer's external, non Amazon server.
The following diagram shows the relationship between the AS2 objects involved in the inbound and outbound processes.
![Diagram that shows the relationship between the AS2 objects involved in the inbound and outbound processes.](images/as2-architecture-in-out-agree-connect.png)
For an end-to-end example AS2 configuration, see Setting up an AS2 configuration.