Adding some notes and cleaning up some notes.

environments/aws-snowplow/README.md

@@ -37,12 +37,6 @@ do that on their own.
 * SnowplowEnrich-gitlab-us-east-1
 * SnowplowS3Loader-gitlab-us-east-1
 
-Going to probably need an elastic IP for the snowplow endpoint. Revisit this!
-
-IAM Policies and Roles:
-Need roles/policies to allow proper access to the collectors, enrichers and s3 loaders.
-ECS Tasks need a IAM role to allow access to things? Yes.
-
 ## Launch Config Changes and Production Instances
 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
@@ -67,6 +61,11 @@ 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…"
 
+IAM Policies and Roles:
+Need roles/policies to allow proper access to the collectors, enrichers and s3 loaders.
+
+Trim down the firehose role?
+
 Last steps:
 Are we using the right SSH key?
 Did we clean up everything we made for testing?