Implementation Guide › Configuring Services › Configuring the Event Log Store › Configuring Non-Interactive Authentication for Auto Archive
Configuring Non-Interactive Authentication for Auto Archive
You can configure auto archiving between servers having different roles. For example:
- From one or more collection servers to a single reporting server.
- From one or more reporting servers to a single remote storage server.
Before configuring auto archiving from one server to another, configure non-interactive ssh authentication from the source server to the destination server. Non-interactive means that one server can move files to another server without requiring passwords.
- If you have only three servers, a collection server, a reporting server, and a remote storage server, you configure non-interactive authentication twice:
- From the collection server to the reporting server
- From the reporting server to the remote storage server.
- If you have six servers with four collection servers, one reporting server, and one remote storage server, you configure non-interactive authentication five times:
- From collection server 1 to the reporting server.
- From collection server 2 to the reporting server.
- From collection server 3 to the reporting server.
- From collection server 4 to the reporting server.
- From the reporting server to the remote storage server.
Configuring non-interactive ssh authentication between two servers uses RSA key pairs, a private key and a public key. You copy the first public key you generate to the destination server as authorized_keys. When you configure multiple instances of non-interactive authentication to the same destination reporting server, you copy the additional public keys to unique filenames to avoid overwriting the original authorized_keys. Then you concatenate these filenames to authorized_keys. For example, you would append authorized_keys_ELM-C2 and authorized_keys_ELM-C3 to the authorized_keys file from ELM-C1.
More information:
Example: Configure Non-Interactive Authentication for Hub and Spoke
Example: Configure Non-Interactive Authentication Across Three Servers