AWS deployment

Deployment Policy
To be able to deploy the deployment user must have at least :
{
"Sid": "Stmt1438583420001",
"Effect": "Allow",
"Action": [
"lambda:*",
"iam:PassRole",
"apigateway:*"
],
"Resource": [
"*"
]
}
This can be restrict more and should, need to update the documentation
Package
The package is a zip of your folder, we dont have advanced cleaning feature nor ignore files, so the package can be big if you forget to clean your folder before.
Lambda
Once the package done, it will be upload as a Lambda function with the name specified, updating if it already exists.
API Gateway
It map all the routes from your application, if a website parameter is found on the parameters of deployment then it will enable CORS for you for this URL
It also deploy the API as Stage named with the name of the deployment.
CORS
CORS response headers are emitted only for the origins accepted by a CORS filter. The simplest is the website parameter (global parameters.website or the Router service), matched on the request Origin header:
{
"parameters": {
"website": ["https://app.example.com", "http://localhost:5173", "https://*.preview.example.com"]
}
}
Each entry is an exact origin (scheme, host and port; not a regular expression), https://*.example.com accepts the subdomains (not example.com itself) and "*" accepts any origin. Services declaring the cors-filter capability, or filters given to useRouter().registerCORSFilter(), can accept more origins; without website and without any filter, no origin is accepted. For an accepted Origin, the Router answers with Access-Control-Allow-Origin (the origin is echoed, never *; Origin: null is never accepted), Access-Control-Allow-Credentials: true and Vary: Origin; a preflight OPTIONS also gets Access-Control-Allow-Methods, Access-Control-Allow-Headers and Access-Control-Max-Age: 3600. Other origins receive no Access-Control-* header. A service needing more request headers (for example tracing headers) calls useRouter().addCorsAllowedHeaders("traceparent").