testing ECS service with API Gateway ingress architecture BEFORE api gateway endpoint is deployed
I'm building a web service that will run on ecs/fargate. Because I expect very infrequent traffic, I'm creating an api gateway ingress that will use cloudmap to find the service following this pattern from Containers on AWS.
Here's a diagram of the architecture:
In developing the service, I'd like to develop and deploy the ECS service BEFORE developing and deploying the Gateway API endpoint and cloudmap integration. That way I can isolate and fix all the bugs in my ECS service before I turn to getting the Gateway config right.
If I do so, is there a way for me to test the service by sending https or http requests to it directly without my API gateway endpoint in place?
- 新しい順
- 投票が多い順
- コメントが多い順
Having learned a little more about how the API Gateway Integration that is used in this architecture works, I think the answer to my question is: "It is possible to test the ecs service in this architecture before setting up the API Gateway part, but doing so is more trouble than its worth! Just go ahead and wire up the API Gateway, then test through that."
Here's why I think this is true (I'm a beginner at AWS, so I can't be sure whether it IS true): In the absence of the API gateway infrastructure in this architecture, there is no public endpoint for the fargate service running the tasks. Thus testing the behavior of the service requires setting up (for instance) an EC2 instance inside the VPC where the tasks are running, and then getting that EC2 instance to send requests to the service. Getting that set up is really just as much work as setting up the API Gateway infrastructure, so might as well go ahead and do that!
関連するコンテンツ
AWS公式更新しました 2年前- AWS公式更新しました 2年前
