POST /2020-04-22/code-signing-configs/
Creates a code signing configuration. A code signing configuration defines a list of allowed signing profiles and defines the code-signing validation policy (action to be taken if deployment validation checks fail).
Servers
- https://lambda.{region}.amazonaws.com
- https://lambda.{region}.amazonaws.com.cn
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
X-Amz-Content-Sha256 |
String | No | |
X-Amz-Credential |
String | No | |
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
X-Amz-Date |
String | No | |
X-Amz-Algorithm |
String | No | |
X-Amz-SignedHeaders |
String | No | |
X-Amz-Security-Token |
String | No | |
X-Amz-Signature |
String | No |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
CodeSigningPolicies |
Object | No |
Code signing configuration policies specify the validation failure action for signature mismatch or expiry. |
CodeSigningPolicies.UntrustedArtifactOnDeployment |
String | No |
Code signing configuration policy for deployment validation failure. If you set the policy to Default value: Valid values:
|
Description |
String | No |
Descriptive name for this code signing configuration. |
AllowedPublishers |
Object | Yes |
List of signing profiles that can sign a code package. |
AllowedPublishers.SigningProfileVersionArns[] |
Array | No |
The Amazon Resource Name (ARN) for each of the signing profiles. A signing profile defines a trusted user who can sign a code package. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.