# Issue with loading AWS dashboard in Kibana

**URL:** <https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629>\
**Category:** Kibana\
**Created:** [December 14, 2020, 6:55pm UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629 "2020-12-14T18:55:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![byoungman](https://avatars.discourse-cdn.com/v4/letter/b/838e76/32.png) [@byoungman](https://discuss.elastic.co/u/byoungman)\
**Post date:** [December 14, 2020, 6:55pm UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629/1 "2020-12-14T18:55:16Z")

</div>

I am having an issue with displaying the AWS Dashboard in Kibana. I have followed the steps detailed in the instructions for enabling & configuring the AWS module in Metricbeat.

When running the setup.exe command there are no errors being thrown during the dashboard creation phase.

I am able to successfully receive data from the module but when I go to launch the dashboard I'm getting the following error...

![AWS-Dashboard-Error](https://us1.discourse-cdn.com/elastic/original/3X/b/e/be8041a8415735cf09b5e988907c4f9a3f6259a9.png)

The name of my Kibana index pattern is metricbeat-\* and the name of my Elasticsearch index is metricbeat-7.10.0-2020.11.16-000001

TIA,  
Bill

---

<div class="post-metadata">

**Author:** ![Patrick\_Mueller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_mueller/32/109425_2.png) [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)\
**Post date:** [December 15, 2020, 4:43am UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629/2 "2020-12-15T04:43:14Z")

</div>

> [@byoungman](#):
>
> When running the setup.exe command there are no errors being thrown during the dashboard creation phase.
> 
> I am able to successfully receive data from the module but when I go to launch the dashboard I'm getting the following error...

Did the setup command print the dashboard id displayed in your screen shot? How did you launch the dashboard? Is there any chance that the Kibana you ran setup against is a different Kibana that you tried to launch the dashboard on? Could the dashboard have been installed in a different space? Could the user launching the dashboard not have privileges to read dashboards?

---

<div class="post-metadata">

**Author:** ![byoungman](https://avatars.discourse-cdn.com/v4/letter/b/838e76/32.png) [@byoungman](https://discuss.elastic.co/u/byoungman)\
**Post date:** [December 15, 2020, 2:09pm UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629/3 "2020-12-15T14:09:05Z")

</div>

Patrick,

Thanks for getting back to me.

1. Did the setup command print the dashboard id displayed in your screen shot?

- No it did not print the dashboard id when completed it just returned to the command line

1. How did you launch the dashboard?

- From within the Metrics =\> Add Data =\> AWS =\> Setup - Launch Dashboard  
-- Note: Yesterday I was trying to launch from within my profile that I created a couple of weeks ago when I got the message however just now I launched the 'Default' profile and was able to get to the AWS Dashboard.  
-- Question: Does this mean that dashboards are assigned Unique Id's based on the profile used (this would make sense - just thought of that)

1. Is there any chance that the Kibana you ran setup against is a different Kibana that you tried to launch the dashboard on?
2. Could the dashboard have been installed in a different space?

- See Note from above -- Yes I did  
-- Question: Does this mean that the AWS Dashboard won't be available across profiles?

1. Could the user launching the dashboard not have privileges to read dashboards?

- I configured my profile to have permissions to everything.

-Bill

---

<div class="post-metadata">

**Author:** ![Patrick\_Mueller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_mueller/32/109425_2.png) [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)\
**Post date:** [December 15, 2020, 3:08pm UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629/4 "2020-12-15T15:08:54Z")

</div>

I think by "profile" you mean "space"; see the [Kibana Spaces doc](https://www.elastic.co/guide/en/kibana/current/xpack-spaces.html) for more info.

I believe visualizations and dashboards are currently space-specific, so if you want the same dashboard in multiple spaces, you would need to copy it. See the doc "[Copy Saved Objects to other Kibana spaces](https://www.elastic.co/guide/en/kibana/current/managing-saved-objects.html#managing-saved-objects-copy-to-space)" for more information.

There are some new capabilities coming with spaces where objects like visualizations and dashboards can be "shared" across spaces. I'm not sure exactly when that will be available.

---

<div class="post-metadata">

**Author:** ![byoungman](https://avatars.discourse-cdn.com/v4/letter/b/838e76/32.png) [@byoungman](https://discuss.elastic.co/u/byoungman)\
**Post date:** [December 15, 2020, 3:55pm UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629/5 "2020-12-15T15:55:02Z")

</div>

Thanks Patrick I'll check them out

-Bill

---

<div class="post-metadata">

**Author:** ![byoungman](https://avatars.discourse-cdn.com/v4/letter/b/838e76/32.png) [@byoungman](https://discuss.elastic.co/u/byoungman)\
**Post date:** [December 15, 2020, 4:12pm UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629/6 "2020-12-15T16:12:36Z")

</div>

Worked like a charm!

Thanks and I'll mark this as resolved.

-Bill

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 12, 2021, 4:12pm UTC](https://discuss.elastic.co/t/issue-with-loading-aws-dashboard-in-kibana/258629/7 "2021-01-12T16:12:37Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
