EmrEtlRunner: scrub credentials from stderr
See original GitHub issueSluice in particular can leak AWS access keys:
F, [2016-07-20T07:38:49.964000 #27217] FATAL -- : Excon::Errors::Forbidden (Expected(200) <=> Actual(403 Forbidden) excon.error.response :body => "<?xml version=\"1.0\" encoding=\"UTF-8\"?> <Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>NEEDS REDACTING</AWSAccessKeyId><StringToSign>GET
/cc @jbeemster
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
EmrEtlRunner | Snowplow Documentation
Snowplow EmrEtlRunner is a deprecated application that ran Snowplow's batch processing jobs in AWS EMR, such as the RDB shredder.
Read more >snowplow/snowplow r112-baalbek on GitHub - NewReleases.io
This release brings reliability improvements to the batch pipeline. Blog post. EmrEtlRunner. Bump to 0.34.0 (#3935); Add support for running steps on a ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Shall we de-schedule?
Didn’t have time to fully investigate, but we’re now using the official aws sdk so it shouldn’t leak credentials. The example above is definitely taken care of now.