Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Feature Request: API Support for EMR Studio Workspace Management

0

We're looking for native API/CLI/SDK support to manage EMR Studio workspaces programmatically. Currently, these operations (create, list, delete, etc.) are only possible via the UI, making it difficult to integrate with Terraform or CI/CD pipelines.

Current Limitations:

  • No API/CLI/Terraform support for workspace-level actions.
  • Terraform destroy fails if workspaces exist, requiring manual cleanup.
  • CI/CD automation is broken due to lack of workspace lifecycle control.
  • Increased ops overhead due to manual intervention.

Business Impact:

  • Slows down infrastructure automation.
  • Leads to orphaned resources and higher costs.
  • Manual steps hinder team scalability.

Feature Request: Please provide API support for: listing, creating, deleting, updating, and describing EMR Studio workspaces.

Use Cases:

  • Full infra-as-code support with Terraform/CDK
  • Seamless CI/CD environment cleanup
  • Internal tooling integrations

I don't think any workarounds exist besides a manual cleanup in the console.

Related GitHub Issue: #38666

This is a high-impact ask—many teams would benefit from smoother EMR Studio integration. Happy to share more details if helpful.

Topics
Analytics
Tags
Amazon EMRAmazon EMR StudioTerraform
Language
English
asked a year ago209 views
1 Answer
-1

Thank you for your detailed feature request regarding API support for EMR Studio Workspace management. We understand your need for programmatic control over EMR Studio Workspaces for better automation and CI/CD pipeline integration.

This is already a feature request, so I will add +1 behalf your inquiry. AWS is continuously improving its services and you can keep track of AWS latest services and products.

However, there is no ETA on when this functionality will be implemented, but you can always keep an eye on what's new at AWS (https://aws.amazon.com/new/ ) to track the latest releasing features. As you mentioned, it will be more better to raise a case and state it's a PFR, or escalate through any formal AWS contacts you have, e.g. an Enterprise Support TAM.

I hope you found this information useful.

Thank you.

Regards, NohJeong

answered a year ago
  • DimitarD
    a year ago

    Getting a standardized chatbot response is not too helpful in this case. I will submit the feature request via a direct AWS Support Case.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content