aws-sdk-securityhub 1.102.0 → 1.103.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.
@@ -505,25 +505,49 @@ module Aws::SecurityHub
505
505
  # @!attribute [rw] created_at
506
506
  # A timestamp that indicates when the rule was created.
507
507
  #
508
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
509
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
510
- # example, `2020-03-22T13:22:13.933Z`.
508
+ # This field accepts only the specified formats. Timestamps can end
509
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
510
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
511
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
512
+ # examples:
511
513
  #
514
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
512
515
  #
516
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
517
+ # `2019-01-31T23:00:00.123456789Z`)
513
518
  #
514
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
519
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
520
+ # `2024-01-04T15:25:10+17:59`)
521
+ #
522
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
523
+ # `2024-01-04T15:25:10-1759`)
524
+ #
525
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
526
+ # `2024-01-04T15:25:10.123456789+17:59`)
515
527
  # @return [Time]
516
528
  #
517
529
  # @!attribute [rw] updated_at
518
530
  # A timestamp that indicates when the rule was most recently updated.
519
531
  #
520
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
521
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
522
- # example, `2020-03-22T13:22:13.933Z`.
532
+ # This field accepts only the specified formats. Timestamps can end
533
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
534
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
535
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
536
+ # examples:
537
+ #
538
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
539
+ #
540
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
541
+ # `2019-01-31T23:00:00.123456789Z`)
523
542
  #
543
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
544
+ # `2024-01-04T15:25:10+17:59`)
524
545
  #
546
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
547
+ # `2024-01-04T15:25:10-1759`)
525
548
  #
526
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
549
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
550
+ # `2024-01-04T15:25:10.123456789+17:59`)
527
551
  # @return [Time]
528
552
  #
529
553
  # @!attribute [rw] created_by
@@ -651,15 +675,27 @@ module Aws::SecurityHub
651
675
  # captured by a finding was first observed by the security findings
652
676
  # product.
653
677
  #
654
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
655
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
656
- # example, `2020-03-22T13:22:13.933Z`.
678
+ # This field accepts only the specified formats. Timestamps can end
679
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
680
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
681
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
682
+ # examples:
657
683
  #
658
- # Array Members: Minimum number of 1 item. Maximum number of 20 items.
684
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
685
+ #
686
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
687
+ # `2019-01-31T23:00:00.123456789Z`)
688
+ #
689
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
690
+ # `2024-01-04T15:25:10+17:59`)
659
691
  #
692
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
693
+ # `2024-01-04T15:25:10-1759`)
660
694
  #
695
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
696
+ # `2024-01-04T15:25:10.123456789+17:59`)
661
697
  #
662
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
698
+ # Array Members: Minimum number of 1 item. Maximum number of 20 items.
663
699
  # @return [Array<Types::DateFilter>]
664
700
  #
665
701
  # @!attribute [rw] last_observed_at
@@ -667,44 +703,80 @@ module Aws::SecurityHub
667
703
  # captured by a finding was most recently observed by the security
668
704
  # findings product.
669
705
  #
670
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
671
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
672
- # example, `2020-03-22T13:22:13.933Z`.
706
+ # This field accepts only the specified formats. Timestamps can end
707
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
708
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
709
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
710
+ # examples:
673
711
  #
674
- # Array Members: Minimum number of 1 item. Maximum number of 20 items.
712
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
713
+ #
714
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
715
+ # `2019-01-31T23:00:00.123456789Z`)
716
+ #
717
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
718
+ # `2024-01-04T15:25:10+17:59`)
675
719
  #
720
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
721
+ # `2024-01-04T15:25:10-1759`)
676
722
  #
723
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
724
+ # `2024-01-04T15:25:10.123456789+17:59`)
677
725
  #
678
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
726
+ # Array Members: Minimum number of 1 item. Maximum number of 20 items.
679
727
  # @return [Array<Types::DateFilter>]
680
728
  #
681
729
  # @!attribute [rw] created_at
682
730
  # A timestamp that indicates when this finding record was created.
683
731
  #
684
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
685
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
686
- # example, `2020-03-22T13:22:13.933Z`.
732
+ # This field accepts only the specified formats. Timestamps can end
733
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
734
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
735
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
736
+ # examples:
687
737
  #
688
- # Array Members: Minimum number of 1 item. Maximum number of 20 items.
738
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
739
+ #
740
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
741
+ # `2019-01-31T23:00:00.123456789Z`)
689
742
  #
743
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
744
+ # `2024-01-04T15:25:10+17:59`)
690
745
  #
746
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
747
+ # `2024-01-04T15:25:10-1759`)
691
748
  #
692
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
749
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
750
+ # `2024-01-04T15:25:10.123456789+17:59`)
751
+ #
752
+ # Array Members: Minimum number of 1 item. Maximum number of 20 items.
693
753
  # @return [Array<Types::DateFilter>]
694
754
  #
695
755
  # @!attribute [rw] updated_at
696
756
  # A timestamp that indicates when the finding record was most recently
697
757
  # updated.
698
758
  #
699
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
700
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
701
- # example, `2020-03-22T13:22:13.933Z`.
759
+ # This field accepts only the specified formats. Timestamps can end
760
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
761
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
762
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
763
+ # examples:
702
764
  #
703
- # Array Members: Minimum number of 1 item. Maximum number of 20 items.
765
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
766
+ #
767
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
768
+ # `2019-01-31T23:00:00.123456789Z`)
704
769
  #
770
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
771
+ # `2024-01-04T15:25:10+17:59`)
705
772
  #
773
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
774
+ # `2024-01-04T15:25:10-1759`)
706
775
  #
707
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
776
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
777
+ # `2024-01-04T15:25:10.123456789+17:59`)
778
+ #
779
+ # Array Members: Minimum number of 1 item. Maximum number of 20 items.
708
780
  # @return [Array<Types::DateFilter>]
709
781
  #
710
782
  # @!attribute [rw] confidence
@@ -891,16 +963,29 @@ module Aws::SecurityHub
891
963
  # @return [Array<Types::StringFilter>]
892
964
  #
893
965
  # @!attribute [rw] note_updated_at
894
- # The timestamp of when the note was updated. Uses the date-time
895
- # format specified in [RFC 3339 section 5.6, Internet Date/Time
896
- # Format][1]. The value cannot contain spaces. For example,
897
- # `2020-03-22T13:22:13.933Z`.
966
+ # The timestamp of when the note was updated.
898
967
  #
899
- # Array Members: Minimum number of 1 item. Maximum number of 20 items.
968
+ # This field accepts only the specified formats. Timestamps can end
969
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
970
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
971
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
972
+ # examples:
973
+ #
974
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
975
+ #
976
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
977
+ # `2019-01-31T23:00:00.123456789Z`)
978
+ #
979
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
980
+ # `2024-01-04T15:25:10+17:59`)
900
981
  #
982
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
983
+ # `2024-01-04T15:25:10-1759`)
901
984
  #
985
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
986
+ # `2024-01-04T15:25:10.123456789+17:59`)
902
987
  #
903
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
988
+ # Array Members: Minimum number of 1 item. Maximum number of 20 items.
904
989
  # @return [Array<Types::DateFilter>]
905
990
  #
906
991
  # @!attribute [rw] note_updated_by
@@ -1027,25 +1112,49 @@ module Aws::SecurityHub
1027
1112
  # @!attribute [rw] created_at
1028
1113
  # A timestamp that indicates when the rule was created.
1029
1114
  #
1030
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
1031
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
1032
- # example, `2020-03-22T13:22:13.933Z`.
1115
+ # This field accepts only the specified formats. Timestamps can end
1116
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
1117
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
1118
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
1119
+ # examples:
1120
+ #
1121
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
1122
+ #
1123
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
1124
+ # `2019-01-31T23:00:00.123456789Z`)
1033
1125
  #
1126
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
1127
+ # `2024-01-04T15:25:10+17:59`)
1034
1128
  #
1129
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
1130
+ # `2024-01-04T15:25:10-1759`)
1035
1131
  #
1036
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
1132
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
1133
+ # `2024-01-04T15:25:10.123456789+17:59`)
1037
1134
  # @return [Time]
1038
1135
  #
1039
1136
  # @!attribute [rw] updated_at
1040
1137
  # A timestamp that indicates when the rule was most recently updated.
1041
1138
  #
1042
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
1043
- # Internet Date/Time Format][1]. The value cannot contain spaces. For
1044
- # example, `2020-03-22T13:22:13.933Z`.
1139
+ # This field accepts only the specified formats. Timestamps can end
1140
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
1141
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
1142
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
1143
+ # examples:
1045
1144
  #
1145
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
1046
1146
  #
1147
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
1148
+ # `2019-01-31T23:00:00.123456789Z`)
1047
1149
  #
1048
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
1150
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
1151
+ # `2024-01-04T15:25:10+17:59`)
1152
+ #
1153
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
1154
+ # `2024-01-04T15:25:10-1759`)
1155
+ #
1156
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
1157
+ # `2024-01-04T15:25:10.123456789+17:59`)
1049
1158
  # @return [Time]
1050
1159
  #
1051
1160
  # @!attribute [rw] created_by
@@ -1433,31 +1542,52 @@ module Aws::SecurityHub
1433
1542
  # @return [Hash<String,String>]
1434
1543
  #
1435
1544
  # @!attribute [rw] first_seen
1436
- # An ISO8601-formatted timestamp that indicates when the API call was
1437
- # first observed.
1545
+ # A timestamp that indicates when the API call was first observed.
1546
+ #
1547
+ # This field accepts only the specified formats. Timestamps can end
1548
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
1549
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
1550
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
1551
+ # examples:
1552
+ #
1553
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
1438
1554
  #
1439
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
1440
- # value cannot contain spaces, and date and time should be separated
1441
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
1442
- # Date/Time Format][1].
1555
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
1556
+ # `2019-01-31T23:00:00.123456789Z`)
1443
1557
  #
1558
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
1559
+ # `2024-01-04T15:25:10+17:59`)
1444
1560
  #
1561
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
1562
+ # `2024-01-04T15:25:10-1759`)
1445
1563
  #
1446
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
1564
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
1565
+ # `2024-01-04T15:25:10.123456789+17:59`)
1447
1566
  # @return [String]
1448
1567
  #
1449
1568
  # @!attribute [rw] last_seen
1450
- # An ISO8601-formatted timestamp that indicates when the API call was
1451
- # most recently observed.
1569
+ # A timestamp that indicates when the API call was most recently
1570
+ # observed.
1452
1571
  #
1453
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
1454
- # value cannot contain spaces, and date and time should be separated
1455
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
1456
- # Date/Time Format][1].
1572
+ # This field accepts only the specified formats. Timestamps can end
1573
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
1574
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
1575
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
1576
+ # examples:
1457
1577
  #
1578
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
1458
1579
  #
1580
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
1581
+ # `2019-01-31T23:00:00.123456789Z`)
1459
1582
  #
1460
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
1583
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
1584
+ # `2024-01-04T15:25:10+17:59`)
1585
+ #
1586
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
1587
+ # `2024-01-04T15:25:10-1759`)
1588
+ #
1589
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
1590
+ # `2024-01-04T15:25:10.123456789+17:59`)
1461
1591
  # @return [String]
1462
1592
  #
1463
1593
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsApiCallAction AWS API Documentation
@@ -1680,14 +1810,25 @@ module Aws::SecurityHub
1680
1810
  # @!attribute [rw] created_date
1681
1811
  # Indicates when the API was created.
1682
1812
  #
1683
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
1684
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
1685
- # date and time should be separated by `T`. For example,
1686
- # `2020-03-22T13:22:13.933Z`.
1813
+ # This field accepts only the specified formats. Timestamps can end
1814
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
1815
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
1816
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
1817
+ # examples:
1818
+ #
1819
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
1687
1820
  #
1821
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
1822
+ # `2019-01-31T23:00:00.123456789Z`)
1688
1823
  #
1824
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
1825
+ # `2024-01-04T15:25:10+17:59`)
1689
1826
  #
1690
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
1827
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
1828
+ # `2024-01-04T15:25:10-1759`)
1829
+ #
1830
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
1831
+ # `2024-01-04T15:25:10.123456789+17:59`)
1691
1832
  # @return [String]
1692
1833
  #
1693
1834
  # @!attribute [rw] version
@@ -1807,27 +1948,49 @@ module Aws::SecurityHub
1807
1948
  # @!attribute [rw] created_date
1808
1949
  # Indicates when the stage was created.
1809
1950
  #
1810
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
1811
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
1812
- # date and time should be separated by `T`. For example,
1813
- # `2020-03-22T13:22:13.933Z`.
1951
+ # This field accepts only the specified formats. Timestamps can end
1952
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
1953
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
1954
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
1955
+ # examples:
1956
+ #
1957
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
1814
1958
  #
1959
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
1960
+ # `2019-01-31T23:00:00.123456789Z`)
1815
1961
  #
1962
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
1963
+ # `2024-01-04T15:25:10+17:59`)
1816
1964
  #
1817
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
1965
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
1966
+ # `2024-01-04T15:25:10-1759`)
1967
+ #
1968
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
1969
+ # `2024-01-04T15:25:10.123456789+17:59`)
1818
1970
  # @return [String]
1819
1971
  #
1820
1972
  # @!attribute [rw] last_updated_date
1821
1973
  # Indicates when the stage was most recently updated.
1822
1974
  #
1823
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
1824
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
1825
- # date and time should be separated by `T`. For example,
1826
- # `2020-03-22T13:22:13.933Z`.
1975
+ # This field accepts only the specified formats. Timestamps can end
1976
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
1977
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
1978
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
1979
+ # examples:
1980
+ #
1981
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
1827
1982
  #
1983
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
1984
+ # `2019-01-31T23:00:00.123456789Z`)
1828
1985
  #
1986
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
1987
+ # `2024-01-04T15:25:10+17:59`)
1829
1988
  #
1830
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
1989
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
1990
+ # `2024-01-04T15:25:10-1759`)
1991
+ #
1992
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
1993
+ # `2024-01-04T15:25:10.123456789+17:59`)
1831
1994
  # @return [String]
1832
1995
  #
1833
1996
  # @!attribute [rw] web_acl_arn
@@ -1879,14 +2042,25 @@ module Aws::SecurityHub
1879
2042
  # @!attribute [rw] created_date
1880
2043
  # Indicates when the API was created.
1881
2044
  #
1882
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
1883
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
1884
- # date and time should be separated by `T`. For example,
1885
- # `2020-03-22T13:22:13.933Z`.
2045
+ # This field accepts only the specified formats. Timestamps can end
2046
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
2047
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
2048
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
2049
+ # examples:
2050
+ #
2051
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
2052
+ #
2053
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
2054
+ # `2019-01-31T23:00:00.123456789Z`)
1886
2055
  #
2056
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
2057
+ # `2024-01-04T15:25:10+17:59`)
1887
2058
  #
2059
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
2060
+ # `2024-01-04T15:25:10-1759`)
1888
2061
  #
1889
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
2062
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
2063
+ # `2024-01-04T15:25:10.123456789+17:59`)
1890
2064
  # @return [String]
1891
2065
  #
1892
2066
  # @!attribute [rw] description
@@ -1993,14 +2167,25 @@ module Aws::SecurityHub
1993
2167
  # @!attribute [rw] created_date
1994
2168
  # Indicates when the stage was created.
1995
2169
  #
1996
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
1997
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
1998
- # date and time should be separated by `T`. For example,
1999
- # `2020-03-22T13:22:13.933Z`.
2170
+ # This field accepts only the specified formats. Timestamps can end
2171
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
2172
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
2173
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
2174
+ # examples:
2000
2175
  #
2176
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
2001
2177
  #
2178
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
2179
+ # `2019-01-31T23:00:00.123456789Z`)
2002
2180
  #
2003
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
2181
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
2182
+ # `2024-01-04T15:25:10+17:59`)
2183
+ #
2184
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
2185
+ # `2024-01-04T15:25:10-1759`)
2186
+ #
2187
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
2188
+ # `2024-01-04T15:25:10.123456789+17:59`)
2004
2189
  # @return [String]
2005
2190
  #
2006
2191
  # @!attribute [rw] description
@@ -2018,14 +2203,25 @@ module Aws::SecurityHub
2018
2203
  # @!attribute [rw] last_updated_date
2019
2204
  # Indicates when the stage was most recently updated.
2020
2205
  #
2021
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
2022
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
2023
- # date and time should be separated by `T`. For example,
2024
- # `2020-03-22T13:22:13.933Z`.
2206
+ # This field accepts only the specified formats. Timestamps can end
2207
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
2208
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
2209
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
2210
+ # examples:
2211
+ #
2212
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
2213
+ #
2214
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
2215
+ # `2019-01-31T23:00:00.123456789Z`)
2025
2216
  #
2217
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
2218
+ # `2024-01-04T15:25:10+17:59`)
2026
2219
  #
2220
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
2221
+ # `2024-01-04T15:25:10-1759`)
2027
2222
  #
2028
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
2223
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
2224
+ # `2024-01-04T15:25:10.123456789+17:59`)
2029
2225
  # @return [String]
2030
2226
  #
2031
2227
  # @!attribute [rw] route_settings
@@ -2460,14 +2656,25 @@ module Aws::SecurityHub
2460
2656
  # @!attribute [rw] created_time
2461
2657
  # Indicates when the auto scaling group was created.
2462
2658
  #
2463
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
2464
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
2465
- # date and time should be separated by `T`. For example,
2466
- # `2020-03-22T13:22:13.933Z`.
2659
+ # This field accepts only the specified formats. Timestamps can end
2660
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
2661
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
2662
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
2663
+ # examples:
2467
2664
  #
2665
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
2468
2666
  #
2667
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
2668
+ # `2019-01-31T23:00:00.123456789Z`)
2469
2669
  #
2470
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
2670
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
2671
+ # `2024-01-04T15:25:10+17:59`)
2672
+ #
2673
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
2674
+ # `2024-01-04T15:25:10-1759`)
2675
+ #
2676
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
2677
+ # `2024-01-04T15:25:10.123456789+17:59`)
2471
2678
  # @return [String]
2472
2679
  #
2473
2680
  # @!attribute [rw] mixed_instances_policy
@@ -2803,14 +3010,25 @@ module Aws::SecurityHub
2803
3010
  # @!attribute [rw] created_time
2804
3011
  # The creation date and time for the launch configuration.
2805
3012
  #
2806
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
2807
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
2808
- # date and time should be separated by `T`. For example,
2809
- # `2020-03-22T13:22:13.933Z`.
3013
+ # This field accepts only the specified formats. Timestamps can end
3014
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
3015
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
3016
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
3017
+ # examples:
3018
+ #
3019
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
2810
3020
  #
3021
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
3022
+ # `2019-01-31T23:00:00.123456789Z`)
2811
3023
  #
3024
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
3025
+ # `2024-01-04T15:25:10+17:59`)
2812
3026
  #
2813
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
3027
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
3028
+ # `2024-01-04T15:25:10-1759`)
3029
+ #
3030
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
3031
+ # `2024-01-04T15:25:10.123456789+17:59`)
2814
3032
  # @return [String]
2815
3033
  #
2816
3034
  # @!attribute [rw] ebs_optimized
@@ -3476,14 +3694,25 @@ module Aws::SecurityHub
3476
3694
  # @!attribute [rw] created_at
3477
3695
  # Indicates when the certificate was requested.
3478
3696
  #
3479
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
3480
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
3481
- # date and time should be separated by `T`. For example,
3482
- # `2020-03-22T13:22:13.933Z`.
3697
+ # This field accepts only the specified formats. Timestamps can end
3698
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
3699
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
3700
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
3701
+ # examples:
3702
+ #
3703
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
3704
+ #
3705
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
3706
+ # `2019-01-31T23:00:00.123456789Z`)
3483
3707
  #
3708
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
3709
+ # `2024-01-04T15:25:10+17:59`)
3484
3710
  #
3711
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
3712
+ # `2024-01-04T15:25:10-1759`)
3485
3713
  #
3486
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
3714
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
3715
+ # `2024-01-04T15:25:10.123456789+17:59`)
3487
3716
  # @return [String]
3488
3717
  #
3489
3718
  # @!attribute [rw] domain_name
@@ -3521,14 +3750,25 @@ module Aws::SecurityHub
3521
3750
  # Indicates when the certificate was imported. Provided if the
3522
3751
  # certificate type is `IMPORTED`.
3523
3752
  #
3524
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
3525
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
3526
- # date and time should be separated by `T`. For example,
3527
- # `2020-03-22T13:22:13.933Z`.
3753
+ # This field accepts only the specified formats. Timestamps can end
3754
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
3755
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
3756
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
3757
+ # examples:
3528
3758
  #
3759
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
3529
3760
  #
3761
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
3762
+ # `2019-01-31T23:00:00.123456789Z`)
3530
3763
  #
3531
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
3764
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
3765
+ # `2024-01-04T15:25:10+17:59`)
3766
+ #
3767
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
3768
+ # `2024-01-04T15:25:10-1759`)
3769
+ #
3770
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
3771
+ # `2024-01-04T15:25:10.123456789+17:59`)
3532
3772
  # @return [String]
3533
3773
  #
3534
3774
  # @!attribute [rw] in_use_by
@@ -3540,14 +3780,25 @@ module Aws::SecurityHub
3540
3780
  # Indicates when the certificate was issued. Provided if the
3541
3781
  # certificate type is `AMAZON_ISSUED`.
3542
3782
  #
3543
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
3544
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
3545
- # date and time should be separated by `T`. For example,
3546
- # `2020-03-22T13:22:13.933Z`.
3783
+ # This field accepts only the specified formats. Timestamps can end
3784
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
3785
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
3786
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
3787
+ # examples:
3788
+ #
3789
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
3547
3790
  #
3791
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
3792
+ # `2019-01-31T23:00:00.123456789Z`)
3548
3793
  #
3794
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
3795
+ # `2024-01-04T15:25:10+17:59`)
3549
3796
  #
3550
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
3797
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
3798
+ # `2024-01-04T15:25:10-1759`)
3799
+ #
3800
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
3801
+ # `2024-01-04T15:25:10.123456789+17:59`)
3551
3802
  # @return [String]
3552
3803
  #
3553
3804
  # @!attribute [rw] issuer
@@ -3569,27 +3820,49 @@ module Aws::SecurityHub
3569
3820
  # @!attribute [rw] not_after
3570
3821
  # The time after which the certificate becomes invalid.
3571
3822
  #
3572
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
3573
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
3574
- # date and time should be separated by `T`. For example,
3575
- # `2020-03-22T13:22:13.933Z`.
3823
+ # This field accepts only the specified formats. Timestamps can end
3824
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
3825
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
3826
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
3827
+ # examples:
3828
+ #
3829
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
3576
3830
  #
3831
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
3832
+ # `2019-01-31T23:00:00.123456789Z`)
3577
3833
  #
3834
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
3835
+ # `2024-01-04T15:25:10+17:59`)
3578
3836
  #
3579
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
3837
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
3838
+ # `2024-01-04T15:25:10-1759`)
3839
+ #
3840
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
3841
+ # `2024-01-04T15:25:10.123456789+17:59`)
3580
3842
  # @return [String]
3581
3843
  #
3582
3844
  # @!attribute [rw] not_before
3583
3845
  # The time before which the certificate is not valid.
3584
3846
  #
3585
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
3586
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
3587
- # date and time should be separated by `T`. For example,
3588
- # `2020-03-22T13:22:13.933Z`.
3847
+ # This field accepts only the specified formats. Timestamps can end
3848
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
3849
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
3850
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
3851
+ # examples:
3852
+ #
3853
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
3589
3854
  #
3855
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
3856
+ # `2019-01-31T23:00:00.123456789Z`)
3590
3857
  #
3858
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
3859
+ # `2024-01-04T15:25:10+17:59`)
3591
3860
  #
3592
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
3861
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
3862
+ # `2024-01-04T15:25:10-1759`)
3863
+ #
3864
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
3865
+ # `2024-01-04T15:25:10.123456789+17:59`)
3593
3866
  # @return [String]
3594
3867
  #
3595
3868
  # @!attribute [rw] options
@@ -3812,14 +4085,25 @@ module Aws::SecurityHub
3812
4085
  # @!attribute [rw] updated_at
3813
4086
  # Indicates when the renewal summary was last updated.
3814
4087
  #
3815
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
3816
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
3817
- # date and time should be separated by `T`. For example,
3818
- # `2020-03-22T13:22:13.933Z`.
4088
+ # This field accepts only the specified formats. Timestamps can end
4089
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
4090
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
4091
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
4092
+ # examples:
4093
+ #
4094
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
4095
+ #
4096
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
4097
+ # `2019-01-31T23:00:00.123456789Z`)
3819
4098
  #
4099
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
4100
+ # `2024-01-04T15:25:10+17:59`)
3820
4101
  #
4102
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
4103
+ # `2024-01-04T15:25:10-1759`)
3821
4104
  #
3822
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
4105
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
4106
+ # `2024-01-04T15:25:10.123456789+17:59`)
3823
4107
  # @return [String]
3824
4108
  #
3825
4109
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsCertificateManagerCertificateRenewalSummary AWS API Documentation
@@ -4081,14 +4365,25 @@ module Aws::SecurityHub
4081
4365
  # @!attribute [rw] last_modified_time
4082
4366
  # Indicates when that the distribution was last modified.
4083
4367
  #
4084
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
4085
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
4086
- # date and time should be separated by `T`. For example,
4087
- # `2020-03-22T13:22:13.933Z`.
4368
+ # This field accepts only the specified formats. Timestamps can end
4369
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
4370
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
4371
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
4372
+ # examples:
4088
4373
  #
4374
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
4089
4375
  #
4376
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
4377
+ # `2019-01-31T23:00:00.123456789Z`)
4090
4378
  #
4091
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
4379
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
4380
+ # `2024-01-04T15:25:10+17:59`)
4381
+ #
4382
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
4383
+ # `2024-01-04T15:25:10-1759`)
4384
+ #
4385
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
4386
+ # `2024-01-04T15:25:10.123456789+17:59`)
4092
4387
  # @return [String]
4093
4388
  #
4094
4389
  # @!attribute [rw] logging
@@ -5479,14 +5774,25 @@ module Aws::SecurityHub
5479
5774
  # If the billing mode is `PAY_PER_REQUEST`, indicates when the billing
5480
5775
  # mode was set to that value.
5481
5776
  #
5482
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
5483
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
5484
- # date and time should be separated by `T`. For example,
5485
- # `2020-03-22T13:22:13.933Z`.
5777
+ # This field accepts only the specified formats. Timestamps can end
5778
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
5779
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
5780
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
5781
+ # examples:
5782
+ #
5783
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
5784
+ #
5785
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
5786
+ # `2019-01-31T23:00:00.123456789Z`)
5486
5787
  #
5788
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
5789
+ # `2024-01-04T15:25:10+17:59`)
5487
5790
  #
5791
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
5792
+ # `2024-01-04T15:25:10-1759`)
5488
5793
  #
5489
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
5794
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
5795
+ # `2024-01-04T15:25:10.123456789+17:59`)
5490
5796
  # @return [String]
5491
5797
  #
5492
5798
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsDynamoDbTableBillingModeSummary AWS API Documentation
@@ -5511,14 +5817,25 @@ module Aws::SecurityHub
5511
5817
  # @!attribute [rw] creation_date_time
5512
5818
  # Indicates when the table was created.
5513
5819
  #
5514
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
5515
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
5516
- # date and time should be separated by `T`. For example,
5517
- # `2020-03-22T13:22:13.933Z`.
5820
+ # This field accepts only the specified formats. Timestamps can end
5821
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
5822
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
5823
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
5824
+ # examples:
5518
5825
  #
5826
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
5519
5827
  #
5828
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
5829
+ # `2019-01-31T23:00:00.123456789Z`)
5520
5830
  #
5521
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
5831
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
5832
+ # `2024-01-04T15:25:10+17:59`)
5833
+ #
5834
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
5835
+ # `2024-01-04T15:25:10-1759`)
5836
+ #
5837
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
5838
+ # `2024-01-04T15:25:10.123456789+17:59`)
5522
5839
  # @return [String]
5523
5840
  #
5524
5841
  # @!attribute [rw] global_secondary_indexes
@@ -5781,27 +6098,49 @@ module Aws::SecurityHub
5781
6098
  # @!attribute [rw] last_decrease_date_time
5782
6099
  # Indicates when the provisioned throughput was last decreased.
5783
6100
  #
5784
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
5785
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
5786
- # date and time should be separated by `T`. For example,
5787
- # `2020-03-22T13:22:13.933Z`.
6101
+ # This field accepts only the specified formats. Timestamps can end
6102
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
6103
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
6104
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
6105
+ # examples:
6106
+ #
6107
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
5788
6108
  #
6109
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
6110
+ # `2019-01-31T23:00:00.123456789Z`)
5789
6111
  #
6112
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
6113
+ # `2024-01-04T15:25:10+17:59`)
5790
6114
  #
5791
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
6115
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
6116
+ # `2024-01-04T15:25:10-1759`)
6117
+ #
6118
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
6119
+ # `2024-01-04T15:25:10.123456789+17:59`)
5792
6120
  # @return [String]
5793
6121
  #
5794
6122
  # @!attribute [rw] last_increase_date_time
5795
6123
  # Indicates when the provisioned throughput was last increased.
5796
6124
  #
5797
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
5798
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
5799
- # date and time should be separated by `T`. For example,
5800
- # `2020-03-22T13:22:13.933Z`.
6125
+ # This field accepts only the specified formats. Timestamps can end
6126
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
6127
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
6128
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
6129
+ # examples:
6130
+ #
6131
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
5801
6132
  #
6133
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
6134
+ # `2019-01-31T23:00:00.123456789Z`)
5802
6135
  #
6136
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
6137
+ # `2024-01-04T15:25:10+17:59`)
5803
6138
  #
5804
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
6139
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
6140
+ # `2024-01-04T15:25:10-1759`)
6141
+ #
6142
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
6143
+ # `2024-01-04T15:25:10.123456789+17:59`)
5805
6144
  # @return [String]
5806
6145
  #
5807
6146
  # @!attribute [rw] number_of_decreases_today
@@ -5929,14 +6268,25 @@ module Aws::SecurityHub
5929
6268
  # @!attribute [rw] restore_date_time
5930
6269
  # Indicates the point in time that the table was restored to.
5931
6270
  #
5932
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
5933
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
5934
- # date and time should be separated by `T`. For example,
5935
- # `2020-03-22T13:22:13.933Z`.
6271
+ # This field accepts only the specified formats. Timestamps can end
6272
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
6273
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
6274
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
6275
+ # examples:
6276
+ #
6277
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
5936
6278
  #
6279
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
6280
+ # `2019-01-31T23:00:00.123456789Z`)
5937
6281
  #
6282
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
6283
+ # `2024-01-04T15:25:10+17:59`)
5938
6284
  #
5939
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
6285
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
6286
+ # `2024-01-04T15:25:10-1759`)
6287
+ #
6288
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
6289
+ # `2024-01-04T15:25:10.123456789+17:59`)
5940
6290
  # @return [String]
5941
6291
  #
5942
6292
  # @!attribute [rw] restore_in_progress
@@ -5960,14 +6310,25 @@ module Aws::SecurityHub
5960
6310
  # If the key is inaccessible, the date and time when DynamoDB detected
5961
6311
  # that the key was inaccessible.
5962
6312
  #
5963
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
5964
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
5965
- # date and time should be separated by `T`. For example,
5966
- # `2020-03-22T13:22:13.933Z`.
6313
+ # This field accepts only the specified formats. Timestamps can end
6314
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
6315
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
6316
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
6317
+ # examples:
6318
+ #
6319
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
6320
+ #
6321
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
6322
+ # `2019-01-31T23:00:00.123456789Z`)
5967
6323
  #
6324
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
6325
+ # `2024-01-04T15:25:10+17:59`)
5968
6326
  #
6327
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
6328
+ # `2024-01-04T15:25:10-1759`)
5969
6329
  #
5970
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
6330
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
6331
+ # `2024-01-04T15:25:10.123456789+17:59`)
5971
6332
  # @return [String]
5972
6333
  #
5973
6334
  # @!attribute [rw] status
@@ -6392,14 +6753,25 @@ module Aws::SecurityHub
6392
6753
  # @!attribute [rw] launched_at
6393
6754
  # Indicates when the instance was launched.
6394
6755
  #
6395
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
6396
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
6397
- # date and time should be separated by `T`. For example,
6398
- # `2020-03-22T13:22:13.933Z`.
6756
+ # This field accepts only the specified formats. Timestamps can end
6757
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
6758
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
6759
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
6760
+ # examples:
6399
6761
  #
6762
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
6400
6763
  #
6764
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
6765
+ # `2019-01-31T23:00:00.123456789Z`)
6401
6766
  #
6402
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
6767
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
6768
+ # `2024-01-04T15:25:10+17:59`)
6769
+ #
6770
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
6771
+ # `2024-01-04T15:25:10-1759`)
6772
+ #
6773
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
6774
+ # `2024-01-04T15:25:10.123456789+17:59`)
6403
6775
  # @return [String]
6404
6776
  #
6405
6777
  # @!attribute [rw] network_interfaces
@@ -7897,14 +8269,25 @@ module Aws::SecurityHub
7897
8269
  # @!attribute [rw] attach_time
7898
8270
  # Indicates when the attachment initiated.
7899
8271
  #
7900
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
7901
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
7902
- # date and time should be separated by `T`. For example,
7903
- # `2020-03-22T13:22:13.933Z`.
8272
+ # This field accepts only the specified formats. Timestamps can end
8273
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
8274
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
8275
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
8276
+ # examples:
8277
+ #
8278
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
8279
+ #
8280
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
8281
+ # `2019-01-31T23:00:00.123456789Z`)
7904
8282
  #
8283
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
8284
+ # `2024-01-04T15:25:10+17:59`)
7905
8285
  #
8286
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
8287
+ # `2024-01-04T15:25:10-1759`)
7906
8288
  #
7907
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
8289
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
8290
+ # `2024-01-04T15:25:10.123456789+17:59`)
7908
8291
  # @return [String]
7909
8292
  #
7910
8293
  # @!attribute [rw] attachment_id
@@ -8488,14 +8871,25 @@ module Aws::SecurityHub
8488
8871
  # @!attribute [rw] create_time
8489
8872
  # Indicates when the volume was created.
8490
8873
  #
8491
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
8492
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
8493
- # date and time should be separated by `T`. For example,
8494
- # `2020-03-22T13:22:13.933Z`.
8874
+ # This field accepts only the specified formats. Timestamps can end
8875
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
8876
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
8877
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
8878
+ # examples:
8495
8879
  #
8880
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
8496
8881
  #
8882
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
8883
+ # `2019-01-31T23:00:00.123456789Z`)
8497
8884
  #
8498
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
8885
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
8886
+ # `2024-01-04T15:25:10+17:59`)
8887
+ #
8888
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
8889
+ # `2024-01-04T15:25:10-1759`)
8890
+ #
8891
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
8892
+ # `2024-01-04T15:25:10.123456789+17:59`)
8499
8893
  # @return [String]
8500
8894
  #
8501
8895
  # @!attribute [rw] device_name
@@ -9025,14 +9419,25 @@ module Aws::SecurityHub
9025
9419
  # @!attribute [rw] last_status_change
9026
9420
  # The date and time of the last change in status.
9027
9421
  #
9028
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
9029
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
9030
- # date and time should be separated by `T`. For example,
9031
- # `2020-03-22T13:22:13.933Z`.
9422
+ # This field accepts only the specified formats. Timestamps can end
9423
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
9424
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
9425
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
9426
+ # examples:
9427
+ #
9428
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
9032
9429
  #
9430
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
9431
+ # `2019-01-31T23:00:00.123456789Z`)
9033
9432
  #
9433
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
9434
+ # `2024-01-04T15:25:10+17:59`)
9034
9435
  #
9035
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
9436
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
9437
+ # `2024-01-04T15:25:10-1759`)
9438
+ #
9439
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
9440
+ # `2024-01-04T15:25:10.123456789+17:59`)
9036
9441
  # @return [String]
9037
9442
  #
9038
9443
  # @!attribute [rw] outside_ip_address
@@ -9093,14 +9498,25 @@ module Aws::SecurityHub
9093
9498
  # @!attribute [rw] image_published_at
9094
9499
  # The date and time when the image was pushed to the repository.
9095
9500
  #
9096
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
9097
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
9098
- # date and time should be separated by `T`. For example,
9099
- # `2020-03-22T13:22:13.933Z`.
9501
+ # This field accepts only the specified formats. Timestamps can end
9502
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
9503
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
9504
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
9505
+ # examples:
9506
+ #
9507
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
9100
9508
  #
9509
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
9510
+ # `2019-01-31T23:00:00.123456789Z`)
9101
9511
  #
9512
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
9513
+ # `2024-01-04T15:25:10+17:59`)
9102
9514
  #
9103
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
9515
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
9516
+ # `2024-01-04T15:25:10-1759`)
9517
+ #
9518
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
9519
+ # `2024-01-04T15:25:10.123456789+17:59`)
9104
9520
  # @return [String]
9105
9521
  #
9106
9522
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsEcrContainerImageDetails AWS API Documentation
@@ -12270,14 +12686,25 @@ module Aws::SecurityHub
12270
12686
  # @!attribute [rw] created_time
12271
12687
  # Indicates when the load balancer was created.
12272
12688
  #
12273
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
12274
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
12275
- # date and time should be separated by `T`. For example,
12276
- # `2020-03-22T13:22:13.933Z`.
12689
+ # This field accepts only the specified formats. Timestamps can end
12690
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
12691
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
12692
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
12693
+ # examples:
12694
+ #
12695
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
12277
12696
  #
12697
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
12698
+ # `2019-01-31T23:00:00.123456789Z`)
12278
12699
  #
12700
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
12701
+ # `2024-01-04T15:25:10+17:59`)
12279
12702
  #
12280
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
12703
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
12704
+ # `2024-01-04T15:25:10-1759`)
12705
+ #
12706
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
12707
+ # `2024-01-04T15:25:10.123456789+17:59`)
12281
12708
  # @return [String]
12282
12709
  #
12283
12710
  # @!attribute [rw] dns_name
@@ -12567,14 +12994,25 @@ module Aws::SecurityHub
12567
12994
  # @!attribute [rw] created_time
12568
12995
  # Indicates when the load balancer was created.
12569
12996
  #
12570
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
12571
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
12572
- # date and time should be separated by `T`. For example,
12573
- # `2020-03-22T13:22:13.933Z`.
12997
+ # This field accepts only the specified formats. Timestamps can end
12998
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
12999
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
13000
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
13001
+ # examples:
13002
+ #
13003
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13004
+ #
13005
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
13006
+ # `2019-01-31T23:00:00.123456789Z`)
12574
13007
  #
13008
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
13009
+ # `2024-01-04T15:25:10+17:59`)
12575
13010
  #
13011
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
13012
+ # `2024-01-04T15:25:10-1759`)
12576
13013
  #
12577
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
13014
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
13015
+ # `2024-01-04T15:25:10.123456789+17:59`)
12578
13016
  # @return [String]
12579
13017
  #
12580
13018
  # @!attribute [rw] dns_name
@@ -13132,14 +13570,25 @@ module Aws::SecurityHub
13132
13570
  # @!attribute [rw] created_at
13133
13571
  # Indicates when the IAM access key was created.
13134
13572
  #
13135
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13136
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13137
- # date and time should be separated by `T`. For example,
13138
- # `2020-03-22T13:22:13.933Z`.
13573
+ # This field accepts only the specified formats. Timestamps can end
13574
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
13575
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
13576
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
13577
+ # examples:
13139
13578
  #
13579
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13140
13580
  #
13581
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
13582
+ # `2019-01-31T23:00:00.123456789Z`)
13141
13583
  #
13142
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
13584
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
13585
+ # `2024-01-04T15:25:10+17:59`)
13586
+ #
13587
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
13588
+ # `2024-01-04T15:25:10-1759`)
13589
+ #
13590
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
13591
+ # `2024-01-04T15:25:10.123456789+17:59`)
13143
13592
  # @return [String]
13144
13593
  #
13145
13594
  # @!attribute [rw] principal_id
@@ -13211,14 +13660,25 @@ module Aws::SecurityHub
13211
13660
  # @!attribute [rw] creation_date
13212
13661
  # Indicates when the session was created.
13213
13662
  #
13214
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13215
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13216
- # date and time should be separated by `T`. For example,
13217
- # `2020-03-22T13:22:13.933Z`.
13663
+ # This field accepts only the specified formats. Timestamps can end
13664
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
13665
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
13666
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
13667
+ # examples:
13668
+ #
13669
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13670
+ #
13671
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
13672
+ # `2019-01-31T23:00:00.123456789Z`)
13218
13673
  #
13674
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
13675
+ # `2024-01-04T15:25:10+17:59`)
13219
13676
  #
13677
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
13678
+ # `2024-01-04T15:25:10-1759`)
13220
13679
  #
13221
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
13680
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
13681
+ # `2024-01-04T15:25:10.123456789+17:59`)
13222
13682
  # @return [String]
13223
13683
  #
13224
13684
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsIamAccessKeySessionContextAttributes AWS API Documentation
@@ -13295,14 +13755,25 @@ module Aws::SecurityHub
13295
13755
  # @!attribute [rw] create_date
13296
13756
  # Indicates when the IAM group was created.
13297
13757
  #
13298
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13299
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13300
- # date and time should be separated by `T`. For example,
13301
- # `2020-03-22T13:22:13.933Z`.
13758
+ # This field accepts only the specified formats. Timestamps can end
13759
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
13760
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
13761
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
13762
+ # examples:
13302
13763
  #
13764
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13303
13765
  #
13766
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
13767
+ # `2019-01-31T23:00:00.123456789Z`)
13304
13768
  #
13305
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
13769
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
13770
+ # `2024-01-04T15:25:10+17:59`)
13771
+ #
13772
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
13773
+ # `2024-01-04T15:25:10-1759`)
13774
+ #
13775
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
13776
+ # `2024-01-04T15:25:10.123456789+17:59`)
13306
13777
  # @return [String]
13307
13778
  #
13308
13779
  # @!attribute [rw] group_id
@@ -13357,14 +13828,25 @@ module Aws::SecurityHub
13357
13828
  # @!attribute [rw] create_date
13358
13829
  # Indicates when the instance profile was created.
13359
13830
  #
13360
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13361
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13362
- # date and time should be separated by `T`. For example,
13363
- # `2020-03-22T13:22:13.933Z`.
13831
+ # This field accepts only the specified formats. Timestamps can end
13832
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
13833
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
13834
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
13835
+ # examples:
13836
+ #
13837
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13364
13838
  #
13839
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
13840
+ # `2019-01-31T23:00:00.123456789Z`)
13365
13841
  #
13842
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
13843
+ # `2024-01-04T15:25:10+17:59`)
13366
13844
  #
13367
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
13845
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
13846
+ # `2024-01-04T15:25:10-1759`)
13847
+ #
13848
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
13849
+ # `2024-01-04T15:25:10.123456789+17:59`)
13368
13850
  # @return [String]
13369
13851
  #
13370
13852
  # @!attribute [rw] instance_profile_id
@@ -13409,14 +13891,25 @@ module Aws::SecurityHub
13409
13891
  # @!attribute [rw] create_date
13410
13892
  # Indicates when the role was created.
13411
13893
  #
13412
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13413
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13414
- # date and time should be separated by `T`. For example,
13415
- # `2020-03-22T13:22:13.933Z`.
13894
+ # This field accepts only the specified formats. Timestamps can end
13895
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
13896
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
13897
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
13898
+ # examples:
13899
+ #
13900
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13416
13901
  #
13902
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
13903
+ # `2019-01-31T23:00:00.123456789Z`)
13417
13904
  #
13905
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
13906
+ # `2024-01-04T15:25:10+17:59`)
13418
13907
  #
13419
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
13908
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
13909
+ # `2024-01-04T15:25:10-1759`)
13910
+ #
13911
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
13912
+ # `2024-01-04T15:25:10.123456789+17:59`)
13420
13913
  # @return [String]
13421
13914
  #
13422
13915
  # @!attribute [rw] path
@@ -13474,14 +13967,25 @@ module Aws::SecurityHub
13474
13967
  # @!attribute [rw] create_date
13475
13968
  # When the policy was created.
13476
13969
  #
13477
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13478
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13479
- # date and time should be separated by `T`. For example,
13480
- # `2020-03-22T13:22:13.933Z`.
13970
+ # This field accepts only the specified formats. Timestamps can end
13971
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
13972
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
13973
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
13974
+ # examples:
13975
+ #
13976
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13481
13977
  #
13978
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
13979
+ # `2019-01-31T23:00:00.123456789Z`)
13482
13980
  #
13981
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
13982
+ # `2024-01-04T15:25:10+17:59`)
13483
13983
  #
13484
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
13984
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
13985
+ # `2024-01-04T15:25:10-1759`)
13986
+ #
13987
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
13988
+ # `2024-01-04T15:25:10.123456789+17:59`)
13485
13989
  # @return [String]
13486
13990
  #
13487
13991
  # @!attribute [rw] default_version_id
@@ -13520,14 +14024,25 @@ module Aws::SecurityHub
13520
14024
  # @!attribute [rw] update_date
13521
14025
  # When the policy was most recently updated.
13522
14026
  #
13523
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13524
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13525
- # date and time should be separated by `T`. For example,
13526
- # `2020-03-22T13:22:13.933Z`.
14027
+ # This field accepts only the specified formats. Timestamps can end
14028
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
14029
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
14030
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
14031
+ # examples:
14032
+ #
14033
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
14034
+ #
14035
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
14036
+ # `2019-01-31T23:00:00.123456789Z`)
13527
14037
  #
14038
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
14039
+ # `2024-01-04T15:25:10+17:59`)
13528
14040
  #
14041
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
14042
+ # `2024-01-04T15:25:10-1759`)
13529
14043
  #
13530
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
14044
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
14045
+ # `2024-01-04T15:25:10.123456789+17:59`)
13531
14046
  # @return [String]
13532
14047
  #
13533
14048
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsIamPolicyDetails AWS API Documentation
@@ -13561,14 +14076,25 @@ module Aws::SecurityHub
13561
14076
  # @!attribute [rw] create_date
13562
14077
  # Indicates when the version was created.
13563
14078
  #
13564
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13565
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13566
- # date and time should be separated by `T`. For example,
13567
- # `2020-03-22T13:22:13.933Z`.
14079
+ # This field accepts only the specified formats. Timestamps can end
14080
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
14081
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
14082
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
14083
+ # examples:
13568
14084
  #
14085
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13569
14086
  #
14087
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
14088
+ # `2019-01-31T23:00:00.123456789Z`)
13570
14089
  #
13571
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
14090
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
14091
+ # `2024-01-04T15:25:10+17:59`)
14092
+ #
14093
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
14094
+ # `2024-01-04T15:25:10-1759`)
14095
+ #
14096
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
14097
+ # `2024-01-04T15:25:10.123456789+17:59`)
13572
14098
  # @return [String]
13573
14099
  #
13574
14100
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsIamPolicyVersion AWS API Documentation
@@ -13595,14 +14121,25 @@ module Aws::SecurityHub
13595
14121
  # @!attribute [rw] create_date
13596
14122
  # Indicates when the role was created.
13597
14123
  #
13598
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13599
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13600
- # date and time should be separated by `T`. For example,
13601
- # `2020-03-22T13:22:13.933Z`.
14124
+ # This field accepts only the specified formats. Timestamps can end
14125
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
14126
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
14127
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
14128
+ # examples:
14129
+ #
14130
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13602
14131
  #
14132
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
14133
+ # `2019-01-31T23:00:00.123456789Z`)
13603
14134
  #
14135
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
14136
+ # `2024-01-04T15:25:10+17:59`)
13604
14137
  #
13605
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
14138
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
14139
+ # `2024-01-04T15:25:10-1759`)
14140
+ #
14141
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
14142
+ # `2024-01-04T15:25:10.123456789+17:59`)
13606
14143
  # @return [String]
13607
14144
  #
13608
14145
  # @!attribute [rw] instance_profile_list
@@ -13675,14 +14212,25 @@ module Aws::SecurityHub
13675
14212
  # @!attribute [rw] create_date
13676
14213
  # Indicates when the user was created.
13677
14214
  #
13678
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13679
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13680
- # date and time should be separated by `T`. For example,
13681
- # `2020-03-22T13:22:13.933Z`.
14215
+ # This field accepts only the specified formats. Timestamps can end
14216
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
14217
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
14218
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
14219
+ # examples:
14220
+ #
14221
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
14222
+ #
14223
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
14224
+ # `2019-01-31T23:00:00.123456789Z`)
13682
14225
  #
14226
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
14227
+ # `2024-01-04T15:25:10+17:59`)
13683
14228
  #
14229
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
14230
+ # `2024-01-04T15:25:10-1759`)
13684
14231
  #
13685
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
14232
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
14233
+ # `2024-01-04T15:25:10.123456789+17:59`)
13686
14234
  # @return [String]
13687
14235
  #
13688
14236
  # @!attribute [rw] group_list
@@ -13807,14 +14355,25 @@ module Aws::SecurityHub
13807
14355
  # @!attribute [rw] creation_date
13808
14356
  # Indicates when the KMS key was created.
13809
14357
  #
13810
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13811
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13812
- # date and time should be separated by `T`. For example,
13813
- # `2020-03-22T13:22:13.933Z`.
14358
+ # This field accepts only the specified formats. Timestamps can end
14359
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
14360
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
14361
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
14362
+ # examples:
13814
14363
  #
14364
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
13815
14365
  #
14366
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
14367
+ # `2019-01-31T23:00:00.123456789Z`)
13816
14368
  #
13817
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
14369
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
14370
+ # `2024-01-04T15:25:10+17:59`)
14371
+ #
14372
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
14373
+ # `2024-01-04T15:25:10-1759`)
14374
+ #
14375
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
14376
+ # `2024-01-04T15:25:10.123456789+17:59`)
13818
14377
  # @return [Float]
13819
14378
  #
13820
14379
  # @!attribute [rw] key_id
@@ -13960,14 +14519,25 @@ module Aws::SecurityHub
13960
14519
  # @!attribute [rw] last_modified
13961
14520
  # Indicates when the function was last updated.
13962
14521
  #
13963
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
13964
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
13965
- # date and time should be separated by `T`. For example,
13966
- # `2020-03-22T13:22:13.933Z`.
14522
+ # This field accepts only the specified formats. Timestamps can end
14523
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
14524
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
14525
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
14526
+ # examples:
14527
+ #
14528
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
14529
+ #
14530
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
14531
+ # `2019-01-31T23:00:00.123456789Z`)
13967
14532
  #
14533
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
14534
+ # `2024-01-04T15:25:10+17:59`)
13968
14535
  #
14536
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
14537
+ # `2024-01-04T15:25:10-1759`)
13969
14538
  #
13970
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
14539
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
14540
+ # `2024-01-04T15:25:10.123456789+17:59`)
13971
14541
  # @return [String]
13972
14542
  #
13973
14543
  # @!attribute [rw] layers
@@ -14152,25 +14722,51 @@ module Aws::SecurityHub
14152
14722
  # @return [Integer]
14153
14723
  #
14154
14724
  # @!attribute [rw] compatible_runtimes
14155
- # The layer's compatible runtimes. Maximum number of five items.
14725
+ # The layer's compatible [function runtimes][1].
14726
+ #
14727
+ # The following list includes deprecated runtimes. For more
14728
+ # information, see [Runtime deprecation policy][2] in the *Lambda
14729
+ # Developer Guide*.
14730
+ #
14731
+ # Array Members: Maximum number of 5 items.
14732
+ #
14733
+ # Valid Values: `nodejs | nodejs4.3 | nodejs6.10 | nodejs8.10 |
14734
+ # nodejs10.x | nodejs12.x | nodejs14.x | nodejs16.x | java8 |
14735
+ # java8.al2 | java11 | python2.7 | python3.6 | python3.7 | python3.8 |
14736
+ # python3.9 | dotnetcore1.0 | dotnetcore2.0 | dotnetcore2.1 |
14737
+ # dotnetcore3.1 | dotnet6 | nodejs4.3-edge | go1.x | ruby2.5 | ruby2.7
14738
+ # | provided | provided.al2 | nodejs18.x | python3.10 | java17 |
14739
+ # ruby3.2 | python3.11 | nodejs20.x | provided.al2023 | python3.12 |
14740
+ # java21`
14156
14741
  #
14157
- # Valid values: `nodejs10.x` \| `nodejs12.x` \| `java8` \| `java11` \|
14158
- # `python2.7` \| `python3.6` \| `python3.7` \| `python3.8` \|
14159
- # `dotnetcore1.0` \| `dotnetcore2.1` \| `go1.x` \| `ruby2.5` \|
14160
- # `provided`
14742
+ #
14743
+ #
14744
+ # [1]: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
14745
+ # [2]: https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtime-support-policy
14161
14746
  # @return [Array<String>]
14162
14747
  #
14163
14748
  # @!attribute [rw] created_date
14164
14749
  # Indicates when the version was created.
14165
14750
  #
14166
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
14167
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
14168
- # date and time should be separated by `T`. For example,
14169
- # `2020-03-22T13:22:13.933Z`.
14751
+ # This field accepts only the specified formats. Timestamps can end
14752
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
14753
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
14754
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
14755
+ # examples:
14756
+ #
14757
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
14758
+ #
14759
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
14760
+ # `2019-01-31T23:00:00.123456789Z`)
14170
14761
  #
14762
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
14763
+ # `2024-01-04T15:25:10+17:59`)
14171
14764
  #
14765
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
14766
+ # `2024-01-04T15:25:10-1759`)
14172
14767
  #
14173
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
14768
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
14769
+ # `2024-01-04T15:25:10.123456789+17:59`)
14174
14770
  # @return [String]
14175
14771
  #
14176
14772
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsLambdaLayerVersionDetails AWS API Documentation
@@ -15172,14 +15768,25 @@ module Aws::SecurityHub
15172
15768
  # Indicates when the DB cluster was created, in Universal Coordinated
15173
15769
  # Time (UTC).
15174
15770
  #
15175
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
15176
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
15177
- # date and time should be separated by `T`. For example,
15178
- # `2020-03-22T13:22:13.933Z`.
15771
+ # This field accepts only the specified formats. Timestamps can end
15772
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
15773
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
15774
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
15775
+ # examples:
15179
15776
  #
15777
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
15180
15778
  #
15779
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
15780
+ # `2019-01-31T23:00:00.123456789Z`)
15181
15781
  #
15182
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
15782
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
15783
+ # `2024-01-04T15:25:10+17:59`)
15784
+ #
15785
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
15786
+ # `2024-01-04T15:25:10-1759`)
15787
+ #
15788
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
15789
+ # `2024-01-04T15:25:10.123456789+17:59`)
15183
15790
  # @return [String]
15184
15791
  #
15185
15792
  # @!attribute [rw] enabled_cloud_watch_logs_exports
@@ -15405,14 +16012,25 @@ module Aws::SecurityHub
15405
16012
  # @!attribute [rw] snapshot_create_time
15406
16013
  # Indicates when the snapshot was taken.
15407
16014
  #
15408
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
15409
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
15410
- # date and time should be separated by `T`. For example,
15411
- # `2020-03-22T13:22:13.933Z`.
16015
+ # This field accepts only the specified formats. Timestamps can end
16016
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
16017
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
16018
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
16019
+ # examples:
16020
+ #
16021
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
15412
16022
  #
16023
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
16024
+ # `2019-01-31T23:00:00.123456789Z`)
15413
16025
  #
16026
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
16027
+ # `2024-01-04T15:25:10+17:59`)
15414
16028
  #
15415
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
16029
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
16030
+ # `2024-01-04T15:25:10-1759`)
16031
+ #
16032
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
16033
+ # `2024-01-04T15:25:10.123456789+17:59`)
15416
16034
  # @return [String]
15417
16035
  #
15418
16036
  # @!attribute [rw] engine
@@ -15441,14 +16059,25 @@ module Aws::SecurityHub
15441
16059
  # Indicates when the DB cluster was created, in Universal Coordinated
15442
16060
  # Time (UTC).
15443
16061
  #
15444
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
15445
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
15446
- # date and time should be separated by `T`. For example,
15447
- # `2020-03-22T13:22:13.933Z`.
16062
+ # This field accepts only the specified formats. Timestamps can end
16063
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
16064
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
16065
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
16066
+ # examples:
16067
+ #
16068
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
15448
16069
  #
16070
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
16071
+ # `2019-01-31T23:00:00.123456789Z`)
15449
16072
  #
16073
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
16074
+ # `2024-01-04T15:25:10+17:59`)
15450
16075
  #
15451
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
16076
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
16077
+ # `2024-01-04T15:25:10-1759`)
16078
+ #
16079
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
16080
+ # `2024-01-04T15:25:10.123456789+17:59`)
15452
16081
  # @return [String]
15453
16082
  #
15454
16083
  # @!attribute [rw] master_username
@@ -15684,14 +16313,25 @@ module Aws::SecurityHub
15684
16313
  # @!attribute [rw] instance_create_time
15685
16314
  # Indicates when the DB instance was created.
15686
16315
  #
15687
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
15688
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
15689
- # date and time should be separated by `T`. For example,
15690
- # `2020-03-22T13:22:13.933Z`.
16316
+ # This field accepts only the specified formats. Timestamps can end
16317
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
16318
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
16319
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
16320
+ # examples:
16321
+ #
16322
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
15691
16323
  #
16324
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
16325
+ # `2019-01-31T23:00:00.123456789Z`)
15692
16326
  #
16327
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
16328
+ # `2024-01-04T15:25:10+17:59`)
15693
16329
  #
15694
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
16330
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
16331
+ # `2024-01-04T15:25:10-1759`)
16332
+ #
16333
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
16334
+ # `2024-01-04T15:25:10.123456789+17:59`)
15695
16335
  # @return [String]
15696
16336
  #
15697
16337
  # @!attribute [rw] kms_key_id
@@ -15792,14 +16432,25 @@ module Aws::SecurityHub
15792
16432
  # Specifies the latest time to which a database can be restored with
15793
16433
  # point-in-time restore.
15794
16434
  #
15795
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
15796
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
15797
- # date and time should be separated by `T`. For example,
15798
- # `2020-03-22T13:22:13.933Z`.
16435
+ # This field accepts only the specified formats. Timestamps can end
16436
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
16437
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
16438
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
16439
+ # examples:
16440
+ #
16441
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
16442
+ #
16443
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
16444
+ # `2019-01-31T23:00:00.123456789Z`)
15799
16445
  #
16446
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
16447
+ # `2024-01-04T15:25:10+17:59`)
15800
16448
  #
16449
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
16450
+ # `2024-01-04T15:25:10-1759`)
15801
16451
  #
15802
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
16452
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
16453
+ # `2024-01-04T15:25:10.123456789+17:59`)
15803
16454
  # @return [String]
15804
16455
  #
15805
16456
  # @!attribute [rw] auto_minor_version_upgrade
@@ -16606,14 +17257,25 @@ module Aws::SecurityHub
16606
17257
  # @!attribute [rw] subscription_creation_time
16607
17258
  # The datetime when the event notification subscription was created.
16608
17259
  #
16609
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
16610
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
16611
- # date and time should be separated by `T`. For example,
16612
- # `2020-03-22T13:22:13.933Z`.
17260
+ # This field accepts only the specified formats. Timestamps can end
17261
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
17262
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
17263
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
17264
+ # examples:
16613
17265
  #
17266
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
16614
17267
  #
17268
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
17269
+ # `2019-01-31T23:00:00.123456789Z`)
16615
17270
  #
16616
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
17271
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
17272
+ # `2024-01-04T15:25:10+17:59`)
17273
+ #
17274
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
17275
+ # `2024-01-04T15:25:10-1759`)
17276
+ #
17277
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
17278
+ # `2024-01-04T15:25:10.123456789+17:59`)
16617
17279
  # @return [String]
16618
17280
  #
16619
17281
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsRdsEventSubscriptionDetails AWS API Documentation
@@ -16798,14 +17460,25 @@ module Aws::SecurityHub
16798
17460
  # @!attribute [rw] defer_maintenance_end_time
16799
17461
  # The end of the time window for which maintenance was deferred.
16800
17462
  #
16801
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
16802
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
16803
- # date and time should be separated by `T`. For example,
16804
- # `2020-03-22T13:22:13.933Z`.
17463
+ # This field accepts only the specified formats. Timestamps can end
17464
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
17465
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
17466
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
17467
+ # examples:
17468
+ #
17469
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
17470
+ #
17471
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
17472
+ # `2019-01-31T23:00:00.123456789Z`)
16805
17473
  #
17474
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
17475
+ # `2024-01-04T15:25:10+17:59`)
16806
17476
  #
17477
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
17478
+ # `2024-01-04T15:25:10-1759`)
16807
17479
  #
16808
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
17480
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
17481
+ # `2024-01-04T15:25:10.123456789+17:59`)
16809
17482
  # @return [String]
16810
17483
  #
16811
17484
  # @!attribute [rw] defer_maintenance_identifier
@@ -16815,14 +17488,25 @@ module Aws::SecurityHub
16815
17488
  # @!attribute [rw] defer_maintenance_start_time
16816
17489
  # The start of the time window for which maintenance was deferred.
16817
17490
  #
16818
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
16819
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
16820
- # date and time should be separated by `T`. For example,
16821
- # `2020-03-22T13:22:13.933Z`.
17491
+ # This field accepts only the specified formats. Timestamps can end
17492
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
17493
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
17494
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
17495
+ # examples:
16822
17496
  #
17497
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
16823
17498
  #
17499
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
17500
+ # `2019-01-31T23:00:00.123456789Z`)
16824
17501
  #
16825
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
17502
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
17503
+ # `2024-01-04T15:25:10+17:59`)
17504
+ #
17505
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
17506
+ # `2024-01-04T15:25:10-1759`)
17507
+ #
17508
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
17509
+ # `2024-01-04T15:25:10.123456789+17:59`)
16826
17510
  # @return [String]
16827
17511
  #
16828
17512
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/AwsRedshiftClusterDeferredMaintenanceWindow AWS API Documentation
@@ -16870,14 +17554,25 @@ module Aws::SecurityHub
16870
17554
  # @!attribute [rw] cluster_create_time
16871
17555
  # Indicates when the cluster was created.
16872
17556
  #
16873
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
16874
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
16875
- # date and time should be separated by `T`. For example,
16876
- # `2020-03-22T13:22:13.933Z`.
17557
+ # This field accepts only the specified formats. Timestamps can end
17558
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
17559
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
17560
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
17561
+ # examples:
17562
+ #
17563
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
16877
17564
  #
17565
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
17566
+ # `2019-01-31T23:00:00.123456789Z`)
16878
17567
  #
17568
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
17569
+ # `2024-01-04T15:25:10+17:59`)
16879
17570
  #
16880
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
17571
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
17572
+ # `2024-01-04T15:25:10-1759`)
17573
+ #
17574
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
17575
+ # `2024-01-04T15:25:10.123456789+17:59`)
16881
17576
  # @return [String]
16882
17577
  #
16883
17578
  # @!attribute [rw] cluster_identifier
@@ -16974,14 +17669,25 @@ module Aws::SecurityHub
16974
17669
  # cluster must have a valid snapshot schedule and have backups
16975
17670
  # enabled.
16976
17671
  #
16977
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
16978
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
16979
- # date and time should be separated by `T`. For example,
16980
- # `2020-03-22T13:22:13.933Z`.
17672
+ # This field accepts only the specified formats. Timestamps can end
17673
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
17674
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
17675
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
17676
+ # examples:
17677
+ #
17678
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
16981
17679
  #
17680
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
17681
+ # `2019-01-31T23:00:00.123456789Z`)
16982
17682
  #
17683
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
17684
+ # `2024-01-04T15:25:10+17:59`)
16983
17685
  #
16984
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
17686
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
17687
+ # `2024-01-04T15:25:10-1759`)
17688
+ #
17689
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
17690
+ # `2024-01-04T15:25:10.123456789+17:59`)
16985
17691
  # @return [String]
16986
17692
  #
16987
17693
  # @!attribute [rw] expected_next_snapshot_schedule_time_status
@@ -17029,14 +17735,25 @@ module Aws::SecurityHub
17029
17735
  # @!attribute [rw] next_maintenance_window_start_time
17030
17736
  # Indicates the start of the next maintenance window.
17031
17737
  #
17032
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
17033
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
17034
- # date and time should be separated by `T`. For example,
17035
- # `2020-03-22T13:22:13.933Z`.
17738
+ # This field accepts only the specified formats. Timestamps can end
17739
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
17740
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
17741
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
17742
+ # examples:
17743
+ #
17744
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
17036
17745
  #
17746
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
17747
+ # `2019-01-31T23:00:00.123456789Z`)
17037
17748
  #
17749
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
17750
+ # `2024-01-04T15:25:10+17:59`)
17038
17751
  #
17039
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
17752
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
17753
+ # `2024-01-04T15:25:10-1759`)
17754
+ #
17755
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
17756
+ # `2024-01-04T15:25:10.123456789+17:59`)
17040
17757
  # @return [String]
17041
17758
  #
17042
17759
  # @!attribute [rw] node_type
@@ -17264,27 +17981,49 @@ module Aws::SecurityHub
17264
17981
  # @!attribute [rw] last_failure_time
17265
17982
  # The last time when logs failed to be delivered.
17266
17983
  #
17267
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
17268
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
17269
- # date and time should be separated by `T`. For example,
17270
- # `2020-03-22T13:22:13.933Z`.
17984
+ # This field accepts only the specified formats. Timestamps can end
17985
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
17986
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
17987
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
17988
+ # examples:
17989
+ #
17990
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
17991
+ #
17992
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
17993
+ # `2019-01-31T23:00:00.123456789Z`)
17271
17994
  #
17995
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
17996
+ # `2024-01-04T15:25:10+17:59`)
17272
17997
  #
17998
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
17999
+ # `2024-01-04T15:25:10-1759`)
17273
18000
  #
17274
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
18001
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
18002
+ # `2024-01-04T15:25:10.123456789+17:59`)
17275
18003
  # @return [String]
17276
18004
  #
17277
18005
  # @!attribute [rw] last_successful_delivery_time
17278
18006
  # The last time that logs were delivered successfully.
17279
18007
  #
17280
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
17281
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
17282
- # date and time should be separated by `T`. For example,
17283
- # `2020-03-22T13:22:13.933Z`.
18008
+ # This field accepts only the specified formats. Timestamps can end
18009
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
18010
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
18011
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
18012
+ # examples:
17284
18013
  #
18014
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
17285
18015
  #
18016
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
18017
+ # `2019-01-31T23:00:00.123456789Z`)
17286
18018
  #
17287
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
18019
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
18020
+ # `2024-01-04T15:25:10+17:59`)
18021
+ #
18022
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
18023
+ # `2024-01-04T15:25:10-1759`)
18024
+ #
18025
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
18026
+ # `2024-01-04T15:25:10.123456789+17:59`)
17288
18027
  # @return [String]
17289
18028
  #
17290
18029
  # @!attribute [rw] logging_enabled
@@ -17743,14 +18482,25 @@ module Aws::SecurityHub
17743
18482
  # @!attribute [rw] expiration_date
17744
18483
  # The date when objects are moved or deleted.
17745
18484
  #
17746
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
17747
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
17748
- # date and time should be separated by `T`. For example,
17749
- # `2020-03-22T13:22:13.933Z`.
18485
+ # This field accepts only the specified formats. Timestamps can end
18486
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
18487
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
18488
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
18489
+ # examples:
18490
+ #
18491
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
18492
+ #
18493
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
18494
+ # `2019-01-31T23:00:00.123456789Z`)
17750
18495
  #
18496
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
18497
+ # `2024-01-04T15:25:10+17:59`)
17751
18498
  #
18499
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
18500
+ # `2024-01-04T15:25:10-1759`)
17752
18501
  #
17753
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
18502
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
18503
+ # `2024-01-04T15:25:10.123456789+17:59`)
17754
18504
  # @return [String]
17755
18505
  #
17756
18506
  # @!attribute [rw] expiration_in_days
@@ -17953,14 +18703,25 @@ module Aws::SecurityHub
17953
18703
  # A date on which to transition objects to the specified storage
17954
18704
  # class. If you provide `Date`, you cannot provide `Days`.
17955
18705
  #
17956
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
17957
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
17958
- # date and time should be separated by `T`. For example,
17959
- # `2020-03-22T13:22:13.933Z`.
18706
+ # This field accepts only the specified formats. Timestamps can end
18707
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
18708
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
18709
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
18710
+ # examples:
17960
18711
  #
18712
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
17961
18713
  #
18714
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
18715
+ # `2019-01-31T23:00:00.123456789Z`)
17962
18716
  #
17963
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
18717
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
18718
+ # `2024-01-04T15:25:10+17:59`)
18719
+ #
18720
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
18721
+ # `2024-01-04T15:25:10-1759`)
18722
+ #
18723
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
18724
+ # `2024-01-04T15:25:10.123456789+17:59`)
17964
18725
  # @return [String]
17965
18726
  #
17966
18727
  # @!attribute [rw] days
@@ -18034,14 +18795,25 @@ module Aws::SecurityHub
18034
18795
  # @!attribute [rw] created_at
18035
18796
  # Indicates when the S3 bucket was created.
18036
18797
  #
18037
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
18038
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
18039
- # date and time should be separated by `T`. For example,
18040
- # `2020-03-22T13:22:13.933Z`.
18798
+ # This field accepts only the specified formats. Timestamps can end
18799
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
18800
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
18801
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
18802
+ # examples:
18803
+ #
18804
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
18041
18805
  #
18806
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
18807
+ # `2019-01-31T23:00:00.123456789Z`)
18042
18808
  #
18809
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
18810
+ # `2024-01-04T15:25:10+17:59`)
18043
18811
  #
18044
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
18812
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
18813
+ # `2024-01-04T15:25:10-1759`)
18814
+ #
18815
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
18816
+ # `2024-01-04T15:25:10.123456789+17:59`)
18045
18817
  # @return [String]
18046
18818
  #
18047
18819
  # @!attribute [rw] server_side_encryption_configuration
@@ -18483,14 +19255,25 @@ module Aws::SecurityHub
18483
19255
  # @!attribute [rw] last_modified
18484
19256
  # Indicates when the object was last modified.
18485
19257
  #
18486
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
18487
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
18488
- # date and time should be separated by `T`. For example,
18489
- # `2020-03-22T13:22:13.933Z`.
19258
+ # This field accepts only the specified formats. Timestamps can end
19259
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
19260
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
19261
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
19262
+ # examples:
19263
+ #
19264
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
18490
19265
  #
19266
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
19267
+ # `2019-01-31T23:00:00.123456789Z`)
18491
19268
  #
19269
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
19270
+ # `2024-01-04T15:25:10+17:59`)
18492
19271
  #
18493
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
19272
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
19273
+ # `2024-01-04T15:25:10-1759`)
19274
+ #
19275
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
19276
+ # `2024-01-04T15:25:10.123456789+17:59`)
18494
19277
  # @return [String]
18495
19278
  #
18496
19279
  # @!attribute [rw] etag
@@ -18847,56 +19630,100 @@ module Aws::SecurityHub
18847
19630
  # Indicates when the security findings provider first observed the
18848
19631
  # potential security issue that a finding captured.
18849
19632
  #
18850
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
18851
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
18852
- # date and time should be separated by `T`. For example,
18853
- # `2020-03-22T13:22:13.933Z`.
19633
+ # This field accepts only the specified formats. Timestamps can end
19634
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
19635
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
19636
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
19637
+ # examples:
19638
+ #
19639
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
18854
19640
  #
19641
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
19642
+ # `2019-01-31T23:00:00.123456789Z`)
18855
19643
  #
19644
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
19645
+ # `2024-01-04T15:25:10+17:59`)
18856
19646
  #
18857
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
19647
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
19648
+ # `2024-01-04T15:25:10-1759`)
19649
+ #
19650
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
19651
+ # `2024-01-04T15:25:10.123456789+17:59`)
18858
19652
  # @return [String]
18859
19653
  #
18860
19654
  # @!attribute [rw] last_observed_at
18861
19655
  # Indicates when the security findings provider most recently observed
18862
19656
  # the potential security issue that a finding captured.
18863
19657
  #
18864
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
18865
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
18866
- # date and time should be separated by `T`. For example,
18867
- # `2020-03-22T13:22:13.933Z`.
19658
+ # This field accepts only the specified formats. Timestamps can end
19659
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
19660
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
19661
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
19662
+ # examples:
19663
+ #
19664
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19665
+ #
19666
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
19667
+ # `2019-01-31T23:00:00.123456789Z`)
18868
19668
  #
19669
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
19670
+ # `2024-01-04T15:25:10+17:59`)
18869
19671
  #
19672
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
19673
+ # `2024-01-04T15:25:10-1759`)
18870
19674
  #
18871
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
19675
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
19676
+ # `2024-01-04T15:25:10.123456789+17:59`)
18872
19677
  # @return [String]
18873
19678
  #
18874
19679
  # @!attribute [rw] created_at
18875
19680
  # Indicates when the security findings provider created the potential
18876
19681
  # security issue that a finding captured.
18877
19682
  #
18878
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
18879
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
18880
- # date and time should be separated by `T`. For example,
18881
- # `2020-03-22T13:22:13.933Z`.
19683
+ # This field accepts only the specified formats. Timestamps can end
19684
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
19685
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
19686
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
19687
+ # examples:
18882
19688
  #
19689
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
18883
19690
  #
19691
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
19692
+ # `2019-01-31T23:00:00.123456789Z`)
18884
19693
  #
18885
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
19694
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
19695
+ # `2024-01-04T15:25:10+17:59`)
19696
+ #
19697
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
19698
+ # `2024-01-04T15:25:10-1759`)
19699
+ #
19700
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
19701
+ # `2024-01-04T15:25:10.123456789+17:59`)
18886
19702
  # @return [String]
18887
19703
  #
18888
19704
  # @!attribute [rw] updated_at
18889
19705
  # Indicates when the security findings provider last updated the
18890
19706
  # finding record.
18891
19707
  #
18892
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
18893
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
18894
- # date and time should be separated by `T`. For example,
18895
- # `2020-03-22T13:22:13.933Z`.
19708
+ # This field accepts only the specified formats. Timestamps can end
19709
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
19710
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
19711
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
19712
+ # examples:
19713
+ #
19714
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
18896
19715
  #
19716
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
19717
+ # `2019-01-31T23:00:00.123456789Z`)
18897
19718
  #
19719
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
19720
+ # `2024-01-04T15:25:10+17:59`)
18898
19721
  #
18899
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
19722
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
19723
+ # `2024-01-04T15:25:10-1759`)
19724
+ #
19725
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
19726
+ # `2024-01-04T15:25:10.123456789+17:59`)
18900
19727
  # @return [String]
18901
19728
  #
18902
19729
  # @!attribute [rw] severity
@@ -19059,17 +19886,28 @@ module Aws::SecurityHub
19059
19886
  # @return [Types::GeneratorDetails]
19060
19887
  #
19061
19888
  # @!attribute [rw] processed_at
19062
- # An ISO8601-formatted timestamp that indicates when Security Hub
19063
- # received a finding and begins to process it.
19889
+ # A imestamp that indicates when Security Hub received a finding and
19890
+ # begins to process it.
19891
+ #
19892
+ # This field accepts only the specified formats. Timestamps can end
19893
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
19894
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
19895
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
19896
+ # examples:
19897
+ #
19898
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19064
19899
  #
19065
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19066
- # value cannot contain spaces, and date and time should be separated
19067
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19068
- # Date/Time Format][1].
19900
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
19901
+ # `2019-01-31T23:00:00.123456789Z`)
19069
19902
  #
19903
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
19904
+ # `2024-01-04T15:25:10+17:59`)
19070
19905
  #
19906
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
19907
+ # `2024-01-04T15:25:10-1759`)
19071
19908
  #
19072
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
19909
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
19910
+ # `2024-01-04T15:25:10.123456789+17:59`)
19073
19911
  # @return [String]
19074
19912
  #
19075
19913
  # @!attribute [rw] aws_account_name
@@ -19166,62 +20004,104 @@ module Aws::SecurityHub
19166
20004
  # @return [Array<Types::StringFilter>]
19167
20005
  #
19168
20006
  # @!attribute [rw] first_observed_at
19169
- # An ISO8601-formatted timestamp that indicates when the security
19170
- # findings provider first observed the potential security issue that a
19171
- # finding captured.
20007
+ # A timestamp that indicates when the security findings provider first
20008
+ # observed the potential security issue that a finding captured.
19172
20009
  #
19173
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19174
- # value cannot contain spaces, and date and time should be separated
19175
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19176
- # Date/Time Format][1].
20010
+ # This field accepts only the specified formats. Timestamps can end
20011
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
20012
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
20013
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
20014
+ # examples:
19177
20015
  #
20016
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19178
20017
  #
20018
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
20019
+ # `2019-01-31T23:00:00.123456789Z`)
19179
20020
  #
19180
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
20021
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
20022
+ # `2024-01-04T15:25:10+17:59`)
20023
+ #
20024
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
20025
+ # `2024-01-04T15:25:10-1759`)
20026
+ #
20027
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
20028
+ # `2024-01-04T15:25:10.123456789+17:59`)
19181
20029
  # @return [Array<Types::DateFilter>]
19182
20030
  #
19183
20031
  # @!attribute [rw] last_observed_at
19184
- # An ISO8601-formatted timestamp that indicates when the security
19185
- # findings provider most recently observed the potential security
19186
- # issue that a finding captured.
20032
+ # A timestamp that indicates when the security findings provider most
20033
+ # recently observed the potential security issue that a finding
20034
+ # captured.
20035
+ #
20036
+ # This field accepts only the specified formats. Timestamps can end
20037
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
20038
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
20039
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
20040
+ # examples:
20041
+ #
20042
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19187
20043
  #
19188
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19189
- # value cannot contain spaces, and date and time should be separated
19190
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19191
- # Date/Time Format][1].
20044
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
20045
+ # `2019-01-31T23:00:00.123456789Z`)
19192
20046
  #
20047
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
20048
+ # `2024-01-04T15:25:10+17:59`)
19193
20049
  #
20050
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
20051
+ # `2024-01-04T15:25:10-1759`)
19194
20052
  #
19195
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
20053
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
20054
+ # `2024-01-04T15:25:10.123456789+17:59`)
19196
20055
  # @return [Array<Types::DateFilter>]
19197
20056
  #
19198
20057
  # @!attribute [rw] created_at
19199
- # An ISO8601-formatted timestamp that indicates when the security
19200
- # findings provider captured the potential security issue that a
19201
- # finding captured.
20058
+ # A timestamp that indicates when the security findings provider
20059
+ # created the potential security issue that a finding reflects.
19202
20060
  #
19203
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19204
- # value cannot contain spaces, and date and time should be separated
19205
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19206
- # Date/Time Format][1].
20061
+ # This field accepts only the specified formats. Timestamps can end
20062
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
20063
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
20064
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
20065
+ # examples:
19207
20066
  #
20067
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19208
20068
  #
20069
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
20070
+ # `2019-01-31T23:00:00.123456789Z`)
19209
20071
  #
19210
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
20072
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
20073
+ # `2024-01-04T15:25:10+17:59`)
20074
+ #
20075
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
20076
+ # `2024-01-04T15:25:10-1759`)
20077
+ #
20078
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
20079
+ # `2024-01-04T15:25:10.123456789+17:59`)
19211
20080
  # @return [Array<Types::DateFilter>]
19212
20081
  #
19213
20082
  # @!attribute [rw] updated_at
19214
- # An ISO8601-formatted timestamp that indicates when the security
19215
- # findings provider last updated the finding record.
20083
+ # A timestamp that indicates when the security findings provider last
20084
+ # updated the finding record.
20085
+ #
20086
+ # This field accepts only the specified formats. Timestamps can end
20087
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
20088
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
20089
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
20090
+ # examples:
19216
20091
  #
19217
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19218
- # value cannot contain spaces, and date and time should be separated
19219
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19220
- # Date/Time Format][1].
20092
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19221
20093
  #
20094
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
20095
+ # `2019-01-31T23:00:00.123456789Z`)
19222
20096
  #
20097
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
20098
+ # `2024-01-04T15:25:10+17:59`)
19223
20099
  #
19224
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
20100
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
20101
+ # `2024-01-04T15:25:10-1759`)
20102
+ #
20103
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
20104
+ # `2024-01-04T15:25:10.123456789+17:59`)
19225
20105
  # @return [Array<Types::DateFilter>]
19226
20106
  #
19227
20107
  # @!attribute [rw] severity_product
@@ -19380,27 +20260,49 @@ module Aws::SecurityHub
19380
20260
  # @!attribute [rw] process_launched_at
19381
20261
  # A timestamp that identifies when the process was launched.
19382
20262
  #
19383
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19384
- # value cannot contain spaces, and date and time should be separated
19385
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19386
- # Date/Time Format][1].
20263
+ # This field accepts only the specified formats. Timestamps can end
20264
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
20265
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
20266
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
20267
+ # examples:
20268
+ #
20269
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19387
20270
  #
20271
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
20272
+ # `2019-01-31T23:00:00.123456789Z`)
19388
20273
  #
20274
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
20275
+ # `2024-01-04T15:25:10+17:59`)
19389
20276
  #
19390
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
20277
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
20278
+ # `2024-01-04T15:25:10-1759`)
20279
+ #
20280
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
20281
+ # `2024-01-04T15:25:10.123456789+17:59`)
19391
20282
  # @return [Array<Types::DateFilter>]
19392
20283
  #
19393
20284
  # @!attribute [rw] process_terminated_at
19394
20285
  # A timestamp that identifies when the process was terminated.
19395
20286
  #
19396
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19397
- # value cannot contain spaces, and date and time should be separated
19398
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19399
- # Date/Time Format][1].
20287
+ # This field accepts only the specified formats. Timestamps can end
20288
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
20289
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
20290
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
20291
+ # examples:
20292
+ #
20293
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
19400
20294
  #
20295
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
20296
+ # `2019-01-31T23:00:00.123456789Z`)
19401
20297
  #
20298
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
20299
+ # `2024-01-04T15:25:10+17:59`)
19402
20300
  #
19403
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
20301
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
20302
+ # `2024-01-04T15:25:10-1759`)
20303
+ #
20304
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
20305
+ # `2024-01-04T15:25:10.123456789+17:59`)
19404
20306
  # @return [Array<Types::DateFilter>]
19405
20307
  #
19406
20308
  # @!attribute [rw] threat_intel_indicator_type
@@ -19530,14 +20432,25 @@ module Aws::SecurityHub
19530
20432
  # @!attribute [rw] resource_container_launched_at
19531
20433
  # A timestamp that identifies when the container was started.
19532
20434
  #
19533
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
19534
- # value cannot contain spaces, and date and time should be separated
19535
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
19536
- # Date/Time Format][1].
20435
+ # This field accepts only the specified formats. Timestamps can end
20436
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
20437
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
20438
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
20439
+ # examples:
20440
+ #
20441
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
20442
+ #
20443
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
20444
+ # `2019-01-31T23:00:00.123456789Z`)
19537
20445
  #
20446
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
20447
+ # `2024-01-04T15:25:10+17:59`)
19538
20448
  #
20449
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
20450
+ # `2024-01-04T15:25:10-1759`)
19539
20451
  #
19540
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
20452
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
20453
+ # `2024-01-04T15:25:10.123456789+17:59`)
19541
20454
  # @return [Array<Types::DateFilter>]
19542
20455
  #
19543
20456
  # @!attribute [rw] resource_details_other
@@ -22441,14 +23354,25 @@ module Aws::SecurityHub
22441
23354
  # @!attribute [rw] launched_at
22442
23355
  # Indicates when the container started.
22443
23356
  #
22444
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
22445
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
22446
- # date and time should be separated by `T`. For example,
22447
- # `2020-03-22T13:22:13.933Z`.
23357
+ # This field accepts only the specified formats. Timestamps can end
23358
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
23359
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
23360
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
23361
+ # examples:
22448
23362
  #
23363
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
22449
23364
  #
23365
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
23366
+ # `2019-01-31T23:00:00.123456789Z`)
22450
23367
  #
22451
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
23368
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
23369
+ # `2024-01-04T15:25:10+17:59`)
23370
+ #
23371
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
23372
+ # `2024-01-04T15:25:10-1759`)
23373
+ #
23374
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
23375
+ # `2024-01-04T15:25:10.123456789+17:59`)
22452
23376
  # @return [String]
22453
23377
  #
22454
23378
  # @!attribute [rw] volume_mounts
@@ -22961,27 +23885,49 @@ module Aws::SecurityHub
22961
23885
  # @!attribute [rw] start
22962
23886
  # A timestamp that provides the start date for the date filter.
22963
23887
  #
22964
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
22965
- # value cannot contain spaces, and date and time should be separated
22966
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
22967
- # Date/Time Format][1].
23888
+ # This field accepts only the specified formats. Timestamps can end
23889
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
23890
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
23891
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
23892
+ # examples:
23893
+ #
23894
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
23895
+ #
23896
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
23897
+ # `2019-01-31T23:00:00.123456789Z`)
22968
23898
  #
23899
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
23900
+ # `2024-01-04T15:25:10+17:59`)
22969
23901
  #
23902
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
23903
+ # `2024-01-04T15:25:10-1759`)
22970
23904
  #
22971
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
23905
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
23906
+ # `2024-01-04T15:25:10.123456789+17:59`)
22972
23907
  # @return [String]
22973
23908
  #
22974
23909
  # @!attribute [rw] end
22975
23910
  # A timestamp that provides the end date for the date filter.
22976
23911
  #
22977
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
22978
- # value cannot contain spaces, and date and time should be separated
22979
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
22980
- # Date/Time Format][1].
23912
+ # This field accepts only the specified formats. Timestamps can end
23913
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
23914
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
23915
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
23916
+ # examples:
22981
23917
  #
23918
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
22982
23919
  #
23920
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
23921
+ # `2019-01-31T23:00:00.123456789Z`)
22983
23922
  #
22984
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
23923
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
23924
+ # `2024-01-04T15:25:10+17:59`)
23925
+ #
23926
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
23927
+ # `2024-01-04T15:25:10-1759`)
23928
+ #
23929
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
23930
+ # `2024-01-04T15:25:10.123456789+17:59`)
22985
23931
  # @return [String]
22986
23932
  #
22987
23933
  # @!attribute [rw] date_range
@@ -23804,17 +24750,28 @@ module Aws::SecurityHub
23804
24750
  # @return [Types::AwsSecurityFindingIdentifier]
23805
24751
  #
23806
24752
  # @!attribute [rw] update_time
23807
- # An ISO 8601-formatted timestamp that indicates when Security Hub
23808
- # processed the updated finding record.
24753
+ # A timestamp that indicates when Security Hub processed the updated
24754
+ # finding record.
23809
24755
  #
23810
- # A correctly formatted example is `2020-05-21T20:16:34.724Z`. The
23811
- # value cannot contain spaces, and date and time should be separated
23812
- # by `T`. For more information, see [RFC 3339 section 5.6, Internet
23813
- # Date/Time Format][1].
24756
+ # This field accepts only the specified formats. Timestamps can end
24757
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
24758
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
24759
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
24760
+ # examples:
23814
24761
  #
24762
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
23815
24763
  #
24764
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
24765
+ # `2019-01-31T23:00:00.123456789Z`)
23816
24766
  #
23817
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
24767
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
24768
+ # `2024-01-04T15:25:10+17:59`)
24769
+ #
24770
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
24771
+ # `2024-01-04T15:25:10-1759`)
24772
+ #
24773
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
24774
+ # `2024-01-04T15:25:10.123456789+17:59`)
23818
24775
  # @return [Time]
23819
24776
  #
23820
24777
  # @!attribute [rw] finding_created
@@ -24383,11 +25340,8 @@ module Aws::SecurityHub
24383
25340
  # @return [Types::AwsSecurityFindingIdentifier]
24384
25341
  #
24385
25342
  # @!attribute [rw] start_time
24386
- # An ISO 8601-formatted timestamp that indicates the start time of the
24387
- # requested finding history. A correctly formatted example is
24388
- # `2020-05-21T20:16:34.724Z`. The value cannot contain spaces, and
24389
- # date and time should be separated by `T`. For more information, see
24390
- # [RFC 3339 section 5.6, Internet Date/Time Format][1].
25343
+ # A timestamp that indicates the start time of the requested finding
25344
+ # history.
24391
25345
  #
24392
25346
  # If you provide values for both `StartTime` and `EndTime`, Security
24393
25347
  # Hub returns finding history for the specified time period. If you
@@ -24395,25 +25349,41 @@ module Aws::SecurityHub
24395
25349
  # returns finding history from the `StartTime` to the time at which
24396
25350
  # the API is called. If you provide a value for `EndTime` but not for
24397
25351
  # `StartTime`, Security Hub returns finding history from the
24398
- # [CreatedAt][2] timestamp of the finding to the `EndTime`. If you
25352
+ # [CreatedAt][1] timestamp of the finding to the `EndTime`. If you
24399
25353
  # provide neither `StartTime` nor `EndTime`, Security Hub returns
24400
25354
  # finding history from the CreatedAt timestamp of the finding to the
24401
25355
  # time at which the API is called. In all of these scenarios, the
24402
25356
  # response is limited to 100 results, and the maximum time period is
24403
25357
  # limited to 90 days.
24404
25358
  #
25359
+ # This field accepts only the specified formats. Timestamps can end
25360
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
25361
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
25362
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
25363
+ # examples:
25364
+ #
25365
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
25366
+ #
25367
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
25368
+ # `2019-01-31T23:00:00.123456789Z`)
25369
+ #
25370
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
25371
+ # `2024-01-04T15:25:10+17:59`)
25372
+ #
25373
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
25374
+ # `2024-01-04T15:25:10-1759`)
24405
25375
  #
25376
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
25377
+ # `2024-01-04T15:25:10.123456789+17:59`)
24406
25378
  #
24407
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
24408
- # [2]: https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_AwsSecurityFindingFilters.html#securityhub-Type-AwsSecurityFindingFilters-CreatedAt
25379
+ #
25380
+ #
25381
+ # [1]: https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_AwsSecurityFindingFilters.html#securityhub-Type-AwsSecurityFindingFilters-CreatedAt
24409
25382
  # @return [Time]
24410
25383
  #
24411
25384
  # @!attribute [rw] end_time
24412
25385
  # An ISO 8601-formatted timestamp that indicates the end time of the
24413
- # requested finding history. A correctly formatted example is
24414
- # `2020-05-21T20:16:34.724Z`. The value cannot contain spaces, and
24415
- # date and time should be separated by `T`. For more information, see
24416
- # [RFC 3339 section 5.6, Internet Date/Time Format][1].
25386
+ # requested finding history.
24417
25387
  #
24418
25388
  # If you provide values for both `StartTime` and `EndTime`, Security
24419
25389
  # Hub returns finding history for the specified time period. If you
@@ -24421,17 +25391,36 @@ module Aws::SecurityHub
24421
25391
  # returns finding history from the `StartTime` to the time at which
24422
25392
  # the API is called. If you provide a value for `EndTime` but not for
24423
25393
  # `StartTime`, Security Hub returns finding history from the
24424
- # [CreatedAt][2] timestamp of the finding to the `EndTime`. If you
25394
+ # [CreatedAt][1] timestamp of the finding to the `EndTime`. If you
24425
25395
  # provide neither `StartTime` nor `EndTime`, Security Hub returns
24426
25396
  # finding history from the CreatedAt timestamp of the finding to the
24427
25397
  # time at which the API is called. In all of these scenarios, the
24428
25398
  # response is limited to 100 results, and the maximum time period is
24429
25399
  # limited to 90 days.
24430
25400
  #
25401
+ # This field accepts only the specified formats. Timestamps can end
25402
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
25403
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
25404
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
25405
+ # examples:
25406
+ #
25407
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
25408
+ #
25409
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
25410
+ # `2019-01-31T23:00:00.123456789Z`)
25411
+ #
25412
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
25413
+ # `2024-01-04T15:25:10+17:59`)
25414
+ #
25415
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
25416
+ # `2024-01-04T15:25:10-1759`)
25417
+ #
25418
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
25419
+ # `2024-01-04T15:25:10.123456789+17:59`)
24431
25420
  #
24432
25421
  #
24433
- # [1]: https://www.rfc-editor.org/rfc/rfc3339#section-5.6
24434
- # [2]: https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_AwsSecurityFindingFilters.html#securityhub-Type-AwsSecurityFindingFilters-CreatedAt
25422
+ #
25423
+ # [1]: https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_AwsSecurityFindingFilters.html#securityhub-Type-AwsSecurityFindingFilters-CreatedAt
24435
25424
  # @return [Time]
24436
25425
  #
24437
25426
  # @!attribute [rw] next_token
@@ -24765,8 +25754,9 @@ module Aws::SecurityHub
24765
25754
  #
24766
25755
  # @!attribute [rw] filters
24767
25756
  # One or more attributes used to filter the findings included in the
24768
- # insight. The insight only includes findings that match the criteria
24769
- # defined in the filters.
25757
+ # insight. You can filter by up to ten finding attributes. For each
25758
+ # attribute, you can provide up to 20 filter values. The insight only
25759
+ # includes findings that match the criteria defined in the filters.
24770
25760
  # @return [Types::AwsSecurityFindingFilters]
24771
25761
  #
24772
25762
  # @!attribute [rw] group_by_attribute
@@ -26028,16 +27018,27 @@ module Aws::SecurityHub
26028
27018
  # @return [String]
26029
27019
  #
26030
27020
  # @!attribute [rw] updated_at
26031
- # The timestamp of when the note was updated.
27021
+ # A timestamp that indicates when the note was updated.
26032
27022
  #
26033
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
26034
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
26035
- # date and time should be separated by `T`. For example,
26036
- # `2020-03-22T13:22:13.933Z`.
27023
+ # This field accepts only the specified formats. Timestamps can end
27024
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
27025
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
27026
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
27027
+ # examples:
26037
27028
  #
27029
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
26038
27030
  #
27031
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
27032
+ # `2019-01-31T23:00:00.123456789Z`)
26039
27033
  #
26040
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
27034
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
27035
+ # `2024-01-04T15:25:10+17:59`)
27036
+ #
27037
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
27038
+ # `2024-01-04T15:25:10-1759`)
27039
+ #
27040
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
27041
+ # `2024-01-04T15:25:10.123456789+17:59`)
26041
27042
  # @return [String]
26042
27043
  #
26043
27044
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/Note AWS API Documentation
@@ -26381,27 +27382,49 @@ module Aws::SecurityHub
26381
27382
  # @!attribute [rw] operation_start_time
26382
27383
  # Indicates when the operation started.
26383
27384
  #
26384
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
26385
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
26386
- # date and time should be separated by `T`. For example,
26387
- # `2020-03-22T13:22:13.933Z`.
27385
+ # This field accepts only the specified formats. Timestamps can end
27386
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
27387
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
27388
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
27389
+ # examples:
27390
+ #
27391
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
26388
27392
  #
27393
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
27394
+ # `2019-01-31T23:00:00.123456789Z`)
26389
27395
  #
27396
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
27397
+ # `2024-01-04T15:25:10+17:59`)
26390
27398
  #
26391
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
27399
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
27400
+ # `2024-01-04T15:25:10-1759`)
27401
+ #
27402
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
27403
+ # `2024-01-04T15:25:10.123456789+17:59`)
26392
27404
  # @return [String]
26393
27405
  #
26394
27406
  # @!attribute [rw] operation_end_time
26395
27407
  # Indicates when the operation completed.
26396
27408
  #
26397
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
26398
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
26399
- # date and time should be separated by `T`. For example,
26400
- # `2020-03-22T13:22:13.933Z`.
27409
+ # This field accepts only the specified formats. Timestamps can end
27410
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
27411
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
27412
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
27413
+ # examples:
27414
+ #
27415
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
26401
27416
  #
27417
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
27418
+ # `2019-01-31T23:00:00.123456789Z`)
26402
27419
  #
27420
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
27421
+ # `2024-01-04T15:25:10+17:59`)
26403
27422
  #
26404
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
27423
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
27424
+ # `2024-01-04T15:25:10-1759`)
27425
+ #
27426
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
27427
+ # `2024-01-04T15:25:10.123456789+17:59`)
26405
27428
  # @return [String]
26406
27429
  #
26407
27430
  # @!attribute [rw] reboot_option
@@ -26571,27 +27594,49 @@ module Aws::SecurityHub
26571
27594
  # @!attribute [rw] launched_at
26572
27595
  # Indicates when the process was launched.
26573
27596
  #
26574
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
26575
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
26576
- # date and time should be separated by `T`. For example,
26577
- # `2020-03-22T13:22:13.933Z`.
27597
+ # This field accepts only the specified formats. Timestamps can end
27598
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
27599
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
27600
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
27601
+ # examples:
27602
+ #
27603
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
26578
27604
  #
27605
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
27606
+ # `2019-01-31T23:00:00.123456789Z`)
26579
27607
  #
27608
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
27609
+ # `2024-01-04T15:25:10+17:59`)
26580
27610
  #
26581
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
27611
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
27612
+ # `2024-01-04T15:25:10-1759`)
27613
+ #
27614
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
27615
+ # `2024-01-04T15:25:10.123456789+17:59`)
26582
27616
  # @return [String]
26583
27617
  #
26584
27618
  # @!attribute [rw] terminated_at
26585
27619
  # Indicates when the process was terminated.
26586
27620
  #
26587
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
26588
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
26589
- # date and time should be separated by `T`. For example,
26590
- # `2020-03-22T13:22:13.933Z`.
27621
+ # This field accepts only the specified formats. Timestamps can end
27622
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
27623
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
27624
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
27625
+ # examples:
27626
+ #
27627
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
27628
+ #
27629
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
27630
+ # `2019-01-31T23:00:00.123456789Z`)
26591
27631
  #
27632
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
27633
+ # `2024-01-04T15:25:10+17:59`)
26592
27634
  #
27635
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
27636
+ # `2024-01-04T15:25:10-1759`)
26593
27637
  #
26594
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
27638
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
27639
+ # `2024-01-04T15:25:10.123456789+17:59`)
26595
27640
  # @return [String]
26596
27641
  #
26597
27642
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/ProcessDetails AWS API Documentation
@@ -29446,14 +30491,25 @@ module Aws::SecurityHub
29446
30491
  # Indicates when the most recent instance of a threat intelligence
29447
30492
  # indicator was observed.
29448
30493
  #
29449
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
29450
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
29451
- # date and time should be separated by `T`. For example,
29452
- # `2020-03-22T13:22:13.933Z`.
30494
+ # This field accepts only the specified formats. Timestamps can end
30495
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
30496
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
30497
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
30498
+ # examples:
29453
30499
  #
30500
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
29454
30501
  #
30502
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
30503
+ # `2019-01-31T23:00:00.123456789Z`)
29455
30504
  #
29456
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
30505
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
30506
+ # `2024-01-04T15:25:10+17:59`)
30507
+ #
30508
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
30509
+ # `2024-01-04T15:25:10-1759`)
30510
+ #
30511
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
30512
+ # `2024-01-04T15:25:10.123456789+17:59`)
29457
30513
  # @return [String]
29458
30514
  #
29459
30515
  # @!attribute [rw] source
@@ -30352,27 +31408,49 @@ module Aws::SecurityHub
30352
31408
  # @!attribute [rw] vendor_created_at
30353
31409
  # Indicates when the vulnerability advisory was created.
30354
31410
  #
30355
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
30356
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
30357
- # date and time should be separated by `T`. For example,
30358
- # `2020-03-22T13:22:13.933Z`.
31411
+ # This field accepts only the specified formats. Timestamps can end
31412
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
31413
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
31414
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
31415
+ # examples:
31416
+ #
31417
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
30359
31418
  #
31419
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
31420
+ # `2019-01-31T23:00:00.123456789Z`)
30360
31421
  #
31422
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
31423
+ # `2024-01-04T15:25:10+17:59`)
30361
31424
  #
30362
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
31425
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
31426
+ # `2024-01-04T15:25:10-1759`)
31427
+ #
31428
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
31429
+ # `2024-01-04T15:25:10.123456789+17:59`)
30363
31430
  # @return [String]
30364
31431
  #
30365
31432
  # @!attribute [rw] vendor_updated_at
30366
31433
  # Indicates when the vulnerability advisory was last updated.
30367
31434
  #
30368
- # Uses the `date-time` format specified in [RFC 3339 section 5.6,
30369
- # Internet Date/Time Format][1]. The value cannot contain spaces, and
30370
- # date and time should be separated by `T`. For example,
30371
- # `2020-03-22T13:22:13.933Z`.
31435
+ # This field accepts only the specified formats. Timestamps can end
31436
+ # with `Z` or `("+" / "-") time-hour [":" time-minute]`. The
31437
+ # time-secfrac after seconds is limited to a maximum of 9 digits. The
31438
+ # offset is bounded by +/-18:00. Here are valid timestamp formats with
31439
+ # examples:
31440
+ #
31441
+ # * `YYYY-MM-DDTHH:MM:SSZ` (for example, `2019-01-31T23:00:00Z`)
31442
+ #
31443
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmmZ` (for example,
31444
+ # `2019-01-31T23:00:00.123456789Z`)
30372
31445
  #
31446
+ # * `YYYY-MM-DDTHH:MM:SS+HH:MM` (for example,
31447
+ # `2024-01-04T15:25:10+17:59`)
30373
31448
  #
31449
+ # * `YYYY-MM-DDTHH:MM:SS-HHMM` (for example,
31450
+ # `2024-01-04T15:25:10-1759`)
30374
31451
  #
30375
- # [1]: https://tools.ietf.org/html/rfc3339#section-5.6
31452
+ # * `YYYY-MM-DDTHH:MM:SS.mmmmmmmmm+HH:MM` (for example,
31453
+ # `2024-01-04T15:25:10.123456789+17:59`)
30376
31454
  # @return [String]
30377
31455
  #
30378
31456
  # @see http://docs.aws.amazon.com/goto/WebAPI/securityhub-2018-10-26/VulnerabilityVendor AWS API Documentation