I'm deploying RisingWave on EKS with S3 as the state store, and I'm encountering an error from the metastore indicating an issue with accessing the object storage. I've tried following the AWS EKS IAM guide for S3, but I'm still facing the same error. The error message is not very informative, just mentioning a service error and ObjectError. I've also tried using both Access Key/Secret Key (AK/SK) and IAM roles for service accounts, but the error persists. How can I resolve this issue?
Matan Perelmuter
Asked on Jul 27, 2023
I resolved the issue with RisingWave deployment on EKS with S3. The problem was with the IAM policy. I needed to specify two resources in my IAM policy, one with a wildcard and one without: arn:aws:s3:::risingwave/* and arn:aws:s3:::risingwave. After adjusting the IAM policy to include both resource paths, the deployment succeeded. This was necessary because RisingWave requires access to both the bucket itself and the objects within it.
