AWS S3 File Location not working

  • 8Views
  • Last Post 04 March 2020
0
votes
Juan Rivera posted this 03 March 2020

Hi Team, 

We are testing a free account to test imports from AWS S3 into our SQL Server. But when creating a connection for AWS S3 it come succesfull when we test the connection for the first time BEFORE hitting Save. 

After saving the connection and trying to use it or re opened the connection again to edit, I hit Test connection again and I get the following message: Error accessing AWS. Error: The remote name could not be resolved: 'restaurant-exports'

On the Bucket Field I'm entering this: restaurant-exports/TheMeltingPotRestaurantsInc

It contain the Bucket/FileLocation.

My question is, Is this possible to do or this need to always hit the root instead of the file location? I really want to use the file location since its what we have access for.

Let me know if there is another way to work this around. We are planning to buy a plan but until we can't get this going we can't buy it. 

*I also leaved the Bucket Field in blank as the AWS S3 Doc said and I can't save the connection unless there is something on that field.

Thanks,

Juan R.

 

 

0
votes
Mariia Zaharova posted this 04 March 2020

Hello Juan!

 

Thank you for contacting us!

 

My question is, Is this possible to do or this need to always hit the root instead of the file location? I really want to use the file location since its what we have access for.

No, there is no way to use file location, it is not supported.

 

I also leaved the Bucket Field in blank as the AWS S3 Doc said and I can't save the connection unless there is something on that field.

Thank you for the report on this. We will check and correct it.

 

On the Bucket Field I'm entering this: restaurant-exports/TheMeltingPotRestaurantsInc


Please specify the bucket name without the file location. You will be able to select the files when configuring Import tasks.

 

 

Please check this link.

 

Best regards,

Mariia

 

Close