Netlix is still using Edda internally, but the code base has diverged from the OSS version. Our internal deployment of Spinnaker relies on it heavily, for example.
At some point, I am interested in modernizing the OSS code base with some of the internal improvements, so that it is more consistently usable externally.
Edda is intended to help with the AWS API throttling use-case, provided that the majority of your other API use cases query Edda instead of AWS.
The Spinnaker Redis cache relies on loading data from Edda, but it can be configured to fall-back to AWS APIs.
As long as you can work with your AWS support representatives to scale your API throttling to support Edda, then you should be fine.