Support

Hello,

which issues are you having?
Please remember that Aurora is just a MySQL-compatible database hosted on AWS infrastructure. Basically they will end up to manage it to keep performances acceptable, without you to worry about tweaking any database configuration.

As long as the writing and reading connections are the same, there is nothing do to. If they are different (ie you have an endpoint to write data and another one to read them) you can't use WordPress (or Joomla) out of the box; you'll need some third party plugin. If that's the case, Admin Tools won't be affected, however Akeeba Backup will be.

Finally, Admin Tools can do very little for you: we have utility tools to tweak your .htaccess file, but that will affect Apache, the webserver that is serving the requests, not the underlying database.

AWS have already managed to setup the database but was just wondering if Admin Tools had anything that might block or slow this down. We are just getting as 5s delat on new loads until the page is cached.

No, I'm sorry, in this case Admin Tools can't do anything for you

If the cluster database will effect Akeeba Backup is there a way I can fix that?

First of all double check if you really have such special setup (write in one place, read from another one). It's a very advanced setup, it's not very common unless you're dealing with a site that receives an huge amount of traffic. If you're 100% sure that you have such configuration, you'd need to override the MySQL connection settings inside Akeeba Backup configuration to point to the master (write) node because we need to both read and update tables using the same connection.

Ok, let me know how it goes