[DRIVERS-2701] Investigate AWS Lambda cold start performance with various configurations Created: 22/Aug/23  Updated: 11/Jan/24  Resolved: 11/Jan/24

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Shane Harvey Assignee: Durran Jordan
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Driver Changes: Not Needed
Quarter: FY24Q4
Start date:

 Description   

Summary

Investigate AWS Lambda cold start performance with:

  • Cluster and load balancer through privatelink with X.509 auth.
  • Cluster using AWS machine workflow for OIDC
  • Cluster using MONGODB-AWS auth
  • Cluster using SCRAM-SHA-1
  • Cluster using SCRAM-SHA-256

Motivation

Who is the affected end user?

Who are the stakeholders?

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

How likely is it that this problem or use case will occur?

Main path? Edge case?

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?



 Comments   
Comment by Durran Jordan [ 15/Sep/23 ]

Starting 14. Sep on OIDC with AWS machine workflow.

Generated at Thu Feb 08 08:26:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.