From 4df15511b5e0e1c0170d6508054ac63fad8c637b Mon Sep 17 00:00:00 2001
From: bitfactory-sem-denbroeder
 <92806503+bitfactory-sem-denbroeder@users.noreply.github.com>
Date: Thu, 30 Mar 2023 15:50:59 +0200
Subject: [PATCH] docs: Update aws-saml.md (#5570)

* Update aws-saml.md

Updated docs to reflect new paths

* Update aws-saml.md
---
 docs/docs/guides/integrate/services/aws-saml.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/docs/guides/integrate/services/aws-saml.md b/docs/docs/guides/integrate/services/aws-saml.md
index 8665e165a7..c5f762a0d2 100644
--- a/docs/docs/guides/integrate/services/aws-saml.md
+++ b/docs/docs/guides/integrate/services/aws-saml.md
@@ -37,9 +37,9 @@ can connect to ZITADEL as a SAML2 IDP.
 3. Fill out the fields as follows, to provide AWS with all the information it needs:
    ![Configure external identity provider](/img/saml/aws/configure_idp.png)
 
-   To connect to another environment, change the domains, for example if you would use ZITADEL under the domain "
-   example.com" you would have the URLs "https://accounts.example.com/saml/SSO"
-   and "https://accounts.exmaple.com/saml/metadata".
+   To connect to another environment, change the domains, for example if you would use ZITADEL under the url "
+   https://example.com" you would have the URLs "https://example.com/saml/v2/SSO"
+   and "https://example.com/saml/v2/metadata".
 
 4. Download the ZITADEL-used certificate to sign the responses, so that AWS can validation the signature.
 
@@ -75,4 +75,4 @@ Everything on the side of ZITADEL is done if the application is correctly create
 ## **AWS**: Test the connection
 
 The result, you can now login to you AWS account through your ZITADEL-login with the AWS SSO Sign-in URL, which you
-should have saved in "Change to external identity provider ZITADEL" step 2.
\ No newline at end of file
+should have saved in "Change to external identity provider ZITADEL" step 2.