You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is how the HTTP listener for new api3 looks like:
When I enter the url, ALB_URL/orders-api it is not going to the new service api3.
Any idea where did I go wrong?
The text was updated successfully, but these errors were encountered:
shain-digix
changed the title
Path specified in manifest file is not working correctly
Stuck on it for 2 days. Path specified in manifest file is not working correctly
Apr 25, 2024
I think the load balancer rules are exact matches, so you would need a rule forwarding /orders-api in addition to /orders-api/*.
Have you tried setting the http.path to /orders-api/* and then add http.additional_rules.path: '/orders-api'? Not sure if including the wildcard is valid or not in the copilot manifest.
Looks like copilot should create a rule for /orders-api OR /orders-api/* just by having http.path set to /orders-api.
Are you importing a load balancer and your screenshot is a rule you added manually?
I have a cluster with 3 services. Below are the configuration for service manifest file
Service 1 - api1
environments: dev: http: path: '/' healthcheck: '/api/healthcheck'
Service 2 - api2
environments: dev: http: path: '/' healthcheck: '/healthcheck'
Service 3 - api3 - Newly Added
environments: dev: http: path: '/orders-api' healthcheck: '/api/healthcheck'
This is how the HTTP listener for new api3 looks like:
When I enter the url, ALB_URL/orders-api it is not going to the new service api3.
Any idea where did I go wrong?
The text was updated successfully, but these errors were encountered: