Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot configure AWS S3 Tier2 storage in Helm chart #489

Closed
junglie85 opened this issue Dec 20, 2020 · 0 comments · Fixed by #585
Closed

Cannot configure AWS S3 Tier2 storage in Helm chart #489

junglie85 opened this issue Dec 20, 2020 · 0 comments · Fixed by #585

Comments

@junglie85
Copy link

I'd like to configure Pravega Tier2 storage to use AWS S3. My understanding from the long term storage docs is that any S3 compatible backend is supported. However, I can't seem to get this working in my Kubernetes cluster.

I'm using the following secret:

apiVersion: v1
kind: Secret
metadata:
  name: aws-credentials
type: Opaque
stringData:
  ACCESS_KEY_ID: [AWS_ACCESS_KEY_ID]
  SECRET_KEY: [AWS_SECRET_ACCESS_KEY]

And the relevant Helm values for the Pravega cluster configuration:

storage:
  longtermStorage:
    type: ecs
    ecs:
      configUri: https://s3.eu-west-2.amazonaws.com
      bucket: "my-aws-s3-bucket"
      prefix: "my-prefix"
      credentials: aws-credentials

Using the toy NFS example I can write to and read from a stream. However, with the above configuration the deployment of Pravega fails. Has anyone had any success with AWS S3 as a Tier2 storage?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant