Added secrets lookup section (RedHatInsights#1081)

* Added secrets lookup section

Added the information for AWS Secrets Lookup Manager

Add missing AWS Secrets Manager credential

https://issues.redhat.com/browse/AAP-21325

* Added secrets lookup section

Corrections from review comments

Add missing AWS Secrets Manager credential

https://issues.redhat.com/browse/AAP-21325

Author: ianf77

downstream/assemblies/platform/assembly-controller-secret-management.adoc

@@ -9,6 +9,7 @@ With external credentials backed by credential plugins, you can map credential f
 
 {ControllerNameStart} provides a secret management system that include integrations for:
 
+* AWS Secrets Manager Lookup
 * Centrify Vault Credential Provider Lookup
 * _CyberArk Central Credential Provider_ Lookup (CCP)
 * CyberArk Conjur Secrets Manager Lookup
@@ -23,6 +24,7 @@ For more information on specifying these credentials in the User Interface, see
 
 include::platform/proc-controller-configure-secret-lookups.adoc[leveloffset=+1]
 include::platform/ref-controller-metadata-credential-input.adoc[leveloffset=+2]
+include::platform/ref-aws-secrets-manager-lookup.adoc[leveloffset=+2]
 include::platform/ref-centrify-vault-lookup.adoc[leveloffset=+2]
 include::platform/ref-cyberark-ccp-lookup.adoc[leveloffset=+2]
 include::platform/ref-cyberark-conjur-lookup.adoc[leveloffset=+2]

downstream/images/credentials-create-aws-secret-credential.png

@@ -15,7 +15,7 @@ Use the following procedure to use {ControllerName} to configure and use each of
 .Procedure
 . Create an external credential for authenticating with the secret management system. At minimum, provide a name for the external credential and select one of the following for the *Credential Type*:
 +
-* xref:ref-controller-metadata-credential-input[Metadata for credential input sources]
+* xref:ref-aws-secrets-manager-lookup[AWS Secrets Manager Lookup]
 * xref:ref-centrify-vault-lookup[Centrify Vault Credential Provider Lookup]
 * xref:ref-cyberark-ccp-lookup[CyberArk Central Credential Provider (CCP) Lookup]
 * xref:ref-cyberark-conjur-lookup[CyberArk Conjur Secrets Manager Lookup]
@@ -39,6 +39,7 @@ image:credentials-link-credential-prompt.png[Credentials link]
 This takes you to the *Metadata* tab of the input source. 
 This example shows the Metadata prompt for HashiVault Secret Lookup. 
 Metadata is specific to the input source you select. 
+
 For more information, see the xref:ref-controller-metadata-credential-input[Metadata for credential input sources] table.
 +
 image:credentials-link-metadata-prompt.png[Metadata]

downstream/modules/platform/proc-controller-configure-secret-lookups.adoc

@@ -0,0 +1,15 @@
+[id="ref-aws-secrets-manager-lookup"]
+
+= AWS Secrets Manager Lookup
+
+This plugin enables {AWS} to be used as a credential input source to pull secrets from the {AWS} Secrets Manager. 
+The AWS Secrets Manager provides similar service to {Azure} Key Vault, and the AWS collection provides a lookup plugin for it.
+
+When AWS Secrets Manager lookup is selected for Credential Type, provide the following metadata to configure your lookup:
+
+* *AWS Access Key* (required): provide the access key used for communicating with AWS key management system
+* *AWS Secret Key* (required): provide the secret as obtained by the AWS IAM console
+
+The following is an example of a configured AWS Secret Manager credential.
+
+image::credentials-create-aws-secret-credential.png[Create AWS secret]

downstream/modules/platform/ref-aws-secrets-manager-lookup.adoc

@@ -2,6 +2,17 @@
 
 = Metadata for credential input sources
 
+[discrete]
+== AWS Secrets Manager Lookup
+
+[cols="25%,50%",options="header"]
+|===
+| Metadata | Description
+| AWS Secrets Manager Region (required) | The region where the secrets manager is located.
+| AWS Secret Name (required) | Specify the AWS secret name that was generated by the AWS access key.
+|===
+
+
 [discrete]
 == CyberArk Central Credential Provider Lookup