Hi All
I have aws apigee and my backend is on-prem, but when I created a proxy and when I call the backend, I get an error saying "503 Service not available"
If anyone Implemented this before please help me out.
Thank you
Sounds like a firewall or network connectivity issue.
If your backend is on-prem you need to make sure it's callable from your MessageProcessor. If that's Apigee SaaS, then ... make sure your firewall allows the IP addresses of your Apigee Org.
If it's "self-managed" Apigee (aka OPDK) running in AWS, then make sure the IP addresses of your EC2 nodes are allowed by your firewall.
There may also be TLS requirements. Check with your firewall people - the people that manage inbound connections into your onprem system.
Answer by Priyadarshi Ajitav Jena · Jul 17, 2020 at 09:02 PM
I faced the same issue in OPDK. if you have OPDK apigee, then from your message processor just make a curl test to check whether its connecting or not. for the route check you can do tracert to the backend ip.
If you have SAAS apigee then you need to open firewall at onprem for all the Apigee org IPs
Enabling SNI and its side effects? 1 Answer
AWS components for OPDK setup 3 Answers
Error in Connecting AWS RDS using API proxies 1 Answer
403 This User Agent is banned from this site 1 Answer
Instaling AIO topology on aws 1 Answer