That's my post, and my misunderstanding. I'll clean it up now, thanks!
Is there any chance the limit of 10 rules will be increased?
Most AWS limitations can be increased by asking support.
BTW, is there any place to log feature requests?
Become a big enough customer
I run an AWS partner who deals with many large ($millions a year each but not tens of millions each) aws customers.
It seems like the number of customers asking for a feature is more important than the size of those customers in my experience.
Re:AWS Application Load Balancer
by gerhardhaering on Thursday August 11, 2016 @02:38PM
(#12270642)
We have the AWS Business support plan. If you have it, you can file feature requests using the support interface.
Those underlined headers hurt the eyes. Could you please switch to a different heading style, please? Maybe smallcaps?
EDIT: And while you're listening: AWS documentation is a mess in the sense that it's way too unorganized; it might be documented but one cannot find it easily.
ELBs (Classic and Application) do support IPv6. You can CNAME or ALIAS to dualstack.[elb-name].
The endpoints are available but traffic silently fails when you are in a VPC.
I was primarily referring to EC2.
Why do you need IPv6? It seems pretty unnecessary in a VPC.
https://developer.apple.com/news/?id=05042016a
> Starting June 1, 2016 all apps submitted to the App Store must support IPv6-only networking.
IPv4 traffic over IPv6 is permitted, though. They just want you to use APIs that work independently of the underlying decision to use IPv4 or IPv6.
Re:AWS Application Load Balancer
by nighthawk454 on Thursday August 11, 2016 @02:09PM
(#12270435)
S3 now supports IPv6 according to this: https://news.ycombinator.com/item?id=12269278
I thought that Classic LB's gave you an AAAA endpoint? Am I mistaken?
Waiting for AWS to embrace IPv6.