Editing IAM Credential Management (section)

==Key Rotation Process for Valentia==
The following process outlines the proposed steps required to rotate access keys for the Valentia IAM user and ensure seamless data uploads to the <code>s3://kpa-valentia</code> bucket.

For access keys, the rotation process involves creating a new key, securely sharing it with Valentia, and deactivating the old key after confirmation of successful integration. 

In order to ensure a smooth key rotation, the general approach is as follows:
# '''Create a new access key''': A new access key is generated for the '''valentia''' IAM user in the AWS Console or via CLI. The old key remains active during this process to avoid disruptions.
# '''Notify Valentia''': Submit a ticket to Valentia with details of the new Access Key ID and offer to securely share the Secret Access Key. 
# '''Test the new key''': Valentia tests the new key by uploading a test file to the S3 bucket <code>s3://kpa-valentia</code>. Validate the key's activity and confirm successful uploads.
# '''Disable the old key''': Once Valentia confirms the new key is in use and testing is successful, the old key is disabled in the AWS Console or CLI.
# '''Delete the old key''': After a buffer period with no errors in data uploads, the old key is permanently deleted.
# '''Document the process''': Record the key rotation possibly in the audit log(?) and update any relevant documentation.

'''Note''': This process is currently under development and has not yet been executed. Additional refinements or adjustments may be needed once the initial rotation is completed.