.Net core DI resolution of IAmazonDynamoDb takes 10+ seconds

[minus-5]

I'm using IAmazonDynamoDb as a dynamodb client to perform some low-level dynamo db queries like ScanAsync, UpdateItemAsync etc.. and I've noticed that it takes more than 10 seconds to resolve a service that uses IAmazonDynamoDb as a dependency for the first time. So I can assume that probably during construction of IAmazonDynamoDb instance it makes some network calls to populate caches etc.. Is my assumption correct and if yes is there any way to speed up this process?

[ashishdhingra]

@minus-5 Good afternoon. Thanks for starting the discussion. Could you please share sample code to reproduce the issue?

[minus-5]

Hello @ashishdhingra, I've uploaded a sample project that reproduces the issue https://github.com/minus-5/awssdk-issueRepro

[ashishdhingra]

@minus-5 At high level, when using DI, AWSSDK.Extensions.NETCore.Setup would:

• Read configuration from the appsettings.json
• Determine credentials
• Create service client object.

In case on DynamoDB, spending on the operation used, it also populates internal config (as pointed out by you). Could you try enabling client side verbose logging using below minimal statements (before the code which configures DI) and see if you are able to capture detailed logs:

Amazon.AWSConfigs.LoggingConfig.LogResponses = Amazon.ResponseLoggingOption.Always;
Amazon.AWSConfigs.LoggingConfig.LogTo = Amazon.LoggingOptions.SystemDiagnostics;
Amazon.AWSConfigs.AddTraceListener("Amazon", new System.Diagnostics.ConsoleTraceListener());

You may also try setting EndpointDiscoveryEnabled to false on AmazonDynamoDBConfig (may be via appsettings.json file) to see if it helps improve performance.

Thanks,
Ashish

[minus-5]

Hello Ashish, thank you for your help, I made the changes that you suggested and here are the logs that I got

Regarding setting EndpointDiscoveryEnabled to false, I've noticed that it's set to false by default, so it doesn't help me much. Maybe the reason why I'm having this problem is because I don't use AWS CLI, I manually created a file .aws/credentials and put my credentials there

[ashishdhingra]

@minus-5 It appears that your .aws/credentials file is not read since it appears to be failing at EC2 instance metadata check. Are you using 3rd party AWS simulated solution since it appears from the discussion title that after 10+ seconds, you are able to access DynamoDB service?

If you platform is Windows, you might want to check %USERPROFILE%. The credentials file needs to be in %USERPROFILE%\.aws folder.

Thanks,
Ashish

@github-actions proposed-answer

[minus-5]

@ashishdhingra The file with credentials is located in the folder that you've mentioned. I'm not using any 3rd party AWS simulated solution, I'm directly connecting to AWS, and I'm able to read and write data to my DynamoDB instance, the only problem is that for some reason it takes 5-10 seconds to resolve an instance of IAmazonDynamoDb for the first time

[ashishdhingra]

@minus-5 In your case, the credential resolution is failing after it tries all the credential generators. Do you have:

• default profile configured in your credentials file?, OR,
• Do you have a named profile?
• Do you have AWS_PROFILE environment variable set?

Could you please clarify what do you mean by directly connecting to AWS? Almost all AWS service API(s) require credentials of some form (either long term or short team). Could you please share the code which reproduces the issue?

Thanks,
Ashish

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.