-
Notifications
You must be signed in to change notification settings - Fork 27
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
Use S3 VPC Gateway Endpoint #5865
Comments
On 27. Sept. 2024: Enabled AWS VPC S3 Gateway Endpoint for osparc-master-zmt.click via the AWS console (no terraform) in us-east-1 |
@YuryHrytsuk @mrnicegyu11 Could you please include here (or a link to it) some evidence (e.g., plots or metrics) that quantifies the extent of the improvement? This can be used for the review meeting. thx |
DirtyS3APIBenchmark-Copy1.zip To test this, we have enabled the The jupyter notebook code executed is attached to this comment. In our tests we see no speedup of aws-master w.r.t. osparc-staging.io.
@mguidon FYI |
Also, @mrnicegyu11 On what ec2 instance type have you been running those tests? |
@mrnicegyu11 Can this be closed? |
Yes this can be considered done, thx |
Concept
Currently, we talk to S3 via the internet. We should use the S3 Endpoint which will talk directly within AWS network and without costs if it is in the same region & load balancing cost should decrease
Tasks
The text was updated successfully, but these errors were encountered: