{"action":"created","issue":{"url":"https://api.github.com/repos/jlund/streisand/issues/320","repository_url":"https://api.github.com/repos/jlund/streisand","labels_url":"https://api.github.com/repos/jlund/streisand/issues/320/labels{/name}","comments_url":"https://api.github.com/repos/jlund/streisand/issues/320/comments","events_url":"https://api.github.com/repos/jlund/streisand/issues/320/events","html_url":"https://github.com/jlund/streisand/issues/320","id":158487462,"number":320,"title":"Assign Elastic IP to AWS EC2 instances","user":{"login":"johnjeffers","id":11821214,"avatar_url":"https://avatars.githubusercontent.com/u/11821214?v=3","gravatar_id":"","url":"https://api.github.com/users/johnjeffers","html_url":"https://github.com/johnjeffers","followers_url":"https://api.github.com/users/johnjeffers/followers","following_url":"https://api.github.com/users/johnjeffers/following{/other_user}","gists_url":"https://api.github.com/users/johnjeffers/gists{/gist_id}","starred_url":"https://api.github.com/users/johnjeffers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/johnjeffers/subscriptions","organizations_url":"https://api.github.com/users/johnjeffers/orgs","repos_url":"https://api.github.com/users/johnjeffers/repos","events_url":"https://api.github.com/users/johnjeffers/events{/privacy}","received_events_url":"https://api.github.com/users/johnjeffers/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-06-04T04:53:44Z","updated_at":"2016-06-07T00:11:05Z","closed_at":"2016-06-07T00:11:05Z","body":"For EC2 instances with public IP addresses, it’s usually desirable to assign an Elastic IP to the instance to ensure that the public IP does not change.\r\n\r\nWithout an Elastic IP, the public IP address will change any time the instance is stopped or restarted. If the public IP of the instance changes, it will break all sorts of things.\r\n\r\nThis update will associate an Elastic IP address to the EC2 instance immediately after instance creation, and assigns the Elastic IP to the streisand_ipv4_address variable for use in the rest of the playbook.\r\n\r\nEDIT: This is now a pull request.\r\n\r\nhttps://github.com/jlund/streisand/pull/323\r\n"},"comment":{"url":"https://api.github.com/repos/jlund/streisand/issues/comments/224126087","html_url":"https://github.com/jlund/streisand/issues/320#issuecomment-224126087","issue_url":"https://api.github.com/repos/jlund/streisand/issues/320","id":224126087,"user":{"login":"jlund","id":144984,"avatar_url":"https://avatars.githubusercontent.com/u/144984?v=3","gravatar_id":"","url":"https://api.github.com/users/jlund","html_url":"https://github.com/jlund","followers_url":"https://api.github.com/users/jlund/followers","following_url":"https://api.github.com/users/jlund/following{/other_user}","gists_url":"https://api.github.com/users/jlund/gists{/gist_id}","starred_url":"https://api.github.com/users/jlund/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jlund/subscriptions","organizations_url":"https://api.github.com/users/jlund/orgs","repos_url":"https://api.github.com/users/jlund/repos","events_url":"https://api.github.com/users/jlund/events{/privacy}","received_events_url":"https://api.github.com/users/jlund/received_events","type":"User","site_admin":false},"created_at":"2016-06-07T00:11:04Z","updated_at":"2016-06-07T00:11:04Z","body":"For this issue, I was planning on making automatic EIP assignment for new EC2 instances part of the default behavior, and I'm grateful to @johnjeffers for making it happen. Not having this in place was causing a lot of problems when an instance had to go through a stop/start cycle and came up with a completely different address. It has been in my backlog for a while.\r\n\r\nRegarding the rest of the discussion, the primary goal of the project is to help people bypass censorship as seamlessly as possible. However, I am also passionate about privacy and anonymity as well. That's why I included support for Tor Bridges from day one.\r\n\r\nI think the discussion here is really interesting, and it seems closely related to #319 too. It's clearly a common pain point for users in China to have to swap their IP addresses on a somewhat regular basis and deal with the configuration changes that necessarily follow. I want to do something to make that easier.\r\n\r\nAt the same time, I also would like people to see their servers as ephemeral and easy to replace. I'm not sure yet how to walk the line between these two worlds, but I think we can figure it out. Let's continue the discussion in #319."}}
{"actor":{"display_login":"jlund"}}