AWS.RDS/AWS.Cloudwatch/MySQL bugfix & config-task1
Budget: €8 – €30 EUR
Quick'n'tiny RDS/MySQL_bugfix+config-task1
!!! Important Preamble note: the minimum EUR Budget is just a dummy-value - We would like to invite you to submit your pricing options for the project.
Project description:
Packet(1) Fixing a bug in AWS.RDS MySQL-Database.
Short Bug-description: the logs (general, error, slowquery, audit) of the RDS Server are not send properly
to Cloudwatch. (Except for the error-logs) the protocoll-streams in Cloudwatch do not include the log-data.
Milestone-I-Requirements:
* Solving the log-data transfer/display problem.
* creating a functioning transfer/storage/and display structure of all log data from the RDS MySQL
instance to Cloudwatch
* Proof of functionality based on a typical data flow of log data from RDS MySQL into the Cloudwatch
protocol stream with at least the general log and audit log.
* Complete documentation of the steps performed and the structures created.
Packet(2) Accessing MySQL-Server logfiles:
Access to the server log files (general-, error-, audit-, slowquery-log) is required to read, store, and continuously monitor the latest entries in real-time (tailing).
This access should be available from any approved server users/IP addresses (just IPv4.
We look forward to receiving your suggestions on the approach and solution structure so that we can discuss and determine them.
Milestone-II-Requirements:
* Implementation of the defined procedures and results.
* Proof of functionality based on executing the operations read/save/tream(follow tail) of the logfiles
(general-,error-,slowquery-,audit-)
* Complete documentation of the steps performed and the structures created.
*Info: IAM-user-login for AWS & MySQL-Server for service-tasks will be provided
!!Important Notice: Please provide a complete and clear list of the required policies/privileges before/during the start of the project.
In order to be able to carry out your analyses and work successfully and in accordance with the Least Privilege Principle. Missing policies/privileges during the project can be added, but may sometimes cause delays.
The attached file illustrates some effects of the bug.
!!! Important Preamble note: the minimum EUR Budget is just a dummy-value - We would like to invite you to submit your pricing options for the project.
Project description:
Packet(1) Fixing a bug in AWS.RDS MySQL-Database.
Short Bug-description: the logs (general, error, slowquery, audit) of the RDS Server are not send properly
to Cloudwatch. (Except for the error-logs) the protocoll-streams in Cloudwatch do not include the log-data.
Milestone-I-Requirements:
* Solving the log-data transfer/display problem.
* creating a functioning transfer/storage/and display structure of all log data from the RDS MySQL
instance to Cloudwatch
* Proof of functionality based on a typical data flow of log data from RDS MySQL into the Cloudwatch
protocol stream with at least the general log and audit log.
* Complete documentation of the steps performed and the structures created.
Packet(2) Accessing MySQL-Server logfiles:
Access to the server log files (general-, error-, audit-, slowquery-log) is required to read, store, and continuously monitor the latest entries in real-time (tailing).
This access should be available from any approved server users/IP addresses (just IPv4.
We look forward to receiving your suggestions on the approach and solution structure so that we can discuss and determine them.
Milestone-II-Requirements:
* Implementation of the defined procedures and results.
* Proof of functionality based on executing the operations read/save/tream(follow tail) of the logfiles
(general-,error-,slowquery-,audit-)
* Complete documentation of the steps performed and the structures created.
*Info: IAM-user-login for AWS & MySQL-Server for service-tasks will be provided
!!Important Notice: Please provide a complete and clear list of the required policies/privileges before/during the start of the project.
In order to be able to carry out your analyses and work successfully and in accordance with the Least Privilege Principle. Missing policies/privileges during the project can be added, but may sometimes cause delays.
The attached file illustrates some effects of the bug.