Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

i'm running a site on a shared host while image hosting is done on amazon s3. i've opened a second shared host account for backups. here's my setup :

A -> site on shared host, pushes images to B (s3 api) and C (via sftp), and daily backups to B (s3 api) and C (via sftp)

B -> amazon s3 buckets for main images host and bucket for backups

C -> second account on shared host, acts at backup of images host B and backup of data of A. Host only allows one sftp account which has full root access but is jailshelled.

my problem with this setup is that A is a point of total failure - anybody who gets access to A will be able to (worst case), wipe A, B and C.

Can somebody please recommend a better setup ? thanks in advance.

share|improve this question
up vote 0 down vote accepted

if your processes are autonomous, there will always be be a single point of failure, how else would you marshall resources and control the process? make a best effort to lock down this machine and you should be okay.

some approaches for locking down your single point of failure:

  1. turn off services and close ports that aren't required

  2. uninstall software that is not needed

  3. follow best practices for hardening ssh. these include but are not limited to: disallow password auth, disallow root login, change the default port, whitelist the users who can login

  4. use a tool like fail2ban to keep port knockers and script kiddies away

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.