Audit Trail Set-up

⌘K
  2. Home
  4. Docs
  6. Audit Trail Set-up
  8. Audit Trail Configuration
  10. Advanced Options

Advanced Options

AWS

  • AWS Options:
    • Select your region, database size and enter your AWS login credentials
    • If already using AWS we advise setting up from a clean instance, either using a region that is not currently in use or speak to us.
    • We recommend using a medium instance as anything larger will incur significantly higher costs. You can find out more about instance size performance here.
    • Your database password should be a new password that you are setting up for the Audit Trail database. It is not a password for any existing system.
  • API Key Rotation
    • Each call to the Process Core API is protected by an API key. For best security practise it is recommend that you rotate the API key regularly.

Note that adding API Key Rotation to an existing Audit Trail requires additional rights for the AWS user running the configuration. See this document for more details.

Azure

  • Azure Options:
    • Select a suitable region. The given resource name should normally be used but can be regenerated if required.
    • If required you can attempt to register the resource providers to ensure your subscription works with the resources that Audit Trail uses. See here for more information.
    • If you do not already have a Cosmo DB in use under your Azure subscription, you are able to make use of a free trial offer for one.
  • API Key Rotation
    • Each call to the Process Core API is protected by an API key. For best security practise it is recommend that you rotate the API key regularly.

You can follow the instructions for the rest of the set-up in the ‘best practice options’ section.