Use configure-aws-credentials instead of passing secret_access_key

[vudiep411]

The problem/use-case that the feature addresses
API calls to AWS need to be signed with credential information, so when you use one of the AWS SDKs or an AWS tool, you must provide it with AWS credentials and and AWS region. One way to do that in GitHub Actions is to use a repository secret with IAM credentials, but this doesn't follow AWS security guidelines on using long term creds.

Description of the feature

• First we need to set up OpenID Connect. OpenID with AWS
• Then Implement the workflow using configure-aws-credentials

- name: Configure AWS Credentials for China region audience
      uses: aws-actions/configure-aws-credentials@v4
      with:
        aws-region: us-east-3
        role-to-assume: arn:aws-cn:iam::123456789100:role/my-github-actions-role

By using this approach we can get rid off the secret keys needed to pass in and also organize the workflow

[madolson]

@roshkhatri Can you look into this? I would love to get rid of long term credentials

[roshkhatri]

Sure, I will also look in to it with @vudiep411 but he will primarily be looking into this. He is also from Amazon.

Meanwhile, @vudiep411 can you make these changes in your repo and raise a PR.
Once it looks good we can replicated those changes on valkey repo.

[vudiep411]

yea definitely. I'm working on that right now on a DEV env AWS account