You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am from EKS team, for some EKS clusters where cuatomers are using Swagger-Codegen/ we have observed this user-agent Swagger-Codegen/1.0-SNAPSHOT/java defaults to using global STS endpoint rather than the regional STS endpoint for authentication.
If you think these calls are made from swagger-api library here is the suggestion.
We propose use the AWS regional STS endpoint by default instead of the global endpoint to enhance performance, reduce latency, and align with AWS best practices.
Note
If you think this is irrelevant feel free to close this issue.
The text was updated successfully, but these errors were encountered:
Description
I am from EKS team, for some EKS clusters where cuatomers are using
Swagger-Codegen/
we have observed this user-agentSwagger-Codegen/1.0-SNAPSHOT/java
defaults to using global STS endpoint rather than the regional STS endpoint for authentication.It is recommended to use the AWS regional endpoint rather than the global endpoint. This ensures better performance and compliance with AWS best practices.
https://docs.aws.amazon.com/sdkref/latest/guide/feature-sts-regionalized-endpoints.html
Swagger-codegen version
N/A
Swagger declaration file content or url
N/A
Command line used for generation
N/A
Steps to reproduce
N/A
Related issues/PRs
N/A
Suggest a fix/enhancement
If you think these calls are made from swagger-api library here is the suggestion.
We propose use the AWS regional STS endpoint by default instead of the global endpoint to enhance performance, reduce latency, and align with AWS best practices.
Note
If you think this is irrelevant feel free to close this issue.
The text was updated successfully, but these errors were encountered: