Transparent ASM profile breaks RDS GW connection?

I do see violations ... right off the bat, there were a lot of characters sets that the ASM thought were suspect, which seemed like it was more likely just binary traffic going through... with that being said the HTTP profile has never caused a problem (alone). I am going to try ignoring the wildcard parameter and uncheck Check characters on this parameter name.

It may also be that ASM just cannot work with RDS GW due to the nature of the traffic. However It'd be nice to have an ASM policy applied even if it's less restrictive.

We're not using dataguard.

We're using 11.5.4 HF4.

Just found this - may be the issue: https://support.f5.com/csp/article/K17411