选择您的 Cookie 首选项

我们使用必要 Cookie 和类似工具提供我们的网站和服务。我们使用性能 Cookie 收集匿名统计数据,以便我们可以了解客户如何使用我们的网站并进行改进。必要 Cookie 无法停用,但您可以单击“自定义”或“拒绝”来拒绝性能 Cookie。

如果您同意,AWS 和经批准的第三方还将使用 Cookie 提供有用的网站功能、记住您的首选项并显示相关内容,包括相关广告。要接受或拒绝所有非必要 Cookie,请单击“接受”或“拒绝”。要做出更详细的选择,请单击“自定义”。

Revoke signatures generated by Signer

聚焦模式
Revoke signatures generated by Signer - AWS Signer
此页面尚未翻译为您的语言。 请求翻译

Revocation of a signature becomes necessary when the signing certificate is compromised in some way, for example, if the secret key is publicly disclosed. Revoking the signature of an AWS Lambda deployment package invalidates it, causing it to fail Lambda signature checks in all Regions of the same partition. Revoking the signature of a container image causes validation to fail if you attempt to deploy the image.

Note

Revocation is an irreversible action and is recommended only for critical scenarios. Revocation checks are valid for six months beyond the expiry of a signature. Expired signatures will fail on expiry checks instead.

You can revoke individual signatures either by using the RevokeSignature API or by selecting a signing job in the AWS Signer console.

You can revoke a signing profile by using the RevokeSigningProfile API or by selecting and revoking a signing profile in the AWS Signer console. Once revoked, a signing profile can no longer be used for creating new signing jobs.

Revocation for a signing profile requires an effective start time in the past. The start time cannot be in the future. The effective start time can be changed to an earlier date and time by repeating the revocation, but cannot be revised to a later date and time.

隐私网站条款Cookie 首选项
© 2025, Amazon Web Services, Inc. 或其附属公司。保留所有权利。