create_sdaccel_afi.sh cannot connect to the S3 endpoint about aws-fpga

[deeppat]

@adki , I believe you have set your default region to us-east-1c which is why the cli can't reach the endpoint. Amazon API endpoints are not AZ specific, so you should set it to the region. For eg, you should set it to us-east-1 and try again.

[deeppat]

Closing this issue as I believe my comment should solve the problem. Please post on the forum for any follow ups!

-Deep

[yunqu]

I have seen similar issue. Did @adki solve this problem by the comment? I used the us-east-1 as region but still no luck.

[deeppat]

@yunqu, could you share the specific error message you saw?

[yunqu]

I used the command:

./SDAccel/tools/create_sdaccel_afi.sh -xclbin=/home/centos/data/build/resizer.xclbin -o=resizer \
-s3_bucket=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld \
-s3_dcp_key=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/dcps/ \
-s3_logs_key=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/logs/

Then it errors out with:

upload failed: ./20_03_06-191234_Developer_SDAccel_Kernel.tar to s3://arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld/dcps//20_03_06-191234_Developer_SDAccel_Kernel.tar Could not connect to the endpoint URL: "https://pynq-helloworld/arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld-186486331965.s3-accesspoint.us-east-1.amazonaws.com/pynq-helloworld%2Farn%3Aaws%3As3%3Aus-east-1%3A186486331965%3Aaccesspoint%2Fpynq-helloworld/dcps//20_03_06-191234_Developer_SDAccel_Kernel.tar?uploads"

[yunqu]

@deeppat Ok I got it. The correct command should be:

./SDAccel/tools/create_sdaccel_afi.sh -xclbin=/home/centos/data/build/resizer.xclbin -o=resizer \
-s3_bucket=arn:aws:s3:us-east-1:186486331965:accesspoint/pynq-helloworld \
-s3_dcp_key=dcps/ \
-s3_logs_key=logs/

The dcp and logs section should not repeat the access point ARN.

[deeppat]

@yunqu That's correct. internally, the script just calls aws s3 cp and only expects the S3Uri for the s3 bucket argument. I'm glad it's all set for you. I'll see if we can update the script to better specify the requirements too.