I am trying to edit an s3 datasource and change the manifest file from a locally uploaded manifest file to a one in s3 but when I try to do that i get an error that it can’t be parsed, although it’s the exact same file that I used locally to create the datasource, is there a way to fix this?
Hi,
Can you check if you can create a new dataset pointing to the URL of the manifest files on S3?
Thanks!
Hi Andres,
It’s also giving the same error, al though when I locally upload the same manifest it creates it normally.
Best.
I am testing with this format and works in both S3 and Local. Can you check if yours looks similar? I am quite sure you have access to the S3 bucket from QuickSight, if not, you will get a different error, but just in case, can you check if your bucket is listed as accessible by QuickSight?
{
"fileLocations": [
{
"URIs": [
"s3://xxxxxx/lastupd.csv"
]
}
],
"globalUploadSettings": {
"format": "CSV",
"delimiter": ","
}
}
the s3 bucket is accessible yes, and the format of the manifest file is correct, when I upload it locally it works, I only face the issue when I try it in URL, and I tried it in a different account and it worked, do you recommend opening a support ticket for this issue?
If it works on another account yes, please go ahead and create a support case. Please let us know how you solved this so we share this with the community.
Thanks!