|
3499 | 3499 | "encryptionType": {
|
3500 | 3500 | "target": "com.amazonaws.ecr#EncryptionType",
|
3501 | 3501 | "traits": {
|
3502 |
| - "smithy.api#documentation": "<p>The encryption type to use.</p>\n <p>If you use the <code>KMS</code> encryption type, the contents of the repository will\n be encrypted using server-side encryption with Key Management Service key stored in KMS. When you\n use KMS to encrypt your data, you can either use the default Amazon Web Services managed KMS key\n for Amazon ECR, or specify your own KMS key, which you already created.</p>\n <p>If you use the <code>KMS_DSSE</code> encryption type, the contents of the repository\n will be encrypted with two layers of encryption using server-side encryption with the\n KMS Management Service key stored in KMS. Similar to the KMS encryption type, you\n can either use the default Amazon Web Services managed KMS key for Amazon ECR, or specify your own KMS\n key, which you've already created. </p>\n <p>If you use the <code>AES256</code> encryption type, Amazon ECR uses server-side encryption\n with Amazon S3-managed encryption keys which encrypts the images in the repository using an\n AES256 encryption algorithm. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html\">Protecting data using\n server-side encryption with Amazon S3-managed encryption keys (SSE-S3)</a> in the\n <i>Amazon Simple Storage Service Console Developer Guide</i>.</p>", |
| 3502 | + "smithy.api#documentation": "<p>The encryption type to use.</p>\n <p>If you use the <code>KMS</code> encryption type, the contents of the repository will\n be encrypted using server-side encryption with Key Management Service key stored in KMS. When you\n use KMS to encrypt your data, you can either use the default Amazon Web Services managed KMS key\n for Amazon ECR, or specify your own KMS key, which you already created.</p>\n <p>If you use the <code>KMS_DSSE</code> encryption type, the contents of the repository\n will be encrypted with two layers of encryption using server-side encryption with the\n KMS Management Service key stored in KMS. Similar to the <code>KMS</code> encryption type, you\n can either use the default Amazon Web Services managed KMS key for Amazon ECR, or specify your own KMS\n key, which you've already created. </p>\n <p>If you use the <code>AES256</code> encryption type, Amazon ECR uses server-side encryption\n with Amazon S3-managed encryption keys which encrypts the images in the repository using an\n AES256 encryption algorithm.</p>\n <p>For more information, see <a href=\"https://docs.aws.amazon.com/AmazonECR/latest/userguide/encryption-at-rest.html\">Amazon ECR encryption at\n rest</a> in the <i>Amazon Elastic Container Registry User Guide</i>.</p>", |
3503 | 3503 | "smithy.api#required": {}
|
3504 | 3504 | }
|
3505 | 3505 | },
|
|
3651 | 3651 | "traits": {
|
3652 | 3652 | "smithy.api#documentation": "<p>The date and time the finding was last updated at.</p>"
|
3653 | 3653 | }
|
| 3654 | + }, |
| 3655 | + "fixAvailable": { |
| 3656 | + "target": "com.amazonaws.ecr#FixAvailable", |
| 3657 | + "traits": { |
| 3658 | + "smithy.api#documentation": "<p>Details on whether a fix is available through a version update. This value can be\n <code>YES</code>, <code>NO</code>, or <code>PARTIAL</code>. A <code>PARTIAL</code>\n fix means that some, but not all, of the packages identified in the finding have fixes\n available through updated versions.</p>" |
| 3659 | + } |
| 3660 | + }, |
| 3661 | + "exploitAvailable": { |
| 3662 | + "target": "com.amazonaws.ecr#ExploitAvailable", |
| 3663 | + "traits": { |
| 3664 | + "smithy.api#documentation": "<p>If a finding discovered in your environment has an exploit available.</p>" |
| 3665 | + } |
3654 | 3666 | }
|
3655 | 3667 | },
|
3656 | 3668 | "traits": {
|
|
3675 | 3687 | "com.amazonaws.ecr#ExpirationTimestamp": {
|
3676 | 3688 | "type": "timestamp"
|
3677 | 3689 | },
|
| 3690 | + "com.amazonaws.ecr#ExploitAvailable": { |
| 3691 | + "type": "string" |
| 3692 | + }, |
3678 | 3693 | "com.amazonaws.ecr#FilePath": {
|
3679 | 3694 | "type": "string"
|
3680 | 3695 | },
|
|
3737 | 3752 | "target": "com.amazonaws.ecr#SeverityCount"
|
3738 | 3753 | }
|
3739 | 3754 | },
|
| 3755 | + "com.amazonaws.ecr#FixAvailable": { |
| 3756 | + "type": "string" |
| 3757 | + }, |
| 3758 | + "com.amazonaws.ecr#FixedInVersion": { |
| 3759 | + "type": "string" |
| 3760 | + }, |
3740 | 3761 | "com.amazonaws.ecr#ForceFlag": {
|
3741 | 3762 | "type": "boolean",
|
3742 | 3763 | "traits": {
|
|
8639 | 8660 | "traits": {
|
8640 | 8661 | "smithy.api#documentation": "<p>The version of the vulnerable package.</p>"
|
8641 | 8662 | }
|
| 8663 | + }, |
| 8664 | + "fixedInVersion": { |
| 8665 | + "target": "com.amazonaws.ecr#FixedInVersion", |
| 8666 | + "traits": { |
| 8667 | + "smithy.api#documentation": "<p>The version of the package that contains the vulnerability fix.</p>" |
| 8668 | + } |
8642 | 8669 | }
|
8643 | 8670 | },
|
8644 | 8671 | "traits": {
|
|
0 commit comments