Hey /r/veeam, hope all is well.

We've created a SOBR archive that, as of a week ago, was working fine. As of this week the archive tier isn't. The Veeam instance fails to connect to the AWS EC2 proxy that Veeam, itself, spins up in AWS.

This proxy is spun up and spun down temporarily. Long enough for the EC2 instance to transfer the files to the archive tier s3 bucket. Problem is the Veeam instance cannot connect to it.

• I've checked the AWS Security groups with veeam, they are correct. We've even opened the security group wide open to allow all traffic from all sources. Still failed to connect.
• Have confirmed there are no NACL rules preventing traffic from reaching the temporary EC2 instance.
• Veeam logs point to an issue with SSH. Saying they can't connect to the EC2 server via SSH. Problem with this, Veeam has admitted that this is actually a generic error message that they use. Not necessarily a 'catch-all' error message. But generic enough that they don't know where the exact problem is.

As of right now we're trying to determine if the issue is networking related or programming related. After reviewing AWS I 'feel' the AWS side isn't the bottle kneck. We've reviewed the EC2, VPC, and Sec. Group setup.

Edit: Full error message isn't related to SSH. My bad :(

"Key is already used", or something to that effect.

We also ruled out networking on our local side, and networking on the AWS Side -_-