Commit 0b667610 authored by Cameron McFarland's avatar Cameron McFarland

Feedback from @skarbek to make things better.

parent 72aa5c22
......@@ -12,8 +12,8 @@ may be more in use, but these are the primary services.
1. VPC (Subnets, VPC, Internet Gateways, Routes, Routing Tables)
## Design Document
If you want to know more about the SnowPlow infrastructure, please consult
the design document. XXX
If you want to know more about the SnowPlow infrastructure, please consult the
[design document](https://about.gitlab.com/handbook/engineering/infrastructure/design/snowplow/).
## SnowPlow Installs and Configs
There are two types of SnowPlow nodes (Collectors and Enrichers) and they are
......@@ -45,25 +45,6 @@ Updating the launch config will apply to new systems coming up in the
auto-scaling group. But existing EC2 instances won't be changed. You will
have to rotate them manually to have them replaced.
## Runbook Material
### Logs
You should find logs for any node to be in **/snowplow/logs**.
### SSL Certificate
### SSL Certificate for Load Balancer
This is referenced as an ARN to the cert in AWS. We're not going to put the
private key in TF, so this will have to remain as an ARN reference.
[ec2-user@ip-10-32-0-206 ~]$ curl http://localhost:8000/health
OK[ec2-user@ip-10-32-0-206 ~]$
Debugging: -Dorg.slf4j.simpleLogger.defaultLogLevel=debug
Testing an event: curl http://34.227.92.217:8000/i\?e\=pv
S3Loader:
"I realize now my folly: the app name needs to be different between the enricher and loader ergo the 2 dynamoDB tables were conflicting. Everything makes so much sense now…"
Last steps:
Are we using the right SSH key?
Did we clean up everything we made for testing?
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment