Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct formatting for AWS managed grafana URLs #275

Open
awl-ops opened this issue Aug 12, 2024 · 0 comments
Open

Correct formatting for AWS managed grafana URLs #275

awl-ops opened this issue Aug 12, 2024 · 0 comments

Comments

@awl-ops
Copy link

awl-ops commented Aug 12, 2024

Hi, we're using this tool with AWS managed grafana. We've created a token and are using it successfully. What's giving us fits is the "correct" URL for our AWS managed grafana.

What's the correct "URL format" for AWS Managed Grafana?

It looks to me like we should be using what AWS calls the "GrafanaWorkspaceURL" which is in this format:

https://.grafana-workspace.us-east-1.amazonaws.com/

It does not look like AWS has an enabled health-check (.../api/health)

So I've tried the following variations of that with the following results:

  • export GRAFANA_URL=https://.grafana-workspace.us-east-1.amazonaws.com:443

  • Result: Hits https://.grafana-workspace.us-east-1.amazonaws.com:443/api/health - Status 400, not allowed

  • export GRAFANA_URL=http://.grafana-workspace.us-east-1.amazonaws.com:80

  • Result: Hits: http://.grafana-workspace.us-east-1.amazonaws.com:80/api/health Status 400, not allowed

  • export GRAFANA_URL=http://.grafana-workspace.us-east-1.amazonaws.com:3000

  • Non-responsive to this URL, never fails, never times out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant