Purchased My First CloudatCost Machine
-
@Aaron-Studer said:
2) Service Interruption Credits
If Services are interrupted for a period of at least 24 hours after notice by the Customer to CloudatCost, an allowance equal to 1/30th of any fixed billing cycle charges for the affected Service shall apply to each full 24 hour period during which the interruption continues. Credit in any billing period shall not exceed the total average monthly charges for that period for the affected Service. No allowance shall apply to any non-recurring or usage charges. The Customer's sole and exclusive remedy for Service interruption shall be the credit outlined above
The Customer must request credit within thirty (30) days of the validated interruption, failing which the Customer forever waives its right to any credit for such outage. CloudatCost reserves the right to determine in its sole and absolute discretion if an interruption is considered a validated interruption.
At no time will multiple remedies be provided to the Customer for same, similar or related troubles for the same service. Customer payables must be current prior to the Customer receiving any credits
No credit shall be provided for interruptions due to the following:
the failure of any component, software, network or system provided by the Customer or a third party;
network maintenance by CloudatCost;
Force Majeure events;
acts or omissions, negligent or otherwise, of the Customer or a third party, or any breach of any term or condition by the Customer of the Master Services Agreement or any schedules or addenda attached thereto.This line needs to either be change or have fine print for it then "CloudatCost provides a 99.99% uptime SLA. Any lost time is credited back to your account at a pro-rated amount for your monthly package."
-
@thecreativeone91 said:
This line needs to either be change or have fine print for it then "CloudatCost provides a 99.99% uptime SLA. Any lost time is credited back to your account at a pro-rated amount for your monthly package."
I'll agree there. The SLA line is correct, 99.99% uptime is fine. But to say "all" is confusing because all could imply truly any rather than "any as measured by the SLA granularity."
-
@thecreativeone91 said:
however many years of fast food have told me there is a very strict no refund policy even on messed up orders.
Isn't that what charge backs are for?
-
@Danp said:
@thecreativeone91 said:
however many years of fast food have told me there is a very strict no refund policy even on messed up orders.
Isn't that what charge backs are for?
Lol. no that's for fraud. I wouldn't do that.. but, I'm sure someone would. That's a good way to piss a company off.
-
I've never done it, but I could see where it could occur often. If they can't get the order correct, then you shouldn't have to pay IMO.
P.S. Burger King is the worst!
-
@Danp said:
I've never done it, but I could see where it could occur often. If they can't get the order correct, then you shouldn't have to pay IMO.
P.S. Burger King is the worst!
I've never done it. I just deal with whatever with the company or just take the wrong order, as It doesn't usually bother me much.
-
OK, I've now joined the C@C party!
-
-
-
One thing I already like better is that, unlike how Amazon uses public and private keys, which makes setting up things like Rsync between servers impossible (so it feels), C@C doesn't do this. I now have my current server on C@C doing mysqldumps and rsyncs to my local server over Pertino and it just works! Woohoo!
-
@thanksajdotcom said:
One thing I already like better is that, unlike how Amazon uses public and private keys, which makes setting up things like Rsync between servers impossible ....
This doesn't make sense. Amazon uses a preset key for your root account. Once you've logged in, everything is the same. Just set a password if you want a password (you should not.) And any user accounts that you make use whatever you tell them to make. Amazon doesn't change how the OS works.
-
@scottalanmiller said:
@thanksajdotcom said:
One thing I already like better is that, unlike how Amazon uses public and private keys, which makes setting up things like Rsync between servers impossible ....
This doesn't make sense. Amazon uses a preset key for your root account. Once you've logged in, everything is the same. Just set a password if you want a password (you should not.) And any user accounts that you make use whatever you tell them to make. Amazon doesn't change how the OS works.
You can't SSH without that public key though. So if you have the IP, username and password, if you don't have that file from Amazon that you get through your account, you can SSH to them, and I couldn't figure out how to Rsync with it...
-
@thanksajdotcom said:
You can't SSH without that public key though. So if you have the IP, username and password, if you don't have that file from Amazon that you get through your account, you can SSH to them, and I couldn't figure out how to Rsync with it...
Of course you can. Just set the password. Amazon doesn't alter anything. It's the same as any Linux OS anywhere else. Why would you need Amazon to set your password for you?
-
@scottalanmiller said:
@thanksajdotcom said:
You can't SSH without that public key though. So if you have the IP, username and password, if you don't have that file from Amazon that you get through your account, you can SSH to them, and I couldn't figure out how to Rsync with it...
Of course you can. Just set the password. Amazon doesn't alter anything. It's the same as any Linux OS anywhere else. Why would you need Amazon to set your password for you?
I did set the password. But if you try to login directly as root, it won't let you.
-
I don't know how they have it setup but I've tried.
-
@thanksajdotcom said:
I did set the password. But if you try to login directly as root, it won't let you.
Just change the SSHD config to allow passwords. And why are you running RSYNC as root and using anything other than KEYS!!!!
-
How are you attempting to use Rsync with a password? There are several things wrong here. That root uses keys is needed for Rsync to be secure and to work properly.
-
@thanksajdotcom said:
@scottalanmiller said:
@thanksajdotcom said:
You can't SSH without that public key though. So if you have the IP, username and password, if you don't have that file from Amazon that you get through your account, you can SSH to them, and I couldn't figure out how to Rsync with it...
Of course you can. Just set the password. Amazon doesn't alter anything. It's the same as any Linux OS anywhere else. Why would you need Amazon to set your password for you?
I did set the password. But if you try to login directly as root, it won't let you.
Why do you want passwords. Keys are more secure. You can use rsync with keys
rsync -avz /path/local -e "ssh -i /path/sshkey" name@awsinstance:/path/remote/ -
@scottalanmiller said:
How are you attempting to use Rsync with a password? There are several things wrong here. That root uses keys is needed for Rsync to be secure and to work properly.
I'm not worried about it anymore. I setup keys between my C@C and local server and got Rsync working that way. I'm dropping AWS.
-
@thecreativeone91 not only more secure, but faster and the only way, with any security, to have Rsync work in a script.
