Tutorial: Microsoft Entra single sign-on (SSO) integration with Amazon Managed Grafana
Article
In this article
In this tutorial, you'll learn how to integrate Amazon Managed Grafana with Microsoft Entra ID. When you integrate Amazon Managed Grafana with Microsoft Entra ID, you can:
Control in Microsoft Entra ID who has access to Amazon Managed Grafana.
Enable your users to be automatically signed-in to Amazon Managed Grafana with their Microsoft Entra accounts.
Manage your accounts in one central location.
Prerequisites
To get started, you need the following items:
A Microsoft Entra subscription. If you don't have a subscription, you can get a
free account
.
Amazon Managed Grafana single sign-on (SSO) enabled subscription.
Scenario description
In this tutorial, you configure and test Microsoft Entra SSO in a test environment.
Amazon Managed Grafana supports
SP
initiated SSO.
Amazon Managed Grafana supports
Just In Time
user provisioning.
Add Amazon Managed Grafana from the gallery
To configure the integration of Amazon Managed Grafana into Microsoft Entra ID, you need to add Amazon Managed Grafana from the gallery to your list of managed SaaS apps.
Configure and test Microsoft Entra SSO for Amazon Managed Grafana
Configure and test Microsoft Entra SSO with Amazon Managed Grafana using a test user called
B.Simon
. For SSO to work, you need to establish a link relationship between a Microsoft Entra user and the related user in Amazon Managed Grafana.
To configure and test Microsoft Entra SSO with Amazon Managed Grafana, perform the following steps:
Browse to
Identity
>
Applications
>
Enterprise applications
>
Amazon Managed Grafana
>
Single sign-on
.
On the
Select a single sign-on method
page, select
SAML
.
On the
Set up single sign-on with SAML
page, click the pencil icon for
Basic SAML Configuration
to edit the settings.
On the
Basic SAML Configuration
section, perform the following steps:
a. In the
Identifier (Entity ID)
text box, type a URL using the following pattern:
https://<namespace>.grafana-workspace.<region>.amazonaws.com/saml/metadata
b. In the
Sign on URL
text box, type a URL using the following pattern:
https://<namespace>.grafana-workspace.<region>.amazonaws.com/login/saml
These values are not real. Update these values with the actual Identifier and Sign on URL. Contact
Amazon Managed Grafana Client support team
to get these values. You can also refer to the patterns shown in the
Basic SAML Configuration
section.
Amazon Managed Grafana application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.
In addition to above, Amazon Managed Grafana application expects few more attributes to be passed back in SAML response which are shown below. These attributes are also pre populated but you can review them as per your requirements.
Source attribute
On the
Set up single sign-on with SAML
page, in the
SAML Signing Certificate
section, find
Federation Metadata XML
and select
Download
to download the certificate and save it on your computer.
On the
Set up Amazon Managed Grafana
section, copy the appropriate URL(s) based on your requirement.
Create a Microsoft Entra test user
In this section, you'll create a test user called B.Simon.
In the app's overview page, select
Users and groups
.
Select
Add user/group
, then select
Users and groups
in the
Add Assignment
dialog.
In the
Users and groups
dialog, select
B.Simon
from the Users list, then click the
Select
button at the bottom of the screen.
If you are expecting a role to be assigned to the users, you can select it from the
Select a role
dropdown. If no role has been set up for this app, you see "Default Access" role selected.
In the
Add Assignment
dialog, click the
Assign
button.
Configure Amazon Managed Grafana SSO
Log in to your Amazon Managed Grafana Console as an administrator.
Click
Create workspace
.
In the
Specify workspace details
page, type a unique
Workspace name
and click
Next
.
In the
Configure settings
page, select
Security Assertion Markup Language(SAML)
checkbox and enable
Service managed
as permission type and click
Next
.
In the
Service managed permission settings
, select
Current account
and click
Next
.
In the
Review and create
page, verify all the workspace details and click
Create workspace
.
After creating workspace, click
Complete setup
to complete the SAML configuration.
In the
Security Assertion Markup Language(SAML)
page, perform the following steps.
Copy
Service provider identifier(Entity ID)
value, paste this value into the
Identifier
text box in the
Basic SAML Configuration
section.
Copy
Service provider reply URL(Assertion consumer service URL)
value, paste this value into the
Reply URL
text box in the
Basic SAML Configuration
section.
Copy
Service provider login URL
value, paste this value into the
Sign on URL
text box in the
Basic SAML Configuration
section.
Open the downloaded
Federation Metadata XML
into Notepad and upload the XML file by clicking
Choose file
option.
In the
Assertion mapping
section, fill the required values according to your requirement.
Click
Save SAML configuration
.
Create Amazon Managed Grafana test user
In this section, a user called Britta Simon is created in Amazon Managed Grafana. Amazon Managed Grafana supports just-in-time user provisioning, which is enabled by default. There is no action item for you in this section. If a user doesn't already exist in Amazon Managed Grafana, a new one is created after authentication.
Test SSO
In this section, you test your Microsoft Entra single sign-on configuration with following options.
Click on
Test this application
, this will redirect to Amazon Managed Grafana Sign-on URL where you can initiate the login flow.
Go to Amazon Managed Grafana Sign-on URL directly and initiate the login flow from there.
You can use Microsoft My Apps. When you click the Amazon Managed Grafana tile in the My Apps, this will redirect to Amazon Managed Grafana Sign-on URL. For more information about the My Apps, see
Introduction to the My Apps
.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:
https://aka.ms/ContentUserFeedback
.
