Store Vault secrets in S3 bucket - amazon-s3

I am trying to store the Vault kv in an AWS S3 bucket.
I deployed Vault in Kubernetes using Helm and also enabled the Kubernetes auth methods.
In the Helm chart values.yaml I have all the credentials required for S3,
vault:
config:
storage:
s3:
access_key: "AWS-ACCESS-KEY"
secret_key: "AWS-SECRET-KEY"
bucket: "AWS-BUCKET"
region: "eu-central-1"
If I use this configuration locally then it works.
Can somebody please provide any working examples for this.
Any help is appreciated.
Thanks

Related

How to read the AWS secrets to karate-configuration file

Created secrets in AWS secret manager. Not sure how to read the secretes to the karate configuration file.
retrieving the secrets from AWS secrete Manager.

Use AWS KMS for encrypt/decrypt secrets in spring-cloud-config server

How to make use of KMS for encrypting and decrypting secrets in the spring cloud config server?

How to access AWS S3 bucket from digital ocean server without access key and secret key

We are planning to continuously generate logs moving from the digital ocean Server to AWS S3 Bucket without access key and secret key

I don't think you can access S3 like that

Is Minio S3 api is compatible with Amazon's S3

I want to have my own private hosted object storage with S3 compatibility.
Now I found minio as a solution. My question is: If I have an application A that is able to connect to amazon S3 storage does that imply that I could also connect to minio?
More specifically if minio created a presigned URL is application A (capable of amazon S3) also able to use the presigned URL?

Yes, minio is compatible with AWS S3. You can have your application that is currently connecting to AWS S3 connect to minio.
Presigned URLs can be used by any application as long as they have not expired.
If you are just starting out on minio, please join our slack channel at https://slack.min.io

How to disable TLS 1.0 for AWS S3 buckets

We are using AWS S3 buckets to store files. Public URL is generated to share with clients. We want to block TLS 1.0 for the bucket. Please advise.