Remove @aws-sdk/client-secrets-manager dependency from backend

[dangtony98]

Feature description

As part of the initiative to reduce dependencies on the backend, it'd be great to remove the @aws-sdk/client-secrets-manager dependency that's currently used as an SDK in the AWS secret manager (AWS SM) integration to sync secrets from Infisical to AWS SM.

This task involves replacing this dependency with the HTTPS Query API as mentioned here.

The HTTPS Query API gives you programmatic access to Secrets Manager and AWS. The HTTPS Query API allows you to issue HTTPS requests directly to the service and thus we can use it to create/read/update/delete secrets in AWS SM.

Why would it be useful?

This would further enhance the security of Infisical by reducing dependencies.

Additional context

This shouldn't be too difficult and I'd recommend it as a great first issue especially since the AWS SM integration is already made; we just need to refactor logic to use the HTTP Query API instead of the AWS SM SDK.

[abdullahranginwala]

I would love to work on this issue. Based on my initial look at the code, I have identified the following services/functions to be replaced with HTTPS Query API:
CreateSecretCommand, GetSecretValueCommand, ResourceNotFoundException, SecretsManagerClient, UpdateSecretCommand .

However, I couldn't find a detailed documentation for making the create/read/update/delete calls.

This seems like a straightforward implementation but some more context about the APIs will be extremely helpful.

[dangtony98]

That would be great @abdullahranginwala - Just assigned it to you!

Definitely join the Slack; best to communicate there

[abdullahranginwala]

I am unable to join slack since it requires a work email ending with @infisical.com

[JunedKhan101]

@abdullahranginwala I don't think so that is the case, I have joined the slack community with my gmail account.

[dangtony98]

Hi @abdullahranginwala,

Can you try joining via this link: https://infisical.com/slack

Let me know if it works!

[abdullahranginwala]

Yup, worked! I was trying to access the other link

[abdullahranginwala]

Apologies for such a late reply. Is this issue still active? @dangtony98

[abdullahranginwala]

Upon further investigation, it seems the issue is more complex due to AWS Signature 4 authentication requirements. For now, I am setting this aside.

[dangtony98]

@abdullahranginwala Sounds good!