Any specific AWS ELB Settings Needed (like cipher suites)?

We use looker within AWS.
We have an ELB infront of a bunch of Looker Instances.

We have port 443 and port 19999 open, but we’ve added a custom ELB policy, and I’m not sure if this was recommended by someone in this forum or by our previous Looker rep:

=========== (sudo code)
aws_lb_ssl_negotiation_policy
  # protocol preferences
  attribute { name = "Protocol-TLSv1.2", value = "true" }
  attribute { name = "Server-Defined-Cipher-Order", value = "true" }

  # cipher preferences
  attribute { name = "ECDHE-ECDSA-AES128-GCM-SHA256", value = "true" }
  attribute { name = "ECDHE-ECDSA-AES128-SHA256", value = "true" }
  attribute { name = "ECDHE-ECDSA-AES256-GCM-SHA384", value = "true" }
  attribute { name = "ECDHE-ECDSA-AES256-SHA384", value = "true" }
  attribute { name = "ECDHE-RSA-AES128-GCM-SHA256", value = "true" }
  attribute { name = "ECDHE-RSA-AES128-SHA256", value = "true" }
  attribute { name = "ECDHE-RSA-AES256-GCM-SHA384", value = "true" }
  attribute { name = "ECDHE-RSA-AES256-SHA384", value = "true" }
  attribute { name = "AES128-GCM-SHA256", value = "true" }
  attribute { name = "AES128-SHA256", value = "true" }
  attribute { name = "AES256-GCM-SHA384", value = "true" }
  attribute { name = "AES256-SHA256", value = "true" }
===========

Is there anything specific we have to tweak on an AWS ELB to have Looker run behind it?
I can’t find any documentation on way or another, which is why I decided to post here.
Thanks!

I touched base with our ops team to see what was up. The word from on high: It’s recommended to use the default “amazon canned” cipher suite unless you are using really old browsers, which can sometimes have some problems with modern TLS/SSL.

So, I don’t think those are looker recommended cipher suites! Not sure where they came from.