PutSigningConfiguration
Creates or updates the registry's signing configuration, which defines rules for automatically signing images with AWS Signer.
For more information, see Managed signing in the Amazon Elastic Container Registry User Guide.
Note
To successfully generate a signature, the IAM principal pushing images must have permission to sign payloads with the AWS Signer signing profile referenced in the signing configuration.
Request Syntax
{
"signingConfiguration": {
"rules": [
{
"repositoryFilters": [
{
"filter": "string",
"filterType": "string"
}
],
"signingProfileArn": "string"
}
]
}
}Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- signingConfiguration
-
The signing configuration to assign to the registry.
Type: SigningConfiguration object
Required: Yes
Response Syntax
{
"signingConfiguration": {
"rules": [
{
"repositoryFilters": [
{
"filter": "string",
"filterType": "string"
}
],
"signingProfileArn": "string"
}
]
}
}Response Elements
If the action is successful, the service sends back an HTTP 200 response.
The following data is returned in JSON format by the service.
- signingConfiguration
-
The registry's updated signing configuration.
Type: SigningConfiguration object
Errors
For information about the errors that are common to all actions, see Common Errors.
- InvalidParameterException
-
The specified parameter is invalid. Review the available parameters for the API request.
- message
-
The error message associated with the exception.
HTTP Status Code: 400
- ServerException
-
These errors are usually caused by a server-side issue.
- message
-
The error message associated with the exception.
HTTP Status Code: 500
- ValidationException
-
There was an exception validating this request.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following:
