By default, the Denodo components store the log files on the local filesystem. However, you can configure them to store the log files on Amazon AWS S3 as well. This is useful for Denodo deployments that run on AWS and that you plan on switching off when you no longer need them. With this feature, you make sure that the logging information is saved even if the instance is deleted.
This feature was added in Denodo 7.0 update 20190903 and it has been added for the Solution Manager in Denodo 8.0 update 20220815.
You have to provide credentials to interact with S3 in order to allow you to send logs to the bucket.
The recommended ways are:
- Use instance profiles with an IAM role (when working with EC2 instances).
- Configure AWS credentials in the operating system.
Create IAM role and associate it to instance at launch time
The AWS documentation about instance profile roles is available here.
In order to give the instances the needed permissions you have to:
- Create a security policy to access the bucket.
- Create an IAM role.
- Launch the instance with the desired role / update instance to work with that role.
Create security policy
Follow these steps to create security policy:
- Open the policies panel in IAM console and click Create policy.
- In the JSON tab, paste and edit the following JSON updating the bucket ARN with your bucket:
- Click Review policy, enter the name and description and create the policy.
Create IAM role
Follow these steps to create an IAM role:
- Open the roles panel in the IAM console, on the left hand side click on Roles and click Create role.
- Select EC2 and click Next: permissions.
- Select the policy created in the previous step.
- In the following dialogs, enter the tags information if you want, provide the Role name and description and create the role.
Launch instance using IAM role
When you launch an instance normally, in order to launch the new instances with permissions, select the corresponding role in the step “Configure instance”.
If you use autoscaling, you can specify the IAM role:
- Selecting the “IAM role” if you use a launch configuration:
- Selecting the “IAM instance profile” in “Advanced details” section if you use a launch template:
The appender also allows to configure the access and secret keys with the properties previously described inside the appender section:
- s3AwsKey: access key.
- s3AwsSecret: secret key.
When s3AwsKey and s3AwsSecret are present, they have precedence over other possible authentication methods defined in the credentials chain.
This method is available, but it is recommended to use the instance profile role option.
Log4j2.xml file configuration
To store the log files of a Denodo server on an S3 bucket you need to modify the $Denodo_Home/conf/vdp/log4j2.xml file of the Denodo component.
Add the S3Appender inside the “Appenders” section:
Add the appender to the Root logger:
The following properties control how the logs are stored in S3:
- s3Bucket: S3 bucket to use. The appender will attempt to create the bucket if it does not exist.
- s3Path: path where each log file will be stored inside the S3 bucket. You can specify the %instanceId keyword in the path. The appender will replace this value with the instance id of the instance in AWS.
With these properties you can control when the appender will send the logs to the S3 bucket:
- stagingBufferSize: Number of log messages after which the content is written to the S3 bucket.
- stagingBufferAge: Number of minutes after which the content is written to the S3 bucket. If this property is defined, stagingBufferSize property value is ignored.
There is also the following connection property:
- s3Region: identifier of the region. The specified region will be used to interact with S3.
The following access properties are optional:
- s3AwsKey: AWS access key to access AWS services / perform some API operations.
- s3AwsSecret: AWS secret key to access AWS services / perform some API operations.
We recommend using instance profile roles instead of configuring AWS credentials directly in the log4j2.xml file.
NOTE: to log the server start / stop messages, you will also need to add these loggers categories in the Loggers section:
<Logger name="server.start" level="info" />
The log4j2.xml files are available in the following paths in a Denodo Platform installation for each type of server:
- Virtual DataPort server: <DENODO_HOME>/conf/vdp/log4j2.xml
- Scheduler server: <DENODO_HOME>/conf/scheduler/log4j2.xml
- Scheduler Index: <DENODO_HOME>/conf/arn-index/log4j2.xml
In each case, you will need to stop the corresponding server, make the changes and start the server with the new appender configured.