Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deduplication Guide
  3. S3 Interface for MSDP
  4. Identity and Access Management (IAM) for S3 interface for MSDP
  5. IAM APIs for S3 interface for MSDP
  6. UpdateAccessKey
NetBackup™ Deduplication Guide

UpdateAccessKey

Changes the status of the specified access key from Active to Inactive, or vice versa. This operation can be used to disable a user's key as part of a key rotation workflow.

If the UserName is not specified, the user name is determined implicitly based on the MSDP S3 access key ID used to sign the request.

Request Parameters

For information about the parameters that are common to all actions, See Common Parameters.

  • AccessKeyId

    The access key ID for the access key that you want to update.

    Type: String

    Length Constraints: Minimum length of 16. Maximum length of 128.

    Pattern: [\w]+

    Required: Yes

  • Status

    The status you want to assign to the secret access key. Active means that the key can be used for programmatic calls to MSDP S3 server, while Inactive means that the key cannot be used.

    Type: String

    Valid Values: Active/Inactive

    Required: Yes

  • UserName

    The name of the IAM user.

    This parameter is optional. If it is not included, it defaults to the user making the request.

    Type: String

    Length Constraints: Minimum length of 1. Maximum length of 64.

    Pattern: [\w+=,.@-]+

    Required: No

Errors

For information about the errors that are common to all actions, See Common Error Codes.

  • NoSuchEntity

    The request was rejected because it referenced a resource entity that does not exist. The error message describes the resource.

    HTTP Status Code: 404

  • ServiceFailure

    The request processing has failed because of an unknown error, exception, or, failure.

    HTTP Status Code: 500

Examples

Sample Request:

https://msdps3.veritas.com:8443/?Action=UpdateAccessKey
&AccessKeyId=GAATH0QN9N5W8TBQPSKPJ
&Status=Inactive
&UserName=User1
&Version=2010-05-08
&AUTHPARAMS

Sample Response:

<?xml version="1.0" encoding="UTF-8"?>
<UpdateAccessKeyResponse
  xmlns="https://iam.amazonaws.com/doc/2010-05-08/">
<ResponseMetadata>
    <RequestId>1648451481105563455</RequestId>
  </ResponseMetadata>
</UpdateAccessKeyResponse>

Feedback

Was this page helpful?
Previous

DeleteAccessKey

Next

PutUserPolicy

Feedback

Was this page helpful?