Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix disabling Scope in the ECS AMI #2435

Merged
merged 2 commits into from
Apr 10, 2017
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions site/ami.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,16 +127,15 @@ There are two methods for running `Weave Scope` within the Weave ECS AMIs:
* [Standalone mode](#running-weave-scope-in-standalone-mode)
* [In Weave Cloud](#running-weave-scope-in-weave-cloud)

You can prevent Weave Scope from automatically starting at boot time by creating
file `/etc/init/scope.override` with contents `manual`.
You can prevent Weave Scope from automatically starting at boot time by removing `/etc/init/scope`.

This can be done at instance initialization time adding the following line to
the
[User Data](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/user-data.html#user-data-shell-scripts)
of the instance.

~~~bash
echo manual > /etc/weave/scope.override
rm /etc/init/scope
~~~

### <a name="running-weave-scope-in-standalone-mode"></a>Running `Weave Scope` in Standalone Mode
Expand Down Expand Up @@ -257,4 +256,4 @@ guide for more information about the AMIs.
**See Also**

* [Installing Weave Scope](/site/installing.md)
* [Service Discovery and Load Balancing with Weave on Amazon ECS](http://weave.works/guides/service-discovery-with-weave-aws-ecs.html)
* [Service Discovery and Load Balancing with Weave on Amazon ECS](http://weave.works/guides/service-discovery-with-weave-aws-ecs.html)