AWS S3 credentials access denied

Hello.

When I try to deploy with the following values:

  values:
    pod:
      env:
        - name: AWS_REGION
          value: us-east-2
        - name: AWS_DEFAULT_REGION
          value: us-east-2
    license:
      key: ##########################
    service:
      type: LoadBalancer
      port: 80
      targetPort: 4242
    awsAccessKeyId: ##########################
    awsSecretAccessKey: ##########################
    config:
      Storage:
        Default: s3
      S3Storage:
        Bucket: rstudio-pm-manual-test

I'm getting the following error:

2022/02/18 18:16:37 Error running services: Error validating S3 session for 'cache': Something went wrong uploading to S3. You may want to check your configuration, error: AccessDenied: Access Denied
        status code: 403, request id: ##########################, host id: ##########################

I checked the secret. It seems fine:

kubectl get secrets rstudio-pm-aws-creds -o yaml
apiVersion: v1
data:
  credentials: ##########################
kind: Secret
metadata:
  annotations:
    meta.helm.sh/release-name: rstudio-pm
    meta.helm.sh/release-namespace: rstudio-pm
  creationTimestamp: "2022-02-18T18:16:26Z"
  labels:
    app.kubernetes.io/managed-by: Helm
    helm.toolkit.fluxcd.io/name: rstudio-pm
    helm.toolkit.fluxcd.io/namespace: rstudio-pm
    manager: helm-controller
    operation: Update
    time: "2022-02-18T18:16:26Z"
  name: rstudio-pm-aws-creds
  namespace: rstudio-pm
  resourceVersion: "783162"
  uid: 26f80151-eb54-417f-af05-a1cdabf92983
type: Opaque
$ echo ##########################|  base64 -d
[default] 
aws_access_key_id=##########################
aws_secret_access_key=##########################

Could you help me?

Start with the Helm deployment values and the rstudio-pm-aws-creds Kubernetes Secret shown in the report, then review the S3 session validation error and its 403 response. Confirm the configured AWS credentials have the required access to the rstudio-pm-manual-test bucket; done means deployment completes without the cache S3 validation error.