I’m working on setting up Mender at AWS ECS at this moment:
- Mender 2.3.0
- using S3 as storage backend, no storage-proxy and minio.
Entire setup seems working for me at this moment: I can add a add/decommission the device(s), run the deployment, but I faced a strange issue when trying to upload an artifact over CLI:
FAILURE: artifact upload failed with status 504, reason: <html> <head><title>504 Gateway Time-out</title></head>
Artifact looks fine for me, and it was generated with last version mender-artifact (3.3.0):
Artifact file 'test-release-1.0.mender' validated successfully
API gateway log:
2020/04/27 12:01:34 [warn] 54#54: *3950 a client request body is buffered to a temporary file /usr/local/openresty/nginx/client_body_temp/0000000007 while sending to client, client: <client>, server: <server>, request: "POST /api/management/v1/deployments/artifacts HTTP/1.1", host: "<server>"
mender-deployments log related entry:
time="2020-04-27T12:01:52Z" level=error msg="unexpected EOF" file=view.go func="view.(*RESTView).RenderError" line=53 request_id=<request_id> user_id=<user> time="2020-04-27T12:01:52Z" level=info msg="400 539196549μs POST /api/management/v1/deployments/artifacts HTTP/1.0 - Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0" file=middleware.go func="accesslog.(*AccessLogMiddleware).MiddlewareFunc.func1" line=60 request_id=<request_id> user_id=<user_id>
Test demo images loads just fine using both CLI tool and UI.
- How could I check the artifact other than using
- Is it OK to exclude storage-proxy and minio from the setup in case of using AWS S3 as a storage?