diff --git a/clients/client-securityhub/src/models/models_0.ts b/clients/client-securityhub/src/models/models_0.ts index 8e5ea7060c90..d69ef459df5f 100644 --- a/clients/client-securityhub/src/models/models_0.ts +++ b/clients/client-securityhub/src/models/models_0.ts @@ -392,31 +392,7 @@ export interface AwsApiCallAction { /** *
A timestamp that indicates when the API call was first * observed.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ FirstSeen?: string | undefined; @@ -424,31 +400,7 @@ export interface AwsApiCallAction { /** *A timestamp that indicates when the API call was most recently * observed.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastSeen?: string | undefined; @@ -1060,7 +1012,7 @@ export type ActorSessionMfaStatus = (typeof ActorSessionMfaStatus)[keyof typeof ** Contains information about the authenticated session used by the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
+ * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. * @public */ export interface ActorSession { @@ -1102,7 +1054,7 @@ export interface ActorSession { ** Provides Amazon Web Services account information of the user involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. + * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. *
* @public */ @@ -1128,7 +1080,7 @@ export interface UserAccount { ** Contains information about the credentials used by the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
+ * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. * @public */ export interface ActorUser { @@ -1177,7 +1129,7 @@ export interface ActorUser { ** Information about the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
+ * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. * @public */ export interface Actor { @@ -1645,62 +1597,14 @@ export interface DateRange { export interface DateFilter { /** *A timestamp that provides the start date for the date filter.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ Start?: string | undefined; /** *A timestamp that provides the end date for the date filter.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ End?: string | undefined; @@ -1872,31 +1776,7 @@ export interface AutomationRulesFindingFilters { * A timestamp that indicates when the potential security issue captured by a * finding was first observed by the security findings product. * - *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
** Array Members: Minimum number of 1 item. Maximum number of 20 items. *
@@ -1906,34 +1786,9 @@ export interface AutomationRulesFindingFilters { /** *- * A timestamp that indicates when the potential security issue captured by a finding - * was most recently observed by the security findings product. + * A timestamp that indicates when the security findings provider most recently observed a change in the resource that is involved in the finding. *
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
** Array Members: Minimum number of 1 item. Maximum number of 20 items. *
@@ -1945,31 +1800,7 @@ export interface AutomationRulesFindingFilters { ** A timestamp that indicates when this finding record was created. *
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
** Array Members: Minimum number of 1 item. Maximum number of 20 items. *
@@ -1981,31 +1812,7 @@ export interface AutomationRulesFindingFilters { ** A timestamp that indicates when the finding record was most recently updated. *
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
** Array Members: Minimum number of 1 item. Maximum number of 20 items. *
@@ -2280,31 +2087,7 @@ export interface AutomationRulesFindingFilters { /** ** The timestamp of when the note was updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
** Array Members: Minimum number of 1 item. Maximum number of 20 items. *
@@ -2463,31 +2246,7 @@ export interface AutomationRulesConfig { ** A timestamp that indicates when the rule was created. *
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedAt?: Date | undefined; @@ -2496,31 +2255,7 @@ export interface AutomationRulesConfig { ** A timestamp that indicates when the rule was most recently updated. *
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdatedAt?: Date | undefined; @@ -2600,31 +2335,7 @@ export interface AutomationRulesMetadata { ** A timestamp that indicates when the rule was created. *
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedAt?: Date | undefined; @@ -2633,31 +2344,7 @@ export interface AutomationRulesMetadata { ** A timestamp that indicates when the rule was most recently updated. *
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdatedAt?: Date | undefined; @@ -3275,31 +2962,7 @@ export interface AwsApiGatewayRestApiDetails { /** *Indicates when the API was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedDate?: string | undefined; @@ -3441,62 +3104,14 @@ export interface AwsApiGatewayStageDetails { /** *Indicates when the stage was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedDate?: string | undefined; /** *Indicates when the stage was most recently updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastUpdatedDate?: string | undefined; @@ -3582,31 +3197,7 @@ export interface AwsApiGatewayV2ApiDetails { /** *Indicates when the API was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedDate?: string | undefined; @@ -3711,31 +3302,7 @@ export interface AwsApiGatewayV2StageDetails { /** *Indicates when the stage was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedDate?: string | undefined; @@ -3760,31 +3327,7 @@ export interface AwsApiGatewayV2StageDetails { /** *Indicates when the stage was most recently updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastUpdatedDate?: string | undefined; @@ -4461,31 +4004,7 @@ export interface AwsAutoScalingAutoScalingGroupDetails { /** *Indicates when the auto scaling group was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedTime?: string | undefined; @@ -4709,31 +4228,7 @@ export interface AwsAutoScalingLaunchConfigurationDetails { /** *The creation date and time for the launch configuration.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedTime?: string | undefined; @@ -5558,31 +5053,7 @@ export interface AwsCertificateManagerCertificateRenewalSummary { /** *Indicates when the renewal summary was last updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdatedAt?: string | undefined; @@ -5602,31 +5073,7 @@ export interface AwsCertificateManagerCertificateDetails { /** *Indicates when the certificate was requested.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedAt?: string | undefined; @@ -5671,32 +5118,8 @@ export interface AwsCertificateManagerCertificateDetails { /** *Indicates when the certificate was imported. Provided if the certificate type is
- * IMPORTED
.
This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
IMPORTED
.
+ * For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ImportedAt?: string | undefined; @@ -5710,31 +5133,7 @@ export interface AwsCertificateManagerCertificateDetails { /** *Indicates when the certificate was issued. Provided if the certificate type is
* AMAZON_ISSUED
.
This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ IssuedAt?: string | undefined; @@ -5763,62 +5162,14 @@ export interface AwsCertificateManagerCertificateDetails { /** *The time after which the certificate becomes invalid.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ NotAfter?: string | undefined; /** *The time before which the certificate is not valid.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ NotBefore?: string | undefined; @@ -6436,31 +5787,7 @@ export interface AwsCloudFrontDistributionDetails { /** *Indicates when that the distribution was last modified.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastModifiedTime?: string | undefined; @@ -7617,31 +6944,7 @@ export interface AwsDynamoDbTableBillingModeSummary { /** *If the billing mode is PAY_PER_REQUEST
, indicates when the billing mode was
* set to that value.
This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastUpdateToPayPerRequestDateTime?: string | undefined; @@ -7711,62 +7014,14 @@ export interface AwsDynamoDbTableProjection { export interface AwsDynamoDbTableProvisionedThroughput { /** *Indicates when the provisioned throughput was last decreased.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastDecreaseDateTime?: string | undefined; /** *Indicates when the provisioned throughput was last increased.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastIncreaseDateTime?: string | undefined; @@ -8025,31 +7280,7 @@ export interface AwsDynamoDbTableRestoreSummary { /** *Indicates the point in time that the table was restored to.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ RestoreDateTime?: string | undefined; @@ -8069,31 +7300,7 @@ export interface AwsDynamoDbTableSseDescription { /** *If the key is inaccessible, the date and time when DynamoDB detected that the key was * inaccessible.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ InaccessibleEncryptionDateTime?: string | undefined; @@ -8155,31 +7362,7 @@ export interface AwsDynamoDbTableDetails { /** *Indicates when the table was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreationDateTime?: string | undefined; @@ -8869,31 +8052,7 @@ export interface AwsEc2InstanceDetails { /** *Indicates when the instance was launched.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LaunchedAt?: string | undefined; @@ -10596,31 +9755,7 @@ export interface AwsEc2NetworkAclDetails { export interface AwsEc2NetworkInterfaceAttachment { /** *Indicates when the attachment initiated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ AttachTime?: string | undefined; @@ -11466,31 +10601,7 @@ export interface AwsEc2VolumeAttachment { export interface AwsEc2VolumeDetails { /** *Indicates when the volume was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateTime?: string | undefined; @@ -12103,31 +11214,7 @@ export interface AwsEc2VpnConnectionVgwTelemetryDetails { /** *The date and time of the last change in status.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastStatusChange?: string | undefined; @@ -12305,31 +11392,7 @@ export interface AwsEcrContainerImageDetails { /** *The date and time when the image was pushed to the repository.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ImagePublishedAt?: string | undefined; diff --git a/clients/client-securityhub/src/models/models_1.ts b/clients/client-securityhub/src/models/models_1.ts index 9185eeb14cf0..c9d4708ae340 100644 --- a/clients/client-securityhub/src/models/models_1.ts +++ b/clients/client-securityhub/src/models/models_1.ts @@ -2296,31 +2296,7 @@ export interface AwsElbLoadBalancerDetails { /** *Indicates when the load balancer was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedTime?: string | undefined; @@ -2462,31 +2438,7 @@ export interface AwsElbv2LoadBalancerDetails { /** *Indicates when the load balancer was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedTime?: string | undefined; @@ -3092,31 +3044,7 @@ export interface AwsIamAccessKeySessionContextAttributes { /** *Indicates when the session was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreationDate?: string | undefined; @@ -3215,31 +3143,7 @@ export interface AwsIamAccessKeyDetails { /** *Indicates when the IAM access key was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedAt?: string | undefined; @@ -3324,31 +3228,7 @@ export interface AwsIamGroupDetails { /** *Indicates when the IAM group was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateDate?: string | undefined; @@ -3397,31 +3277,7 @@ export interface AwsIamInstanceProfileRole { /** *Indicates when the role was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateDate?: string | undefined; @@ -3458,31 +3314,7 @@ export interface AwsIamInstanceProfile { /** *Indicates when the instance profile was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateDate?: string | undefined; @@ -3550,31 +3382,7 @@ export interface AwsIamPolicyVersion { /** *Indicates when the version was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateDate?: string | undefined; @@ -3593,31 +3401,7 @@ export interface AwsIamPolicyDetails { /** *When the policy was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateDate?: string | undefined; @@ -3673,31 +3457,7 @@ export interface AwsIamPolicyDetails { /** *When the policy was most recently updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdateDate?: string | undefined; @@ -3734,31 +3494,7 @@ export interface AwsIamRoleDetails { /** *Indicates when the role was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateDate?: string | undefined; @@ -3832,31 +3568,7 @@ export interface AwsIamUserDetails { /** *Indicates when the user was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreateDate?: string | undefined; @@ -3975,31 +3687,7 @@ export interface AwsKmsKeyDetails { /** *Indicates when the KMS key was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreationDate?: number | undefined; @@ -4253,31 +3941,7 @@ export interface AwsLambdaFunctionDetails { /** *Indicates when the function was last updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastModified?: string | undefined; @@ -4380,31 +4044,7 @@ export interface AwsLambdaLayerVersionDetails { /** *Indicates when the version was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedDate?: string | undefined; @@ -6074,31 +5714,7 @@ export interface AwsRdsDbClusterDetails { /** *Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ClusterCreateTime?: string | undefined; @@ -6290,31 +5906,7 @@ export interface AwsRdsDbClusterSnapshotDetails { /** *Indicates when the snapshot was taken.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ SnapshotCreateTime?: string | undefined; @@ -6351,31 +5943,7 @@ export interface AwsRdsDbClusterSnapshotDetails { /** *Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ClusterCreateTime?: string | undefined; @@ -6910,31 +6478,7 @@ export interface AwsRdsDbInstanceDetails { /** *Indicates when the DB instance was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ InstanceCreateTime?: string | undefined; @@ -7064,31 +6608,7 @@ export interface AwsRdsDbInstanceDetails { /** *Specifies the latest time to which a database can be restored with point-in-time * restore.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LatestRestorableTime?: string | undefined; @@ -7664,31 +7184,7 @@ export interface AwsRdsEventSubscriptionDetails { /** *The datetime when the event notification subscription was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ SubscriptionCreationTime?: string | undefined; @@ -7836,31 +7332,7 @@ export interface AwsRedshiftClusterClusterSnapshotCopyStatus { export interface AwsRedshiftClusterDeferredMaintenanceWindow { /** *The end of the time window for which maintenance was deferred.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ DeferMaintenanceEndTime?: string | undefined; @@ -7873,31 +7345,7 @@ export interface AwsRedshiftClusterDeferredMaintenanceWindow { /** *The start of the time window for which maintenance was deferred.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ DeferMaintenanceStartTime?: string | undefined; @@ -8010,62 +7458,14 @@ export interface AwsRedshiftClusterLoggingStatus { /** *The last time when logs failed to be delivered.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastFailureTime?: string | undefined; /** *The last time that logs were delivered successfully.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastSuccessfulDeliveryTime?: string | undefined; @@ -8306,31 +7706,7 @@ export interface AwsRedshiftClusterDetails { /** *Indicates when the cluster was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ClusterCreateTime?: string | undefined; @@ -8456,31 +7832,7 @@ export interface AwsRedshiftClusterDetails { /** *Indicates when the next snapshot is expected to be taken. The cluster must have a valid * snapshot schedule and have backups enabled.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ExpectedNextSnapshotScheduleTime?: string | undefined; @@ -8538,31 +7890,7 @@ export interface AwsRedshiftClusterDetails { /** *Indicates the start of the next maintenance window.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ NextMaintenanceWindowStartTime?: string | undefined; @@ -9066,31 +8394,7 @@ export interface AwsS3BucketBucketLifecycleConfigurationRulesNoncurrentVersionTr export interface AwsS3BucketBucketLifecycleConfigurationRulesTransitionsDetails { /** *A date on which to transition objects to the specified storage class. If you provide Date
, you cannot provide Days
.
This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ Date?: string | undefined; @@ -9151,31 +8455,7 @@ export interface AwsS3BucketBucketLifecycleConfigurationRulesDetails { /** *The date when objects are moved or deleted.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ExpirationDate?: string | undefined; @@ -9682,31 +8962,7 @@ export interface AwsS3BucketDetails { /** *Indicates when the S3 bucket was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedAt?: string | undefined; @@ -9783,31 +9039,7 @@ export interface AwsS3BucketDetails { export interface AwsS3ObjectDetails { /** *Indicates when the object was last modified.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastModified?: string | undefined; @@ -9863,7 +9095,7 @@ export interface AwsSageMakerNotebookInstanceMetadataServiceConfigurationDetails /** *- * Provides details about an Amazon SageMaker notebook instance. + * Provides details about an Amazon SageMaker AI notebook instance. *
* @public */ @@ -9879,7 +9111,7 @@ export interface AwsSageMakerNotebookInstanceDetails { /** ** An array of up to three Git repositories associated with the notebook instance. These can be either the names of Git repositories stored as resources in your account, or the URL of Git repositories in CodeCommit or in any other Git repository. - * These repositories are cloned at the same level as the default repository of your notebook instance. For more information, see Associating Git repositories with SageMaker notebook instances in the Amazon SageMaker Developer Guide. + * These repositories are cloned at the same level as the default repository of your notebook instance. For more information, see Associating Git repositories with SageMaker AI notebook instances in the Amazon SageMaker AI Developer Guide. *
* @public */ @@ -9888,7 +9120,7 @@ export interface AwsSageMakerNotebookInstanceDetails { /** ** The Git repository associated with the notebook instance as its default code repository. This can be either the name of a Git repository stored as a resource in your account, or the URL of a Git repository in CodeCommit or in any other Git repository. - * When you open a notebook instance, it opens in the directory that contains this repository. For more information, see Associating Git repositories with SageMaker notebook instances in the Amazon SageMaker Developer Guide. + * When you open a notebook instance, it opens in the directory that contains this repository. For more information, see Associating Git repositories with SageMaker AI notebook instances in the Amazon SageMaker AI Developer Guide. *
* @public */ @@ -9896,7 +9128,7 @@ export interface AwsSageMakerNotebookInstanceDetails { /** *
- * Sets whether SageMaker provides internet access to the notebook instance. If you set this to Disabled
, this notebook instance is able to access resources only in your VPC, and is not be able to connect to SageMaker training and endpoint services unless you configure a Network Address Translation (NAT) Gateway in your VPC.
+ * Sets whether SageMaker AI provides internet access to the notebook instance. If you set this to Disabled
, this notebook instance is able to access resources only in your VPC, and is not be able to connect to SageMaker AI training and endpoint services unless you configure a Network Address Translation (NAT) Gateway in your VPC.
*
- * The Amazon Resource Name (ARN) of an Key Management Service (KMS) key that SageMaker uses to encrypt data on the storage volume attached to your notebook instance. The KMS key you provide must be enabled. For information, see + * The Amazon Resource Name (ARN) of an Key Management Service (KMS) key that SageMaker AI uses to encrypt data on the storage volume attached to your notebook instance. The KMS key you provide must be enabled. For information, see * Enabling and disabling keys in the Key Management Service Developer Guide. *
* @public @@ -9937,7 +9169,7 @@ export interface AwsSageMakerNotebookInstanceDetails { /** *- * The network interface ID that SageMaker created when the instance was created. + * The network interface ID that SageMaker AI created when the instance was created. *
* @public */ @@ -10247,7 +9479,7 @@ export interface Compliance { * Contains information about the Autonomous System (AS) of the network * endpoints involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. + * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. * * @public */ @@ -10287,7 +9519,7 @@ export type ConnectionDirection = (typeof ConnectionDirection)[keyof typeof Conn ** Contains information about the network connection involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. + * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. *
* @public */ @@ -10306,7 +9538,7 @@ export interface NetworkConnection { * Contains information about the location of a network endpoint involved in an Amazon GuardDuty Extended Threat Detection attack sequence. * GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. + * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. * * @public */ @@ -10348,7 +9580,7 @@ export interface NetworkGeoLocation { ** Contains information about network endpoints involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. + * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. *
*This field can provide information about the network endpoints associated with the resource in the attack sequence finding, * or about a specific network endpoint used for the attack.
@@ -10584,7 +9816,7 @@ export interface Signal { /** *The severity associated with the signal. For more information about severity, see - * Findings severity levels + * Severity levels for GuardDuty findings * in the Amazon GuardDuty User Guide.
* @public */ @@ -10617,7 +9849,7 @@ export interface Signal { ** Contains information about an Amazon GuardDuty Extended Threat Detection attack sequence finding. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. + * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. *
* @public */ @@ -10668,7 +9900,7 @@ export interface Sequence { ** A top-level object field that provides details about an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
+ * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. * @public */ export interface Detection { @@ -11148,31 +10380,7 @@ export interface Note { /** *A timestamp that indicates when the note was updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdatedAt: string | undefined; @@ -11240,62 +10448,14 @@ export interface PatchSummary { /** *Indicates when the operation started.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ OperationStartTime?: string | undefined; /** *Indicates when the operation completed.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ OperationEndTime?: string | undefined; @@ -11349,62 +10509,14 @@ export interface ProcessDetails { /** *Indicates when the process was launched.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LaunchedAt?: string | undefined; /** *Indicates when the process was terminated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ TerminatedAt?: string | undefined; diff --git a/clients/client-securityhub/src/models/models_2.ts b/clients/client-securityhub/src/models/models_2.ts index 13cfe0c30a59..4a63b879d3cf 100644 --- a/clients/client-securityhub/src/models/models_2.ts +++ b/clients/client-securityhub/src/models/models_2.ts @@ -1606,31 +1606,7 @@ export interface ContainerDetails { /** *Indicates when the container started.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LaunchedAt?: string | undefined; @@ -2173,7 +2149,7 @@ export interface ResourceDetails { /** *- * Provides details about an Amazon SageMaker notebook instance. + * Provides details about an Amazon SageMaker AI notebook instance. *
* @public */ @@ -2606,31 +2582,7 @@ export interface ThreatIntelIndicator { /** *Indicates when the most recent instance of a threat intelligence indicator was * observed.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastObservedAt?: string | undefined; @@ -2890,62 +2842,14 @@ export interface VulnerabilityVendor { /** *Indicates when the vulnerability advisory was created.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ VendorCreatedAt?: string | undefined; /** *Indicates when the vulnerability advisory was last updated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ VendorUpdatedAt?: string | undefined; @@ -3280,63 +3184,14 @@ export interface AwsSecurityFinding { /** *Indicates when the security findings provider first observed the potential security * issue that a finding captured.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ FirstObservedAt?: string | undefined; /** - *Indicates when the security findings provider most recently observed the potential - * security issue that a finding captured.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the security findings provider most recently observed a change in the resource that is involved in the finding.
+ *For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastObservedAt?: string | undefined; @@ -3344,62 +3199,14 @@ export interface AwsSecurityFinding { /** *Indicates when the security findings provider created the potential security issue that * a finding captured.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedAt: string | undefined; /** *Indicates when the security findings provider last updated the finding record.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdatedAt: string | undefined; @@ -3609,31 +3416,7 @@ export interface AwsSecurityFinding { /** *A timestamp that indicates when Security Hub received a finding and begins to process it.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ProcessedAt?: string | undefined; @@ -3651,7 +3434,7 @@ export interface AwsSecurityFinding { ** Provides details about an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack * sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you - * must have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. + * must have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. *
* @public */ @@ -3745,63 +3528,14 @@ export interface AwsSecurityFindingFilters { /** *A timestamp that indicates when the security findings provider first * observed the potential security issue that a finding captured.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ FirstObservedAt?: DateFilter[] | undefined; /** - *A timestamp that indicates when the security findings provider most - * recently observed the potential security issue that a finding captured.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the security findings provider most recently observed a change in the resource that is involved in the finding.
+ *For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ LastObservedAt?: DateFilter[] | undefined; @@ -3809,31 +3543,7 @@ export interface AwsSecurityFindingFilters { /** *A timestamp that indicates when the security findings provider * created the potential security issue that a finding reflects.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ CreatedAt?: DateFilter[] | undefined; @@ -3841,31 +3551,7 @@ export interface AwsSecurityFindingFilters { /** *A timestamp that indicates when the security findings provider last * updated the finding record.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdatedAt?: DateFilter[] | undefined; @@ -4079,62 +3765,14 @@ export interface AwsSecurityFindingFilters { /** *A timestamp that identifies when the process was launched.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ProcessLaunchedAt?: DateFilter[] | undefined; /** *A timestamp that identifies when the process was terminated.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ProcessTerminatedAt?: DateFilter[] | undefined; @@ -4159,6 +3797,7 @@ export interface AwsSecurityFindingFilters { /** *A timestamp that identifies the last observation of a threat intelligence indicator.
+ *For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ThreatIntelIndicatorLastObservedAt?: DateFilter[] | undefined; @@ -4324,31 +3963,7 @@ export interface AwsSecurityFindingFilters { /** *A timestamp that identifies when the container was started.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ ResourceContainerLaunchedAt?: DateFilter[] | undefined; @@ -7634,6 +7249,12 @@ export interface DescribeHubResponse { * enabled. *If set to true
, then new controls for enabled standards are enabled
* automatically. If set to false
, then new controls are not enabled.
When you automatically enable new controls, you can interact with the controls in
+ * the console and programmatically immediately after release. However, automatically enabled controls have a temporary default status of
+ * DISABLED
. It can take up to several days for Security Hub to process the control release and designate the
+ * control as ENABLED
in your account. During the processing period, you can manually enable or disable a
+ * control, and Security Hub will maintain that designation regardless of whether you have AutoEnableControls
set to
+ * true
.
A timestamp that indicates when Security Hub * processed the updated finding record.
- *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ UpdateTime?: Date | undefined; @@ -8779,31 +8376,7 @@ export interface GetFindingHistoryRequest { * returns finding history from the CreatedAt timestamp of the finding to the time at which * the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is * limited to 90 days. - *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ StartTime?: Date | undefined; @@ -8820,31 +8393,7 @@ export interface GetFindingHistoryRequest { * returns finding history from the CreatedAt timestamp of the finding to the time at which * the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is * limited to 90 days. - *This field accepts only the specified formats. Timestamps
- * can end with Z
or ("+" / "-") time-hour [":" time-minute]
. The time-secfrac after seconds is limited
- * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
- * YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
- * YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
- * YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
- * YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
* @public */ EndTime?: Date | undefined; @@ -10562,6 +10111,12 @@ export interface UpdateSecurityHubConfigurationRequest { *By default, this is set to true
, and new controls are enabled
* automatically. To not automatically enable new controls, set this to false
.
*
When you automatically enable new controls, you can interact with the controls in
+ * the console and programmatically immediately after release. However, automatically enabled controls have a temporary default status of
+ * DISABLED
. It can take up to several days for Security Hub to process the control release and designate the
+ * control as ENABLED
in your account. During the processing period, you can manually enable or disable a
+ * control, and Security Hub will maintain that designation regardless of whether you have AutoEnableControls
set to
+ * true
.
\n Information about the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" + "smithy.api#documentation": "\n Information about the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" } }, "com.amazonaws.securityhub#ActorSession": { @@ -466,7 +466,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Contains information about the authenticated session used by the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" + "smithy.api#documentation": "\n Contains information about the authenticated session used by the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" } }, "com.amazonaws.securityhub#ActorSessionMfaStatus": { @@ -521,7 +521,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Contains information about the credentials used by the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" + "smithy.api#documentation": "\n Contains information about the credentials used by the threat actor identified in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" } }, "com.amazonaws.securityhub#ActorsList": { @@ -890,13 +890,13 @@ "CreatedAt": { "target": "com.amazonaws.securityhub#Timestamp", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when the rule was created.\n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n A timestamp that indicates when the rule was created.\n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "UpdatedAt": { "target": "com.amazonaws.securityhub#Timestamp", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when the rule was most recently updated.\n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n A timestamp that indicates when the rule was most recently updated.\n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "CreatedBy": { @@ -1005,25 +1005,25 @@ "FirstObservedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when the potential security issue captured by a \n finding was first observed by the security findings product.\n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" + "smithy.api#documentation": "\n A timestamp that indicates when the potential security issue captured by a \n finding was first observed by the security findings product.\n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
\n\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" } }, "LastObservedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when the potential security issue captured by a finding \n was most recently observed by the security findings product.\n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" + "smithy.api#documentation": "\n A timestamp that indicates when the security findings provider most recently observed a change in the resource that is involved in the finding.\n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
\n\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" } }, "CreatedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when this finding record was created.\n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" + "smithy.api#documentation": "\n A timestamp that indicates when this finding record was created.\n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
\n\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" } }, "UpdatedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when the finding record was most recently updated. \n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" + "smithy.api#documentation": "\n A timestamp that indicates when the finding record was most recently updated. \n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
\n\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" } }, "Confidence": { @@ -1167,7 +1167,7 @@ "NoteUpdatedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "\n The timestamp of when the note was updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" + "smithy.api#documentation": "\n The timestamp of when the note was updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
\n\n \t\tArray Members: Minimum number of 1 item. Maximum number of 20 items.\n \t
" } }, "NoteUpdatedBy": { @@ -1247,13 +1247,13 @@ "CreatedAt": { "target": "com.amazonaws.securityhub#Timestamp", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when the rule was created.\n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n A timestamp that indicates when the rule was created.\n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "UpdatedAt": { "target": "com.amazonaws.securityhub#Timestamp", "traits": { - "smithy.api#documentation": "\n A timestamp that indicates when the rule was most recently updated.\n
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n A timestamp that indicates when the rule was most recently updated.\n
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "CreatedBy": { @@ -1655,13 +1655,13 @@ "FirstSeen": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "A timestamp that indicates when the API call was first\n observed.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the API call was first\n observed.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "LastSeen": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "A timestamp that indicates when the API call was most recently\n observed.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the API call was most recently\n observed.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -1859,7 +1859,7 @@ "CreatedDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the API was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the API was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Version": { @@ -1981,13 +1981,13 @@ "CreatedDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the stage was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the stage was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "LastUpdatedDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the stage was most recently updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the stage was most recently updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "WebAclArn": { @@ -2025,7 +2025,7 @@ "CreatedDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the API was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the API was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Description": { @@ -2119,7 +2119,7 @@ "CreatedDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the stage was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the stage was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Description": { @@ -2143,7 +2143,7 @@ "LastUpdatedDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the stage was most recently updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the stage was most recently updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "RouteSettings": { @@ -2557,7 +2557,7 @@ "CreatedTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the auto scaling group was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the auto scaling group was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "MixedInstancesPolicy": { @@ -2863,7 +2863,7 @@ "CreatedTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The creation date and time for the launch configuration.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The creation date and time for the launch configuration.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "EbsOptimized": { @@ -3457,7 +3457,7 @@ "CreatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the certificate was requested.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the certificate was requested.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "DomainName": { @@ -3487,7 +3487,7 @@ "ImportedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the certificate was imported. Provided if the certificate type is\n IMPORTED
.
This field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the certificate was imported. Provided if the certificate type is\n IMPORTED
.
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "InUseBy": { @@ -3499,7 +3499,7 @@ "IssuedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the certificate was issued. Provided if the certificate type is\n AMAZON_ISSUED
.
This field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the certificate was issued. Provided if the certificate type is\n AMAZON_ISSUED
.
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Issuer": { @@ -3523,13 +3523,13 @@ "NotAfter": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The time after which the certificate becomes invalid.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The time after which the certificate becomes invalid.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "NotBefore": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The time before which the certificate is not valid.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The time before which the certificate is not valid.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Options": { @@ -3725,7 +3725,7 @@ "UpdatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the renewal summary was last updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the renewal summary was last updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -3987,7 +3987,7 @@ "LastModifiedTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when that the distribution was last modified.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when that the distribution was last modified.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Logging": { @@ -5311,7 +5311,7 @@ "LastUpdateToPayPerRequestDateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "If the billing mode is PAY_PER_REQUEST
, indicates when the billing mode was\n set to that value.
This field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
If the billing mode is PAY_PER_REQUEST
, indicates when the billing mode was\n set to that value.
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -5337,7 +5337,7 @@ "CreationDateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the table was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the table was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "GlobalSecondaryIndexes": { @@ -5605,13 +5605,13 @@ "LastDecreaseDateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the provisioned throughput was last decreased.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the provisioned throughput was last decreased.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "LastIncreaseDateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the provisioned throughput was last increased.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the provisioned throughput was last increased.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "NumberOfDecreasesToday": { @@ -5745,7 +5745,7 @@ "RestoreDateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates the point in time that the table was restored to.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates the point in time that the table was restored to.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "RestoreInProgress": { @@ -5765,7 +5765,7 @@ "InaccessibleEncryptionDateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "If the key is inaccessible, the date and time when DynamoDB detected that the key was\n inaccessible.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
If the key is inaccessible, the date and time when DynamoDB detected that the key was\n inaccessible.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Status": { @@ -6215,7 +6215,7 @@ "LaunchedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the instance was launched.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the instance was launched.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "NetworkInterfaces": { @@ -7685,7 +7685,7 @@ "AttachTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the attachment initiated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the attachment initiated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "AttachmentId": { @@ -8321,7 +8321,7 @@ "CreateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the volume was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the volume was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "DeviceName": { @@ -8871,7 +8871,7 @@ "LastStatusChange": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The date and time of the last change in status.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The date and time of the last change in status.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "OutsideIpAddress": { @@ -8939,7 +8939,7 @@ "ImagePublishedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The date and time when the image was pushed to the repository.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The date and time when the image was pushed to the repository.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -11948,7 +11948,7 @@ "CreatedTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the load balancer was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the load balancer was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "DnsName": { @@ -12240,7 +12240,7 @@ "CreatedTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the load balancer was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the load balancer was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "DNSName": { @@ -12785,7 +12785,7 @@ "CreatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the IAM access key was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the IAM access key was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "PrincipalId": { @@ -12861,7 +12861,7 @@ "CreationDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the session was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the session was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -12962,7 +12962,7 @@ "CreateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the IAM group was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the IAM group was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "GroupId": { @@ -13026,7 +13026,7 @@ "CreateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the instance profile was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the instance profile was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "InstanceProfileId": { @@ -13082,7 +13082,7 @@ "CreateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the role was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the role was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Path": { @@ -13146,7 +13146,7 @@ "CreateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "When the policy was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
When the policy was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "DefaultVersionId": { @@ -13200,7 +13200,7 @@ "UpdateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "When the policy was most recently updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
When the policy was most recently updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -13226,7 +13226,7 @@ "CreateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the version was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the version was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -13268,7 +13268,7 @@ "CreateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the role was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the role was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "InstanceProfileList": { @@ -13347,7 +13347,7 @@ "CreateDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the user was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the user was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "GroupList": { @@ -13481,7 +13481,7 @@ "CreationDate": { "target": "com.amazonaws.securityhub#Double", "traits": { - "smithy.api#documentation": "Indicates when the KMS key was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the KMS key was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "KeyId": { @@ -13619,7 +13619,7 @@ "LastModified": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the function was last updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the function was last updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Layers": { @@ -13823,7 +13823,7 @@ "CreatedDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the version was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the version was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -14846,7 +14846,7 @@ "ClusterCreateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "EnabledCloudWatchLogsExports": { @@ -15046,7 +15046,7 @@ "SnapshotCreateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the snapshot was taken.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the snapshot was taken.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Engine": { @@ -15082,7 +15082,7 @@ "ClusterCreateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "MasterUsername": { @@ -15310,7 +15310,7 @@ "InstanceCreateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the DB instance was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the DB instance was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "KmsKeyId": { @@ -15424,7 +15424,7 @@ "LatestRestorableTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Specifies the latest time to which a database can be restored with point-in-time\n restore.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Specifies the latest time to which a database can be restored with point-in-time\n restore.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "AutoMinorVersionUpgrade": { @@ -16273,7 +16273,7 @@ "SubscriptionCreationTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The datetime when the event notification subscription was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The datetime when the event notification subscription was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -16461,7 +16461,7 @@ "DeferMaintenanceEndTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The end of the time window for which maintenance was deferred.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The end of the time window for which maintenance was deferred.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "DeferMaintenanceIdentifier": { @@ -16473,7 +16473,7 @@ "DeferMaintenanceStartTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The start of the time window for which maintenance was deferred.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The start of the time window for which maintenance was deferred.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -16517,7 +16517,7 @@ "ClusterCreateTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the cluster was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the cluster was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ClusterIdentifier": { @@ -16625,7 +16625,7 @@ "ExpectedNextSnapshotScheduleTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the next snapshot is expected to be taken. The cluster must have a valid\n snapshot schedule and have backups enabled.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the next snapshot is expected to be taken. The cluster must have a valid\n snapshot schedule and have backups enabled.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ExpectedNextSnapshotScheduleTimeStatus": { @@ -16673,7 +16673,7 @@ "NextMaintenanceWindowStartTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates the start of the next maintenance window.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates the start of the next maintenance window.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "NodeType": { @@ -16869,13 +16869,13 @@ "LastFailureTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The last time when logs failed to be delivered.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The last time when logs failed to be delivered.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "LastSuccessfulDeliveryTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The last time that logs were delivered successfully.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The last time that logs were delivered successfully.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "LoggingEnabled": { @@ -17316,7 +17316,7 @@ "ExpirationDate": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "The date when objects are moved or deleted.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
The date when objects are moved or deleted.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ExpirationInDays": { @@ -17534,7 +17534,7 @@ "Date": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "A date on which to transition objects to the specified storage class. If you provide Date
, you cannot provide Days
.
This field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A date on which to transition objects to the specified storage class. If you provide Date
, you cannot provide Days
.
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Days": { @@ -17604,7 +17604,7 @@ "CreatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the S3 bucket was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the S3 bucket was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ServerSideEncryptionConfiguration": { @@ -18077,7 +18077,7 @@ "LastModified": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the object was last modified.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the object was last modified.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ETag": { @@ -18127,19 +18127,19 @@ "AdditionalCodeRepositories": { "target": "com.amazonaws.securityhub#NonEmptyStringList", "traits": { - "smithy.api#documentation": "\n An array of up to three Git repositories associated with the notebook instance. These can be either the names of Git repositories stored as resources in your account, or the URL of Git repositories in CodeCommit or in any other Git repository. \n These repositories are cloned at the same level as the default repository of your notebook instance. For more information, see Associating Git repositories with SageMaker notebook instances in the Amazon SageMaker Developer Guide.\n
" + "smithy.api#documentation": "\n An array of up to three Git repositories associated with the notebook instance. These can be either the names of Git repositories stored as resources in your account, or the URL of Git repositories in CodeCommit or in any other Git repository. \n These repositories are cloned at the same level as the default repository of your notebook instance. For more information, see Associating Git repositories with SageMaker AI notebook instances in the Amazon SageMaker AI Developer Guide.\n
" } }, "DefaultCodeRepository": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "\n The Git repository associated with the notebook instance as its default code repository. This can be either the name of a Git repository stored as a resource in your account, or the URL of a Git repository in CodeCommit or in any other Git repository. \n When you open a notebook instance, it opens in the directory that contains this repository. For more information, see Associating Git repositories with SageMaker notebook instances in the Amazon SageMaker Developer Guide.\n
" + "smithy.api#documentation": "\n The Git repository associated with the notebook instance as its default code repository. This can be either the name of a Git repository stored as a resource in your account, or the URL of a Git repository in CodeCommit or in any other Git repository. \n When you open a notebook instance, it opens in the directory that contains this repository. For more information, see Associating Git repositories with SageMaker AI notebook instances in the Amazon SageMaker AI Developer Guide.\n
" } }, "DirectInternetAccess": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "\n Sets whether SageMaker provides internet access to the notebook instance. If you set this to Disabled
, this notebook instance is able to access resources only in your VPC, and is not be able to connect to SageMaker training and endpoint services unless you configure a Network Address Translation (NAT) Gateway in your VPC.\n
\n Sets whether SageMaker AI provides internet access to the notebook instance. If you set this to Disabled
, this notebook instance is able to access resources only in your VPC, and is not be able to connect to SageMaker AI training and endpoint services unless you configure a Network Address Translation (NAT) Gateway in your VPC.\n
\n The Amazon Resource Name (ARN) of an Key Management Service (KMS) key that SageMaker uses to encrypt data on the storage volume attached to your notebook instance. The KMS key you provide must be enabled. For information, see \n Enabling and disabling keys in the Key Management Service Developer Guide.\n
" + "smithy.api#documentation": "\n The Amazon Resource Name (ARN) of an Key Management Service (KMS) key that SageMaker AI uses to encrypt data on the storage volume attached to your notebook instance. The KMS key you provide must be enabled. For information, see \n Enabling and disabling keys in the Key Management Service Developer Guide.\n
" } }, "NetworkInterfaceId": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "\n The network interface ID that SageMaker created when the instance was created.\n
" + "smithy.api#documentation": "\n The network interface ID that SageMaker AI created when the instance was created.\n
" } }, "NotebookInstanceArn": { @@ -18240,7 +18240,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Provides details about an Amazon SageMaker notebook instance.\n
" + "smithy.api#documentation": "\n Provides details about an Amazon SageMaker AI notebook instance.\n
" } }, "com.amazonaws.securityhub#AwsSageMakerNotebookInstanceMetadataServiceConfigurationDetails": { @@ -18397,20 +18397,20 @@ "FirstObservedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the security findings provider first observed the potential security\n issue that a finding captured.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the security findings provider first observed the potential security\n issue that a finding captured.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "LastObservedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the security findings provider most recently observed the potential\n security issue that a finding captured.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the security findings provider most recently observed a change in the resource that is involved in the finding.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "CreatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { "smithy.api#clientOptional": {}, - "smithy.api#documentation": "Indicates when the security findings provider created the potential security issue that\n a finding captured.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the security findings provider created the potential security issue that\n a finding captured.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
", "smithy.api#required": {} } }, @@ -18418,7 +18418,7 @@ "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { "smithy.api#clientOptional": {}, - "smithy.api#documentation": "Indicates when the security findings provider last updated the finding record.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the security findings provider last updated the finding record.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
", "smithy.api#required": {} } }, @@ -18605,7 +18605,7 @@ "ProcessedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "A timestamp that indicates when Security Hub received a finding and begins to process it.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when Security Hub received a finding and begins to process it.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "AwsAccountName": { @@ -18617,7 +18617,7 @@ "Detection": { "target": "com.amazonaws.securityhub#Detection", "traits": { - "smithy.api#documentation": "\n Provides details about an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" + "smithy.api#documentation": "\n Provides details about an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" } } }, @@ -18667,25 +18667,25 @@ "FirstObservedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that indicates when the security findings provider first\n observed the potential security issue that a finding captured.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the security findings provider first\n observed the potential security issue that a finding captured.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "LastObservedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that indicates when the security findings provider most\n recently observed the potential security issue that a finding captured.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the security findings provider most recently observed a change in the resource that is involved in the finding.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "CreatedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that indicates when the security findings provider\n created the potential security issue that a finding reflects.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the security findings provider\n created the potential security issue that a finding reflects.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "UpdatedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that indicates when the security findings provider last\n updated the finding record.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the security findings provider last\n updated the finding record.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "SeverityProduct": { @@ -18889,13 +18889,13 @@ "ProcessLaunchedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that identifies when the process was launched.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that identifies when the process was launched.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ProcessTerminatedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that identifies when the process was terminated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that identifies when the process was terminated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ThreatIntelIndicatorType": { @@ -18919,7 +18919,7 @@ "ThreatIntelIndicatorLastObservedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that identifies the last observation of a threat intelligence indicator.
" + "smithy.api#documentation": "A timestamp that identifies the last observation of a threat intelligence indicator.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ThreatIntelIndicatorSource": { @@ -19084,7 +19084,7 @@ "ResourceContainerLaunchedAt": { "target": "com.amazonaws.securityhub#DateFilterList", "traits": { - "smithy.api#documentation": "A timestamp that identifies when the container was started.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that identifies when the container was started.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "ResourceDetailsOther": { @@ -22627,7 +22627,7 @@ "LaunchedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the container started.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the container started.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "VolumeMounts": { @@ -23609,13 +23609,13 @@ "Start": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "A timestamp that provides the start date for the date filter.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that provides the start date for the date filter.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "End": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "A timestamp that provides the end date for the date filter.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that provides the end date for the date filter.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "DateRange": { @@ -24370,7 +24370,7 @@ "AutoEnableControls": { "target": "com.amazonaws.securityhub#Boolean", "traits": { - "smithy.api#documentation": "Whether to automatically enable new controls when they are added to standards that are\n enabled.
\nIf set to true
, then new controls for enabled standards are enabled\n automatically. If set to false
, then new controls are not enabled.
Whether to automatically enable new controls when they are added to standards that are\n enabled.
\nIf set to true
, then new controls for enabled standards are enabled\n automatically. If set to false
, then new controls are not enabled.
When you automatically enable new controls, you can interact with the controls in \n the console and programmatically immediately after release. However, automatically enabled controls have a temporary default status of \n DISABLED
. It can take up to several days for Security Hub to process the control release and designate the \n control as ENABLED
in your account. During the processing period, you can manually enable or disable a \n control, and Security Hub will maintain that designation regardless of whether you have AutoEnableControls
set to \n true
.
\n A top-level object field that provides details about an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" + "smithy.api#documentation": "\n A top-level object field that provides details about an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.
" } }, "com.amazonaws.securityhub#DisableImportFindingsForProduct": { @@ -25574,7 +25574,7 @@ "UpdateTime": { "target": "com.amazonaws.securityhub#Timestamp", "traits": { - "smithy.api#documentation": "A timestamp that indicates when Security Hub \n processed the updated finding record.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when Security Hub \n processed the updated finding record.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "FindingCreated": { @@ -26467,13 +26467,13 @@ "StartTime": { "target": "com.amazonaws.securityhub#Timestamp", "traits": { - "smithy.api#documentation": "A timestamp that indicates the start time of the requested finding history.
\nIf you provide values for both StartTime
and EndTime
,\n Security Hub returns finding history for the specified time period. If you\n provide a value for StartTime
but not for EndTime
, Security Hub returns finding history from the StartTime
to the time at\n which the API is called. If you provide a value for EndTime
but not for\n StartTime
, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime
. If you\n provide neither StartTime
nor EndTime
, Security Hub\n returns finding history from the CreatedAt timestamp of the finding to the time at which\n the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is \n limited to 90 days.
This field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates the start time of the requested finding history.
\nIf you provide values for both StartTime
and EndTime
,\n Security Hub returns finding history for the specified time period. If you\n provide a value for StartTime
but not for EndTime
, Security Hub returns finding history from the StartTime
to the time at\n which the API is called. If you provide a value for EndTime
but not for\n StartTime
, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime
. If you\n provide neither StartTime
nor EndTime
, Security Hub\n returns finding history from the CreatedAt timestamp of the finding to the time at which\n the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is \n limited to 90 days.
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "EndTime": { "target": "com.amazonaws.securityhub#Timestamp", "traits": { - "smithy.api#documentation": "\n An ISO 8601-formatted timestamp that indicates the end time of the requested finding history.
\nIf you provide values for both StartTime
and EndTime
,\n Security Hub returns finding history for the specified time period. If you\n provide a value for StartTime
but not for EndTime
, Security Hub returns finding history from the StartTime
to the time at\n which the API is called. If you provide a value for EndTime
but not for\n StartTime
, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime
. If you\n provide neither StartTime
nor EndTime
, Security Hub\n returns finding history from the CreatedAt timestamp of the finding to the time at which\n the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is \n limited to 90 days.
This field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
\n An ISO 8601-formatted timestamp that indicates the end time of the requested finding history.
\nIf you provide values for both StartTime
and EndTime
,\n Security Hub returns finding history for the specified time period. If you\n provide a value for StartTime
but not for EndTime
, Security Hub returns finding history from the StartTime
to the time at\n which the API is called. If you provide a value for EndTime
but not for\n StartTime
, Security Hub returns finding history from the CreatedAt timestamp of the finding to the EndTime
. If you\n provide neither StartTime
nor EndTime
, Security Hub\n returns finding history from the CreatedAt timestamp of the finding to the time at which\n the API is called. In all of these scenarios, the response is limited to 100 results, and the maximum time period is \n limited to 90 days.
For more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "NextToken": { @@ -29265,7 +29265,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Contains information about the Autonomous System (AS) of the network \n endpoints involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" + "smithy.api#documentation": "\n Contains information about the Autonomous System (AS) of the network \n endpoints involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" } }, "com.amazonaws.securityhub#NetworkConnection": { @@ -29279,7 +29279,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Contains information about the network connection involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" + "smithy.api#documentation": "\n Contains information about the network connection involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" } }, "com.amazonaws.securityhub#NetworkConnectionAction": { @@ -29390,7 +29390,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Contains information about network endpoints involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
\nThis field can provide information about the network endpoints associated with the resource in the attack sequence finding, \nor about a specific network endpoint used for the attack.
" + "smithy.api#documentation": "\n Contains information about network endpoints involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
\nThis field can provide information about the network endpoints associated with the resource in the attack sequence finding, \nor about a specific network endpoint used for the attack.
" } }, "com.amazonaws.securityhub#NetworkEndpointsList": { @@ -29434,7 +29434,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Contains information about the location of a network endpoint involved in an Amazon GuardDuty Extended Threat Detection attack sequence. \nGuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" + "smithy.api#documentation": "\n Contains information about the location of a network endpoint involved in an Amazon GuardDuty Extended Threat Detection attack sequence. \nGuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" } }, "com.amazonaws.securityhub#NetworkHeader": { @@ -29559,7 +29559,7 @@ "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { "smithy.api#clientOptional": {}, - "smithy.api#documentation": "A timestamp that indicates when the note was updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
A timestamp that indicates when the note was updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
", "smithy.api#required": {} } } @@ -29982,13 +29982,13 @@ "OperationStartTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the operation started.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the operation started.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "OperationEndTime": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the operation completed.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the operation completed.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "RebootOption": { @@ -30150,13 +30150,13 @@ "LaunchedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the process was launched.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the process was launched.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "TerminatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the process was terminated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the process was terminated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } }, @@ -33428,7 +33428,7 @@ } }, "traits": { - "smithy.api#documentation": "\n Contains information about an Amazon GuardDuty Extended Threat Detection attack sequence finding. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" + "smithy.api#documentation": "\n Contains information about an Amazon GuardDuty Extended Threat Detection attack sequence finding. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide.\n
" } }, "com.amazonaws.securityhub#Severity": { @@ -33625,7 +33625,7 @@ "Severity": { "target": "com.amazonaws.securityhub#Double", "traits": { - "smithy.api#documentation": "The severity associated with the signal. For more information about severity, see \n Findings severity levels\n in the Amazon GuardDuty User Guide.
" + "smithy.api#documentation": "The severity associated with the signal. For more information about severity, see \n Severity levels for GuardDuty findings\n in the Amazon GuardDuty User Guide.
" } }, "Count": { @@ -34980,7 +34980,7 @@ "LastObservedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the most recent instance of a threat intelligence indicator was\n observed.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the most recent instance of a threat intelligence indicator was\n observed.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "Source": { @@ -36272,7 +36272,7 @@ "AutoEnableControls": { "target": "com.amazonaws.securityhub#Boolean", "traits": { - "smithy.api#documentation": "Whether to automatically enable new controls when they are added to standards that are\n enabled.
\nBy default, this is set to true
, and new controls are enabled\n automatically. To not automatically enable new controls, set this to false
.\n
Whether to automatically enable new controls when they are added to standards that are\n enabled.
\nBy default, this is set to true
, and new controls are enabled\n automatically. To not automatically enable new controls, set this to false
.\n
When you automatically enable new controls, you can interact with the controls in \n the console and programmatically immediately after release. However, automatically enabled controls have a temporary default status of \n DISABLED
. It can take up to several days for Security Hub to process the control release and designate the \n control as ENABLED
in your account. During the processing period, you can manually enable or disable a \n control, and Security Hub will maintain that designation regardless of whether you have AutoEnableControls
set to \n true
.
\n Provides Amazon Web Services account information of the user involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty and GuardDuty S3 Protection enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. \n
" + "smithy.api#documentation": "\n Provides Amazon Web Services account information of the user involved in an Amazon GuardDuty Extended Threat Detection attack sequence. GuardDuty generates an attack \n sequence finding when multiple events align to a potentially suspicious activity. To receive GuardDuty attack sequence findings in Security Hub, you \n\t\t\t\tmust have GuardDuty enabled. For more information, see GuardDuty Extended Threat Detection in the Amazon GuardDuty User Guide. \n
" } }, "com.amazonaws.securityhub#VerificationState": { @@ -36711,13 +36711,13 @@ "VendorCreatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the vulnerability advisory was created.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the vulnerability advisory was created.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } }, "VendorUpdatedAt": { "target": "com.amazonaws.securityhub#NonEmptyString", "traits": { - "smithy.api#documentation": "Indicates when the vulnerability advisory was last updated.
\nThis field accepts only the specified formats. Timestamps \ncan end with Z
or (\"+\" / \"-\") time-hour [\":\" time-minute]
. The time-secfrac after seconds is limited \nto a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:
\n YYYY-MM-DDTHH:MM:SSZ
(for example, 2019-01-31T23:00:00Z
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ
(for example, 2019-01-31T23:00:00.123456789Z
)
\n YYYY-MM-DDTHH:MM:SS+HH:MM
(for example, 2024-01-04T15:25:10+17:59
)
\n YYYY-MM-DDTHH:MM:SS-HHMM
(for example, 2024-01-04T15:25:10-1759
)
\n YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM
(for example, 2024-01-04T15:25:10.123456789+17:59
)
Indicates when the vulnerability advisory was last updated.
\nFor more information about the validation and formatting of timestamp fields in Security Hub, see Timestamps.
" } } },