Open benarent opened 2 weeks ago
This issue would be solved by combining the aurora and rds instance flows into one.
A frequent point of friction is people click on the wrong flow and then they are confused when no databases are listed to choose from.
In our discovery config we have combined RDS and Aurora under the matcher type "rds"
- it would therefore be consistent UX to combine them into a single discover flow as well.
cc @stevenGravy ran into this problem recently. If we do not combine the flows together, but we include "RDS" in the name like "RDS Aurora PostgreSQL", then I think people will be even more likely to click on the wrong flow. An alternative to that problem, as we discussed on slack, is to just be more clear about which flow is currently being used and showing some tip to double-check that the user has chosen the right flow when there are no databases listed.
When setting up a RDS Database, the "Enroll a RDS Database" wasn't finding the DB ( Aurora PostgreSQL ) since I had started the RDS Flow and not the Aurora flow. While these engines are the same, they are both under the umbrella item of RDS. I would suggest we either have a catch all RDS Engines, or edit the search to show RDS Aurora DB engines.