Print AWS request information to debug log

[phinze]

Back in goamz days the debug log could be used to ensure the proper data was going over the wire to AWS. As we switched to aws-sdk-go, all of the struct members are now pointers, which makes the debug output basically just a bunch of memory addresses.

[DEBUG] ELB create configuration: &elb.CreateLoadBalancerInput{AvailabilityZones:[]*string{(*string)(0xc208d85fc0), (*string)(0xc208d85fd0), (*string)(0xc208d85fe0), (*string)(0xc208d85ff0)}...

We should figure out how to get these structs to print to the log nicely and make a sweep of the AWS provider.

[clstokes]

Perhaps related to #2875?

[phinze]

This was actually just related to aws/aws-sdk-go#299 and our using it to get pretty request / response information into the debug log. We do this now for AWS resources.

Specific instances of cryptic error messaging are good to track as individudal cases.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.