[jira] [Commented] (AIRFLOW-115) Migrate and Refactor AWS integration to use boto3 and better structured hooks

["Vitor Baptista (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861245#comment-15861245 ] 

Vitor Baptista commented on AIRFLOW-115:
----------------------------------------

[~artwr] Are you working on this issue? I'm facing many errors when using the current `S3Hook` mostly caused by it using `boto` instead of `boto3` (e.g. https://github.com/boto/boto/issues/2836)

> Migrate and Refactor AWS integration to use boto3 and better structured hooks
> -----------------------------------------------------------------------------
>
>                 Key: AIRFLOW-115
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-115
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: aws, boto3, hooks
>            Reporter: Arthur Wiedmer
>            Assignee: Arthur Wiedmer
>            Priority: Minor
>
> h2. Current State
> The current AWS integration is mostly done through the S3Hook, which uses non standard credentials parsing on top of using boto instead of boto3 which is the current supported AWS sdk for Python.
> h2. Proposal
> an AWSHook should be provided that maps Airflow connections to the boto3 API. Operators working with s3, as well as other AWS services would then inherit from this hook but extend the functionality with service specific methods like get_key for S3, start_cluster for EMR, enqueue for SQS, send_email for SES etc...
> * AWSHook
> ** S3Hook
> ** EMRHook
> ** SQSHook
> ** SESHook
> ...
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)