LabCollector Installation Requirements for AWS - LabCollector

Search Knowledge Base by Keyword

LabCollector Installation Requirements for AWS

You are here:
← All Topics

AWS stands for Amazon Web Serviceswhich is a cloud-based platform that offers a variety of services and solutions for hosting and managing applications and data.

If you’re planning to install LabCollector on AWS, you need to meet specific requirements and apply certain configurations to ensure smooth performance.

This knowledge base will guide you through the dedicated requirements and configuration steps needed to install LabCollector on AWS.

Dedicated Requirements for MySQL Configuration:

*Check out our KB on LabCollector’s linux requirements & installation

  • Firstly, if you are hosting MySQL on localhost, you will need to apply a configuration to the /etc/my.cnf file. Specifically, you should set the “innodb_strict_mode” parameter to 0. This can be done by adding the following line to the my.cnf file:innodb_strict_mode=0After making this change, you need to restart the MySQL.
  • If you are using Amazon RDS (Relational Database Service) instead of hosting MySQL on localhost, you can create a custom parameter group for your RDS instance and set the “innodb_strict_mode” parameter to 0 (as shown in the screenshot below).

    • This can be done by following these steps:
      1. Create a custom parameter group for your RDS instance.
      2. Modify the custom parameter group and set the “log_bin_trust_function_creators” parameter to 1.
      3. Save the changes to the parameter group.
      4. Associate the custom parameter group with your RDS instance.
      5. Reboot the RDS instance.

It’s important to note that if you are already using a custom parameter group, you only need to complete steps 2 and 3 above, and then reboot the RDS instance. The “log_bin_trust_function_creators” parameter is a dynamic parameter and does not require a reboot.


  • The “log_bin_trust_function_creators” parameter is particularly important when turning on automated backups for a MySQL RDS instance. If the client receives the error message “ERROR 1419 (HY000): You don’t have the SUPER privilege and binary logging is enabled (you might want to use the less safe log_bin_trust_function_creators variable)” when creating a trigger, they need to modify the “log_bin_trust_function_creators” parameter to 1. This allows functions, procedures, and triggers to be used on the RDS instance.

However, it’s important to note that setting the “log_bin_trust_function_creators” parameter to 1 may result in unsafe events being written to the binary log. The binary logging format is statement-based when the “log_bin_trust_function_creators” parameter is set to 1, which can result in larger binary logs.

Related topics:
error: Content is protected !!