The time when Shopify and EC2 disliked each other
In 2019, a junior engineer faced connectivity issues between Shopify and their EC2 instance. Despite initial debugging efforts, the team discovered that calls to Shopify were timing out. Ultimately, they implemented a proxy server solution that successfully resolved the issue.
- ▪The team was unable to update Shopify from their EC2 instance due to connection timeouts.
- ▪After testing in different regions, they determined the issue was localized to their original EC2 instance.
- ▪A proxy server was created to route requests to Shopify, which successfully mitigated the connectivity problem.
Opening excerpt (first ~120 words) tap to expand
EC2 and Shopify dislike each otherDev Tales #2: Thoughts of a junior engineerMay 25, 2026ShareBack in 2019, I was a junior software engineer at Turmswear. One blissful morning while giving my updates in the standup, our packer, stormed in yelling that there were no orders placed in the last fifteen minutes.To understand what the yelling was about we need to start with the setup:There’s a monolith server (in ap-south-1 AWS EC2) that holds the business logic for dealing with courier partners (order fulfillment), loyalty program, return & exchange and taxation. We use Shopify for product and order management. Shopify communicated with our backend via webhooks. We updated Shopify regularly via REST apis.Our frontend was a regular Shopify Store.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (Newest).
Discussion
0 commentsMore from Hacker News (Newest)
