@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.
@@ -1870,9 +1870,31 @@ export interface AwsElbLoadBalancerDetails {
1870
1870
  CanonicalHostedZoneNameID?: string;
1871
1871
  /**
1872
1872
  * <p>Indicates when the load balancer was created.</p>
1873
- * <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
1874
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
1875
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
1873
+ * <p>This field accepts only the specified formats. Timestamps
1874
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
1875
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
1876
+ * <ul>
1877
+ * <li>
1878
+ * <p>
1879
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
1880
+ * </li>
1881
+ * <li>
1882
+ * <p>
1883
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
1884
+ * </li>
1885
+ * <li>
1886
+ * <p>
1887
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
1888
+ * </li>
1889
+ * <li>
1890
+ * <p>
1891
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
1892
+ * </li>
1893
+ * <li>
1894
+ * <p>
1895
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
1896
+ * </li>
1897
+ * </ul>
1876
1898
  * @public
1877
1899
  */
1878
1900
  CreatedTime?: string;
@@ -1995,9 +2017,31 @@ export interface AwsElbv2LoadBalancerDetails {
1995
2017
  CanonicalHostedZoneId?: string;
1996
2018
  /**
1997
2019
  * <p>Indicates when the load balancer was created.</p>
1998
- * <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
1999
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2000
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
2020
+ * <p>This field accepts only the specified formats. Timestamps
2021
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
2022
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
2023
+ * <ul>
2024
+ * <li>
2025
+ * <p>
2026
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
2027
+ * </li>
2028
+ * <li>
2029
+ * <p>
2030
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
2031
+ * </li>
2032
+ * <li>
2033
+ * <p>
2034
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
2035
+ * </li>
2036
+ * <li>
2037
+ * <p>
2038
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
2039
+ * </li>
2040
+ * <li>
2041
+ * <p>
2042
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
2043
+ * </li>
2044
+ * </ul>
2001
2045
  * @public
2002
2046
  */
2003
2047
  CreatedTime?: string;
@@ -2543,9 +2587,31 @@ export interface AwsIamAccessKeySessionContextAttributes {
2543
2587
  MfaAuthenticated?: boolean;
2544
2588
  /**
2545
2589
  * <p>Indicates when the session was created.</p>
2546
- * <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
2547
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2548
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
2590
+ * <p>This field accepts only the specified formats. Timestamps
2591
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
2592
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
2593
+ * <ul>
2594
+ * <li>
2595
+ * <p>
2596
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
2597
+ * </li>
2598
+ * <li>
2599
+ * <p>
2600
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
2601
+ * </li>
2602
+ * <li>
2603
+ * <p>
2604
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
2605
+ * </li>
2606
+ * <li>
2607
+ * <p>
2608
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
2609
+ * </li>
2610
+ * <li>
2611
+ * <p>
2612
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
2613
+ * </li>
2614
+ * </ul>
2549
2615
  * @public
2550
2616
  */
2551
2617
  CreationDate?: string;
@@ -2632,9 +2698,31 @@ export interface AwsIamAccessKeyDetails {
2632
2698
  Status?: AwsIamAccessKeyStatus;
2633
2699
  /**
2634
2700
  * <p>Indicates when the IAM access key was created.</p>
2635
- * <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
2636
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2637
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
2701
+ * <p>This field accepts only the specified formats. Timestamps
2702
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
2703
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
2704
+ * <ul>
2705
+ * <li>
2706
+ * <p>
2707
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
2708
+ * </li>
2709
+ * <li>
2710
+ * <p>
2711
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
2712
+ * </li>
2713
+ * <li>
2714
+ * <p>
2715
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
2716
+ * </li>
2717
+ * <li>
2718
+ * <p>
2719
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
2720
+ * </li>
2721
+ * <li>
2722
+ * <p>
2723
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
2724
+ * </li>
2725
+ * </ul>
2638
2726
  * @public
2639
2727
  */
2640
2728
  CreatedAt?: string;
@@ -2708,9 +2796,31 @@ export interface AwsIamGroupDetails {
2708
2796
  AttachedManagedPolicies?: AwsIamAttachedManagedPolicy[];
2709
2797
  /**
2710
2798
  * <p>Indicates when the IAM group was created.</p>
2711
- * <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
2712
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2713
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
2799
+ * <p>This field accepts only the specified formats. Timestamps
2800
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
2801
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
2802
+ * <ul>
2803
+ * <li>
2804
+ * <p>
2805
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
2806
+ * </li>
2807
+ * <li>
2808
+ * <p>
2809
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
2810
+ * </li>
2811
+ * <li>
2812
+ * <p>
2813
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
2814
+ * </li>
2815
+ * <li>
2816
+ * <p>
2817
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
2818
+ * </li>
2819
+ * <li>
2820
+ * <p>
2821
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
2822
+ * </li>
2823
+ * </ul>
2714
2824
  * @public
2715
2825
  */
2716
2826
  CreateDate?: string;
@@ -2752,9 +2862,31 @@ export interface AwsIamInstanceProfileRole {
2752
2862
  AssumeRolePolicyDocument?: string;
2753
2863
  /**
2754
2864
  * <p>Indicates when the role was created.</p>
2755
- * <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
2756
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2757
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
2865
+ * <p>This field accepts only the specified formats. Timestamps
2866
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
2867
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
2868
+ * <ul>
2869
+ * <li>
2870
+ * <p>
2871
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
2872
+ * </li>
2873
+ * <li>
2874
+ * <p>
2875
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
2876
+ * </li>
2877
+ * <li>
2878
+ * <p>
2879
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
2880
+ * </li>
2881
+ * <li>
2882
+ * <p>
2883
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
2884
+ * </li>
2885
+ * <li>
2886
+ * <p>
2887
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
2888
+ * </li>
2889
+ * </ul>
2758
2890
  * @public
2759
2891
  */
2760
2892
  CreateDate?: string;
@@ -2786,9 +2918,31 @@ export interface AwsIamInstanceProfile {
2786
2918
  Arn?: string;
2787
2919
  /**
2788
2920
  * <p>Indicates when the instance profile was created.</p>
2789
- * <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
2790
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2791
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
2921
+ * <p>This field accepts only the specified formats. Timestamps
2922
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
2923
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
2924
+ * <ul>
2925
+ * <li>
2926
+ * <p>
2927
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
2928
+ * </li>
2929
+ * <li>
2930
+ * <p>
2931
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
2932
+ * </li>
2933
+ * <li>
2934
+ * <p>
2935
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
2936
+ * </li>
2937
+ * <li>
2938
+ * <p>
2939
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
2940
+ * </li>
2941
+ * <li>
2942
+ * <p>
2943
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
2944
+ * </li>
2945
+ * </ul>
2792
2946
  * @public
2793
2947
  */
2794
2948
  CreateDate?: string;
@@ -2847,9 +3001,31 @@ export interface AwsIamPolicyVersion {
2847
3001
  IsDefaultVersion?: boolean;
2848
3002
  /**
2849
3003
  * <p>Indicates when the version was created.</p>
2850
- * <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
2851
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2852
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3004
+ * <p>This field accepts only the specified formats. Timestamps
3005
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3006
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3007
+ * <ul>
3008
+ * <li>
3009
+ * <p>
3010
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3011
+ * </li>
3012
+ * <li>
3013
+ * <p>
3014
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3015
+ * </li>
3016
+ * <li>
3017
+ * <p>
3018
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3019
+ * </li>
3020
+ * <li>
3021
+ * <p>
3022
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3023
+ * </li>
3024
+ * <li>
3025
+ * <p>
3026
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3027
+ * </li>
3028
+ * </ul>
2853
3029
  * @public
2854
3030
  */
2855
3031
  CreateDate?: string;
@@ -2866,9 +3042,31 @@ export interface AwsIamPolicyDetails {
2866
3042
  AttachmentCount?: number;
2867
3043
  /**
2868
3044
  * <p>When the policy was created.</p>
2869
- * <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
2870
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2871
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3045
+ * <p>This field accepts only the specified formats. Timestamps
3046
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3047
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3048
+ * <ul>
3049
+ * <li>
3050
+ * <p>
3051
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3052
+ * </li>
3053
+ * <li>
3054
+ * <p>
3055
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3056
+ * </li>
3057
+ * <li>
3058
+ * <p>
3059
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3060
+ * </li>
3061
+ * <li>
3062
+ * <p>
3063
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3064
+ * </li>
3065
+ * <li>
3066
+ * <p>
3067
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3068
+ * </li>
3069
+ * </ul>
2872
3070
  * @public
2873
3071
  */
2874
3072
  CreateDate?: string;
@@ -2915,9 +3113,31 @@ export interface AwsIamPolicyDetails {
2915
3113
  PolicyVersionList?: AwsIamPolicyVersion[];
2916
3114
  /**
2917
3115
  * <p>When the policy was most recently updated.</p>
2918
- * <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
2919
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2920
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3116
+ * <p>This field accepts only the specified formats. Timestamps
3117
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3118
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3119
+ * <ul>
3120
+ * <li>
3121
+ * <p>
3122
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3123
+ * </li>
3124
+ * <li>
3125
+ * <p>
3126
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3127
+ * </li>
3128
+ * <li>
3129
+ * <p>
3130
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3131
+ * </li>
3132
+ * <li>
3133
+ * <p>
3134
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3135
+ * </li>
3136
+ * <li>
3137
+ * <p>
3138
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3139
+ * </li>
3140
+ * </ul>
2921
3141
  * @public
2922
3142
  */
2923
3143
  UpdateDate?: string;
@@ -2950,9 +3170,31 @@ export interface AwsIamRoleDetails {
2950
3170
  AttachedManagedPolicies?: AwsIamAttachedManagedPolicy[];
2951
3171
  /**
2952
3172
  * <p>Indicates when the role was created.</p>
2953
- * <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
2954
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
2955
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3173
+ * <p>This field accepts only the specified formats. Timestamps
3174
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3175
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3176
+ * <ul>
3177
+ * <li>
3178
+ * <p>
3179
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3180
+ * </li>
3181
+ * <li>
3182
+ * <p>
3183
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3184
+ * </li>
3185
+ * <li>
3186
+ * <p>
3187
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3188
+ * </li>
3189
+ * <li>
3190
+ * <p>
3191
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3192
+ * </li>
3193
+ * <li>
3194
+ * <p>
3195
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3196
+ * </li>
3197
+ * </ul>
2956
3198
  * @public
2957
3199
  */
2958
3200
  CreateDate?: string;
@@ -3016,9 +3258,31 @@ export interface AwsIamUserDetails {
3016
3258
  AttachedManagedPolicies?: AwsIamAttachedManagedPolicy[];
3017
3259
  /**
3018
3260
  * <p>Indicates when the user was created.</p>
3019
- * <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
3020
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
3021
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3261
+ * <p>This field accepts only the specified formats. Timestamps
3262
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3263
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3264
+ * <ul>
3265
+ * <li>
3266
+ * <p>
3267
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3268
+ * </li>
3269
+ * <li>
3270
+ * <p>
3271
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3272
+ * </li>
3273
+ * <li>
3274
+ * <p>
3275
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3276
+ * </li>
3277
+ * <li>
3278
+ * <p>
3279
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3280
+ * </li>
3281
+ * <li>
3282
+ * <p>
3283
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3284
+ * </li>
3285
+ * </ul>
3022
3286
  * @public
3023
3287
  */
3024
3288
  CreateDate?: string;
@@ -3122,9 +3386,31 @@ export interface AwsKmsKeyDetails {
3122
3386
  AWSAccountId?: string;
3123
3387
  /**
3124
3388
  * <p>Indicates when the KMS key was created.</p>
3125
- * <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
3126
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
3127
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3389
+ * <p>This field accepts only the specified formats. Timestamps
3390
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3391
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3392
+ * <ul>
3393
+ * <li>
3394
+ * <p>
3395
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3396
+ * </li>
3397
+ * <li>
3398
+ * <p>
3399
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3400
+ * </li>
3401
+ * <li>
3402
+ * <p>
3403
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3404
+ * </li>
3405
+ * <li>
3406
+ * <p>
3407
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3408
+ * </li>
3409
+ * <li>
3410
+ * <p>
3411
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3412
+ * </li>
3413
+ * </ul>
3128
3414
  * @public
3129
3415
  */
3130
3416
  CreationDate?: number;
@@ -3349,9 +3635,31 @@ export interface AwsLambdaFunctionDetails {
3349
3635
  KmsKeyArn?: string;
3350
3636
  /**
3351
3637
  * <p>Indicates when the function was last updated.</p>
3352
- * <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
3353
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
3354
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3638
+ * <p>This field accepts only the specified formats. Timestamps
3639
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3640
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3641
+ * <ul>
3642
+ * <li>
3643
+ * <p>
3644
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3645
+ * </li>
3646
+ * <li>
3647
+ * <p>
3648
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3649
+ * </li>
3650
+ * <li>
3651
+ * <p>
3652
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3653
+ * </li>
3654
+ * <li>
3655
+ * <p>
3656
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3657
+ * </li>
3658
+ * <li>
3659
+ * <p>
3660
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3661
+ * </li>
3662
+ * </ul>
3355
3663
  * @public
3356
3664
  */
3357
3665
  LastModified?: string;
@@ -3429,21 +3737,41 @@ export interface AwsLambdaLayerVersionDetails {
3429
3737
  */
3430
3738
  Version?: number;
3431
3739
  /**
3432
- * <p>The layer's compatible runtimes. Maximum number of five items.</p>
3433
- * <p>Valid values: <code>nodejs10.x</code> | <code>nodejs12.x</code> | <code>java8</code> |
3434
- * <code>java11</code> | <code>python2.7</code> | <code>python3.6</code> |
3435
- * <code>python3.7</code> | <code>python3.8</code> | <code>dotnetcore1.0</code> |
3436
- * <code>dotnetcore2.1</code> | <code>go1.x</code> | <code>ruby2.5</code> |
3437
- * <code>provided</code>
3740
+ * <p>The layer's compatible <a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html">function runtimes</a>.</p>
3741
+ * <p>The following list includes deprecated runtimes. For more information, see <a href="https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy">Runtime deprecation policy</a> in the <i>Lambda Developer Guide</i>.</p>
3742
+ * <p>Array Members: Maximum number of 5 items.</p>
3743
+ * <p>Valid Values: <code>nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 | nodejs10.x | nodejs12.x | nodejs14.x | nodejs16.x | java8 | java8.al2 | java11 | python2.7 | python3.6 | python3.7 | python3.8 | python3.9 | dotnetcore1.0 | dotnetcore2.0 | dotnetcore2.1 | dotnetcore3.1 | dotnet6 | nodejs4.3-edge | go1.x | ruby2.5 | ruby2.7 | provided | provided.al2 | nodejs18.x | python3.10 | java17 | ruby3.2 | python3.11 | nodejs20.x | provided.al2023 | python3.12 | java21</code>
3438
3744
  * </p>
3439
3745
  * @public
3440
3746
  */
3441
3747
  CompatibleRuntimes?: string[];
3442
3748
  /**
3443
3749
  * <p>Indicates when the version was created.</p>
3444
- * <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
3445
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
3446
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
3750
+ * <p>This field accepts only the specified formats. Timestamps
3751
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
3752
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
3753
+ * <ul>
3754
+ * <li>
3755
+ * <p>
3756
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
3757
+ * </li>
3758
+ * <li>
3759
+ * <p>
3760
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
3761
+ * </li>
3762
+ * <li>
3763
+ * <p>
3764
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
3765
+ * </li>
3766
+ * <li>
3767
+ * <p>
3768
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
3769
+ * </li>
3770
+ * <li>
3771
+ * <p>
3772
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
3773
+ * </li>
3774
+ * </ul>
3447
3775
  * @public
3448
3776
  */
3449
3777
  CreatedDate?: string;
@@ -4917,10 +5245,32 @@ export interface AwsRdsDbClusterDetails {
4917
5245
  AssociatedRoles?: AwsRdsDbClusterAssociatedRole[];
4918
5246
  /**
4919
5247
  * <p>Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).</p>
4920
- * <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
4921
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
4922
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
4923
- * @public
5248
+ * <p>This field accepts only the specified formats. Timestamps
5249
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
5250
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
5251
+ * <ul>
5252
+ * <li>
5253
+ * <p>
5254
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
5255
+ * </li>
5256
+ * <li>
5257
+ * <p>
5258
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
5259
+ * </li>
5260
+ * <li>
5261
+ * <p>
5262
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
5263
+ * </li>
5264
+ * <li>
5265
+ * <p>
5266
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
5267
+ * </li>
5268
+ * <li>
5269
+ * <p>
5270
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
5271
+ * </li>
5272
+ * </ul>
5273
+ * @public
4924
5274
  */
4925
5275
  ClusterCreateTime?: string;
4926
5276
  /**
@@ -5092,9 +5442,31 @@ export interface AwsRdsDbClusterSnapshotDetails {
5092
5442
  AvailabilityZones?: string[];
5093
5443
  /**
5094
5444
  * <p>Indicates when the snapshot was taken.</p>
5095
- * <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
5096
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
5097
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
5445
+ * <p>This field accepts only the specified formats. Timestamps
5446
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
5447
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
5448
+ * <ul>
5449
+ * <li>
5450
+ * <p>
5451
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
5452
+ * </li>
5453
+ * <li>
5454
+ * <p>
5455
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
5456
+ * </li>
5457
+ * <li>
5458
+ * <p>
5459
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
5460
+ * </li>
5461
+ * <li>
5462
+ * <p>
5463
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
5464
+ * </li>
5465
+ * <li>
5466
+ * <p>
5467
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
5468
+ * </li>
5469
+ * </ul>
5098
5470
  * @public
5099
5471
  */
5100
5472
  SnapshotCreateTime?: string;
@@ -5125,9 +5497,31 @@ export interface AwsRdsDbClusterSnapshotDetails {
5125
5497
  VpcId?: string;
5126
5498
  /**
5127
5499
  * <p>Indicates when the DB cluster was created, in Universal Coordinated Time (UTC).</p>
5128
- * <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
5129
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
5130
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
5500
+ * <p>This field accepts only the specified formats. Timestamps
5501
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
5502
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
5503
+ * <ul>
5504
+ * <li>
5505
+ * <p>
5506
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
5507
+ * </li>
5508
+ * <li>
5509
+ * <p>
5510
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
5511
+ * </li>
5512
+ * <li>
5513
+ * <p>
5514
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
5515
+ * </li>
5516
+ * <li>
5517
+ * <p>
5518
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
5519
+ * </li>
5520
+ * <li>
5521
+ * <p>
5522
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
5523
+ * </li>
5524
+ * </ul>
5131
5525
  * @public
5132
5526
  */
5133
5527
  ClusterCreateTime?: string;
@@ -5594,9 +5988,31 @@ export interface AwsRdsDbInstanceDetails {
5594
5988
  IAMDatabaseAuthenticationEnabled?: boolean;
5595
5989
  /**
5596
5990
  * <p>Indicates when the DB instance was created.</p>
5597
- * <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
5598
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
5599
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
5991
+ * <p>This field accepts only the specified formats. Timestamps
5992
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
5993
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
5994
+ * <ul>
5995
+ * <li>
5996
+ * <p>
5997
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
5998
+ * </li>
5999
+ * <li>
6000
+ * <p>
6001
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
6002
+ * </li>
6003
+ * <li>
6004
+ * <p>
6005
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
6006
+ * </li>
6007
+ * <li>
6008
+ * <p>
6009
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
6010
+ * </li>
6011
+ * <li>
6012
+ * <p>
6013
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
6014
+ * </li>
6015
+ * </ul>
5600
6016
  * @public
5601
6017
  */
5602
6018
  InstanceCreateTime?: string;
@@ -5707,9 +6123,31 @@ export interface AwsRdsDbInstanceDetails {
5707
6123
  /**
5708
6124
  * <p>Specifies the latest time to which a database can be restored with point-in-time
5709
6125
  * restore.</p>
5710
- * <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
5711
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
5712
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
6126
+ * <p>This field accepts only the specified formats. Timestamps
6127
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
6128
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
6129
+ * <ul>
6130
+ * <li>
6131
+ * <p>
6132
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
6133
+ * </li>
6134
+ * <li>
6135
+ * <p>
6136
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
6137
+ * </li>
6138
+ * <li>
6139
+ * <p>
6140
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
6141
+ * </li>
6142
+ * <li>
6143
+ * <p>
6144
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
6145
+ * </li>
6146
+ * <li>
6147
+ * <p>
6148
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
6149
+ * </li>
6150
+ * </ul>
5713
6151
  * @public
5714
6152
  */
5715
6153
  LatestRestorableTime?: string;
@@ -6211,9 +6649,31 @@ export interface AwsRdsEventSubscriptionDetails {
6211
6649
  Status?: string;
6212
6650
  /**
6213
6651
  * <p>The datetime when the event notification subscription was created.</p>
6214
- * <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
6215
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6216
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
6652
+ * <p>This field accepts only the specified formats. Timestamps
6653
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
6654
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
6655
+ * <ul>
6656
+ * <li>
6657
+ * <p>
6658
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
6659
+ * </li>
6660
+ * <li>
6661
+ * <p>
6662
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
6663
+ * </li>
6664
+ * <li>
6665
+ * <p>
6666
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
6667
+ * </li>
6668
+ * <li>
6669
+ * <p>
6670
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
6671
+ * </li>
6672
+ * <li>
6673
+ * <p>
6674
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
6675
+ * </li>
6676
+ * </ul>
6217
6677
  * @public
6218
6678
  */
6219
6679
  SubscriptionCreationTime?: string;
@@ -6345,9 +6805,31 @@ export interface AwsRedshiftClusterClusterSnapshotCopyStatus {
6345
6805
  export interface AwsRedshiftClusterDeferredMaintenanceWindow {
6346
6806
  /**
6347
6807
  * <p>The end of the time window for which maintenance was deferred.</p>
6348
- * <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
6349
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6350
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
6808
+ * <p>This field accepts only the specified formats. Timestamps
6809
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
6810
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
6811
+ * <ul>
6812
+ * <li>
6813
+ * <p>
6814
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
6815
+ * </li>
6816
+ * <li>
6817
+ * <p>
6818
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
6819
+ * </li>
6820
+ * <li>
6821
+ * <p>
6822
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
6823
+ * </li>
6824
+ * <li>
6825
+ * <p>
6826
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
6827
+ * </li>
6828
+ * <li>
6829
+ * <p>
6830
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
6831
+ * </li>
6832
+ * </ul>
6351
6833
  * @public
6352
6834
  */
6353
6835
  DeferMaintenanceEndTime?: string;
@@ -6358,9 +6840,31 @@ export interface AwsRedshiftClusterDeferredMaintenanceWindow {
6358
6840
  DeferMaintenanceIdentifier?: string;
6359
6841
  /**
6360
6842
  * <p>The start of the time window for which maintenance was deferred.</p>
6361
- * <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
6362
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6363
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
6843
+ * <p>This field accepts only the specified formats. Timestamps
6844
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
6845
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
6846
+ * <ul>
6847
+ * <li>
6848
+ * <p>
6849
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
6850
+ * </li>
6851
+ * <li>
6852
+ * <p>
6853
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
6854
+ * </li>
6855
+ * <li>
6856
+ * <p>
6857
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
6858
+ * </li>
6859
+ * <li>
6860
+ * <p>
6861
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
6862
+ * </li>
6863
+ * <li>
6864
+ * <p>
6865
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
6866
+ * </li>
6867
+ * </ul>
6364
6868
  * @public
6365
6869
  */
6366
6870
  DeferMaintenanceStartTime?: string;
@@ -6461,17 +6965,61 @@ export interface AwsRedshiftClusterLoggingStatus {
6461
6965
  LastFailureMessage?: string;
6462
6966
  /**
6463
6967
  * <p>The last time when logs failed to be delivered.</p>
6464
- * <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
6465
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6466
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
6968
+ * <p>This field accepts only the specified formats. Timestamps
6969
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
6970
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
6971
+ * <ul>
6972
+ * <li>
6973
+ * <p>
6974
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
6975
+ * </li>
6976
+ * <li>
6977
+ * <p>
6978
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
6979
+ * </li>
6980
+ * <li>
6981
+ * <p>
6982
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
6983
+ * </li>
6984
+ * <li>
6985
+ * <p>
6986
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
6987
+ * </li>
6988
+ * <li>
6989
+ * <p>
6990
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
6991
+ * </li>
6992
+ * </ul>
6467
6993
  * @public
6468
6994
  */
6469
6995
  LastFailureTime?: string;
6470
6996
  /**
6471
6997
  * <p>The last time that logs were delivered successfully.</p>
6472
- * <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
6473
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6474
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
6998
+ * <p>This field accepts only the specified formats. Timestamps
6999
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
7000
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
7001
+ * <ul>
7002
+ * <li>
7003
+ * <p>
7004
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
7005
+ * </li>
7006
+ * <li>
7007
+ * <p>
7008
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
7009
+ * </li>
7010
+ * <li>
7011
+ * <p>
7012
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
7013
+ * </li>
7014
+ * <li>
7015
+ * <p>
7016
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
7017
+ * </li>
7018
+ * <li>
7019
+ * <p>
7020
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
7021
+ * </li>
7022
+ * </ul>
6475
7023
  * @public
6476
7024
  */
6477
7025
  LastSuccessfulDeliveryTime?: string;
@@ -6684,9 +7232,31 @@ export interface AwsRedshiftClusterDetails {
6684
7232
  ClusterAvailabilityStatus?: string;
6685
7233
  /**
6686
7234
  * <p>Indicates when the cluster was created.</p>
6687
- * <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
6688
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6689
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
7235
+ * <p>This field accepts only the specified formats. Timestamps
7236
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
7237
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
7238
+ * <ul>
7239
+ * <li>
7240
+ * <p>
7241
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
7242
+ * </li>
7243
+ * <li>
7244
+ * <p>
7245
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
7246
+ * </li>
7247
+ * <li>
7248
+ * <p>
7249
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
7250
+ * </li>
7251
+ * <li>
7252
+ * <p>
7253
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
7254
+ * </li>
7255
+ * <li>
7256
+ * <p>
7257
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
7258
+ * </li>
7259
+ * </ul>
6690
7260
  * @public
6691
7261
  */
6692
7262
  ClusterCreateTime?: string;
@@ -6794,9 +7364,31 @@ export interface AwsRedshiftClusterDetails {
6794
7364
  /**
6795
7365
  * <p>Indicates when the next snapshot is expected to be taken. The cluster must have a valid
6796
7366
  * snapshot schedule and have backups enabled.</p>
6797
- * <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
6798
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6799
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
7367
+ * <p>This field accepts only the specified formats. Timestamps
7368
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
7369
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
7370
+ * <ul>
7371
+ * <li>
7372
+ * <p>
7373
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
7374
+ * </li>
7375
+ * <li>
7376
+ * <p>
7377
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
7378
+ * </li>
7379
+ * <li>
7380
+ * <p>
7381
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
7382
+ * </li>
7383
+ * <li>
7384
+ * <p>
7385
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
7386
+ * </li>
7387
+ * <li>
7388
+ * <p>
7389
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
7390
+ * </li>
7391
+ * </ul>
6800
7392
  * @public
6801
7393
  */
6802
7394
  ExpectedNextSnapshotScheduleTime?: string;
@@ -6846,9 +7438,31 @@ export interface AwsRedshiftClusterDetails {
6846
7438
  MasterUsername?: string;
6847
7439
  /**
6848
7440
  * <p>Indicates the start of the next maintenance window.</p>
6849
- * <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
6850
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
6851
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
7441
+ * <p>This field accepts only the specified formats. Timestamps
7442
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
7443
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
7444
+ * <ul>
7445
+ * <li>
7446
+ * <p>
7447
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
7448
+ * </li>
7449
+ * <li>
7450
+ * <p>
7451
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
7452
+ * </li>
7453
+ * <li>
7454
+ * <p>
7455
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
7456
+ * </li>
7457
+ * <li>
7458
+ * <p>
7459
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
7460
+ * </li>
7461
+ * <li>
7462
+ * <p>
7463
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
7464
+ * </li>
7465
+ * </ul>
6852
7466
  * @public
6853
7467
  */
6854
7468
  NextMaintenanceWindowStartTime?: string;
@@ -7296,9 +7910,31 @@ export interface AwsS3BucketBucketLifecycleConfigurationRulesNoncurrentVersionTr
7296
7910
  export interface AwsS3BucketBucketLifecycleConfigurationRulesTransitionsDetails {
7297
7911
  /**
7298
7912
  * <p>A date on which to transition objects to the specified storage class. If you provide <code>Date</code>, you cannot provide <code>Days</code>.</p>
7299
- * <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
7300
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
7301
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
7913
+ * <p>This field accepts only the specified formats. Timestamps
7914
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
7915
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
7916
+ * <ul>
7917
+ * <li>
7918
+ * <p>
7919
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
7920
+ * </li>
7921
+ * <li>
7922
+ * <p>
7923
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
7924
+ * </li>
7925
+ * <li>
7926
+ * <p>
7927
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
7928
+ * </li>
7929
+ * <li>
7930
+ * <p>
7931
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
7932
+ * </li>
7933
+ * <li>
7934
+ * <p>
7935
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
7936
+ * </li>
7937
+ * </ul>
7302
7938
  * @public
7303
7939
  */
7304
7940
  Date?: string;
@@ -7353,9 +7989,31 @@ export interface AwsS3BucketBucketLifecycleConfigurationRulesDetails {
7353
7989
  AbortIncompleteMultipartUpload?: AwsS3BucketBucketLifecycleConfigurationRulesAbortIncompleteMultipartUploadDetails;
7354
7990
  /**
7355
7991
  * <p>The date when objects are moved or deleted.</p>
7356
- * <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
7357
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
7358
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
7992
+ * <p>This field accepts only the specified formats. Timestamps
7993
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
7994
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
7995
+ * <ul>
7996
+ * <li>
7997
+ * <p>
7998
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
7999
+ * </li>
8000
+ * <li>
8001
+ * <p>
8002
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
8003
+ * </li>
8004
+ * <li>
8005
+ * <p>
8006
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
8007
+ * </li>
8008
+ * <li>
8009
+ * <p>
8010
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
8011
+ * </li>
8012
+ * <li>
8013
+ * <p>
8014
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
8015
+ * </li>
8016
+ * </ul>
7359
8017
  * @public
7360
8018
  */
7361
8019
  ExpirationDate?: string;
@@ -7805,9 +8463,31 @@ export interface AwsS3BucketDetails {
7805
8463
  OwnerAccountId?: string;
7806
8464
  /**
7807
8465
  * <p>Indicates when the S3 bucket was created.</p>
7808
- * <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
7809
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
7810
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
8466
+ * <p>This field accepts only the specified formats. Timestamps
8467
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
8468
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
8469
+ * <ul>
8470
+ * <li>
8471
+ * <p>
8472
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
8473
+ * </li>
8474
+ * <li>
8475
+ * <p>
8476
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
8477
+ * </li>
8478
+ * <li>
8479
+ * <p>
8480
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
8481
+ * </li>
8482
+ * <li>
8483
+ * <p>
8484
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
8485
+ * </li>
8486
+ * <li>
8487
+ * <p>
8488
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
8489
+ * </li>
8490
+ * </ul>
7811
8491
  * @public
7812
8492
  */
7813
8493
  CreatedAt?: string;
@@ -7873,9 +8553,31 @@ export interface AwsS3BucketDetails {
7873
8553
  export interface AwsS3ObjectDetails {
7874
8554
  /**
7875
8555
  * <p>Indicates when the object was last modified.</p>
7876
- * <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
7877
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
7878
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
8556
+ * <p>This field accepts only the specified formats. Timestamps
8557
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
8558
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
8559
+ * <ul>
8560
+ * <li>
8561
+ * <p>
8562
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
8563
+ * </li>
8564
+ * <li>
8565
+ * <p>
8566
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
8567
+ * </li>
8568
+ * <li>
8569
+ * <p>
8570
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
8571
+ * </li>
8572
+ * <li>
8573
+ * <p>
8574
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
8575
+ * </li>
8576
+ * <li>
8577
+ * <p>
8578
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
8579
+ * </li>
8580
+ * </ul>
7879
8581
  * @public
7880
8582
  */
7881
8583
  LastModified?: string;
@@ -8590,10 +9292,32 @@ export interface Note {
8590
9292
  */
8591
9293
  UpdatedBy: string | undefined;
8592
9294
  /**
8593
- * <p>The timestamp of when the note was updated.</p>
8594
- * <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
8595
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
8596
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
9295
+ * <p>A timestamp that indicates when the note was updated.</p>
9296
+ * <p>This field accepts only the specified formats. Timestamps
9297
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
9298
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
9299
+ * <ul>
9300
+ * <li>
9301
+ * <p>
9302
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
9303
+ * </li>
9304
+ * <li>
9305
+ * <p>
9306
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
9307
+ * </li>
9308
+ * <li>
9309
+ * <p>
9310
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
9311
+ * </li>
9312
+ * <li>
9313
+ * <p>
9314
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
9315
+ * </li>
9316
+ * <li>
9317
+ * <p>
9318
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
9319
+ * </li>
9320
+ * </ul>
8597
9321
  * @public
8598
9322
  */
8599
9323
  UpdatedAt: string | undefined;
@@ -8646,17 +9370,61 @@ export interface PatchSummary {
8646
9370
  InstalledPendingReboot?: number;
8647
9371
  /**
8648
9372
  * <p>Indicates when the operation started.</p>
8649
- * <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
8650
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
8651
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
9373
+ * <p>This field accepts only the specified formats. Timestamps
9374
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
9375
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
9376
+ * <ul>
9377
+ * <li>
9378
+ * <p>
9379
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
9380
+ * </li>
9381
+ * <li>
9382
+ * <p>
9383
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
9384
+ * </li>
9385
+ * <li>
9386
+ * <p>
9387
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
9388
+ * </li>
9389
+ * <li>
9390
+ * <p>
9391
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
9392
+ * </li>
9393
+ * <li>
9394
+ * <p>
9395
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
9396
+ * </li>
9397
+ * </ul>
8652
9398
  * @public
8653
9399
  */
8654
9400
  OperationStartTime?: string;
8655
9401
  /**
8656
9402
  * <p>Indicates when the operation completed.</p>
8657
- * <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
8658
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
8659
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
9403
+ * <p>This field accepts only the specified formats. Timestamps
9404
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
9405
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
9406
+ * <ul>
9407
+ * <li>
9408
+ * <p>
9409
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
9410
+ * </li>
9411
+ * <li>
9412
+ * <p>
9413
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
9414
+ * </li>
9415
+ * <li>
9416
+ * <p>
9417
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
9418
+ * </li>
9419
+ * <li>
9420
+ * <p>
9421
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
9422
+ * </li>
9423
+ * <li>
9424
+ * <p>
9425
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
9426
+ * </li>
9427
+ * </ul>
8660
9428
  * @public
8661
9429
  */
8662
9430
  OperationEndTime?: string;
@@ -8699,17 +9467,61 @@ export interface ProcessDetails {
8699
9467
  ParentPid?: number;
8700
9468
  /**
8701
9469
  * <p>Indicates when the process was launched.</p>
8702
- * <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
8703
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
8704
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
9470
+ * <p>This field accepts only the specified formats. Timestamps
9471
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
9472
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
9473
+ * <ul>
9474
+ * <li>
9475
+ * <p>
9476
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
9477
+ * </li>
9478
+ * <li>
9479
+ * <p>
9480
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
9481
+ * </li>
9482
+ * <li>
9483
+ * <p>
9484
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
9485
+ * </li>
9486
+ * <li>
9487
+ * <p>
9488
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
9489
+ * </li>
9490
+ * <li>
9491
+ * <p>
9492
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
9493
+ * </li>
9494
+ * </ul>
8705
9495
  * @public
8706
9496
  */
8707
9497
  LaunchedAt?: string;
8708
9498
  /**
8709
9499
  * <p>Indicates when the process was terminated.</p>
8710
- * <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
8711
- * Date/Time Format</a>. The value cannot contain spaces, and date and time should be separated by <code>T</code>. For example,
8712
- * <code>2020-03-22T13:22:13.933Z</code>.</p>
9500
+ * <p>This field accepts only the specified formats. Timestamps
9501
+ * can end with <code>Z</code> or <code>("+" / "-") time-hour [":" time-minute]</code>. The time-secfrac after seconds is limited
9502
+ * to a maximum of 9 digits. The offset is bounded by +/-18:00. Here are valid timestamp formats with examples:</p>
9503
+ * <ul>
9504
+ * <li>
9505
+ * <p>
9506
+ * <code>YYYY-MM-DDTHH:MM:SSZ</code> (for example, <code>2019-01-31T23:00:00Z</code>)</p>
9507
+ * </li>
9508
+ * <li>
9509
+ * <p>
9510
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ</code> (for example, <code>2019-01-31T23:00:00.123456789Z</code>)</p>
9511
+ * </li>
9512
+ * <li>
9513
+ * <p>
9514
+ * <code>YYYY-MM-DDTHH:MM:SS+HH:MM</code> (for example, <code>2024-01-04T15:25:10+17:59</code>)</p>
9515
+ * </li>
9516
+ * <li>
9517
+ * <p>
9518
+ * <code>YYYY-MM-DDTHH:MM:SS-HHMM</code> (for example, <code>2024-01-04T15:25:10-1759</code>)</p>
9519
+ * </li>
9520
+ * <li>
9521
+ * <p>
9522
+ * <code>YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM</code> (for example, <code>2024-01-04T15:25:10.123456789+17:59</code>)</p>
9523
+ * </li>
9524
+ * </ul>
8713
9525
  * @public
8714
9526
  */
8715
9527
  TerminatedAt?: string;