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

Support Amazon Managed Workflows for Apache Airflow #16432

Closed
kotobot opened this issue Nov 25, 2020 · 16 comments · Fixed by #16616
Closed

Support Amazon Managed Workflows for Apache Airflow #16432

kotobot opened this issue Nov 25, 2020 · 16 comments · Fixed by #16616
Assignees
Labels
new-resource Introduces a new resource. service/mwaa Issues and PRs that pertain to the mwaa service.
Milestone

Comments

@kotobot
Copy link

kotobot commented Nov 25, 2020

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

Recently Amazon introduced Managed Workflows for Apache Airflow: a feature that allows to schedule Airflow workflows in managed environment

New or Affected Resource(s)

No existing resources affected.
New resources:

  • aws_airflow_environment

Potential Terraform Configuration

resource "aws_airflow_environment" "airflow_test_env" {
  name = "MyAirflowEnvironment"
  airflow_version = "1.10.12"

  #each environment includes a scheduler, a web server, and a worker
  environment {
    class = "pw1.small"
    max_worker_count = 10 #workers automatically scale up and down according to workload
  }

  #role used to access DAGs, write logs, and run DAGs accessing other AWS resources.
  role_arn = data.airflow_role.arn

  #each environment occupies two AZs
  vpc_id = "vpc-01234567890abcdef"
  subnet1 = "subnet-01234567890abcdee"
  subnet2 = "subnet-01234567890abcdef"

  public = false #false by default

  dag_code {
    s3_bucket = "s3://test-airflow"
    dags_folder = "s3://test-airflow/dags"
    plugins_file = "s3://test-airflow/dags/plugins.zip" #optional
    requirements_file = "s3://test-airflow/dags/requirements.txt" #optional
  }

  #optional key-value map
  airflow_config = {
    "default_task_retries "  = 1
    "default_ui_timezone" = "UTC"
    "dag_concurrency" = 3
  }

  # optional with defaults like this
  logging {
    level = "INFO"
    task_logs = true
    webserver_logs = true
    scheduler_logs = true
    worker_logs = true
    dag_processing = true
  }

}

References

AWS blog post:
https://aws.amazon.com/blogs/aws/introducing-amazon-managed-workflows-for-apache-airflow-mwaa/

  • #0000
@kotobot kotobot added the enhancement Requests to existing resources that expand the functionality or scope. label Nov 25, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Nov 25, 2020
@ewbankkit
Copy link
Contributor

@bflad bflad added new-resource Introduces a new resource. and removed enhancement Requests to existing resources that expand the functionality or scope. needs-triage Waiting for first response or review from a maintainer. labels Nov 25, 2020
@bflad bflad added the service/mwaa Issues and PRs that pertain to the mwaa service. label Dec 2, 2020
@shuheiktgw
Copy link
Collaborator

shuheiktgw commented Dec 18, 2020

The PR is ready for review! 🎉 Thank you all for your patience!
Please upvote the PR for a faster review 👍

#16616

@bukhbayar
Copy link

Any example for VPC, Subnet and Security Group that specifically configured for Amazon MWAA?

@Shaneprrlt
Copy link

Any movement on this?

@ewbankkit
Copy link
Contributor

Addressing this issue is on the quarter's Roadmap.

@mrn3
Copy link

mrn3 commented Feb 18, 2021

Thanks so much - so on the roadmap, it has February - April. Is it likely this will take a month or more to finish, or is it getting pretty close? I am just trying to do some tentative planning around it - thanks again!

@QAM
Copy link

QAM commented Mar 1, 2021

@bukhbayar you can refer to this for vpc mwaa terraform setup
link

@francescomucio
Copy link

Same question here, any idea when the support for MWAA will be released?
Will it be end of April or sooner?

@bhushan-chirmade-tm
Copy link

When is this expected to be released?

@nikvaklinov
Copy link

Do we have any update on this?

@ilyanoskov
Copy link

yes, any updates?

@pvspencer22
Copy link

Also, checking in here on progress :)

@HARI5KRISHNAN
Copy link

The provider provider.aws does not support resource type
"aws_airflow_environment"

@bflad bflad self-assigned this Mar 31, 2021
@bflad bflad linked a pull request Mar 31, 2021 that will close this issue
@claudiobizzotto
Copy link

Thank you for this! Works like a charm 🔥
https://github.com/claudiobizzotto/aws-mwaa-terraform

@bflad bflad added this to the v3.36.0 milestone Apr 5, 2021
@ghost
Copy link

ghost commented Apr 9, 2021

This has been released in version 3.36.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 for triage. Thanks!

@ghost
Copy link

ghost commented May 5, 2021

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators May 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
new-resource Introduces a new resource. service/mwaa Issues and PRs that pertain to the mwaa service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.