|
1144 | 1144 | } |
1145 | 1145 | ], |
1146 | 1146 | "traits": { |
1147 | | - "smithy.api#documentation": "<p>Lists the secrets that are stored by Secrets Manager in the Amazon Web Services account, not including secrets \n that are marked for deletion. To see secrets marked for deletion, use the Secrets Manager console.</p>\n <p>To list the versions of a secret, use <a>ListSecretVersionIds</a>.</p>\n <p>To get the secret value from <code>SecretString</code> or <code>SecretBinary</code>, \n call <a>GetSecretValue</a>.</p> \n <p>For information about finding secrets in the console, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_search-secret.html\">Find secrets in Secrets Manager</a>.</p>\n <p>\n <b>Required permissions: </b>\n <code>secretsmanager:ListSecrets</code>. \n For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions\">\n IAM policy actions for Secrets Manager</a> and <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html\">Authentication \n and access control in Secrets Manager</a>. </p>", |
| 1147 | + "smithy.api#documentation": "<p>Lists the secrets that are stored by Secrets Manager in the Amazon Web Services account, not including secrets \n that are marked for deletion. To see secrets marked for deletion, use the Secrets Manager console.</p>\n <p>ListSecrets is eventually consistent, however it might not reflect changes from the last five minutes. \n To get the latest information for a specific secret, use <a>DescribeSecret</a>.</p>\n <p>To list the versions of a secret, use <a>ListSecretVersionIds</a>.</p>\n <p>To get the secret value from <code>SecretString</code> or <code>SecretBinary</code>, \n call <a>GetSecretValue</a>.</p> \n <p>For information about finding secrets in the console, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/manage_search-secret.html\">Find secrets in Secrets Manager</a>.</p>\n <p>\n <b>Required permissions: </b>\n <code>secretsmanager:ListSecrets</code>. \n For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions\">\n IAM policy actions for Secrets Manager</a> and <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html\">Authentication \n and access control in Secrets Manager</a>. </p>", |
1148 | 1148 | "smithy.api#paginated": { |
1149 | 1149 | "inputToken": "NextToken", |
1150 | 1150 | "outputToken": "NextToken", |
|
1399 | 1399 | } |
1400 | 1400 | ], |
1401 | 1401 | "traits": { |
1402 | | - "smithy.api#documentation": "<p>Creates a new version with a new encrypted secret value and attaches it to the secret. The \n version can contain a new <code>SecretString</code> value or a new <code>SecretBinary</code> value. </p>\n <p>We recommend you avoid calling <code>PutSecretValue</code> at a sustained rate of more than \n once every 10 minutes. When you update the secret value, Secrets Manager creates a new version \n of the secret. Secrets Manager removes outdated versions when there are more than 100, but it does not \n remove versions created less than 24 hours ago. If you call <code>PutSecretValue</code> more \n than once every 10 minutes, you create more versions than Secrets Manager removes, and you will reach \n the quota for secret versions.</p>\n <p>You can specify the staging labels to attach to the new version in <code>VersionStages</code>. \n If you don't include <code>VersionStages</code>, then Secrets Manager automatically\n moves the staging label <code>AWSCURRENT</code> to this version. If this operation creates \n the first version for the secret, then Secrets Manager\n automatically attaches the staging label <code>AWSCURRENT</code> to it .</p>\n <p>If this operation moves the staging label <code>AWSCURRENT</code> from another version to this\n version, then Secrets Manager also automatically moves the staging label <code>AWSPREVIOUS</code> to\n the version that <code>AWSCURRENT</code> was removed from.</p>\n <p>This operation is idempotent. If a version with a <code>VersionId</code> with the same\n value as the <code>ClientRequestToken</code> parameter already exists, and you specify the\n same secret data, the operation succeeds but does nothing. However, if the secret data is\n different, then the operation fails because you can't modify an existing version; you can\n only create new ones.</p>\n <p>\n <b>Required permissions: </b>\n <code>secretsmanager:PutSecretValue</code>. \n For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions\">\n IAM policy actions for Secrets Manager</a> and <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html\">Authentication \n and access control in Secrets Manager</a>. </p>" |
| 1402 | + "smithy.api#documentation": "<p>Creates a new version with a new encrypted secret value and attaches it to the secret. The \n version can contain a new <code>SecretString</code> value or a new <code>SecretBinary</code> value. </p>\n <p>We recommend you avoid calling <code>PutSecretValue</code> at a sustained rate of more than \n once every 10 minutes. When you update the secret value, Secrets Manager creates a new version \n of the secret. Secrets Manager removes outdated versions when there are more than 100, but it does not \n remove versions created less than 24 hours ago. If you call <code>PutSecretValue</code> more \n than once every 10 minutes, you create more versions than Secrets Manager removes, and you will reach \n the quota for secret versions.</p>\n <p>You can specify the staging labels to attach to the new version in <code>VersionStages</code>. \n If you don't include <code>VersionStages</code>, then Secrets Manager automatically\n moves the staging label <code>AWSCURRENT</code> to this version. If this operation creates \n the first version for the secret, then Secrets Manager\n automatically attaches the staging label <code>AWSCURRENT</code> to it .</p>\n <p>If this operation moves the staging label <code>AWSCURRENT</code> from another version to this\n version, then Secrets Manager also automatically moves the staging label <code>AWSPREVIOUS</code> to\n the version that <code>AWSCURRENT</code> was removed from.</p>\n <p>This operation is idempotent. If you call this operation with a <code>ClientRequestToken</code> \n that matches an existing version's VersionId, and you specify the\n same secret data, the operation succeeds but does nothing. However, if the secret data is\n different, then the operation fails because you can't modify an existing version; you can\n only create new ones.</p>\n <p>\n <b>Required permissions: </b>\n <code>secretsmanager:PutSecretValue</code>. \n For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions\">\n IAM policy actions for Secrets Manager</a> and <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html\">Authentication \n and access control in Secrets Manager</a>. </p>" |
1403 | 1403 | } |
1404 | 1404 | }, |
1405 | 1405 | "com.amazonaws.secretsmanager#PutSecretValueRequest": { |
|
2431 | 2431 | } |
2432 | 2432 | ], |
2433 | 2433 | "traits": { |
2434 | | - "smithy.api#documentation": "<p>Modifies the details of a secret, including metadata and the secret value. To change the secret value, you can also use <a>PutSecretValue</a>.</p>\n <p>To change the rotation configuration of a secret, use <a>RotateSecret</a> instead.</p>\n \n <p>We recommend you avoid calling <code>UpdateSecret</code> at a sustained rate of more than \n once every 10 minutes. When you call <code>UpdateSecret</code> to update the secret value, Secrets Manager creates a new version \n of the secret. Secrets Manager removes outdated versions when there are more than 100, but it does not \n remove versions created less than 24 hours ago. If you update the secret value more \n than once every 10 minutes, you create more versions than Secrets Manager removes, and you will reach \n the quota for secret versions.</p>\n <p>If you include <code>SecretString</code> or <code>SecretBinary</code> to create a new\n secret version, Secrets Manager automatically attaches the staging label <code>AWSCURRENT</code> to the new\n version. </p>\n <p>If you call this operation with a <code>VersionId</code> that matches an existing version's \n <code>ClientRequestToken</code>, the operation results in an error. You can't modify an existing \n version, you can only create a new version. To remove a version, remove all staging labels from it. See \n <a>UpdateSecretVersionStage</a>.</p>\n <p>If you don't specify an KMS encryption key, Secrets Manager uses the Amazon Web Services managed key \n <code>aws/secretsmanager</code>. If this key doesn't already exist in your account, then Secrets Manager \n creates it for you automatically. All users and roles in the Amazon Web Services account automatically have access \n to use <code>aws/secretsmanager</code>. Creating <code>aws/secretsmanager</code> can result in a one-time \n significant delay in returning the result. </p>\n <p>If the secret is in a different Amazon Web Services account from the credentials calling the API, then you can't \n use <code>aws/secretsmanager</code> to encrypt the secret, and you must create and use a customer managed key. </p>\n <p>\n <b>Required permissions: </b>\n <code>secretsmanager:UpdateSecret</code>. \n For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions\">\n IAM policy actions for Secrets Manager</a> and <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html\">Authentication \n and access control in Secrets Manager</a>. \n If you use a customer managed key, you must also have <code>kms:GenerateDataKey</code> and \n <code>kms:Decrypt</code> permissions on the key. For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/security-encryption.html\">\n Secret encryption and decryption</a>.</p>" |
| 2434 | + "smithy.api#documentation": "<p>Modifies the details of a secret, including metadata and the secret value. To change the secret value, you can also use <a>PutSecretValue</a>.</p>\n <p>To change the rotation configuration of a secret, use <a>RotateSecret</a> instead.</p>\n \n <p>We recommend you avoid calling <code>UpdateSecret</code> at a sustained rate of more than \n once every 10 minutes. When you call <code>UpdateSecret</code> to update the secret value, Secrets Manager creates a new version \n of the secret. Secrets Manager removes outdated versions when there are more than 100, but it does not \n remove versions created less than 24 hours ago. If you update the secret value more \n than once every 10 minutes, you create more versions than Secrets Manager removes, and you will reach \n the quota for secret versions.</p>\n <p>If you include <code>SecretString</code> or <code>SecretBinary</code> to create a new\n secret version, Secrets Manager automatically attaches the staging label <code>AWSCURRENT</code> to the new\n version. </p>\n <p>If you call this operation with a <code>ClientRequestToken</code> that matches an existing version's \n <code>VersionId</code>, the operation results in an error. You can't modify an existing \n version, you can only create a new version. To remove a version, remove all staging labels from it. See \n <a>UpdateSecretVersionStage</a>.</p>\n <p>If you don't specify an KMS encryption key, Secrets Manager uses the Amazon Web Services managed key \n <code>aws/secretsmanager</code>. If this key doesn't already exist in your account, then Secrets Manager \n creates it for you automatically. All users and roles in the Amazon Web Services account automatically have access \n to use <code>aws/secretsmanager</code>. Creating <code>aws/secretsmanager</code> can result in a one-time \n significant delay in returning the result. </p>\n <p>If the secret is in a different Amazon Web Services account from the credentials calling the API, then you can't \n use <code>aws/secretsmanager</code> to encrypt the secret, and you must create and use a customer managed key. </p>\n <p>\n <b>Required permissions: </b>\n <code>secretsmanager:UpdateSecret</code>. \n For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions\">\n IAM policy actions for Secrets Manager</a> and <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html\">Authentication \n and access control in Secrets Manager</a>. \n If you use a customer managed key, you must also have <code>kms:GenerateDataKey</code> and \n <code>kms:Decrypt</code> permissions on the key. For more information, see <a href=\"https://docs.aws.amazon.com/secretsmanager/latest/userguide/security-encryption.html\">\n Secret encryption and decryption</a>.</p>" |
2435 | 2435 | } |
2436 | 2436 | }, |
2437 | 2437 | "com.amazonaws.secretsmanager#UpdateSecretRequest": { |
|
0 commit comments