aws-sdk-health 1.28.0 → 1.33.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 1d471d435fbec6b47f325f65c663d948c34ce267b6a002245f4d4e68af2a7e9f
4
- data.tar.gz: 4a9fc5891f2c3bcbb9461a3c8e1f973972daa06e94e3e24b3a9fb0886d4be111
3
+ metadata.gz: d800aac727d82c251d437f2372c09031fff98e7340a9e4b0cf5beff169a0ce19
4
+ data.tar.gz: c7cc332f1be7aa0e333e02f12a1dcf2b34670a4fe13140820e5e42708abf89e1
5
5
  SHA512:
6
- metadata.gz: cd1fafd95f921c88370f8b3d1613f088b6d8152cc757ed2f2213a55adffc0464b63afc9f4acb64c72393b78d2484c14ee591c79a6df4dd4d45c40a05d80e1c8f
7
- data.tar.gz: 7f8fc7b1e4aa458244aed80e5e25db1b79724da712fc4d59cf5093e68df5eb46698c104f36dff441b0232e3ff9ca04cf74f30f92daecc163897992baffac0776
6
+ metadata.gz: e35ed16d14b06ced5d4268b545ff4379bc5c15e1ce24a0de6eaed28ce940de492f04f765f451dc26f86c235faa589324266894c26c5690fdcfb3f93c3fea8bba
7
+ data.tar.gz: e131e988f3f6c28df37b95c2d97e1f177749066310a8fb751a9e22045a2349532a8f6f38b83160e9ecd7ea7c4a79546bd273877cdad27e546016099cae98db17
@@ -7,6 +7,7 @@
7
7
  #
8
8
  # WARNING ABOUT GENERATED CODE
9
9
 
10
+
10
11
  require 'aws-sdk-core'
11
12
  require 'aws-sigv4'
12
13
 
@@ -44,9 +45,9 @@ require_relative 'aws-sdk-health/customizations'
44
45
  #
45
46
  # See {Errors} for more information.
46
47
  #
47
- # @service
48
+ # @!group service
48
49
  module Aws::Health
49
50
 
50
- GEM_VERSION = '1.28.0'
51
+ GEM_VERSION = '1.33.0'
51
52
 
52
53
  end
@@ -85,13 +85,28 @@ module Aws::Health
85
85
  # * `Aws::Credentials` - Used for configuring static, non-refreshing
86
86
  # credentials.
87
87
  #
88
+ # * `Aws::SharedCredentials` - Used for loading static credentials from a
89
+ # shared file, such as `~/.aws/config`.
90
+ #
91
+ # * `Aws::AssumeRoleCredentials` - Used when you need to assume a role.
92
+ #
93
+ # * `Aws::AssumeRoleWebIdentityCredentials` - Used when you need to
94
+ # assume a role after providing credentials via the web.
95
+ #
96
+ # * `Aws::SSOCredentials` - Used for loading credentials from AWS SSO using an
97
+ # access token generated from `aws login`.
98
+ #
99
+ # * `Aws::ProcessCredentials` - Used for loading credentials from a
100
+ # process that outputs to stdout.
101
+ #
88
102
  # * `Aws::InstanceProfileCredentials` - Used for loading credentials
89
103
  # from an EC2 IMDS on an EC2 instance.
90
104
  #
91
- # * `Aws::SharedCredentials` - Used for loading credentials from a
92
- # shared file, such as `~/.aws/config`.
105
+ # * `Aws::ECSCredentials` - Used for loading credentials from
106
+ # instances running in ECS.
93
107
  #
94
- # * `Aws::AssumeRoleCredentials` - Used when you need to assume a role.
108
+ # * `Aws::CognitoIdentityCredentials` - Used for loading credentials
109
+ # from the Cognito Identity service.
95
110
  #
96
111
  # When `:credentials` are not configured directly, the following
97
112
  # locations will be searched for credentials:
@@ -101,10 +116,10 @@ module Aws::Health
101
116
  # * ENV['AWS_ACCESS_KEY_ID'], ENV['AWS_SECRET_ACCESS_KEY']
102
117
  # * `~/.aws/credentials`
103
118
  # * `~/.aws/config`
104
- # * EC2 IMDS instance profile - When used by default, the timeouts are
105
- # very aggressive. Construct and pass an instance of
106
- # `Aws::InstanceProfileCredentails` to enable retries and extended
107
- # timeouts.
119
+ # * EC2/ECS IMDS instance profile - When used by default, the timeouts
120
+ # are very aggressive. Construct and pass an instance of
121
+ # `Aws::InstanceProfileCredentails` or `Aws::ECSCredentials` to
122
+ # enable retries and extended timeouts.
108
123
  #
109
124
  # @option options [required, String] :region
110
125
  # The AWS region to connect to. The configured `:region` is
@@ -329,7 +344,7 @@ module Aws::Health
329
344
  # Before you can call this operation, you must first enable AWS Health
330
345
  # to work with AWS Organizations. To do this, call the
331
346
  # [EnableHealthServiceAccessForOrganization][2] operation from your
332
- # organization's master account.
347
+ # organization's management account.
333
348
  #
334
349
  # <note markdown="1"> This API operation uses pagination. Specify the `nextToken` parameter
335
350
  # in the next request to return more results.
@@ -400,11 +415,20 @@ module Aws::Health
400
415
  # At least one event ARN is required. Results are sorted by the
401
416
  # `lastUpdatedTime` of the entity, starting with the most recent.
402
417
  #
403
- # <note markdown="1"> This API operation uses pagination. Specify the `nextToken` parameter
404
- # in the next request to return more results.
418
+ # <note markdown="1"> * This API operation uses pagination. Specify the `nextToken`
419
+ # parameter in the next request to return more results.
420
+ #
421
+ # * This operation supports resource-level permissions. You can use this
422
+ # operation to allow or deny access to specific AWS Health events. For
423
+ # more information, see [Resource- and action-based conditions][1] in
424
+ # the *AWS Health User Guide*.
405
425
  #
406
426
  # </note>
407
427
  #
428
+ #
429
+ #
430
+ # [1]: https://docs.aws.amazon.com/health/latest/ug/security_iam_id-based-policy-examples.html#resource-action-based-conditions
431
+ #
408
432
  # @option params [required, Types::EntityFilter] :filter
409
433
  # Values to narrow the results returned. At least one event ARN is
410
434
  # required.
@@ -492,16 +516,22 @@ module Aws::Health
492
516
  # Before you can call this operation, you must first enable AWS Health
493
517
  # to work with AWS Organizations. To do this, call the
494
518
  # [EnableHealthServiceAccessForOrganization][1] operation from your
495
- # organization's master account.
519
+ # organization's management account.
496
520
  #
497
- # <note markdown="1"> This API operation uses pagination. Specify the `nextToken` parameter
498
- # in the next request to return more results.
521
+ # <note markdown="1"> * This API operation uses pagination. Specify the `nextToken`
522
+ # parameter in the next request to return more results.
523
+ #
524
+ # * This operation doesn't support resource-level permissions. You
525
+ # can't use this operation to allow or deny access to specific AWS
526
+ # Health events. For more information, see [Resource- and action-based
527
+ # conditions][2] in the *AWS Health User Guide*.
499
528
  #
500
529
  # </note>
501
530
  #
502
531
  #
503
532
  #
504
533
  # [1]: https://docs.aws.amazon.com/health/latest/APIReference/API_EnableHealthServiceAccessForOrganization.html
534
+ # [2]: https://docs.aws.amazon.com/health/latest/ug/security_iam_id-based-policy-examples.html#resource-action-based-conditions
505
535
  #
506
536
  # @option params [required, Array<Types::EventAccountFilter>] :organization_entity_filters
507
537
  # A JSON set of elements including the `awsAccountId` and the
@@ -698,19 +728,27 @@ module Aws::Health
698
728
  end
699
729
 
700
730
  # Returns detailed information about one or more specified events.
701
- # Information includes standard event data (Region, service, and so on,
702
- # as returned by [DescribeEvents][1]), a detailed event description, and
703
- # possible additional metadata that depends upon the nature of the
731
+ # Information includes standard event data (AWS Region, service, and so
732
+ # on, as returned by [DescribeEvents][1]), a detailed event description,
733
+ # and possible additional metadata that depends upon the nature of the
704
734
  # event. Affected entities are not included. To retrieve those, use the
705
735
  # [DescribeAffectedEntities][2] operation.
706
736
  #
707
737
  # If a specified event cannot be retrieved, an error message is returned
708
738
  # for that event.
709
739
  #
740
+ # <note markdown="1"> This operation supports resource-level permissions. You can use this
741
+ # operation to allow or deny access to specific AWS Health events. For
742
+ # more information, see [Resource- and action-based conditions][3] in
743
+ # the *AWS Health User Guide*.
744
+ #
745
+ # </note>
746
+ #
710
747
  #
711
748
  #
712
749
  # [1]: https://docs.aws.amazon.com/health/latest/APIReference/API_DescribeEvents.html
713
750
  # [2]: https://docs.aws.amazon.com/health/latest/APIReference/API_DescribeAffectedEntities.html
751
+ # [3]: https://docs.aws.amazon.com/health/latest/ug/security_iam_id-based-policy-examples.html#resource-action-based-conditions
714
752
  #
715
753
  # @option params [required, Array<String>] :event_arns
716
754
  # A list of event ARNs (unique identifiers). For example:
@@ -766,7 +804,7 @@ module Aws::Health
766
804
 
767
805
  # Returns detailed information about one or more specified events for
768
806
  # one or more accounts in your organization. Information includes
769
- # standard event data (Region, service, and so on, as returned by
807
+ # standard event data (AWS Region, service, and so on, as returned by
770
808
  # [DescribeEventsForOrganization][1]), a detailed event description, and
771
809
  # possible additional metadata that depends upon the nature of the
772
810
  # event. Affected entities are not included; to retrieve those, use the
@@ -775,7 +813,7 @@ module Aws::Health
775
813
  # Before you can call this operation, you must first enable AWS Health
776
814
  # to work with AWS Organizations. To do this, call the
777
815
  # [EnableHealthServiceAccessForOrganization][3] operation from your
778
- # organization's master account.
816
+ # organization's management account.
779
817
  #
780
818
  # When you call the `DescribeEventDetailsForOrganization` operation, you
781
819
  # specify the `organizationEventDetailFilters` object in the request.
@@ -794,12 +832,20 @@ module Aws::Health
794
832
  #
795
833
  # For more information, see [Event][4].
796
834
  #
835
+ # <note markdown="1"> This operation doesn't support resource-level permissions. You can't
836
+ # use this operation to allow or deny access to specific AWS Health
837
+ # events. For more information, see [Resource- and action-based
838
+ # conditions][5] in the *AWS Health User Guide*.
839
+ #
840
+ # </note>
841
+ #
797
842
  #
798
843
  #
799
844
  # [1]: https://docs.aws.amazon.com/health/latest/APIReference/API_DescribeEventsForOrganization.html
800
845
  # [2]: https://docs.aws.amazon.com/health/latest/APIReference/API_DescribeAffectedEntitiesForOrganization.html
801
846
  # [3]: https://docs.aws.amazon.com/health/latest/APIReference/API_EnableHealthServiceAccessForOrganization.html
802
847
  # [4]: https://docs.aws.amazon.com/health/latest/APIReference/API_Event.html
848
+ # [5]: https://docs.aws.amazon.com/health/latest/ug/security_iam_id-based-policy-examples.html#resource-action-based-conditions
803
849
  #
804
850
  # @option params [required, Array<Types::EventAccountFilter>] :organization_event_detail_filters
805
851
  # A set of JSON elements that includes the `awsAccountId` and the
@@ -859,15 +905,23 @@ module Aws::Health
859
905
  req.send_request(options)
860
906
  end
861
907
 
862
- # Returns the event types that meet the specified filter criteria. If no
863
- # filter criteria are specified, all event types are returned, in no
864
- # particular order.
908
+ # Returns the event types that meet the specified filter criteria. You
909
+ # can use this API operation to find information about the AWS Health
910
+ # event, such as the category, AWS service, and event code. The metadata
911
+ # for each event appears in the [EventType][1] object.
912
+ #
913
+ # If you don't specify a filter criteria, the API operation returns all
914
+ # event types, in no particular order.
865
915
  #
866
916
  # <note markdown="1"> This API operation uses pagination. Specify the `nextToken` parameter
867
917
  # in the next request to return more results.
868
918
  #
869
919
  # </note>
870
920
  #
921
+ #
922
+ #
923
+ # [1]: https://docs.aws.amazon.com/health/latest/APIReference/API_EventType.html
924
+ #
871
925
  # @option params [Types::EventTypeFilter] :filter
872
926
  # Values to narrow the results returned.
873
927
  #
@@ -1068,7 +1122,7 @@ module Aws::Health
1068
1122
  # Before you can call this operation, you must first enable AWS Health
1069
1123
  # to work with AWS Organizations. To do this, call the
1070
1124
  # [EnableHealthServiceAccessForOrganization][5] operation from your
1071
- # organization's master AWS account.
1125
+ # organization's management account.
1072
1126
  #
1073
1127
  # <note markdown="1"> This API operation uses pagination. Specify the `nextToken` parameter
1074
1128
  # in the next request to return more results.
@@ -1165,7 +1219,7 @@ module Aws::Health
1165
1219
  # This operation provides status information on enabling or disabling
1166
1220
  # AWS Health to work with your organization. To call this operation, you
1167
1221
  # must sign in as an IAM user, assume an IAM role, or sign in as the
1168
- # root user (not recommended) in the organization's master account.
1222
+ # root user (not recommended) in the organization's management account.
1169
1223
  #
1170
1224
  # @return [Types::DescribeHealthServiceStatusForOrganizationResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
1171
1225
  #
@@ -1187,15 +1241,15 @@ module Aws::Health
1187
1241
  # Disables AWS Health from working with AWS Organizations. To call this
1188
1242
  # operation, you must sign in as an AWS Identity and Access Management
1189
1243
  # (IAM) user, assume an IAM role, or sign in as the root user (not
1190
- # recommended) in the organization's master AWS account. For more
1244
+ # recommended) in the organization's management account. For more
1191
1245
  # information, see [Aggregating AWS Health events][1] in the *AWS Health
1192
1246
  # User Guide*.
1193
1247
  #
1194
- # This operation doesn't remove the service-linked role (SLR) from the
1195
- # AWS master account in your organization. You must use the IAM console,
1196
- # API, or AWS Command Line Interface (AWS CLI) to remove the SLR. For
1197
- # more information, see [Deleting a Service-Linked Role][2] in the *IAM
1198
- # User Guide*.
1248
+ # This operation doesn't remove the service-linked role from the
1249
+ # management account in your organization. You must use the IAM console,
1250
+ # API, or AWS Command Line Interface (AWS CLI) to remove the
1251
+ # service-linked role. For more information, see [Deleting a
1252
+ # Service-Linked Role][2] in the *IAM User Guide*.
1199
1253
  #
1200
1254
  # <note markdown="1"> You can also disable the organizational feature by using the
1201
1255
  # Organizations [DisableAWSServiceAccess][3] API operation. After you
@@ -1223,18 +1277,36 @@ module Aws::Health
1223
1277
  req.send_request(options)
1224
1278
  end
1225
1279
 
1226
- # Calling this operation enables AWS Health to work with AWS
1227
- # Organizations. This applies a service-linked role (SLR) to the master
1228
- # account in the organization. To call this operation, you must sign in
1229
- # as an IAM user, assume an IAM role, or sign in as the root user (not
1230
- # recommended) in the organization's master account.
1280
+ # Enables AWS Health to work with AWS Organizations. You can use the
1281
+ # organizational view feature to aggregate events from all AWS accounts
1282
+ # in your organization in a centralized location.
1231
1283
  #
1232
- # For more information, see [Aggregating AWS Health events][1] in the
1233
- # *AWS Health User Guide*.
1284
+ # This operation also creates a service-linked role for the management
1285
+ # account in the organization.
1234
1286
  #
1287
+ # <note markdown="1"> To call this operation, you must meet the following requirements:
1235
1288
  #
1289
+ # * You must have a Business or Enterprise support plan from [AWS
1290
+ # Support][1] to use the AWS Health API. If you call the AWS Health
1291
+ # API from an AWS account that doesn't have a Business or Enterprise
1292
+ # support plan, you receive a `SubscriptionRequiredException` error.
1236
1293
  #
1237
- # [1]: https://docs.aws.amazon.com/health/latest/ug/aggregate-events.html
1294
+ # * You must have permission to call this operation from the
1295
+ # organization's management account. For example IAM policies, see
1296
+ # [AWS Health identity-based policy examples][2].
1297
+ #
1298
+ # </note>
1299
+ #
1300
+ # If you don't have the required support plan, you can instead use the
1301
+ # AWS Health console to enable the organizational view feature. For more
1302
+ # information, see [Aggregating AWS Health events][3] in the *AWS Health
1303
+ # User Guide*.
1304
+ #
1305
+ #
1306
+ #
1307
+ # [1]: http://aws.amazon.com/premiumsupport/
1308
+ # [2]: https://docs.aws.amazon.com/health/latest/ug/security_iam_id-based-policy-examples.html
1309
+ # [3]: https://docs.aws.amazon.com/health/latest/ug/aggregate-events.html
1238
1310
  #
1239
1311
  # @return [Struct] Returns an empty {Seahorse::Client::Response response}.
1240
1312
  #
@@ -1260,7 +1332,7 @@ module Aws::Health
1260
1332
  params: params,
1261
1333
  config: config)
1262
1334
  context[:gem_name] = 'aws-sdk-health'
1263
- context[:gem_version] = '1.28.0'
1335
+ context[:gem_version] = '1.33.0'
1264
1336
  Seahorse::Client::Request.new(handlers, context)
1265
1337
  end
1266
1338
 
@@ -1341,10 +1341,25 @@ module Aws::Health
1341
1341
  include Aws::Structure
1342
1342
  end
1343
1343
 
1344
- # Metadata about a type of event that is reported by AWS Health. Data
1345
- # consists of the category (for example, `issue`), the service (for
1346
- # example, `EC2`), and the event type code (for example,
1347
- # `AWS_EC2_SYSTEM_MAINTENANCE_EVENT`).
1344
+ # Contains the metadata about a type of event that is reported by AWS
1345
+ # Health. The `EventType` shows the category, service, and the event
1346
+ # type code of the event. For example, an `issue` might be the category,
1347
+ # `EC2` the service, and `AWS_EC2_SYSTEM_MAINTENANCE_EVENT` the event
1348
+ # type code.
1349
+ #
1350
+ # You can use the [DescribeEventTypes][1] API operation to return this
1351
+ # information about an event.
1352
+ #
1353
+ # You can also use the Amazon CloudWatch Events console to create a rule
1354
+ # so that you can get notified or take action when AWS Health delivers a
1355
+ # specific event to your AWS account. For more information, see [Monitor
1356
+ # for AWS Health events with Amazon CloudWatch Events][2] in the *AWS
1357
+ # Health User Guide*.
1358
+ #
1359
+ #
1360
+ #
1361
+ # [1]: https://docs.aws.amazon.com/health/latest/APIReference/API_DescribeEventTypes.html
1362
+ # [2]: https://docs.aws.amazon.com/health/latest/ug/cloudwatch-events-health.html
1348
1363
  #
1349
1364
  # @!attribute [rw] service
1350
1365
  # The AWS service that is affected by the event. For example, `EC2`,
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-health
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.28.0
4
+ version: 1.33.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2020-08-04 00:00:00.000000000 Z
11
+ date: 2021-02-18 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core
@@ -19,7 +19,7 @@ dependencies:
19
19
  version: '3'
20
20
  - - ">="
21
21
  - !ruby/object:Gem::Version
22
- version: 3.99.0
22
+ version: 3.112.0
23
23
  type: :runtime
24
24
  prerelease: false
25
25
  version_requirements: !ruby/object:Gem::Requirement
@@ -29,7 +29,7 @@ dependencies:
29
29
  version: '3'
30
30
  - - ">="
31
31
  - !ruby/object:Gem::Version
32
- version: 3.99.0
32
+ version: 3.112.0
33
33
  - !ruby/object:Gem::Dependency
34
34
  name: aws-sigv4
35
35
  requirement: !ruby/object:Gem::Requirement