Prisma Accelerate and Aurora Serverless
Hello, I'm looking to set up prisma accelerate with a database hosted in AWS. We are moving away from render.com because our clients are enterprise and only have AWS as an approved vendor.
We use serverless functions for our back end, so we'd like to use accelerate or another connection pooler to avoid maxing our db connections.
We were looking at Aurora Serverless for our db option. It doesn't seem like aurora serverless supports static IPs, so we are unsure how we'd connect accelerate to aurora serverless.
Would we need to do some proxying from an EC2 instance in the VPC? Any advice would be greatly apprecieated
2 Replies
You selected the bot's instantaneous insights. Let me compile your answer right away!
Based on the knowledge sources provided, I can offer some insights on using Prisma Accelerate with AWS Aurora Serverless, but there are some limitations to consider:
1. Prisma Accelerate and Static IPs:
Currently, Prisma Accelerate does not support static IPs. This feature is planned for the future, but it's not available at the moment. As stated in the Prisma blog post about Accelerate static IP support, static IP support is a recent addition to Accelerate, but it requires being on the Pro or Business plan.
2. Aurora Serverless and VPC:
Aurora Serverless can only be run behind a VPC, which means it's not directly accessible from the public internet. This is a security feature of Aurora Serverless.
3. Connecting Prisma Accelerate to Aurora Serverless:
Given that Accelerate doesn't currently support static IPs and Aurora Serverless requires VPC access, there isn't a straightforward way to connect Prisma Accelerate directly to Aurora Serverless based on the information provided in the knowledge sources.
4. Potential Workarounds:
While not ideal, you might need to consider setting up a proxy within your VPC to allow Accelerate to connect to Aurora Serverless. This could involve using an EC2 instance as you suggested, but keep in mind that this adds complexity and potential points of failure to your architecture.
5. Alternative Considerations:
If using Prisma Accelerate is not feasible due to these limitations, you might want to explore other options for connection pooling with Aurora Serverless. The knowledge sources mention the possibility of using PgBouncer or exploring the AWS Data API for Aurora Serverless, although Prisma doesn't currently support the Data API directly.
6. Future Developments:
The Prisma team is aware of the need for better serverless database support, including for Aurora Serverless. They are working on improvements, but there's no specific timeline provided in the knowledge sourc
es for when full support might be available.
Given the current limitations, you might need to reconsider your architecture or explore alternative solutions that better fit your requirements for AWS compatibility and serverless functions. It would be advisable to reach out to Prisma support or consult AWS documentation for the most up-to-date information on potential solutions for your specific use case.
š¤ Alright, thanks for letting us know that there's still some help needed. A team member will reply to you shortly.
In the meantime, please let us know any additional info, questions, or which parts of the answer may need clarification.
Hey š
You can spin up a lightweight proxy on an EC2 instance that has an Elastic IP. This proxy would sit inside your VPC and forward connections to Aurora Serverless, effectively giving you a stable endpoint you can use