Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

I am facing an issue related to CORS

I get the following response whenever I try to run
Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

What could that be?

I am trying to make a post request to a serverless endpoint running on AWS...

As shown down bellow a successfull POST request for my API.
`

- :authority: czy9w4unel.execute-api.eu-west-1.amazonaws.com
- :method: POST
- :path: /category/9d107639-b278-44e2-a2f3-2efba2d0798f/quizzes
- :scheme: https
- accept: application/json, text/plain, */*
- accept-encoding: gzip, deflate, br
- accept-language: pt-BR,pt;q=0.9,en-US;q=0.8,en;q=0.7,da;q=0.6
- authorization: Bearer eyJraWQiOiJwT3dhSmd0VGNodEl3RnpDWHN2czdXUU1pSHJuWTM0NUl4aG5LalBHbEhZPSIsImFsZyI6IlJTMjU2In0.eyJzdWIiOiJkMjkzMzNmOC0yZWY1LTQ2NzYtOTc1Ni03ZDljMWEzZTRmMTMiLCJpc3MiOiJodHRwczpcL1wvY29nbml0by1pZHAuZXUtd2VzdC0xLmFtYXpvbmF3cy5jb21cL2V1LXdlc3QtMV9BSWVNWE15enoiLCJjb2duaXRvOnVzZXJuYW1lIjoiZDI5MzMzZjgtMmVmNS00Njc2LTk3NTYtN2Q5YzFhM2U0ZjEzIiwib3JpZ2luX2p0aSI6IjBjNWU0ZmFiLTkxZTAtNGVkYS04ZGZlLTAxYzA2N2I3OWFhMSIsImF1ZCI6IjJ0aGVwM29kcGhjdW5hNTBjaDcxNTJrNjVyIiwiZXZlbnRfaWQiOiIzMWQwNjhkZi0yNzRjLTQxZTYtODc0MS01MGUwODdiNjk0MWUiLCJ0b2tlbl91c2UiOiJpZCIsImF1dGhfdGltZSI6MTY3MDc5OTk5MCwiZXhwIjoxNjcwODIwMDY4LCJpYXQiOjE2NzA4MTY0NjgsImp0aSI6ImVmNDU0ZDMxLTVlOWMtNGMyZS1hMDc0LWY0MTE1MDU0MmY3NiIsImVtYWlsIjoibHVjYXMuYnJhZ2Erc3R1ZGVudCsyQGdvY28uZGsifQ.MPphW1kkNuZbva-qbXwGlKUKwH2r7zjkrTX_3-Lof1O3eacRW3dO9wyryJfAu7QUK7_DrKLbK6Oyz_WQAVlSflxa_YaWiNE5AgYq7THwSTyz3LZJVF3cFVZjKQGhhEztR4NvIlmNQbxdFgsvygcyVd677owc7d3yZ7hA6f7S74eSU-UOXEmSGVHk2EGKWdgTW92_AeRREgT4bwKmDKgit1Z-TpXFri-6HAMkvvmYN8diQVZ6Qoy19DAO0ikvKzUX0IErUbyQQB6US2hUI_7qdB7EmLCdyvO7vtn_vlhRX9UVA8_eVp8R59CTxbCmWQydD4GkmA4MC96DYzh7uFFltg
- content-length: 56
- content-type: application/json; charset=UTF-8
- origin: http://localhost:3000
- referer: http://localhost:3000/
- sec-ch-ua: "Google Chrome";v="107", "Chromium";v="107", "Not=A?Brand";v="24"
- sec-ch-ua-mobile: ?0
- sec-ch-ua-platform: "Linux"
- sec-fetch-dest: empty
- sec-fetch-mode: cors
- sec-fetch-site: cross-site
- user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36

`

And here it goes the request headers from the API call made by your component

`

- Accept: application/json
- Authorization: Bearer eyJraWQiOiIxR3NremplTjlQY1RGcGo4QnBHUkFEMjNyY2txTEZ4ZGcyZFB5K2l3bStjPSIsImFsZyI6IlJTMjU2In0.eyJzdWIiOiJkMjkzMzNmOC0yZWY1LTQ2NzYtOTc1Ni03ZDljMWEzZTRmMTMiLCJpc3MiOiJodHRwczpcL1wvY29nbml0by1pZHAuZXUtd2VzdC0xLmFtYXpvbmF3cy5jb21cL2V1LXdlc3QtMV9BSWVNWE15enoiLCJjbGllbnRfaWQiOiIydGhlcDNvZHBoY3VuYTUwY2g3MTUyazY1ciIsIm9yaWdpbl9qdGkiOiIwYzVlNGZhYi05MWUwLTRlZGEtOGRmZS0wMWMwNjdiNzlhYTEiLCJldmVudF9pZCI6IjMxZDA2OGRmLTI3NGMtNDFlNi04NzQxLTUwZTA4N2I2OTQxZSIsInRva2VuX3VzZSI6ImFjY2VzcyIsInNjb3BlIjoiYXdzLmNvZ25pdG8uc2lnbmluLnVzZXIuYWRtaW4iLCJhdXRoX3RpbWUiOjE2NzA3OTk5OTAsImV4cCI6MTY3MDgxNjQ2MywiaWF0IjoxNjcwODEyODYzLCJqdGkiOiI3MzgwZDgzYi00NTc4LTQzNTItYTAwNy1iMzE3NDk5ZGJmMDgiLCJ1c2VybmFtZSI6ImQyOTMzM2Y4LTJlZjUtNDY3Ni05NzU2LTdkOWMxYTNlNGYxMyJ9.VGDixvQquP7Dl56frhLqAvLjGa2FmQdLZqwwQjhQUji8biZSCm1cGHNfP3ufS9Oq18VBz_SHpcf1jPUu9BeiukNCmW779kTkBgu57hJ8OxsvtvYFF499H87wLDVJJq81oz-YXPDWzZAjQoafQogM1yYkrkY58-T7WgpDL4yqlKcZeRk2oetZyw7EyoscuBGd5Y09ag_uZ0GdDrH7pQ3GodRUGwCf0I_tMPjVPyLIpGxiu-d4-itm7QwCVQ8v-4f1krxFXF2xQkkZheYVoWOAqxIQijSq3Rd_lcg5ufc6hqrFlmpveXlnLvVvYKEfwux0CeV9H-YnXvlgcEg5u3DJ1Q
- Cache-Control: no-cache
- Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryfYAAIAF46B0ThX2O
- Referer: http://localhost:3000/
- sec-ch-ua: "Google Chrome";v="107", "Chromium";v="107", "Not=A?Brand";v="24"
- sec-ch-ua-mobile: ?0
- sec-ch-ua-platform: "Linux"
- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36
- X-Requested-With: XMLHttpRequest

`

The report names no repository file, test, or entry point; start by reproducing the request from the React component against the AWS endpoint and compare the preflight response with the successful POST. Done would require a confirmed project-side change and a regression check, neither of which the issue specifies.

Written by the indexing model from the issue text.