[DOCS] Manual backport of changes in PR #22629 to release/1.14.x (#22707

)

* Manual backport of changes via cherrypicking

website/content/docs/release-notes/1.14.0.mdx

@@ -17,6 +17,7 @@ Version | Issue
 ------- | ------------------------------------------------------------
 1.14.0+ | [Users limited by control groups can only access issuer detail from PKI overview page](/vault/docs/upgrading/upgrade-to-1.14.x#ui-pki-control-groups)
 All     | [API calls to update-primary may lead to data loss](/vault/docs/upgrading/upgrade-to-1.14.x#update-primary-data-loss)
+1.14.0+ | AWS static roles ignore changes to rotation period](/vault/docs/upgrading/upgrade-to-1.14.x#aws-static-role-rotation)
 
 ## Vault companion updates
 

website/content/docs/upgrading/upgrade-to-1.14.x.mdx

@@ -37,4 +37,9 @@ is measuring cumulative time writing, and not the distribution of individual wri
 
 @include 'known-issues/update-primary-data-loss.mdx'
 
-@include 'known-issues/update-primary-addrs-panic.mdx'
+@include 'known-issues/update-primary-addrs-panic.mdx'
+
+@include 'known-issues/ui-safari-login-screen.mdx'
+
+@include 'known-issues/aws-static-roles.mdx'
+

website/content/partials/known-issues/aws-static-roles.mdx

@@ -0,0 +1,16 @@
+### AWS static roles ignore changes to rotation period ((#aws-static-role-rotation))
+
+#### Affected versions
+
+- 1.14.0+
+
+#### Issue
+
+AWS static roles currently ignore configuration changes made to the key rotation
+period. As a result, Vault will continue to use whatever rotation period was set
+when the roles were originally created.
+
+#### Workaround
+
+Delete and recreate any static role objects that should use the new rotation
+period.