[
https://issues.apache.org/jira/browse/AIRFLOW-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944869#comment-16944869
]
Francesco Macagno commented on AIRFLOW-4493:
--------------------------------------------
I believe this is still a problem. an aws connection can work for multiple
regions, and locking it to a specific one requires creating redundant
connections, ruining their purpose.
> emr_add_step_operator needs region_name as parameter
> ----------------------------------------------------
>
> Key: AIRFLOW-4493
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4493
> Project: Apache Airflow
> Issue Type: Improvement
> Components: aws
> Reporter: Guang Hu
> Priority: Minor
>
> when adding EmrAddStepsOperator to dag, the boto3 lib cannot find the
> corresponding job flow id if we do not specify the region_name if our emr
> cluster located in no default az.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
