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

Amazon S3 Tables with EMR on EKS, Spark blueprints #713

Open
askulkarni2 opened this issue Dec 10, 2024 · 0 comments
Open

Amazon S3 Tables with EMR on EKS, Spark blueprints #713

askulkarni2 opened this issue Dec 10, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@askulkarni2
Copy link
Collaborator

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

Amazon S3 Tables was announced at Re:Invent 2024. This is a feature request for an example with the existing EMR on EKS and OSS Spark blueprints to show use of Amazon S3 Tables. (Ref: https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-tables-integrating-open-source-spark.html)

Describe the solution you would like

A complete example showing, granular access control, cloudtrail logging, maybe a benchmark too.

Describe alternatives you have considered

Glue Catalog

Additional context

This is not a request for a completely new blueprint. The current blueprints should be enhanced with the S3 Tables example.

@askulkarni2 askulkarni2 added the enhancement New feature or request label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants