payload: {"action":"opened","issue":{"url":"https://api.github.com/repos/snowplow/snowplow/issues/4019","repository_url":"https://api.github.com/repos/snowplow/snowplow","labels_url":"https://api.github.com/repos/snowplow/snowplow/issues/4019/labels{/name}","comments_url":"https://api.github.com/repos/snowplow/snowplow/issues/4019/comments","events_url":"https://api.github.com/repos/snowplow/snowplow/issues/4019/events","html_url":"https://github.com/snowplow/snowplow/issues/4019","id":424579737,"node_id":"MDU6SXNzdWU0MjQ1Nzk3Mzc=","number":4019,"title":"EmrEtlRunner: investigate possibility of deploying cluster across multiple subnets and AZs","user":{"login":"jbeemster","id":7984544,"node_id":"MDQ6VXNlcjc5ODQ1NDQ=","avatar_url":"https://avatars1.githubusercontent.com/u/7984544?v=4","gravatar_id":"","url":"https://api.github.com/users/jbeemster","html_url":"https://github.com/jbeemster","followers_url":"https://api.github.com/users/jbeemster/followers","following_url":"https://api.github.com/users/jbeemster/following{/other_user}","gists_url":"https://api.github.com/users/jbeemster/gists{/gist_id}","starred_url":"https://api.github.com/users/jbeemster/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbeemster/subscriptions","organizations_url":"https://api.github.com/users/jbeemster/orgs","repos_url":"https://api.github.com/users/jbeemster/repos","events_url":"https://api.github.com/users/jbeemster/events{/privacy}","received_events_url":"https://api.github.com/users/jbeemster/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-03-24T06:18:40Z","updated_at":"2019-03-24T06:18:40Z","closed_at":null,"author_association":"MEMBER","body":"Currently we can only specify a single subnet for the EMR cluster but in the case of an outage affecting launching new EC2 nodes in a single AZ within a region this can mean that we cannot launch any EMR clusters.\r\n\r\nBy being able to specify multiple subnets and therefore multiple AZs we can achieve a highly available cluster which would work around the problem we saw on Friday night when EC2 decided not to work in us-east-1a.\r\n\r\ncc/ @ihortom "}}
other: {"actor":{"display_login":"jbeemster"}}