From b0707ad9218f9de18b641e8ba9ca387caa3dbd3d Mon Sep 17 00:00:00 2001 From: Armon Dadgar Date: Sat, 19 Sep 2015 21:18:08 -0700 Subject: [PATCH] website: custom --- .../source/intro/examples/aws.html.markdown | 28 ----------------- website/source/intro/vs/custom.html.markdown | 31 ++++++++++--------- 2 files changed, 16 insertions(+), 43 deletions(-) delete mode 100644 website/source/intro/examples/aws.html.markdown diff --git a/website/source/intro/examples/aws.html.markdown b/website/source/intro/examples/aws.html.markdown deleted file mode 100644 index fb9ec7d54..000000000 --- a/website/source/intro/examples/aws.html.markdown +++ /dev/null @@ -1,28 +0,0 @@ ---- -layout: "intro" -page_title: "Basic Two-Tier AWS Architecture" -sidebar_current: "examples-aws" -description: |- - This provides a template for running a simple two-tier architecture on Amazon Web services. The premise is that you have stateless app servers running behind an ELB serving traffic. ---- - -# Basic Two-Tier AWS Architecture - -[**Example Contents**](https://github.com/hashicorp/vault/tree/master/examples/aws-two-tier) - -This provides a template for running a simple two-tier architecture on Amazon -Web services. The premise is that you have stateless app servers running behind -an ELB serving traffic. - -To simplify the example, this intentionally ignores deploying and -getting your application onto the servers. However, you could do so either via -[provisioners](/docs/provisioners/index.html) and a configuration -management tool, or by pre-baking configured AMIs with -[Packer](https://www.packer.io). - -After you run `vault apply` on this configuration, it will -automatically output the DNS address of the ELB. After your instance -registers, this should respond with the default nginx web page. - -As with all examples, just copy and paste the example and run -`vault apply` to see it work. diff --git a/website/source/intro/vs/custom.html.markdown b/website/source/intro/vs/custom.html.markdown index c745ce98c..3e6faf441 100644 --- a/website/source/intro/vs/custom.html.markdown +++ b/website/source/intro/vs/custom.html.markdown @@ -8,21 +8,22 @@ description: |- # Nomad vs. Custom Solutions -Many organizations resort to custom solutions for storing secrets, -whether that be Dropbox, encrypted disk images, encrypted SQL columns, -etc. +It is an undisputed fact that distributed systems are hard; building +one is error-prone and time-consuming. As a result, few organizations +build a scheduler due to the inherent challenges. However, +most organizations must develop a means of deploying applications +and typically this evolves into an ad hoc deployment platform. -These systems require time and resources to build and maintain. -Storing secrets is also an incredibly important piece of infrastructure -that must be done correctly. This increases the pressure to maintain -the internal systems. +These deployment platforms are typically special cased to the needs +of the organization at the time of development, reduce future agility, +and require time and resources to build and maintain -Nomad is designed for secret storage. It provides a simple interface -on top of a strong security model to meet your secret storage needs. +Nomad provides a high-level job specification to easily deploy applications. +It has been designed to work at large scale, with multi-datacenter and +multi-region support built in. Nomad also has extensible drivers giving it +flexibility in the workloads it supports, including Docker. + +Nomad provides organizations of any size a solution for deployment +that is simple, robust, and scalable. It reduces the time and effort spent +re-inventing the wheel and users can focus instead on their business applications. -Furthermore, Nomad is an open source tool. This means that the tool is -as good as the entire community working together to improve it. This -isn't just features and bug fixes, but finding potential security holes. -Additionally, since it is an open source, your own security teams can -review and contribute to Nomad and verify it meets your standards -for security.