Over a million developers have joined DZone.

Prepare for Failure in Your AWS Environment

DZone's Guide to

Prepare for Failure in Your AWS Environment

Anything can happen in your cloud environments—so learn early that you need to be prepared for everything.

· Cloud Zone ·
Free Resource

Discover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.

In the cloud everything can happen. Actually, everything will happen.

Therefore, in your design, you should be ready for failures: even if you expect your disk mounts to be there for you, they might not be. And you are doing auto-scaling, it is most likely that at some time they won't be there for you.

Therefore, to avoid hanging servers due to failure to mount disks and bad messages such as: "The disk drive for /tmp is not ready yet or not present," make sure your servers are not bound by your disks; otherwise, you will not be able to contact your servers, or your OpsWorks will notify you that the server is booting forever.

Avoid Waiting for Your Mount

The secret is a small option: nobootwait that will make sure your server is not waiting for the mount to be ready. You can configure it in your /etc/fstab, or even better in your Chef recipe:

mount "/tmp" do
  device ""
  fstype "nfs"
  options "rw,nobootwait"
  action [:mount, :enable]

Bottom Line

The right design will help you keep you system running in a cloud-based environment.

Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.

EBS ,Cloud Architecture ,aws ,scaling ,cloud

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}