Feature Request: EMR Serverless support

[dacort]

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

Description

EMR Serverless is a new serverless Spark/Hive platform currently in preview.

New or Affected Resource(s)

• aws_emrserverless_application

Potential Terraform Configuration

resource "aws_emrserverless_application" "example" {
  name = "example-application"
  type = "SPARK"
  release_label = "emr-6.5.0-latest"
}

References

• https://docs.aws.amazon.com/emr/latest/EMR-Serverless-UserGuide/emr-serverless.html
• https://aws.amazon.com/blogs/big-data/announcing-amazon-emr-serverless-preview-run-big-data-applications-without-managing-servers/

Happy to help build this. :)

[bschaatsbergen]

Hi @dacort,

Thanks for raising this. I'm not sure if it's a good idea to add a sign-up based preview feature to the provider as it's subject to change and not accessible for everyone.

How do we usually go about this? @justinretzolk

[dacort]

Hi @bschaatsbergen - completely agree, but wanted to be proactive and get the feature request filed.

My thought was to at least begin development/testing locally, and have a PR ready for when the feature is generally available.

[justinretzolk]

Hey @dacort and @bschaatsbergen 👋 Thank you for taking the time to raise this! We've done public preview items before; typically we add a note in the docs warning that there's no guarantee of stability

I'm not familiar enough to know how popular this particular feature will wind up being, but thinking through it, it may be worth waiting until the feature is generally available, in case there's not enough community feedback to have this get prioritized before some sort of breaking change gets introduced. That said, this being a preview feature won't stop us from reviewing a PR if time/feedback from the community indicates we should 🙂

[dacort]

Thanks, @justinretzolk! That makes perfect sense. I agree we should wait until the feature is GA so that we can be confident the API won't change. I'll continue to work on it locally.

Thanks for the feedback, very much appreciated! 🙏

[ewbankkit]

Now GA:

• Announcement
• Blog post

[dacort]

Indeed!

Looks like aws-sdk-go has already been bumped to v1.44.25, which has support for EMR Serverless. I've started doing a little development locally, but haven't added a service from scratch before so a little bit slow-going. 😁

[bschaatsbergen]

Great @dacort, if I can give you a hand let me know. I'll keep an eye out on the PR 👍

[dacort]

Looks like @DrFaust92 was much faster than I! See #25144

[bryantbiggs]

I don't know when @DrFaust92 sleeps - or I think he has crafty auto-generate-provider-code tool and he's not telling us 😅

[bschaatsbergen]

Damn, he always beats us to it! Nevertheless, nice work @DrFaust92 😜

[DrFaust92]

Thanks all, was planning to look into it and missed this ticket.

[github-actions]

This functionality has been released in v4.18.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.