[
https://issues.apache.org/jira/browse/AIRFLOW-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197037#comment-16197037
]
Andy Hadjigeorgiou commented on AIRFLOW-115:
--------------------------------------------
Yes, that's mine! Currently working on a couple branches with the refactored
ones. I think it should fall back to inspecting the extra field as well,
changing the display labels may be more work though, I think it's one template
for all the Connections (not certain though). I wonder if that could fall into
a more general "Connection UI re-work" ticket (there seems to be a lot of
improvements for that page). Included there would also potentially be changing
the 'S3' type to a more general 'AWS' type, given that it's really just used
now to store aws key and secret.
> 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.4.14#64029)
