Let's further troubleshoot and fix the 500 error. I'll implement a more robust solution with better error handling and debugging.

I've made several significant changes to help diagnose and fix the 500 error:

1. Simplified API Route: I've simplified the /api/chat/route.ts to return a mock response for now. This helps us determine if the issue is with the AWS integration or with the API route itself.
2. Added AWS Credential Testing: I've created a new /api/test-aws/route.ts endpoint that tests your AWS credentials by attempting to list S3 buckets. This is a simple operation that will verify if your credentials are working correctly.
3. Added AWS Status Component: I've added an AwsStatus component that displays the status of your AWS credentials on the page. This will help you see immediately if there's an issue with your AWS setup.
4. Improved Error Handling: I've enhanced the error handling in the chat hook to better capture and display errors.
5. Added Alert Component: I've added an Alert component to display errors more prominently in the UI.
6. Switched to aws-sdk: I'm now using the standard aws-sdk package which is more stable and well-tested than the Bedrock-specific clients.

This approach will help us diagnose the exact issue with your AWS setup. Once we confirm your AWS credentials are working correctly, we can re-implement the Bedrock integration.

The mock response will allow you to test the chat interface while we troubleshoot the AWS integration. If the AWS credentials test passes but you still want to use Bedrock, we can then update the chat API to use the correct Bedrock client.

Let's fix the AWS SDK import and configuration issue:

I've fixed the AWS SDK configuration issue by:

1. Switching to AWS SDK v3: I've updated the code to use the newer AWS SDK v3 modules instead of the older v2 package. This provides better TypeScript support and more modular imports.
2. Using Specific Clients: Instead of importing the entire AWS SDK, I'm now importing only the specific clients we need (S3Client for testing credentials and BedrockRuntimeClient for the chat functionality).
3. Proper Client Initialization: I've updated how we initialize the AWS clients, using the proper constructor pattern with the credentials object.
4. Added Default Region: I've added a default region (us-east-1) in case the environment variable is not set.
5. Improved Error Handling: I've enhanced the error handling to better capture and display any issues with the AWS credentials.

The chat API route still returns a mock response for now, but I've included the commented-out code for the Bedrock integration. Once we confirm that your AWS credentials are working correctly with the S3 test, we can uncomment and use the Bedrock integration.

This approach allows us to:

1. First verify that your AWS credentials are valid
2. Then implement the Bedrock integration once we know the credentials work

The AWS status component will show you whether your credentials are working correctly, which will help diagnose any issues with your AWS setup.