Is the '/v1/oauth/token' rate-limited per IP and what is the recommended pattern for bursty cold-start fleets?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

hey hey

anyone hitting per-IP 429s on POST /v1/oauth/token recently?
started seeing them ~may 10 from server workloads (small egress IP pool). Same clientId/clientSecret:
• from my laptop → 200 OK
• from the worker → 429 with server: awselb/2.0, empty body
looks like an ELB-layer per IP cap rather than per-credential, since different PD projects hit the same wall

two questions:

  1. is /v1/oauth/token rate-limited per IP? i don’t see it on the Connect rate limits page
  2. recommended pattern for bursty cold-start fleets: is shared-bearer-across-processes the right move, or is there a better auth flow?
    using @pipedream/sdk@2.3.8
Are Per-IP 429 Errors Occurring on 'POST /v1/oauth/token'? What is the Recommended Auth Flow for Bursty Cold-Start Fleets?
2

That is possible — can you tell me more about what kind of volume you’re sending to that endpoint?

3

would you mind DM’ing us your project ID / egress IP range so I can take a look? We did recently set lower rate limits on /v1/oauth/token and to Danny’s question - would love to know what kind of traffic you’d need to send there.

4

thanks! DMed to Dylan (we already discussing the issue)!