From f6db43773c07328feab11c361f0189c4aac9bc7f Mon Sep 17 00:00:00 2001
From: Sannya Singal <32308435+sannya-singal@users.noreply.github.com>
Date: Mon, 30 Oct 2023 14:18:21 +0530
Subject: [PATCH] add unsupported key spec in kms doc (#878)

---
 content/en/user-guide/aws/kms/index.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/en/user-guide/aws/kms/index.md b/content/en/user-guide/aws/kms/index.md
index c3f8e29cd6..88c40a0229 100644
--- a/content/en/user-guide/aws/kms/index.md
+++ b/content/en/user-guide/aws/kms/index.md
@@ -130,3 +130,7 @@ LocalStack's KMS implementation is equipped to facilitate [multi-region keys](ht
 ### Key aliases 
 
 While AWS KMS conveniently establishes [aliases](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html), LocalStack follows suit by supporting these pre-configured aliases. However, it's important to note that in LocalStack, these aliases come into picture after the initial access attempt. Until that point, they are not visible.
+
+### Key specs 
+
+In AWS KMS, [SM2](https://docs.aws.amazon.com/kms/latest/developerguide/asymmetric-key-specs.html#key-spec-sm:~:text=the%20message%20digest.-,SM2%20key%20spec%20(China%20Regions%20only),-The%20SM2%20key) is a supported key spec for asymmetric keys. However, LocalStack's KMS implementation doesn't support this key spec.