Hi all, I am looking for advice on how best to handle errors derived from the inability to connect to AWS S3. We are building a job that connects to S3 and gets some files that we load in our local environment. It works OK. However, we want to be able to log the possibility of S3 being unavailable or down. I am testing this option by giving the wrong credentials, and although it triggers a series of warning that are displayed in the console, they don't error out. I have tried using other components such as tS3bucketexists, however this components errors all the time (good or bad credentials). Any other suggestion? Your advice would be appreciated. Thanks,
If you want to capture the exception and handle error, here is a component called tLogCatcher which can be used to capture exception and log them (console, file or db table)
Thanks Sabrina for your prompt response.
I have tried adding a tLogCatcher component. Unfortunately, it doesn't seem to catch the warning logged in the Console as an exception.
This is an example of a warning logged on the Console that we would like to catch when the connection to S3 is not available:
[WARN ]: uat.job_framework_s3get_incwarnings_0_1.job_Framework_S3Get_IncWarnings - tS3List_2 - Failed to list objects from bucket nnnnnn
[WARN ]: uat.job_framework_s3get_incwarnings_0_1.job_Framework_S3Get_IncWarnings - tS3List_2 - The request signature we calculated does not match the signature you provided. Check your key and signing method. (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch)
Any other suggestion?
Thanks,
Gemma
