7

I'm not sure if this is intended or I configured it incorrectly.

I set up my Aurora Serverless PostgreSQL Database to pause after 5 min of inactivity.

Problem is, everytime I try to access it after it has paused, it takes almost 1 minutes for the server to respond for the first time.

Is there any configuration I can do to workaround this other than disabling pausing?

Mojimi
  • 2,561
  • 9
  • 52
  • 116
  • 1
    No. That's the _price_ you pay for the pause/start feature. It's mostly targeted for Dev/UAT instances (i.e. when you stop work in the evening and start again in the morning) or similar usage patterns (i.e. work hours / work days only) – Tasos P. Jul 09 '20 at 13:53
  • @Cascader Thank you, I feel stupid now for not researching properly. So I guess if I leave it running 24 hours it will always be more expensive than a equivalent regular RDS? – Mojimi Jul 09 '20 at 13:55
  • That depends on a lot of factors. I suggest you play around with https://calculator.aws/ and try different scenarios. In the meantime, have a look at [this](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.html#aurora-serverless.use-cases) – Tasos P. Jul 09 '20 at 13:56

1 Answers1

6

yes that's one of the main issues when taking advantage from pause but downside it takes time to warm up, you can extend the pause something bigger than five minutes so it will be warm-up always as if you create connection during the time so the timer will reset for inactivity.

Expand the Additional scaling configuration section. You can disable cluster pausing by unchecking the Pause compute capacity after consecutive minutes of inactivity checkbox. Using the hours, minutes, and seconds drop down list boxes, you can change the length of inactivity time until the cluster pauses. By default your cluster will pause after 5 consecutive minutes of inactivity.

configure-connect-serverless-mysql-database-aurora

Select RDS -> DB instance -> database -> configuration enter image description here

24hr is the maximum time, you can set something lower then this but if there is one connection at least in 24 hr, it will be warmup always.

Adiii
  • 54,482
  • 7
  • 145
  • 148
  • 1
    Heads up for future readers! AWS Just announced they have fixed this issue – Mojimi Dec 07 '20 at 12:09
  • 1
    @Mojimi, not completely, the warm up still takes some time and the API calls timeout during that time. – Uttam Jun 03 '21 at 03:26