AWS Bedrock Agent - Orchestration Strategy - Couldn't save post processing

I understand you're experiencing issues with saving changes to the post-processing output in the Orchestration Strategy section of your AWS Bedrock Agent. This is a frustrating situation, and I'll try to provide some insights and potential solutions.

First, it's important to note that the ability to save changes in the Orchestration Strategy section can sometimes be affected by various factors, including the complexity of the prompt, the specific configuration of your agent, or temporary service issues.

Here are a few suggestions that might help resolve your issue:

1. Simplify your prompt: If you've made your post-processing prompt very complex, try simplifying it and saving incrementally. This can help isolate whether the issue is related to the content of your prompt.

2. Clear browser cache: Sometimes, browser-related issues can interfere with console operations. Try clearing your browser cache and cookies, then attempt to save again.

3. Use a different browser: If the issue persists, try accessing the AWS Bedrock console from a different browser to rule out any browser-specific problems.

4. Check your IAM permissions: Ensure that your IAM role has the necessary permissions to modify and update Bedrock Agents.

5. Verify your agent's configuration: Make sure all other aspects of your agent's configuration are correct and complete. Sometimes, issues in one area can prevent updates in another.

6. Wait and retry: If there's a temporary service issue, waiting for a short period and trying again might resolve the problem.

Regarding your desire to move to Claude 3.5 and the cross-region block for RAG (Retrieval-Augmented Generation), this is indeed a separate issue. Cross-region limitations can affect certain functionalities, including RAG. You may need to ensure that your agent and associated resources (like knowledge bases) are in the same region to fully utilize all features.

If the issue persists after trying these steps, it would be best to contact AWS Support directly. They can provide more specific assistance based on your account and configuration details.

Remember to always test your agent thoroughly after making changes to ensure it's functioning as expected.

Sources
Customize agent orchestration strategy - Amazon Bedrock
Customize your Amazon Bedrock Agent's behavior with custom orchestration - Amazon Bedrock
Bug report: Bedrock Agent console | AWS re:Post