SES Production Access request redirects to Dedicated IP Limit Increase after previous Production Access case was permanently closed

The rePost-Agent's response suggests navigating manually through the Support Center, however my understanding is, because your previous case was hard-closed, the console state is stuck. Navigating to "Service Limit Increase" will likely just trigger the exact same redirect loop to the Dedicated IP form.

Since you mentioned that you have already installed and successfully configured the AWS CLI (and verified it with sts get-caller-identity), you have the workaround available. You can completely bypass the broken AWS Console UI and submit your Production Access request directly via the SESv2 API.

Here is how to do it.

Step 1: Submit the Request via AWS CLI

You can trigger the Production Access workflow directly from your terminal using the put-account-details command. This will automatically open the correct case in the AWS backend.

Run the following command, making sure to replace the placeholder values with your actual details:

aws sesv2 put-account-details \
  --production-access-enabled \
  --mail-type TRANSACTIONAL \
  --website-url "https://www.yourdomain.com" \
  --additional-contact-email-addresses "admin@yourdomain.com" \
  --use-case-description "1. How you build your mailing list. 2. How you handle bounces and complaints. 3. How recipients opt-out. 4. What kind of emails you send." \
  --region us-east-1

• --region: Ensure you run this against the specific region where you want SES production access (e.g., us-east-1 or ap-south-1).
• --mail-type: If your primary mail type is marketing, change TRANSACTIONAL to MARKETING.
• --use-case-description: Be as detailed as possible here to prevent AWS from rejecting the request.

Step 2: Verify the Submission

Once you run the command, it will silently return to the prompt if successful.

You can verify that AWS has registered your request by running:

aws sesv2 get-account --region us-east-1 --query 'ProductionAccess'

Step 3: Check your Email and Support Center

Within a few minutes of successfully running the command, you should receive an automated email from AWS Support confirming that they have received your request to move out of the Amazon SES sandbox.

If you go to the AWS Support Center now, you will see a properly categorized case for your SES Production Access request—bypassing the Dedicated IP redirect loop entirely.

References

• AWS CLI Command Reference - sesv2 put-account-details

I understand you're experiencing difficulty submitting a new Amazon SES Production Access request after your previous case was closed. Let me help clarify the situation and provide guidance.

Understanding the Production Access Request Process:

When you request production access for Amazon SES, you're asking to remove your account from the SES sandbox. This process typically involves submitting a support case through the AWS Support Center where you provide details about your use case, email sending practices, and compliance with AWS policies.

Regarding Your Situation:

The redirect behavior you're experiencing—where clicking "Request Production Access" takes you to a Dedicated IP limit increase form instead of the production access request form—suggests there may be a workflow issue or your account state needs attention.

Recommended Steps:

1. Submit Through AWS Support Center Directly: Instead of using the SES Console button, go directly to the AWS Support Center (https://console.aws.amazon.com/support/) and create a new case. Select "Service Limit Increase" as the case type, then choose "SES Sending Limits" as the limit type. This should present you with the appropriate form for production access.

2. Provide Complete Information: When submitting your new request, include:

• Your use case and how you'll use SES
• How you handle bounces and complaints
• Your email sending volume estimates
• Confirmation that you'll only send to recipients who have opted in

3. Reference Your Situation: In your case description, you can mention that you had a previous request that was closed, and you're now ready to proceed with production access. However, focus primarily on providing the required information for the new request rather than dwelling on the previous case.

Important Notes:

• Each production access request is evaluated independently based on the information provided and AWS policies at the time of submission
• The Support API access limitation you encountered is expected with the Basic Support plan, but you don't need API access to submit a production access request through the console
• Make sure you're submitting from the correct AWS region where you want to use SES, as production access is granted per region

If you continue experiencing technical difficulties with the form itself after trying the direct Support Center approach, you can add correspondence through the AWS Support Center describing the specific technical issue with the form redirect.

Your account should not be permanently blocked from requesting production access due to a previous closed case. The system is designed to allow new requests to be submitted and evaluated on their own merits.