not specifying credentials at all lets the AWS sdk figure out the credentials on its own, which will work with setting key id and secret key as environment variables, but it will also work on EC2 instances that have an IAM Role set - the SDK will automatically pick up the ever-changing keys from the role.
Optionally, the credentials in the config could still be usable, but they shouldn't have a default and shouldn't be required - for our uses this is not necessary though.
Also, implemented giving failed messages back to the queue and made logging a little less verbose
not specifying credentials at all lets the AWS sdk figure out the credentials on its own, which will work with setting key id and secret key as environment variables, but it will also work on EC2 instances that have an IAM Role set - the SDK will automatically pick up the ever-changing keys from the role.
Optionally, the credentials in the config could still be usable, but they shouldn't have a default and shouldn't be required - for our uses this is not necessary though.
Also, implemented giving failed messages back to the queue and made logging a little less verbose