[FLINK-28978] Kinesis connector doesn't work for new AWS regions

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.6, 1.14.5, 1.15.1
• Fix Version/s: 1.16.0, 1.15.2, 1.14.6
• Component/s: Connectors / Kinesis
• Labels: pull-request-available
• Assignee: Hong Liang Teoh
• Reporter: Hong Liang Teoh
• Created: 15/Aug/22 23:25
• Updated: 17/Aug/22 19:11
• Resolved: 17/Aug/22 19:11

Description

The current validation in the Kinesis connector checks that the AWS Region string specified is present in the Regions enum attached in the AWS SDK. This is not desirable because every time AWS launches a new region, we will have to update the AWS SDK shaded into the connector. 

We want to change it such that we validate the shape of the string, allowing for future AWS Regions. 

 

Current list of regions:

ap-south-1, eu-south-1, us-gov-east-1, ca-central-1, eu-central-1, us-west-1, us-west-2, af-south-1, eu-north-1, eu-west-3, eu-west-2, eu-west-1, ap-northeast-3, ap-northeast-2, ap-northeast-1, me-south-1, sa-east-1, ap-east-1, cn-north-1, us-gov-west-1, ap-southeast-1, ap-southeast-2, ap-southeast-3, us-iso-east-1, us-east-1, us-east-2, cn-northwest-1, us-isob-east-1, aws-global, aws-cn-global, aws-us-gov-global, aws-iso-global, aws-iso-b-global

Issue Links

• links to: GitHub Pull Request #20588
• links to: GitHub Pull Request #20605
• links to: GitHub Pull Request #20606