cloud:aws:apigateway
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cloud:aws:apigateway [2021/04/30 19:28] – skipidar | cloud:aws:apigateway [2023/11/01 07:13] (current) – ↷ Page moved from business_process_management:camunda:cloud:aws:apigateway to cloud:aws:apigateway skipidar | ||
|---|---|---|---|
| Line 192: | Line 192: | ||
| This is the most powerful integration: | This is the most powerful integration: | ||
| - | - **{{proxy}}** sends all resources - to the Lambda | + | - **\{{proxy}}** sends all resources - to the Lambda |
| - **ANY** - accepts all methods | - **ANY** - accepts all methods | ||
| Line 199: | Line 199: | ||
| {{https:// | {{https:// | ||
| + | * <color # | ||
| + | * <color # | ||
| + | |||
| + | After that the lambda reacts on | ||
| + | < | ||
| + | curl -X POST https:// | ||
| + | curl -X GET https:// | ||
| + | </ | ||
| ==== Mapping Templates ==== | ==== Mapping Templates ==== | ||
| Line 208: | Line 216: | ||
| https:// | https:// | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ==== Token Exchange ===== | ||
| + | The token exchange is possible with 2 pieces: | ||
| + | |||
| + | * obtain a new token at the lambda authorizer | ||
| + | * set the header via VLT as in | ||
| + | |||
| + | https:// | ||
| + | |||
| + | |||
| + | |||
| + | ===== A Detailed Overview of AWS API Gateway ===== | ||
| + | An overview of the API gateway functions. | ||
| + | https:// | ||
| + | |||
| + | {{https:// | ||
| + | |||
| + | {{https:// | ||
cloud/aws/apigateway.1619810912.txt.gz · Last modified: by skipidar
