Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hi,

I’m part of a team that supports a client’s Zapier.com connectivity with an AWS hosted RDS.

 

Traffic from zapier.com actually needs to pass through another AWS account were 3 network resources do additional filtering - a Global Accelerator > NLB > Nginx before traffic finally gets through to an RDS DB instance hosted in another AWS account.

 

My question is: is there a simpler way to implement this?  The client wants to migrate the current setup into a new AWS account but we can’t seem to reverse-engineer whatever was setup in the AWS account with the 3 network resources.

 

To rephrase the question, is it safe to just setup the Global Accelerator > NLB > NGINX > RDS DB instance in one AWS account?

 

Thanks in advance for any inputs!

Hi ​@Eric J,

 

Welcome to the Community.

 

For a Zapier-AWS integration, simplifying the architecture by consolidating Global Accelerator, NLB, NGINX, and RDS within one AWS account can reduce maintenance and potential failure points. Key considerations include security (using AWS security features), performance (ensuring traffic distribution and low latency), cost (evaluating savings vs. data transfer fees), and maintenance (easier troubleshooting). If reverse-engineering the existing setup is challenging, AWS Support may provide insights. Always test changes thoroughly before deploying in production.

 

I hope this helps. Please let me know if you have any questions.

Terms & ConditionsAccessibility statement