Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

'ProviderName' is not a valid Amazon Redshift option.

Hello, I got this error and searching through here I found that few others saw the same issue. Previous errors seems to have been fixed after a connector update, but I am still seeing this error today.

Error observed while trying to use access Amazon Redshift on dataflow.

 

An exception occurred: 'ProviderName' is not a valid Amazon Redshift option. Valid options are: 'BatchSize, Role' (Session ID: fa9794f5-cfac-40c5-980f-033ff78def7d, Region: southeastasia)

 

I dont have access to the gateway machine, so I am not able to use ODBC connector per some suggestions (and I should be able to use Amazon Redshift to access Amazon Redshift). Can anyone help with this issue?

 

 

  • Anonymous's avatar
    Anonymous
    4 years ago

    Thanks Henry, but this seems to be too complicated for me to digest and understand. Instead, I found a workaround:
    1. Create a blank query dataflow

    2. Write the M-code in Advance Editor to connect Source to Amazon Redshift

    3. Input credentials if requested

    4. Under "Options" --> "Project Options", select the gateway to be used

     

    Now it works for me.

2 Replies

  • v-henryk-mstf's avatar
    v-henryk-mstf
    Community Support

    Hi Anonymous ,

     

    For this type of issue, you may need to coordinate with Amazon to set up the IAM role (the value in the role) before you can use it.

    For more details, you can read below blog:

    Integrate Power BI with Amazon Redshift for insights and analytics | AWS Big Data Blog

    IAM identifiers - AWS Identity and Access Management (amazon.com)


    If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.


    Best Regards,
    Henry


    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thanks Henry, but this seems to be too complicated for me to digest and understand. Instead, I found a workaround:
      1. Create a blank query dataflow

      2. Write the M-code in Advance Editor to connect Source to Amazon Redshift

      3. Input credentials if requested

      4. Under "Options" --> "Project Options", select the gateway to be used

       

      Now it works for me.