SES production access blocked by closed case — ConflictException on PutAccountDetails

The ConflictException on PutAccountDetails is a locking issue, not a request error. AWS throws it specifically when a previous account details update is still sitting in a "under review" state on their backend, and a closed support case does NOT automatically clear that lock. So even though the case is closed, the review state can stay frozen.

You need a new support case, but the category matters a lot here. File it under "SES" > "Account Issues" > "Sending limits / production access" and explicitly mention the ConflictException plus the closed case ID. Ask them to clear the stale pending review state on your account so you can resubmit. That's the actual action they need to take on their side, and it won't happen just by reopening the old case.

If the first agent tries to close it again without doing anything, ask them to escalate to the SES service team. The API docs confirm the ConflictException means an active review is in progress, so there's a paper trail to point at.

You're experiencing a workflow conflict where your SES production access request is tied to a closed support case, preventing you from submitting new account details through either the console or the PutAccountDetails API. This ConflictException typically occurs when there's an existing review in progress or when the system hasn't fully cleared the previous review state.

To resolve this situation, you should continue working through the AWS Support Center at https://console.aws.amazon.com/support/. Since you've already opened a support case on August 3rd, add a new correspondence to that existing case explaining the technical details you've shared: the ConflictException error, the fact that your ReviewDetails.Status shows DENIED with a CaseId pointing to a closed case, and that you're unable to submit new information through the API or console.

The AWS Support team will need to clear the stale review state on the backend so you can submit a fresh production access request with your updated information and 30-day sending history. This type of account-level configuration issue requires direct support intervention and cannot be resolved through self-service tools.

When you add correspondence to your existing case, be specific about the error message and the API response details you've provided here, as this will help the support engineer understand the exact state of your account and expedite the resolution. If you feel your current support plan's response times don't meet your business needs, you may also want to review your AWS Support plan options for faster response times.