fixing a bug in logging an extract run

[DevanathanSabapathy1]

Issue #, if available:
When Cluster endpoint was not given, it breaks extract because of a recent code addition for logging.
Description of changes:
Added an if statement for now, to unblock the customer.
But we should have an elaborate discussion on if we need to have this logging done for extract because when the customer does not give the cluster endpoint we wont log extract as being used. THis wont give a full picture of how many times extract was used. Also logging Replay is more useful in my opinion than extract as customers cant do much with just the extract.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[karle-nishi]

Hey Dev,
Did you test this? Because locally I had tried doing the same but I get Unable to locate credentials error.

[DevanathanSabapathy1]

YEs tested it with and without the cluster endpoint and it worked.
Your error seems to be that aws credentials are not properly set ?