What happened

On 2024-05-27T16:09 the AuraDB Professional tier environment in the us-east-1 region of AWS was affected by a lack of network resources (addresses on a subnet). This issue occurred due to a suboptimal management of this resource and came to light on this region with high volumes of instances. 

A default setting was pre-allocating too many addresses and exhausted the pool. Operations (Create, Resize, Clone, Backup, Load) on the instances that need to allocate computing resources couldn’t start for lack of network access. 

How the service was affected

During the incident (between 2024-05-27 at 16:09 and 2024-05-28 at 10:29 ), customer operations (Create, Resize, Clone, Backup, Load) were either not starting or not able to complete successfully. Other regions remained unaffected.

What we are doing now

• We have improved the network resource management to ensure we more optimally allocate network addresses within an environment.
• We are creating an alarm to monitor across our environments our network address pools and detect any resource exhaustion.
• We are planning on making better use of zones for AuraDB Professional tiers to benefit from more network resources.