Closed ashu1230 closed 2 months ago
@ashu1230,
I don't think this is AWS SDK JS specific issue. Could you please check with the API owner to make sure your request URL is on the allowlist?
@zshzbh
Yes it is.
issue now solved
Thanks for closing the ticket, just want to get more info for future reference.
May I know how does this issue get resolved on your end?
Describe the issue
I have deployed a NestJS backend on an AWS EC2 instance. The Swagger UI is accessible, but when I try to hit the API using Swagger, I receive the following error:
ISSUE: Failed to fetch. Possible Reasons:
curl
). The Swagger UI is accessed via the public IP address of the EC2 instance. The error occurs when trying to access the API endpoint through the Swagger UI. My backend is running onhttp://localhost:3033
, and the Swagger UI is being accessed via the public IP of the EC2 instance.Troubleshooting Steps Taken: Confirmed that the backend API is accessible directly from the EC2 instance. Verified that the server is configured to handle CORS requests by setting the appropriate CORS headers in the NestJS application. Checked the network configurations and security groups in AWS EC2 to ensure proper access.
Environment: NestJS version: AWS EC2 Instance: Amazon linus(t2.micor). Swagger version: 6.0.5 Browser: Chrome, Edge Node.js version: Latest CORE: 9.0.0 Request URL: http://localhost:3033/api/v1/auth/signin
Question: How can I resolve this CORS issue, and what configurations are required to allow the Swagger UI to make successful API requests in this setup?
Links
Request URL: http://localhost:3033/api/v1/auth/signin