Update protocol and target port list

[jason-linthwaite]

I don't know if anybody else would want this but two changes here:

1. The protocol includes the "colon". For me the scheme should not include the colon and is redundant data
2. The target:port_list conflicts with another field that's parsed in using logstash (I have two concurrent processes loading data). The logstash filters use the column name "target_port_list" and it's more complicated to change that so just removing the special character from this field

Thoughts?

[igtm]

Thank you for sending me PR!

(1) looked good to me at a glance. but I found this.
Although it seems controversial, i'd follow this low layer implementation.
and this change may break other apps...
You can trim after parsing URL if you like.

(2) Although i'm not sure the logstash implementation, I think it's better to do "as it is" because target:port_list is written in AWS documentation and there may be lots of users who don't use logstash.

[igtm]

inactive issue. thanks for your great suggestion!