I think we’re going to need a bit more info to get to the bottom of this. As a start, I would say that this tutorial is now more complex than it needs to be: if this is your first time working with Vault, you might want to consider using one of the official HashiCorp packages, instead of doing a manual installation.
That said, I would say that that isn’t your problem. It’s likely that Vault doesn’t have the proper permissions to write to your S3 bucket.
Can you share some of what systemctl / journalctl are showing as logged around the time of this error? And maybe your Vault configuration file (without the secrets)?
Please let me know if something else is needed.
I will check on the policies to the attached IAM role on the EC2 where I am running this.
Do we also need to configure a bucket policy in this setup?
So I have not set S3 with KMS. Its just a normal S3 bucket with default settings, nothing different.
I checked the role attached to the EC2 instance and it has list and put object access to the given S3 bucket.
I am new to Vault, so can you tell me about the api_addr paramter actually. I looked up in the documentation but still do not have a clear understanding on what it should be set to.
Can anyone please provide links or videos for the same?
My use case is to setup vault so that I can store the keys that I use to encrypt data stored in S3. If anyone can provide links or videos to this as well that would be really helpful!