07-19-2020 22:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-19-2020 22:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
We are trying to whitelist Fitbit source IPs based on recommended approach FCrDNS. But AWS API Gateway appears not to be supporting this. Is there any other way to have some access control to the updates API with AWS API Gateway?

- Labels:
-
Subscriptions API
07-20-2020 09:17
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-20-2020 09:17
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I brought up a similar question a while back in this thread. It doesn't seem like an alternative will be provided.
07-28-2020 02:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-28-2020 02:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks for the advise. Using the signature header is one way but, the point of doing this earlier at the gateway level is to potentially block malicious attackers from hitting the backend with many invalid requests. So I am still looking for a viable alternative.

09-01-2020 01:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

09-01-2020 01:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I would appreciate if FitBit support team can advise.

09-03-2020 05:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

09-03-2020 05:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
This wasn't a blocker for my team, but we also would have appreciated the additional layer of security. I was just made aware of feature requests recently and created a request to address this issue: FCrDNS Alternative - Add API Keys to Subscriptions.

