api-gateway | API Gateway | REST library

You have to think of a container as an individual minimal host. And in that case, when you say to your ticket_service app to call localhost it will call itself, which is not what we want.

Whenever using docker-compose, a docker network is created and the containers are configured to use it.
You can use that network to make your containers communicate with each other by their names.

In your case, as the Jaeger container is called jaeger, you have to configure the endpoint of your JaegerExporter as follows:

Make your state as an array :

Please note that Spring Cloud Gateway is not compatible with Spring MVC (spring-boot-starter-web). This is outlined in section "How to include Spring Cloud Gateway in the official reference documentation":

Spring Cloud Gateway is built on Spring Boot 2.x, Spring WebFlux, and Project Reactor. As a consequence, many of the familiar synchronous libraries (Spring Data and Spring Security, for example) and patterns you know may not apply when you use Spring Cloud Gateway.

Additionally, it is stated that:

Spring Cloud Gateway requires the Netty runtime provided by Spring Boot and Spring Webflux. It does not work in a traditional Servlet Container or when built as a WAR.

As already suggested by the error message, you would need to remove the dependency on spring-boot-starter-web. You can list all your direct and transitive dependencies with the following command:

API Gateway v2 is only supported in pro version of LocalStack. So if you want to use it, please buy the pro version.

Your yaml is not valid. Check this validator as example.

Note how on line 16 and next, uri, predicates and path are not on the same column as just before.

Valid yaml is:

Since there was no fitting tool for my problem or an answer for 6 months, i decided to write an open source tool myself. It is still a WIP but it may already be enough for you, just like it is for my current needs.

Basically what it does is detecting the swagger definitions, generating each of those using the openapi-cli-generator and then merging all generated files together. At the end there are no duplicate files and a single Configuration.

If you find any bugs or unhandled edge cases please contribute via Github!

https://github.com/Deitsch/angler

it looks like your payload value for the options node is being interpreted as object instead of string. Can you try the following settings instead to solve the problem?

The aws_lambda_function has invoke_arn which is:

ARN to be used for invoking Lambda Function from API Gateway - to be used in aws_api_gateway_integration's uri

So you have to use that in your aws_api_gateway_integration.

It is not possible to create one AWS REST API Gateway which is both private and public (either regional or edge optimized). You will have to create two separate API Gateways. You can have the same configurations in both API Gateways in terms of backend integrations.

If you try to specify two endpoint types for the CreateRestAPI operation when using a SDK/CLI you would get the following error:

An error occurred (BadRequestException) when calling the CreateRestApi operation: Cannot create an api with multiple Endpoint Types.