Use public cloud for digital ocean and secure with TLS #654
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This closes #651 |
|
|
||
| subject { | ||
| common_name = "*" | ||
| organization = "skybase" |
There was a problem hiding this comment.
v minor: wonder if we should make this ${var.organization} and default it to "apollo" or similar. all the other changes look sweet!
"Private network" on digital ocean is really a shared private network. It means all other hosts in datacenter, even of other users, can access deployed nodes on digitalocean. It means deploying on public ips is not less secure than deploying on private ones. In this setup we additionaly secure etcd with wildcard tls certs. As an additional bonus, we can not deploy servers across datacenters. Also, we generate initial ssh key for digital ocean dynamically, for better security, and export it to "id_rsa" file for easy ssh access.
sheerun
force-pushed
the
digitalocean1
branch
from
b1e98cf to
c8f8cfa
Compare
|
Made the fix you suggested :) |
|
Thanks! |
tayzlor
added a commit
that referenced
this pull request
Feb 29, 2016
Use public cloud for digital ocean and secure with TLS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"Private network" on digital ocean is really a shared private network.
It means all other hosts in datacenter, even of other users, can access deployed nodes on digitalocean. It means deploying on public ips is not less secure than deploying on private ones.
In this setup we additionaly secure etcd with wildcard tls certs.
As an additional bonus, we can not deploy servers across datacenters.
Also, we generate initial ssh key for digital ocean dynamically, for better security, and export it to "id_rsa" file for easy ssh access.