Skip to content

Commit efa5f31

Browse files
author
Matthew Fisher
committed
docs(managing_deis): add note for public cloud environments
1 parent afa84a1 commit efa5f31

3 files changed

Lines changed: 36 additions & 1 deletion

File tree

docs/installing_deis/digitalocean.rst

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,6 @@ Generate a New Discovery URL
3737

3838
Please refer to :ref:`generate_discovery_url` for generating a new Discovery URL.
3939

40-
4140
Create CoreOS Droplets
4241
----------------------
4342

@@ -121,6 +120,19 @@ For convenience, you can also set up DNS records for each node:
121120
If you need help using the DNS control panel, check out `this tutorial`_ on DigitalOcean's
122121
community site.
123122

123+
Apply Security Group Settings
124+
-----------------------------
125+
126+
Because DigitalOcean does not have a security group feature, we'll need to add some custom
127+
``iptables`` rules so our components are not accessible from the outside world. To do this, there
128+
is a script in ``contrib/`` which will help us with that. To run it, use:
129+
130+
.. code-block:: console
131+
132+
$ for i in 1 2 3; do ssh core@deis-$i.example.com 'bash -s' < contrib/util/custom-firewall.sh; done
133+
134+
Our components should now be locked down from external sources.
135+
124136
Install Deis Platform
125137
---------------------
126138

docs/managing_deis/add_remove_host.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -98,6 +98,11 @@ We're back in a ``HEALTH_OK``, and note the following:
9898
9999
We have 4 monitors, OSDs, and metadata servers. Hooray!
100100

101+
.. note::
102+
103+
If you have applied the `custom firewall script`_ to your cluster, you will have to run this
104+
script again and reboot your nodes for iptables to remove the duplicate rules.
105+
101106
Removing a node
102107
---------------
103108

@@ -273,6 +278,7 @@ Removing the host from etcd
273278
The etcd cluster still has an entry for the host we've removed, so we'll need to remove this entry.
274279
This can be achieved by making a request to the etcd API. See `remove machines`_ for details.
275280

281+
.. _`custom firewall script`: https://github.com/deis/deis/blob/master/contrib/util/custom-firewall.sh
276282
.. _`remove machines`: https://coreos.com/docs/distributed-configuration/etcd-api/#remove-machines
277283
.. _`removing monitors`: http://ceph.com/docs/giant/rados/operations/add-or-rm-mons/#removing-monitors
278284
.. _`removing OSDs`: http://docs.ceph.com/docs/giant/rados/operations/add-or-rm-osds/#removing-osds-manual

docs/managing_deis/security_considerations.rst

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,4 +51,21 @@ environment by using ```deis tags set environment=production```. Deis will pass
5151
along to the scheduler, and your applications in different environments on running on separate
5252
hardware.
5353

54+
.. _deis_on_public_clouds:
55+
56+
Running Deis on Public Clouds
57+
-----------------------------
58+
If you are running on a public cloud without security group features, you will have to set up
59+
security groups yourself through either ``iptables`` or a similar tool. The only ports that should
60+
be exposed to the public are:
61+
62+
- 22: for remote SSH
63+
- 80: for the routers
64+
- 443: (optional) routers w/ SSL enabled
65+
- 2222: for the builder
66+
67+
For providers that do not supply a security group feature, please try
68+
`contrib/util/custom-firewall.sh`_.
69+
5470
.. _`#986`: https://github.com/deis/deis/issues/986
71+
.. _`contrib/util/custom-firewall.sh`: https://github.com/deis/deis/blob/master/contrib/util/custom-firewall.sh

0 commit comments

Comments
 (0)