Skip to content
This repository has been archived by the owner on Jun 17, 2020. It is now read-only.

initial version of wireguard on the monitoring-devops deployment #595

Merged
merged 7 commits into from
May 24, 2019

Conversation

cleverca22
Copy link
Contributor

No description provided.

Copy link
Contributor

@disassembler disassembler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like this approach and look forward to seeing it used for securing communications between AWS and other physical data centers and cloud services.

require = [ ./monitoring.nix ];
monitoring = { ... }:
a1 = mkUplink 10 ../static/a1.wgprivate;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this stuff needs to be undone and moved to infra for all packet.net servers.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was mainly a testing ground for the concept, and matching code has now been put into the infra deployments
i'm thinking it can be ok to leave wireguard in this devops deployment, for future testing?

securityGroups = [
resources.ec2SecurityGroups."allow-wireguard-in-${region}-${org}"
resources.ec2SecurityGroups."allow-to-monitoring-${region}"
resources.ec2SecurityGroups."allow-monitoring-static-peers-${region}-${org}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wireguard SG replaces the need for this SG.


ownIp = mkOption {
type = types.str;
description = "the address a remote prometheus node will use to contact this machine";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could also mention wireguard IP will be used preferentially if enabled.

done
exit 0
'';
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like this. Maybe it would be good to add similar for graylog and grafana initial cred creation to save new cluster spin up time.

@cleverca22 cleverca22 force-pushed the jal-infra-monitoring-wireguard branch 12 times, most recently from c707acd to c33297b Compare May 23, 2019 20:04
@cleverca22 cleverca22 force-pushed the jal-infra-monitoring-wireguard branch 3 times, most recently from 9f0924c to 347ce6d Compare May 23, 2019 21:21
@cleverca22 cleverca22 force-pushed the jal-infra-monitoring-wireguard branch from 347ce6d to 6d5446e Compare May 23, 2019 21:27
@cleverca22 cleverca22 force-pushed the jal-infra-monitoring-wireguard branch 2 times, most recently from 75c468f to 12b8461 Compare May 23, 2019 22:38
@cleverca22 cleverca22 force-pushed the jal-infra-monitoring-wireguard branch from 12b8461 to 2ffc974 Compare May 23, 2019 22:51
@cleverca22 cleverca22 force-pushed the jal-infra-monitoring-wireguard branch from 2ffc974 to 61b7c9c Compare May 23, 2019 23:03
@cleverca22 cleverca22 merged commit 8414034 into jal-infra-monitoring May 24, 2019
@iohk-bors iohk-bors bot deleted the jal-infra-monitoring-wireguard branch May 24, 2019 02:21
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants