跳至內容

GLM-5 (zai.glm-5) unreachable on Amazon Bedrock — eu-north-1

0

Setup: Region: eu-north-1 Auth: AWS SigV4 (IAM Access Key / Secret Key) API: Bedrock Converse

Test 1: zai.glm-4.7-flash — works

POST https://bedrock-runtime.eu-north-1.amazonaws.com/model/zai.glm-4.7-flash/converse Content-Type: application/json Authorization: AWS SigV4

{"messages": [{"role": "user", "content": [{"text": "Hello"}]}]}

Result: 200 OK, response in 401ms

{"metrics":{"latencyMs":401},"output":{"message":{"content":[{"text":"Hello! I'm a large language model developed by Z.ai..."}],"role":"assistant"}},"stopReason":"end_turn","usage":{"inputTokens":6,"outputTokens":34,"totalTokens":40}}

Test 2: zai.glm-5 — timeout, no response

POST https://bedrock-runtime.eu-north-1.amazonaws.com/model/zai.glm-5/converse Content-Type: application/json Authorization: AWS SigV4

{"messages": [{"role": "user", "content": [{"text": "Hello"}]}]}

Result: Request hangs, no response, no error — times out after 30 seconds.

Summary: zai.glm-4.7-flash works without issues via the Converse API in eu-north-1 zai.glm-5 is unreachable via the same API, same account, and same region — the request hangs with no error message The endpoint bedrock-runtime.eu-north-1.amazonaws.com itself is reachable (HTTP 404 on GET confirms connectivity)

已提問 2 個月前檢視次數 114 次
2 個答案
1

Hello.

I also tried it with my AWS account.
I tried sending a request using the AWS CLI, but I got the same timeout error as you.

~ $ aws bedrock-runtime converse \
> --model-id zai.glm-5 \
> --messages '[{"role":"user","content":[{"text":"hello"}]}]' \
> --region ap-northeast-1
{
    "output": {
        "message": {
            "role": "assistant",
            "content": [
                {
                    "text": "Hello! How can I help you today?"
                }
            ]
        }
    },
    "stopReason": "end_turn",
    "usage": {
        "inputTokens": 6,
        "outputTokens": 10,
        "totalTokens": 16
    },
    "metrics": {
        "latencyMs": 385
    }
}
~ $ aws bedrock-runtime converse \
> --model-id zai.glm-5 \
> --messages '[{"role":"user","content":[{"text":"hello"}]}]' \
> --region eu-north-1

aws: [ERROR]: Read timeout on endpoint URL: "https://bedrock-runtime.eu-north-1.amazonaws.com/model/zai.glm-5/converse"

AWS may have imposed some kind of restriction.
This is probably something the user cannot resolve, so you will need to contact AWS support.
I'm also concerned about this issue, so I'll contact AWS support.
I'll share any findings.

專家
已回答 2 個月前
  • I checked with AWS support. Apparently, the problem is caused by the capacity in the eu-north-1 region, and it seems that sufficient on-demand capacity for the GLM 4.7 / GLM 5 / MiniMax M2.1 / MiniMax M2.5 models is not provisioned at this time. It seems that it is not possible to share the specific schedule from AWS about when on-demand capacity will be available in the eu-north-1 region.

-3

Based on the behavior you're describing, there are a few potential issues to investigate:

Model Availability in Region: The most likely cause is that the GLM-5 model may not be available in the eu-north-1 region, even though GLM-4.7-flash is. Foundation model availability varies by AWS region, and newer or specific models may have limited regional availability at launch.

Model Access Permissions: You may need to explicitly request access to the GLM-5 model in your account for that specific region. Amazon Bedrock requires you to request access to foundation models before you can use them, and this access is granted on a per-region basis. Even if you have access to GLM-4.7-flash, you may not automatically have access to GLM-5.

Recommendations:

  1. Check the Amazon Bedrock console in eu-north-1 to verify that GLM-5 is listed as an available model in that region
  2. Navigate to the Model Access section in the Bedrock console and confirm that you have explicitly requested and been granted access to the GLM-5 model for eu-north-1
  3. Review the AWS regional services list to confirm GLM-5 availability in eu-north-1
  4. If the model is not available in eu-north-1, consider using a region where it is available, or continue using GLM-4.7-flash in your current region

The timeout behavior (rather than an explicit error) suggests the request is being accepted but cannot be fulfilled, which is consistent with a model availability or access issue rather than a connectivity problem.
Sources
Foundation Model Choice and Customization - Amazon Bedrock Developer Experience - AWS

已回答 2 個月前
  • The model is available in eu-north-1. But in playgorund it also not working. When i try it in an other region it is working like london or usa. ihave the same problem with glm 4.7

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。