feat(aws-iam-rotation): docs improvements

This commit is contained in:
carlosmonastyrski
2025-04-25 16:35:57 -03:00
parent 7a4a877e39
commit b506393765
2 changed files with 6 additions and 5 deletions
@@ -22,7 +22,7 @@ at a specified interval or on-demand.
"iam:CreateAccessKey", "iam:CreateAccessKey",
"iam:UpdateAccessKey", "iam:UpdateAccessKey",
"iam:DeleteAccessKey", "iam:DeleteAccessKey",
"iam:ListUsers" "iam:ListUsers"
], ],
"Resource": "*" "Resource": "*"
} }
@@ -68,7 +68,7 @@ In the following steps, we explore the end-to-end workflow for setting up this s
5. Specify the secret names that the AWS IAM access key credentials should be mapped to. Then click **Next**. 5. Specify the secret names that the AWS IAM access key credentials should be mapped to. Then click **Next**.
![Rotation Secrets Mapping](/images/secret-rotations-v2/aws-iam-user-secret/aws-iam-user-secret-secrets-mapping.png) ![Rotation Secrets Mapping](/images/secret-rotations-v2/aws-iam-user-secret/aws-iam-user-secret-secrets-mapping.png)
- **Access Key ID** - the name of the secret that the aws access key ID will be mapped to. - **Access Key ID** - the name of the secret that the AWS access key ID will be mapped to.
- **Secret Access Key** - the name of the secret that the rotated secret access key will be mapped to. - **Secret Access Key** - the name of the secret that the rotated secret access key will be mapped to.
6. Give your rotation a name and description (optional). Then click **Next**. 6. Give your rotation a name and description (optional). Then click **Next**.
@@ -97,7 +97,7 @@ In the following steps, we explore the end-to-end workflow for setting up this s
--url https://us.infisical.com/api/v2/secret-rotations/aws-iam-user-secret \ --url https://us.infisical.com/api/v2/secret-rotations/aws-iam-user-secret \
--header 'Content-Type: application/json' \ --header 'Content-Type: application/json' \
--data '{ --data '{
"name": "My AWS rotation", "name": "my-aws-rotation",
"projectId": "9602cfc5-20b9-4c35-a056-dd7372db0f25", "projectId": "9602cfc5-20b9-4c35-a056-dd7372db0f25",
"description": "My rotation strategy description", "description": "My rotation strategy description",
"connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a", "connectionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
@@ -126,7 +126,7 @@ In the following steps, we explore the end-to-end workflow for setting up this s
{ {
"secretRotation": { "secretRotation": {
"id": "3c90c3cc-0d44-4b50-8888-8dd25736052a", "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"name": "My AWS rotation", "name": "my-aws-rotation",
"description": "My rotation strategy description", "description": "My rotation strategy description",
"secretsMapping": { "secretsMapping": {
"accessKeyId": "AWS_ACCESS_KEY_ID", "accessKeyId": "AWS_ACCESS_KEY_ID",
@@ -69,10 +69,11 @@ export const AwsIamUserSecretRotationParametersFields = () => {
name="parameters.region" name="parameters.region"
render={({ field: { value, onChange }, fieldState: { error } }) => ( render={({ field: { value, onChange }, fieldState: { error } }) => (
<FormControl <FormControl
isOptional
isError={Boolean(error)} isError={Boolean(error)}
errorText={error?.message} errorText={error?.message}
label="Region" label="Region"
helperText="Required only if no global scope is set." tooltipText="Required only if no global scope is set."
> >
<AwsRegionSelect value={value ?? ""} onChange={onChange} /> <AwsRegionSelect value={value ?? ""} onChange={onChange} />
</FormControl> </FormControl>