Uploads an X.509 signing certificate and associates it with the specified IAM user. Some AWS services use X.509 signing certificates to validate requests that are signed with a corresponding private key. When you upload the certificate, its default status is
Active.
If the UserName field is not specified, the IAM user name is determined implicitly based on the AWS access key ID used to sign the request. Because this action works for access keys under the AWS account, you can use this action to manage root credentials even if the AWS account has no associated users.
Because the body of a X.509 certificate can be large, you should use POST rather than GET when calling UploadSigningCertificate. For information about setting up signatures and authorization through the API, go to Signing AWS API Requests in the AWS General Reference. For general information about using the Query API with IAM, go to Making Query Requests in the IAM User Guide.
/// The request was rejected because the same certificate is associated with an IAM user
/// in the account.
///
/// The request was rejected because it attempted to create a resource that already exists.
///
/// The request was rejected because the certificate is invalid.
///
/// The request was rejected because it attempted to create resources beyond the current
/// AWS account limits. The error message describes the limit exceeded.
///
/// The request was rejected because the certificate was malformed or expired. The error
/// message describes the specific error.
///
/// The request was rejected because it referenced an entity that does not exist. The
/// error message describes the entity.
///
/// The request processing has failed because of an unknown error, exception or failure.
///
