We have weekly full and daily diff backups scheduled (created via a maintenance plan). The backups are created on a network share. There is a new requirement to also copy the backups to AWS S3.
I have a windows command that i can execute outside of the sql server job and it runs as expected and copies the backup files to our S3 bucket.
When I try to run from within a sql server job, it fails. I have tried various things like
- setting the %userprofile% to my user which has the aws credentials
- copying my aws credentials to the C:\Users\SQLSERVERAGENT
...and the aws command part of the windows .cmd script fail. I am just trying something simple at first:
aws s3 ls s3://mybucket/folder1/
The error message is:
('Connection aborted.', error(10060, 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'))
As i wrote, i can run the same .cmd file and it works every time.
Could this still be an issue with aws credentials? Or, any other suggestions?