Table of Contents


  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Licenses
  5. Ecosystem single sign-on
  6. SAML single sign-on
  7. Metering
  8. Source control and service upgrade settings
  9. Users and user groups
  10. User roles
  11. Permissions
  12. Runtime environments
  13. Serverless runtime environments
  14. Secure Agent services
  15. Secure Agent installation
  16. Schedules
  17. Bundle management
  18. Event monitoring
  19. File transfer
  20. Troubleshooting



Elastic Server properties

Elastic Server

To change the behavior of the
Elastic Server
, configure the
Elastic Server
properties in the
System Configuration Details
area when you edit a Secure Agent.
The following image shows the
Elastic Server
When you view or edit a Secure Agent and select the Elastic Server, the Elastic Server properties appear in the System Configuration Details area. In this image, the service type is set to "All Types," and the LOG4J and AWS properties are displayed.
You can configure the following
Elastic Server
Level of detail that the
Elastic Server
writes to log files. Enter the logging level as a string, such as 'INFO.'
As the logging level increases, the messages that the
Elastic Server
writes to log files include the messages in the prior logging levels. For example, if the logging level is INFO, the log contains FATAL, ERROR, WARNING, and INFO code messages.
The following values are valid:
  1. FATAL. Includes nonrecoverable system failures that cause the service to shut down or become unavailable.
  2. ERROR. Includes connection failures, failures to save or retrieve metadata, and service errors.
  3. WARNING. Includes recoverable system failures or warnings.
  4. INFO. Includes system and service change messages.
  5. TRACE. Logs user request failures.
  6. DEBUG. Logs user request logs.
External ID that the Secure Agent specifies when the agent attempts to assume the kops role. Required if you configure an external ID in the trust relationship of the kops role.
Ignore this property in an Azure environment.
ARN of the kops role.
Required when you set up separate kops and Secure Agent roles in an AWS environment. Ignore this property in an Azure environment.
Session duration of the AWS AssumeRole API in seconds. By default, the session duration is 1800 seconds (30 minutes).
Overrides the maximum CLI/API session duration that is configured for the kops role. If the session duration configured for the
Elastic Server
is longer than session duration for the kops role, the Secure Agent might fail to assume the kops role.
Ignore this property in an Azure environment.

Updated November 30, 2020