[jira] [Closed] (FLINK-7035) Flink Kinesis connector forces hard coding the AWS Region

["Aljoscha Krettek (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-7035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aljoscha Krettek closed FLINK-7035.
-----------------------------------
    Resolution: Abandoned

I'm closing this as "Abandoned", since there is no more activity and the code base has moved on quite a bit. Please re-open this if you feel otherwise and work should continue.

> Flink Kinesis connector forces hard coding the AWS Region
> ---------------------------------------------------------
>
>                 Key: FLINK-7035
>                 URL: https://issues.apache.org/jira/browse/FLINK-7035
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kinesis
>    Affects Versions: 1.2.0, 1.3.1
>         Environment: All AWS Amazon Linux nodes (including EMR) and AWS Lambda functions.
>            Reporter: Matt Pouttu-clarke
>            Priority: Major
>
> Hard coding the region frequently causes cross-region network access which can in the worst cases could cause brown-out of AWS services and nodes, violation of availability requirements per region, security and compliance issues, and extremely poor performance for the end user's jobs.  All AWS nodes and services are aware of the region they are running in, please see: 
> https://aws.amazon.com/blogs/developer/determining-an-applications-current-region/
> Need to change the following line of code to use Regions.getCurrentRegion() rather than throwing an exception.  Also, code examples should be changed to reflect correct practices.
> https://github.com/apache/flink/blob/master/flink-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/util/KinesisConfigUtil.java#L174



--
This message was sent by Atlassian Jira
(v8.3.4#803005)