npm - @aws-sdk/client-securityhub - Versions diffs - 3.540.0 → 3.549.0 - Mend

@aws-sdk/client-securityhub 3.540.0 → 3.549.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (8) hide show

package/README.md +39 -15
package/dist-types/SecurityHub.d.ts +39 -15
package/dist-types/SecurityHubClient.d.ts +39 -15
package/dist-types/index.d.ts +39 -15
package/dist-types/models/models_0.d.ts +978 -114
package/dist-types/models/models_1.d.ts +931 -119
package/dist-types/models/models_2.d.ts +488 -56
package/package.json +6 -6

package/dist-types/models/models_0.d.ts CHANGED Viewed

@@ -297,16 +297,64 @@ export interface AwsApiCallAction {
      */
     AffectedResources?: Record<string, string>;
     /**
-     * <p>An ISO8601-formatted timestamp that indicates when the API call was first
+     * <p>A timestamp that indicates when the API call was first
      *          observed.</p>
-     *          <p>A correctly formatted example is <code>2020-05-21T20:16:34.724Z</code>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For more information, see <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC 3339 section 5.6, Internet Date/Time Format</a>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     FirstSeen?: string;
     /**
-     * <p>An ISO8601-formatted timestamp that indicates when the API call was most recently
+     * <p>A timestamp that indicates when the API call was most recently
      *          observed.</p>
-     *          <p>A correctly formatted example is <code>2020-05-21T20:16:34.724Z</code>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For more information, see <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC 3339 section 5.6, Internet Date/Time Format</a>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastSeen?: string;
@@ -1244,15 +1292,61 @@ export interface DateRange {
 export interface DateFilter {
     /**
      * <p>A timestamp that provides the start date for the date filter.</p>
-     *          <p>A correctly formatted example is <code>2020-05-21T20:16:34.724Z</code>. The value cannot contain spaces, and date and time should be separated by <code>T</code>.
-     *          For more information, see <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC 3339 section 5.6, Internet Date/Time Format</a>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     Start?: string;
     /**
      * <p>A timestamp that provides the end date for the date filter.</p>
-     *          <p>A correctly formatted example is <code>2020-05-21T20:16:34.724Z</code>. The value cannot contain spaces, and date and time should be separated by <code>T</code>.
-     *          For more information, see <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC 3339 section 5.6, Internet Date/Time Format</a>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     End?: string;
@@ -1412,9 +1506,31 @@ export interface AutomationRulesFindingFilters {
      *          A timestamp that indicates when the potential security issue captured by a
      *          finding was first observed by the security findings product.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      *          <p>
      *    		Array Members: Minimum number of 1 item. Maximum number of 20 items.
      *    	</p>
@@ -1426,9 +1542,31 @@ 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.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      *          <p>
      *    		Array Members: Minimum number of 1 item. Maximum number of 20 items.
      *    	</p>
@@ -1439,9 +1577,31 @@ export interface AutomationRulesFindingFilters {
      * <p>
      *          A timestamp that indicates when this finding record was created.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      *          <p>
      *    		Array Members: Minimum number of 1 item. Maximum number of 20 items.
      *    	</p>
@@ -1452,9 +1612,31 @@ export interface AutomationRulesFindingFilters {
      * <p>
      *          A timestamp that indicates when the finding record was most recently updated.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      *          <p>
      *    		Array Members: Minimum number of 1 item. Maximum number of 20 items.
      *    	</p>
@@ -1704,10 +1886,32 @@ export interface AutomationRulesFindingFilters {
     NoteText?: StringFilter[];
     /**
      * <p>
-     *          The timestamp of when the note was updated. Uses the date-time format specified in
-     *          <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6">RFC 3339 section 5.6, Internet Date/Time Format</a>. The value cannot contain spaces.
-     *          For example, <code>2020-03-22T13:22:13.933Z</code>.
-     *       </p>
+     *          The timestamp of when the note was updated.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      *          <p>
      *    		Array Members: Minimum number of 1 item. Maximum number of 20 items.
      *    	</p>
@@ -1850,9 +2054,31 @@ export interface AutomationRulesConfig {
      * <p>
      *          A timestamp that indicates when the rule was created.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedAt?: Date;
@@ -1860,9 +2086,31 @@ export interface AutomationRulesConfig {
      * <p>
      *          A timestamp that indicates when the rule was most recently updated.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     UpdatedAt?: Date;
@@ -1934,9 +2182,31 @@ export interface AutomationRulesMetadata {
      * <p>
      *          A timestamp that indicates when the rule was created.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedAt?: Date;
@@ -1944,9 +2214,31 @@ export interface AutomationRulesMetadata {
      * <p>
      *          A timestamp that indicates when the rule was most recently updated.
      *       </p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     UpdatedAt?: Date;
@@ -2496,9 +2788,31 @@ export interface AwsApiGatewayRestApiDetails {
     Description?: string;
     /**
      * <p>Indicates when the API was created.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedDate?: string;
@@ -2621,17 +2935,61 @@ export interface AwsApiGatewayStageDetails {
     TracingEnabled?: boolean;
     /**
      * <p>Indicates when the stage was created.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedDate?: string;
     /**
      * <p>Indicates when the stage was most recently updated.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastUpdatedDate?: string;
@@ -2706,9 +3064,31 @@ export interface AwsApiGatewayV2ApiDetails {
     ApiKeySelectionExpression?: string;
     /**
      * <p>Indicates when the API was created.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedDate?: string;
@@ -2800,9 +3180,31 @@ export interface AwsApiGatewayV2StageDetails {
     ClientCertificateId?: string;
     /**
      * <p>Indicates when the stage was created.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedDate?: string;
@@ -2823,9 +3225,31 @@ export interface AwsApiGatewayV2StageDetails {
     DeploymentId?: string;
     /**
      * <p>Indicates when the stage was most recently updated.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastUpdatedDate?: string;
@@ -3429,9 +3853,31 @@ export interface AwsAutoScalingAutoScalingGroupDetails {
     HealthCheckGracePeriod?: number;
     /**
      * <p>Indicates when the auto scaling group was created.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedTime?: string;
@@ -3632,9 +4078,31 @@ export interface AwsAutoScalingLaunchConfigurationDetails {
     ClassicLinkVpcSecurityGroups?: string[];
     /**
      * <p>The creation date and time for the launch configuration.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedTime?: string;
@@ -4372,9 +4840,31 @@ export interface AwsCertificateManagerCertificateRenewalSummary {
     RenewalStatusReason?: string;
     /**
      * <p>Indicates when the renewal summary was last updated.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     UpdatedAt?: string;
@@ -4392,9 +4882,31 @@ export interface AwsCertificateManagerCertificateDetails {
     CertificateAuthorityArn?: string;
     /**
      * <p>Indicates when the certificate was requested.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreatedAt?: string;
@@ -4435,9 +4947,31 @@ export interface AwsCertificateManagerCertificateDetails {
     /**
      * <p>Indicates when the certificate was imported. Provided if the certificate type is
      *             <code>IMPORTED</code>.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     ImportedAt?: string;
@@ -4449,9 +4983,31 @@ export interface AwsCertificateManagerCertificateDetails {
     /**
      * <p>Indicates when the certificate was issued. Provided if the certificate type is
      *             <code>AMAZON_ISSUED</code>.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     IssuedAt?: string;
@@ -4476,17 +5032,61 @@ export interface AwsCertificateManagerCertificateDetails {
     KeyUsages?: AwsCertificateManagerCertificateKeyUsage[];
     /**
      * <p>The time after which the certificate becomes invalid.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     NotAfter?: string;
     /**
      * <p>The time before which the certificate is not valid.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     NotBefore?: string;
@@ -5036,9 +5636,31 @@ export interface AwsCloudFrontDistributionDetails {
     ETag?: string;
     /**
      * <p>Indicates when that the distribution was last modified.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastModifiedTime?: string;
@@ -6062,9 +6684,31 @@ export interface AwsDynamoDbTableBillingModeSummary {
     /**
      * <p>If the billing mode is <code>PAY_PER_REQUEST</code>, indicates when the billing mode was
      *          set to that value.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastUpdateToPayPerRequestDateTime?: string;
@@ -6129,17 +6773,61 @@ export interface AwsDynamoDbTableProjection {
 export interface AwsDynamoDbTableProvisionedThroughput {
     /**
      * <p>Indicates when the provisioned throughput was last decreased.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastDecreaseDateTime?: string;
     /**
      * <p>Indicates when the provisioned throughput was last increased.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastIncreaseDateTime?: string;
@@ -6370,9 +7058,31 @@ export interface AwsDynamoDbTableRestoreSummary {
     SourceTableArn?: string;
     /**
      * <p>Indicates the point in time that the table was restored to.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     RestoreDateTime?: string;
@@ -6390,9 +7100,31 @@ export interface AwsDynamoDbTableSseDescription {
     /**
      * <p>If the key is inaccessible, the date and time when DynamoDB detected that the key was
      *          inaccessible.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     InaccessibleEncryptionDateTime?: string;
@@ -6446,9 +7178,31 @@ export interface AwsDynamoDbTableDetails {
     BillingModeSummary?: AwsDynamoDbTableBillingModeSummary;
     /**
      * <p>Indicates when the table was created.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreationDateTime?: string;
@@ -7061,9 +7815,31 @@ export interface AwsEc2InstanceDetails {
     SubnetId?: string;
     /**
      * <p>Indicates when the instance was launched.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LaunchedAt?: string;
@@ -8590,9 +9366,31 @@ export interface AwsEc2NetworkAclDetails {
 export interface AwsEc2NetworkInterfaceAttachment {
     /**
      * <p>Indicates when the attachment initiated.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     AttachTime?: string;
@@ -9341,9 +10139,31 @@ export interface AwsEc2VolumeAttachment {
 export interface AwsEc2VolumeDetails {
     /**
      * <p>Indicates when the volume was created.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *             Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *             <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     CreateTime?: string;
@@ -9885,9 +10705,31 @@ export interface AwsEc2VpnConnectionVgwTelemetryDetails {
     CertificateArn?: string;
     /**
      * <p>The date and time of the last change in status.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     LastStatusChange?: string;
@@ -10045,9 +10887,31 @@ export interface AwsEcrContainerImageDetails {
     ImageTags?: string[];
     /**
      * <p>The date and time when the image was pushed to the repository.</p>
-     *          <p>Uses the <code>date-time</code> format specified in <a href="https://tools.ietf.org/html/rfc3339#section-5.6">RFC 3339 section 5.6, Internet
-     *          Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
-     *          <code>2020-03-22T13:22:13.933Z</code>.</p>
+     *          <p>This field accepts only the specified formats. Timestamps
+     * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. 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:</p>
+     *          <ul>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
+     *             </li>
+     *          </ul>
      * @public
      */
     ImagePublishedAt?: string;