3 ms·
Nice point about the minimum 0.5 ACU, forgot about that one. From what I've read 0.5 on v2 is the same price as 1 on v1, which seems pretty dumb coming from aws
by ranguna 4y ago
Nice point about the minimum 0.5 ACU, forgot about that one. From what I've read 0.5 on v2 is the same price as 1 on v1, which seems pretty dumb coming from aws.
Could you elaborate more on this:
> You can have public access to serverless v2
Because the docs mention the following:
> You can’t give an Aurora Serverless DB cluster a public IP address; you can only access it from within a VPC based on the Amazon VPC service.
Potentially I could setup an RDS proxy or vpn inside the vpc and give that public access, but that seems a bit of a roundabout way of handling this.
https://aws.amazon.com/blogs/database/best-practices-for-working-with-amazon-aurora-serverless/ https://aws.amazon.com/blogs/database/best-practices-for-wor...
- lysecret 4y agoI can 100% confirm public access works :)
- ranguna 4y agoCould you elaborate on how you got it to work without a public IP?
- lysecret 4y agoIts a completely crazy process but it works roughly like this: (going from RDS Postgres on 12.6 to Aurora Serverless V2) 1. You create a snapshot of your original db 2. You update that snapshot to 13.4 (NOT 13.6!!) 3. You have to use the AWS CLI (because the online migrate doesn't work) to create a cluster from the snapshot 4. Remember this cluster is 13.4, serverless only works with 13.6, so we have to upgrade it later again 5. However we can only upgrade it when there is a running system 6. so we create a non-serverless aurora instance. Most instance types returned an error but using t3.medium worked, you can create that with public access. 7. when they are both created you can already try to ping your DB (it should work) 8. upgrade to 13.6 9. Now you are able to change the DB instance type to serverless Edit: BTW I am available for hire as an external contractor for this kind of stuff ;)