sdk_apimanagement for a Websocket in Lambda - Error: NoMatchingAuthScheme #981
Answered
by
jdisanti
Sandy-Garrido
asked this question in
Q&A
-
Describe the bugPrefacing this issue with the fact that it could be my misconfiguring. I'm currently having trouble posting a message back to a connection via a Websocket API. I've tried a few things such as getting credentials using some of the methods I've seen around github but whichever way I do try I just haven't managed to crack the right combination. I have a lambda role which I usually set privs there but it doesn't seem to even work when I give it full admin. I assumed action Expected BehaviorI just expected either a less confusing error message or a success :D Current BehaviorReproduction Steps// not 100% certain what endpoint url it needs here?
// https://xxxxx.execute-api.xx-xx-xx.amazonaws.com/dev/@connections ??
let endpoint_url = "xxxxxx";
let config = SdkConfig::builder()
.endpoint_url(endpoint_url)
.behavior_version(BehaviorVersion::latest())
.build();
let client = aws_sdk_apigatewaymanagement::Client::new(&config);
client
.post_to_connection()
.connection_id(connection_id)
.data(data_as_blob)
.send().await;Possible SolutionNo response Additional Information/ContextNo response VersionEnvironment details (OS name and version, etc.)Custom runtime on Amazon Linux 2 - cargo lambda v1 Rust Function LogsNo response |
Beta Was this translation helpful? Give feedback.
Answered by
jdisanti
Nov 29, 2023
Replies: 2 comments
-
|
You need to configure credentials. Unfortunately, the error message is really bad right now. We're working on a fix in #979. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
Sandy-Garrido
-
|
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You need to configure credentials. Unfortunately, the error message is really bad right now. We're working on a fix in #979.