-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VPC endpoint to unirpc #881
base: main
Are you sure you want to change the base?
Conversation
melodylove-uniswap
commented
Oct 19, 2024
•
edited
Loading
edited
- put routing-api behind a vpc
- created a vpc endpoint to connect to unirpc vpc endpoint service in uniswap-backend account
- created route53 to point routing-dev to the vpc endpoint to avoid updating the endpoint on the service side.
d9bd8a0
to
5a50abc
Compare
Graphite Automations"Request reviewers once CI passes on routing-api repo" took an action on this PR • (10/31/24)1 assignee was added and 5 reviewers were added to this PR based on 's automation. |
@@ -171,6 +244,8 @@ export class RoutingLambdaStack extends cdk.NestedStack { | |||
runtime: aws_lambda.Runtime.NODEJS_18_X, | |||
entry: path.join(__dirname, '../../lib/handlers/index.ts'), | |||
handler: 'quoteHandler', | |||
vpc: vpc, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it possible to set vpc to only caching routing lambda first?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated to put both lambda under vpc as we discussed
996fb92
to
452fcb6
Compare
cidrMask: 24, // IP range for private subnet | ||
}, | ||
], | ||
natGateways: 1, // One NAT Gateway for private subnet internet access |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure if related but good to mention here:
on the unirpc side we started hitting a port connections limit once i started ramping up traffic for routing api
It's weird that routing api lambda didn't hit similar issue, as it is doing similar size of http calls to QN directly.
After further digging, I see that routing api default VPC doesn't have a NAT gateway (and can't see active connections dashboards)?
But with this change we are introducing new VPC with NAT gateway, so trying to understand if that might cause issues due to high amount of traffic.
Anyway we could test the new vpc introduction somehow before fully enabling?
452fcb6
to
e8bc29a
Compare