status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Website: GH-730 links for /docs/guides/atlas.html

This commit is contained in:
Ryan Breen 2015-02-24 22:38:25 -05:00
parent a022dfcb32
commit fa2328a07d
1 changed files with 15 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
website/source/docs/guides/atlas.html.markdown
View File

@ -10,7 +10,7 @@ description: |-
[Atlas](https://atlas.hashicorp.com) is a service provided by HashiCorp to deploy applications and manage infrastructure. [Atlas](https://atlas.hashicorp.com) is a service provided by HashiCorp to deploy applications and manage infrastructure.
Starting with Consul 0.5, it is possible to integrate Consul with Atlas. This is done by registering a node as part Starting with Consul 0.5, it is possible to integrate Consul with Atlas. This is done by registering a node as part
of an Atlas infrastructure (specified with the `-atlas` flag). Consul maintains a long-running connection to the of an Atlas infrastructure (specified with the [`-atlas`](/docs/agent/options.html#_atlas) flag). Consul maintains a long-running connection to the
[SCADA](http://scada.hashicorp.com) service which allows Atlas to retrieve data and control nodes. [SCADA](http://scada.hashicorp.com) service which allows Atlas to retrieve data and control nodes.
Data acquisition allows Atlas to display the state of the Consul cluster in its dashboard and set up alerts Data acquisition allows Atlas to display the state of the Consul cluster in its dashboard and set up alerts
@ -19,9 +19,11 @@ based on health checks. Remote control enables Atlas to provide features like au
## Enabling Atlas Integration ## Enabling Atlas Integration
To enable Atlas integration, you must specify the name of the Atlas infrastructure and the Atlas authentication To enable Atlas integration, you must specify the name of the Atlas infrastructure and the Atlas authentication
token. The Atlas infrastructure name can be set either with the `-atlas` CLI flag, or with the `atlas_infrastructure` token. The Atlas infrastructure name can be set either with the [`-atlas`](/docs/agent/options.html#_atlas)
[configuration option](/docs/agent/options.html). The Atlas token is set with the `-atlas-token` CLI flag, `atlas_token` CLI flag or with the [`atlas_infrastructure`](/docs/agent/options.html#atlas_infrastructure) config option.
configuration option, or `ATLAS_TOKEN` environment variable. The Atlas token is set with the [`-atlas-token`](/docs/agent/options.html#_atlas_token) CLI flag,
[`-atlas-token`](/docs/agent/options.html#atlas_token) configuration option, or `ATLAS_TOKEN`
environment variable.
To verify the integration, either run the agent with `debug`-level logging or use `consul monitor -log-level=debug` To verify the integration, either run the agent with `debug`-level logging or use `consul monitor -log-level=debug`
and look for a line like: and look for a line like:
@ -36,22 +38,23 @@ Once integrated with Atlas, the auto-join feature can be used to have nodes auto
peers in their datacenter. Server nodes will automatically join peer LAN nodes and other WAN nodes. peers in their datacenter. Server nodes will automatically join peer LAN nodes and other WAN nodes.
Client nodes will only join other LAN nodes in their datacenter. Client nodes will only join other LAN nodes in their datacenter.
Auto-join is enabled with the `-atlas-join` CLI flag or the `atlas_join` configuration option. Auto-join is enabled with the [`-atlas-join`](/docs/agent/options.html#_atlas_join) CLI flag or the
[`atlas_join`](/docs/agent/options.html#atlas_join) configuration option.
## Securing Atlas ## Securing Atlas
The connection to Atlas does not have elevated privileges. API requests made by Atlas The connection to Atlas does not have elevated privileges. API requests made by Atlas
are served in the same way any other HTTP request is handled. If ACLs are enabled, it is possible, via are served in the same way any other HTTP request is handled. If ACLs are enabled, it is possible, via
the `atlas_acl_token` configuration option, to force an Atlas ACL token to be used instead of the the [`atlas_acl_token`](/docs/agent/options.html#atlas_acl_token) configuration option, to force an
agent's default token. Atlas ACL token to be used instead of the agent's default token.
The resolution order for ACL tokens is: The resolution order for ACL tokens is:
1. Request-specific token provided by `?token=`. These tokens are set in the Atlas UI. 1. Request-specific token provided by `?token=`. These tokens are set in the Atlas UI.
2. The agent's `atlas_acl_token`, if configured. 2. The agent's [`atlas_acl_token`](/docs/agent/options.html#atlas_acl_token), if configured.
3. The agent's `acl_token`, if configured. 3. The agent's [`acl_token`](/docs/agent/options.html#acl_token), if configured.
4. The `anonymous` token. 4. The `anonymous` token.
Because the `acl_token` typically has elevated permissions compared to the `anonymous` token, Because the [`acl_token`](/docs/agent/options.html#acl_token) typically has elevated permissions
the `atlas_acl_token` can be set to `anonymous` to drop privileges that would otherwise be compared to the `anonymous` token, the [`atlas_acl_token`](/docs/agent/options.html#atlas_acl_token)
inherited from the agent. can be set to `anonymous` to drop privileges that would otherwise be inherited from the agent.