AWS UrBackup EC2 Deployment S3 Error


#1

Hi,
Trying to deploy our first AWS Ec2 instance of UrBackup from “infscape.com”, all goes well until the first step of the Infscape server configuration. This when entering the S3 bucket name and storage limit plus the S3 storage class.
Then I get this error.
Error setting up S3 backup storage: Error verifying cloud storage settings:

2019-05-20 11:12:16: AES key length=32
2019-05-20 11:12:16: All depenencies available. Starting up…
2019-05-20 11:12:16: Total available RAM: 957.473 MB
2019-05-20 11:12:17: WARNING: AWS-Client: Encountered enum member eu-north-1 which is not modeled in your clients. You should update your clients when you get a chance.
2019-05-20 11:12:17: Database with identifier "40" couldn't be opened
2019-05-20 11:12:17: Retrieving object cd_magic_file
2019-05-20 11:12:17: WARNING: Unknown bucket location constraint -441884340. Returning US_EAST_1
2019-05-20 11:12:17: WARNING: AWS-Client: Encountered Unknown AWSError
AuthorizationHeaderMalformed
The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'eu-north-1':
2019-05-20 11:12:17: WARNING: AWS-Client: If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
2019-05-20 11:12:17: WARNING: AWS-Client: Encountered Unknown AWSError
AuthorizationHeaderMalformed
The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'eu-north-1':
2019-05-20 11:12:17: WARNING: AWS-Client: If the signature check failed. This could be because of a time skew. Attempting to adjust the signer.
2019-05-20 11:12:17: ERROR: Error listing objects on cloud drive
2019-05-20 11:12:17: WARNING: Exception: Error listing objects on cloud drive

As you can tell we have created the EC2 and S3 Bucket in region “eu-north-1” but it looks as the server tries to access the bucket in “us-east-1” ??

/Erik


#2

So we added a replication policy to the S3 bucket (to replicate it to US-EAST-1) and then also added this bucket to the IAM policy and it went through! So our conclusion is that the data now will be stored in N. Virginia…? Not what we aimed for, but I guess it can be enhanced later.

/Erik


#3

Thanks for the heads up! The appliance will be updated such that it supports this new region (update AWS SDK/library used to access S3). Other (older) EU regions should work.


#4

Great!
The last steps of the configuration guide one configures AWS CloudFront and thats all good.
The problem I faced is that port 55415 is not handled mentioned, can it be added in the cloudfront config as well?
When bypassing cloudfront it works just fine. :slight_smile:

/Erik


#5

CloudFront is really just for getting https (the s) for your web interface. It incurs additional cost and a better way would be to use your own domain/sub-domain and map it to the the aws IP, then use the setup ssl option in the appliance (this doesn’t work for initial setup).

For 55415 urbackup does its own encryption and it isn’t http(s) anyway so CloudFront wouldn’t even work.