Sr. Consultant, Data Protection
Need help with your Guardium deployment? Contact me directly to discuss engagement opportunities. Currently serving North America.
Original Message:
Sent: Thu May 22, 2025 05:32 PM
From: sara rehan
Subject: Universal Connector MariaDB on AWS RDS
is this any better?
Collector is not on cloud, its virtual appliance. this is why we are using access and secret access key. Do we have to allow outbound port 443 from collector?
------------------------------
sara rehan
Original Message:
Sent: Thu May 22, 2025 04:53 PM
From: Wendy Zemba
Subject: Universal Connector MariaDB on AWS RDS
@sara rehan,
Sorry to hear you are still having issues.
Guardium UC is a "pull", so one way from Guardium to the CloudWatch group is required.
Is your Collector and the CloudWatch group in different aws accounts? If so, did you follow the configuration for cross account IAM Role? https://github.com/IBM/universal-connectors/blob/main/input-plugin/logstash-input-cloudwatch-logs/SettingsForRoleArn.md
I've also run into a situation where the VPC wasn't opened between the two accounts.
------------------------------
Wendy Zemba
Sr. Consultant, Data Protection
Converge Technology Solutions
wendy.zemba@convergetp.com
Need help with your Guardium deployment? Contact me directly to discuss engagement opportunities. Currently serving North America.
Original Message:
Sent: Thu May 22, 2025 02:53 PM
From: sara rehan
Subject: Universal Connector MariaDB on AWS RDS
Hi Wendy,
I am still having issues connecting UC with aws rds. Do we need any bidirectional port opening to use UC with aws rds? We have run the allow domain command as well . But the aws team telling us that their access key and secret access key hasn't been used not even once so something is stopping UC to connect to aws rds . What could it be ?
Thank
Sara
Sent from my iPhoneX
Hi Wendy ,
Thanks for sharing the steps
I ran the troubleshooting and it basically checks in two logs uc-logs task.log and logstash-plain.log and in the first one it says internal error: invalid syntax and the second one has no errors . But it doesn't tell me which line has syntax error .
Original Message:
Sent: 5/9/2025 8:35:00 AM
From: Wendy Zemba
Subject: RE: Universal Connector MariaDB on AWS RDS
Hi @sara rehan,
Here's how to debug the Universal Connector and view the logs.
- Login to the Collector CLI
- grdapi set_universal_connector_log_level uc_debug_level=debug
- Log into the Collector UI, navigate to Universal Connector, open the UC configuration and re-save it.
- From the Collector CLI, start fileserver.
- From fileserver, navigate to:
logs > opt-ibm-guardium-log/ > uc_container_log/ > uc-logstash.log
- From there, there's a lot of different directions it could go based on what you find in the log.
- Remove debug (note, restarting the UC will set it back to the default, which is info, but I like to keep set it to error):
grdapi set_universal_connector_log_level uc_debug_level=error
Regarding the policy. For testing purposes it is helpful to have a policy that contains, at minimum, a Log Masked Details rule so you can validate that the SQLs were captured, but you will get a session record by default.
------------------------------
Wendy Zemba
Sr. Consultant, Data Protection
Converge Technology Solutions
wendy.zemba@convergetp.com
Need help with your Guardium deployment? Contact me directly to discuss engagement opportunities. Currently serving North America.
Original Message:
Sent: Thu May 08, 2025 01:01 PM
From: Wendy Zemba
Subject: Universal Connector MariaDB on AWS RDS
Hi @sara rehan,
Just because it saved ok, doesn't mean it's correct, the evaluation at save simply looks for issues with the construct of the code, it doesn't test for successful communication or anything. Since it doesn't show up in the STAP status table that tells me logs aren't getting to the collector.
As far as debugging, there's a troubleshooting tool in 11.5+: Troubleshooting tool.
If that doesn't work, let me know and I'll share some CLI commands and where to look at logs in the fileserver.
------------------------------
Wendy Zemba
Sr. Consultant, Data Protection
Converge Technology Solutions
wendy.zemba@convergetp.com
Need help with your Guardium deployment? Contact me directly to discuss engagement opportunities. Currently serving North America.
Original Message:
Sent: Thu May 08, 2025 11:29 AM
From: sara rehan
Subject: Universal Connector MariaDB on AWS RDS
@Wendy Zemba Thanks for the reply Wendy. I don't see anything under s-tap status. no universal connector. but i have checked it has been enabled and configuration was saved successfully have couple of questions
1.I have not setup any policy for UC , do i have setup a policy first before logs can be pulled from cloudwatch?
2.What will be the troubleshooting steps? where should i start from?
I read somewhere that Universal connector logs cannot be retrieved through normal sessions reports. since logs pulled through universal connector are stored in a table at the backend and it has to be pulled to collector through reports. But i am not sure if its correct or not. I would appreciate any help.
Thanks
------------------------------
sara rehan
------------------------------