Closed 1rjt closed 10 months ago
Hello, there are now two possible ways to work around this:
var config = new AmazonS3CryptoConfigurationV2(securityProfile)
{
Timeout = TimeSpan.FromSeconds(10) // this will apply to both S3 and KMS
}
var config = new AmazonS3CryptoConfigurationV2(securityProfile)
{
KmsConfig = new AmazonKeyManagementServiceConfig
{
Timeout = TimeSpan.FromSeconds(10) // this will only apply to KMS
}
};
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Description
A client timeout can be set via AmazonS3CryptoConfigurationV2.Timeout but this value is not used by the internal KMSClient. The internal KMS client does not have a timeout set so is always 100 seconds
The only value copied over to the KMS client config is region endpoint https://github.com/aws/amazon-s3-encryption-client-dotnet/blob/main/src/AmazonS3EncryptionClientBase.cs#L54
Reproduction Steps
Logs
Environment
Resolution
This is a :bug: bug-report