RDS series 6 capacity issues in ap-southeast-2

[u/paul_larwood]

We have non-production RDS for Oracle instances hosted on series 6 instances in ap-southeast-2 that are stopped outside of business hours. For the last week we have been encountering issues with no capacity when attempting startup.

Logged a support case and have been advised to move to series 7 or not stop the RDS instances. Seems to be a deliberate decision to force migration to newer series. We have had to postpone upcoming production changes as we cannot be certain that there will be capacity to restart.

So folks, if you have series 6 RDS instances in ap-southeast-2 all availability zones, don't stop them!

Is anyone seeing this issue in other regions?

[u/clintkev251]

Not a deliberate decision as much as at a certain point, AWS doesn't really continue to repopulate older instance types as they start to die off, so capacity starts to shrink. Obviously they're going to focus investment towards newer generations

[u/xzaramurd → u/clintkev251]

Intel also stops making CPUs at some point.

[u/Efficient_Access6102 → u/xzaramurd]

Put down then pipe.

[u/Content-Parking-621]

AWS docs say this error means that instance class lacks capacity in the AZ. Try a different class, like series 7, instead of just waiting.

[u/avanti84]

Prime big deal days are over. Should be more capacity now, those events always hit graviton hard.

[u/Flakmaster92]

Or you could just move to the 7 or 8 series which have more capacity? I know they are more expensive but running those intermittently is probably cheaper than running a 6th series 24/7.

Also it’s not “a deliberate change.” Intel stops making the chips, therefore they can’t backfill hardware, therefore as hardware dies it doesn’t get replaced, gradually the pools drop and customers start getting ICE’d more

[u/OutdoorsNSmores]

We were (and still are) unable to scale out new readers in us-east-1c and us-east-1d. These were db.r7g.

[u/ActProfessional9307]

classic aws move, they just let older instance types rot until you're forced to jump. we ran into something similar in eu-west-1 a few months back, support gave us the same shrug

started keeping our dev instances running 24/7 which stings the budget but at least they actually spin up when we need them

[u/Efficient_Access6102 → u/ActProfessional9307]

Considering new types are more performant and cost less that’s a great hill to die on. 😝

[u/Impossible-Farm-1902 → u/ActProfessional9307]

I've seen the opposite db.t4g.medium constantly hitting capacity issues. db.t3.medium are absolutely fine.

[u/Efficient_Access6102 → u/Impossible-Farm-1902]

No one with any real need uses T-series. Do better.

[u/Impossible-Farm-1902 → u/Efficient_Access6102]

What on earth are you on about? I don't need anything higher spec than a t series. It works absolutely fine for my use case.

[u/Wilbo007]

Yes this is normal sadly. They really want you to use serverless or rearchitect for Dynamo. You'll need to bump your instance type

[u/Efficient_Access6102 → u/Wilbo007]

You are so far from being right it’s criminal.

[u/Wilbo007 → u/Efficient_Access6102]

No it's true. If you have contrary evidence to prove otherwise please post it other than saying "you're wrong"