aws-sdk 2.1433.0 → 2.1434.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.
@@ -99,6 +99,14 @@ declare class Connect extends Service {
99
99
  * This API is in preview release for Amazon Connect and is subject to change. Associates a security key to the instance.
100
100
  */
101
101
  associateSecurityKey(callback?: (err: AWSError, data: Connect.Types.AssociateSecurityKeyResponse) => void): Request<Connect.Types.AssociateSecurityKeyResponse, AWSError>;
102
+ /**
103
+ * Associates an agent with a traffic distribution group.
104
+ */
105
+ associateTrafficDistributionGroupUser(params: Connect.Types.AssociateTrafficDistributionGroupUserRequest, callback?: (err: AWSError, data: Connect.Types.AssociateTrafficDistributionGroupUserResponse) => void): Request<Connect.Types.AssociateTrafficDistributionGroupUserResponse, AWSError>;
106
+ /**
107
+ * Associates an agent with a traffic distribution group.
108
+ */
109
+ associateTrafficDistributionGroupUser(callback?: (err: AWSError, data: Connect.Types.AssociateTrafficDistributionGroupUserResponse) => void): Request<Connect.Types.AssociateTrafficDistributionGroupUserResponse, AWSError>;
102
110
  /**
103
111
  * Claims an available phone number to your Amazon Connect instance or traffic distribution group. You can call this API only in the same Amazon Web Services Region where the Amazon Connect instance or traffic distribution group was created. For more information about how to use this operation, see Claim a phone number in your country and Claim phone numbers to traffic distribution groups in the Amazon Connect Administrator Guide. You can call the SearchAvailablePhoneNumbers API for available phone numbers that you can claim. Call the DescribePhoneNumber API to verify the status of a previous ClaimPhoneNumber operation. If you plan to claim and release numbers frequently during a 30 day period, contact us for a service quota exception. Otherwise, it is possible you will be blocked from claiming and releasing any more numbers until 30 days past the oldest number released has expired. By default you can claim and release up to 200% of your maximum number of active phone numbers during any 30 day period. If you claim and release phone numbers using the UI or API during a rolling 30 day cycle that exceeds 200% of your phone number service level quota, you will be blocked from claiming any more numbers until 30 days past the oldest number released has expired. For example, if you already have 99 claimed numbers and a service level quota of 99 phone numbers, and in any 30 day period you release 99, claim 99, and then release 99, you will have exceeded the 200% limit. At that point you are blocked from claiming any more numbers until you open an Amazon Web Services support ticket.
104
112
  */
@@ -675,6 +683,14 @@ declare class Connect extends Service {
675
683
  * This API is in preview release for Amazon Connect and is subject to change. Deletes the specified security key.
676
684
  */
677
685
  disassociateSecurityKey(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
686
+ /**
687
+ * Disassociates an agent from a traffic distribution group.
688
+ */
689
+ disassociateTrafficDistributionGroupUser(params: Connect.Types.DisassociateTrafficDistributionGroupUserRequest, callback?: (err: AWSError, data: Connect.Types.DisassociateTrafficDistributionGroupUserResponse) => void): Request<Connect.Types.DisassociateTrafficDistributionGroupUserResponse, AWSError>;
690
+ /**
691
+ * Disassociates an agent from a traffic distribution group.
692
+ */
693
+ disassociateTrafficDistributionGroupUser(callback?: (err: AWSError, data: Connect.Types.DisassociateTrafficDistributionGroupUserResponse) => void): Request<Connect.Types.DisassociateTrafficDistributionGroupUserResponse, AWSError>;
678
694
  /**
679
695
  * Dismisses contacts from an agent’s CCP and returns the agent to an available state, which allows the agent to receive a new routed contact. Contacts can only be dismissed if they are in a MISSED, ERROR, ENDED, or REJECTED state in the Agent Event Stream.
680
696
  */
@@ -900,11 +916,11 @@ declare class Connect extends Service {
900
916
  */
901
917
  listPhoneNumbers(callback?: (err: AWSError, data: Connect.Types.ListPhoneNumbersResponse) => void): Request<Connect.Types.ListPhoneNumbersResponse, AWSError>;
902
918
  /**
903
- * Lists phone numbers claimed to your Amazon Connect instance or traffic distribution group. If the provided TargetArn is a traffic distribution group, you can call this API in both Amazon Web Services Regions associated with traffic distribution group. For more information about phone numbers, see Set Up Phone Numbers for Your Contact Center in the Amazon Connect Administrator Guide.
919
+ * Lists phone numbers claimed to your Amazon Connect instance or traffic distribution group. If the provided TargetArn is a traffic distribution group, you can call this API in both Amazon Web Services Regions associated with traffic distribution group. For more information about phone numbers, see Set Up Phone Numbers for Your Contact Center in the Amazon Connect Administrator Guide. When given an instance ARN, ListPhoneNumbersV2 returns only the phone numbers claimed to the instance. When given a traffic distribution group ARN ListPhoneNumbersV2 returns only the phone numbers claimed to the traffic distribution group.
904
920
  */
905
921
  listPhoneNumbersV2(params: Connect.Types.ListPhoneNumbersV2Request, callback?: (err: AWSError, data: Connect.Types.ListPhoneNumbersV2Response) => void): Request<Connect.Types.ListPhoneNumbersV2Response, AWSError>;
906
922
  /**
907
- * Lists phone numbers claimed to your Amazon Connect instance or traffic distribution group. If the provided TargetArn is a traffic distribution group, you can call this API in both Amazon Web Services Regions associated with traffic distribution group. For more information about phone numbers, see Set Up Phone Numbers for Your Contact Center in the Amazon Connect Administrator Guide.
923
+ * Lists phone numbers claimed to your Amazon Connect instance or traffic distribution group. If the provided TargetArn is a traffic distribution group, you can call this API in both Amazon Web Services Regions associated with traffic distribution group. For more information about phone numbers, see Set Up Phone Numbers for Your Contact Center in the Amazon Connect Administrator Guide. When given an instance ARN, ListPhoneNumbersV2 returns only the phone numbers claimed to the instance. When given a traffic distribution group ARN ListPhoneNumbersV2 returns only the phone numbers claimed to the traffic distribution group.
908
924
  */
909
925
  listPhoneNumbersV2(callback?: (err: AWSError, data: Connect.Types.ListPhoneNumbersV2Response) => void): Request<Connect.Types.ListPhoneNumbersV2Response, AWSError>;
910
926
  /**
@@ -1003,6 +1019,14 @@ declare class Connect extends Service {
1003
1019
  * Lists task templates for the specified Amazon Connect instance.
1004
1020
  */
1005
1021
  listTaskTemplates(callback?: (err: AWSError, data: Connect.Types.ListTaskTemplatesResponse) => void): Request<Connect.Types.ListTaskTemplatesResponse, AWSError>;
1022
+ /**
1023
+ * Lists traffic distribution group users.
1024
+ */
1025
+ listTrafficDistributionGroupUsers(params: Connect.Types.ListTrafficDistributionGroupUsersRequest, callback?: (err: AWSError, data: Connect.Types.ListTrafficDistributionGroupUsersResponse) => void): Request<Connect.Types.ListTrafficDistributionGroupUsersResponse, AWSError>;
1026
+ /**
1027
+ * Lists traffic distribution group users.
1028
+ */
1029
+ listTrafficDistributionGroupUsers(callback?: (err: AWSError, data: Connect.Types.ListTrafficDistributionGroupUsersResponse) => void): Request<Connect.Types.ListTrafficDistributionGroupUsersResponse, AWSError>;
1006
1030
  /**
1007
1031
  * Lists traffic distribution groups.
1008
1032
  */
@@ -1524,11 +1548,11 @@ declare class Connect extends Service {
1524
1548
  */
1525
1549
  updateTaskTemplate(callback?: (err: AWSError, data: Connect.Types.UpdateTaskTemplateResponse) => void): Request<Connect.Types.UpdateTaskTemplateResponse, AWSError>;
1526
1550
  /**
1527
- * Updates the traffic distribution for a given traffic distribution group. For more information about updating a traffic distribution group, see Update telephony traffic distribution across Amazon Web Services Regions in the Amazon Connect Administrator Guide.
1551
+ * Updates the traffic distribution for a given traffic distribution group. You can change the SignInConfig only for a default TrafficDistributionGroup. If you call UpdateTrafficDistribution with a modified SignInConfig and a non-default TrafficDistributionGroup, an InvalidRequestException is returned. For more information about updating a traffic distribution group, see Update telephony traffic distribution across Amazon Web Services Regions in the Amazon Connect Administrator Guide.
1528
1552
  */
1529
1553
  updateTrafficDistribution(params: Connect.Types.UpdateTrafficDistributionRequest, callback?: (err: AWSError, data: Connect.Types.UpdateTrafficDistributionResponse) => void): Request<Connect.Types.UpdateTrafficDistributionResponse, AWSError>;
1530
1554
  /**
1531
- * Updates the traffic distribution for a given traffic distribution group. For more information about updating a traffic distribution group, see Update telephony traffic distribution across Amazon Web Services Regions in the Amazon Connect Administrator Guide.
1555
+ * Updates the traffic distribution for a given traffic distribution group. You can change the SignInConfig only for a default TrafficDistributionGroup. If you call UpdateTrafficDistribution with a modified SignInConfig and a non-default TrafficDistributionGroup, an InvalidRequestException is returned. For more information about updating a traffic distribution group, see Update telephony traffic distribution across Amazon Web Services Regions in the Amazon Connect Administrator Guide.
1532
1556
  */
1533
1557
  updateTrafficDistribution(callback?: (err: AWSError, data: Connect.Types.UpdateTrafficDistributionResponse) => void): Request<Connect.Types.UpdateTrafficDistributionResponse, AWSError>;
1534
1558
  /**
@@ -1628,6 +1652,12 @@ declare namespace Connect {
1628
1652
  }
1629
1653
  export type AfterContactWorkTimeLimit = number;
1630
1654
  export type AgentAvailabilityTimer = "TIME_SINCE_LAST_ACTIVITY"|"TIME_SINCE_LAST_INBOUND"|string;
1655
+ export interface AgentConfig {
1656
+ /**
1657
+ * Information about traffic distributions.
1658
+ */
1659
+ Distributions: DistributionList;
1660
+ }
1631
1661
  export interface AgentContactReference {
1632
1662
  /**
1633
1663
  * The identifier of the contact in this instance of Amazon Connect.
@@ -1896,6 +1926,22 @@ declare namespace Connect {
1896
1926
  */
1897
1927
  AssociationId?: AssociationId;
1898
1928
  }
1929
+ export interface AssociateTrafficDistributionGroupUserRequest {
1930
+ /**
1931
+ * The identifier of the traffic distribution group. This can be the ID or the ARN if the API is being called in the Region where the traffic distribution group was created. The ARN must be provided if the call is from the replicated Region.
1932
+ */
1933
+ TrafficDistributionGroupId: TrafficDistributionGroupIdOrArn;
1934
+ /**
1935
+ * The identifier of the user account. This can be the ID or the ARN of the user.
1936
+ */
1937
+ UserId: UserId;
1938
+ /**
1939
+ * The identifier of the Amazon Connect instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance.
1940
+ */
1941
+ InstanceId: InstanceId;
1942
+ }
1943
+ export interface AssociateTrafficDistributionGroupUserResponse {
1944
+ }
1899
1945
  export type AssociationId = string;
1900
1946
  export interface AttachmentReference {
1901
1947
  /**
@@ -2688,7 +2734,7 @@ declare namespace Connect {
2688
2734
  */
2689
2735
  Tags?: TagMap;
2690
2736
  /**
2691
- * Whether agents with this routing profile will have their routing order calculated based on time since their last inbound contact or longest idle time.
2737
+ * Whether agents with this routing profile will have their routing order calculated based on longest idle time or time since their last inbound contact.
2692
2738
  */
2693
2739
  AgentAvailabilityTimer?: AgentAvailabilityTimer;
2694
2740
  }
@@ -3822,6 +3868,22 @@ declare namespace Connect {
3822
3868
  */
3823
3869
  AssociationId: AssociationId;
3824
3870
  }
3871
+ export interface DisassociateTrafficDistributionGroupUserRequest {
3872
+ /**
3873
+ * The identifier of the traffic distribution group. This can be the ID or the ARN if the API is being called in the Region where the traffic distribution group was created. The ARN must be provided if the call is from the replicated Region.
3874
+ */
3875
+ TrafficDistributionGroupId: TrafficDistributionGroupIdOrArn;
3876
+ /**
3877
+ * The identifier for the user. This can be the ID or the ARN of the user.
3878
+ */
3879
+ UserId: UserId;
3880
+ /**
3881
+ * The identifier of the Amazon Connect instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance.
3882
+ */
3883
+ InstanceId: InstanceId;
3884
+ }
3885
+ export interface DisassociateTrafficDistributionGroupUserResponse {
3886
+ }
3825
3887
  export interface DismissUserContactRequest {
3826
3888
  /**
3827
3889
  * The identifier of the user account.
@@ -4546,7 +4608,7 @@ declare namespace Connect {
4546
4608
  */
4547
4609
  UserArn?: ARN;
4548
4610
  /**
4549
- * The identifier for the user.
4611
+ * The identifier for the user. This can be the ID or the ARN of the user.
4550
4612
  */
4551
4613
  UserId?: AgentResourceId;
4552
4614
  }
@@ -4741,6 +4803,14 @@ declare namespace Connect {
4741
4803
  * The Amazon Resource Name (ARN) of the traffic distribution group.
4742
4804
  */
4743
4805
  Arn?: TrafficDistributionGroupArn;
4806
+ /**
4807
+ * The distribution of allowing signing in to the instance and its replica(s).
4808
+ */
4809
+ SignInConfig?: SignInConfig;
4810
+ /**
4811
+ * The distribution of agents between the instance and its replica(s).
4812
+ */
4813
+ AgentConfig?: AgentConfig;
4744
4814
  }
4745
4815
  export type Grouping = "QUEUE"|"CHANNEL"|"ROUTING_PROFILE"|string;
4746
4816
  export type GroupingV2 = string;
@@ -6136,6 +6206,30 @@ declare namespace Connect {
6136
6206
  */
6137
6207
  NextToken?: NextToken;
6138
6208
  }
6209
+ export interface ListTrafficDistributionGroupUsersRequest {
6210
+ /**
6211
+ * The identifier of the traffic distribution group. This can be the ID or the ARN if the API is being called in the Region where the traffic distribution group was created. The ARN must be provided if the call is from the replicated Region.
6212
+ */
6213
+ TrafficDistributionGroupId: TrafficDistributionGroupIdOrArn;
6214
+ /**
6215
+ * The maximum number of results to return per page.
6216
+ */
6217
+ MaxResults?: MaxResult10;
6218
+ /**
6219
+ * The token for the next set of results. Use the value returned in the previous response in the next request to retrieve the next set of results.
6220
+ */
6221
+ NextToken?: NextToken;
6222
+ }
6223
+ export interface ListTrafficDistributionGroupUsersResponse {
6224
+ /**
6225
+ * If there are additional results, this is the token for the next set of results.
6226
+ */
6227
+ NextToken?: NextToken;
6228
+ /**
6229
+ * A list of traffic distribution group users.
6230
+ */
6231
+ TrafficDistributionGroupUserSummaryList?: TrafficDistributionGroupUserSummaryList;
6232
+ }
6139
6233
  export interface ListTrafficDistributionGroupsRequest {
6140
6234
  /**
6141
6235
  * The maximum number of results to return per page.
@@ -7690,6 +7784,23 @@ declare namespace Connect {
7690
7784
  */
7691
7785
  Recipient: NotificationRecipientType;
7692
7786
  }
7787
+ export interface SignInConfig {
7788
+ /**
7789
+ * Information about traffic distributions.
7790
+ */
7791
+ Distributions: SignInDistributionList;
7792
+ }
7793
+ export interface SignInDistribution {
7794
+ /**
7795
+ * The Amazon Web Services Region of the sign in distribution.
7796
+ */
7797
+ Region: AwsRegion;
7798
+ /**
7799
+ * Whether sign in distribution is enabled.
7800
+ */
7801
+ Enabled: Boolean;
7802
+ }
7803
+ export type SignInDistributionList = SignInDistribution[];
7693
7804
  export type SingleSelectOptions = TaskTemplateSingleSelectOption[];
7694
7805
  export interface SingleSelectQuestionRuleCategoryAutomation {
7695
7806
  /**
@@ -8303,6 +8414,10 @@ declare namespace Connect {
8303
8414
  * The tags used to organize, track, or control access for this resource. For example, { "tags": {"key1":"value1", "key2":"value2"} }.
8304
8415
  */
8305
8416
  Tags?: TagMap;
8417
+ /**
8418
+ * Whether this is the default traffic distribution group created during instance replication. The default traffic distribution group cannot be deleted by the DeleteTrafficDistributionGroup API. The default traffic distribution group is deleted as part of the process for deleting a replica. You can change the SignInConfig only for a default TrafficDistributionGroup. If you call UpdateTrafficDistribution with a modified SignInConfig and a non-default TrafficDistributionGroup, an InvalidRequestException is returned.
8419
+ */
8420
+ IsDefault?: Boolean;
8306
8421
  }
8307
8422
  export type TrafficDistributionGroupArn = string;
8308
8423
  export type TrafficDistributionGroupId = string;
@@ -8329,8 +8444,19 @@ declare namespace Connect {
8329
8444
  * The status of the traffic distribution group. CREATION_IN_PROGRESS means the previous CreateTrafficDistributionGroup operation is still in progress and has not yet completed. ACTIVE means the previous CreateTrafficDistributionGroup operation has succeeded. CREATION_FAILED indicates that the previous CreateTrafficDistributionGroup operation has failed. PENDING_DELETION means the previous DeleteTrafficDistributionGroup operation is still in progress and has not yet completed. DELETION_FAILED means the previous DeleteTrafficDistributionGroup operation has failed. UPDATE_IN_PROGRESS means the previous UpdateTrafficDistributionGroup operation is still in progress and has not yet completed.
8330
8445
  */
8331
8446
  Status?: TrafficDistributionGroupStatus;
8447
+ /**
8448
+ * Whether this is the default traffic distribution group created during instance replication. The default traffic distribution group cannot be deleted by the DeleteTrafficDistributionGroup API. The default traffic distribution group is deleted as part of the process for deleting a replica.
8449
+ */
8450
+ IsDefault?: Boolean;
8332
8451
  }
8333
8452
  export type TrafficDistributionGroupSummaryList = TrafficDistributionGroupSummary[];
8453
+ export interface TrafficDistributionGroupUserSummary {
8454
+ /**
8455
+ * The identifier for the user. This can be the ID or the ARN of the user.
8456
+ */
8457
+ UserId?: UserId;
8458
+ }
8459
+ export type TrafficDistributionGroupUserSummaryList = TrafficDistributionGroupUserSummary[];
8334
8460
  export type TrafficType = "GENERAL"|"CAMPAIGN"|string;
8335
8461
  export interface TransferContactRequest {
8336
8462
  /**
@@ -8346,7 +8472,7 @@ declare namespace Connect {
8346
8472
  */
8347
8473
  QueueId?: QueueId;
8348
8474
  /**
8349
- * The identifier for the user.
8475
+ * The identifier for the user. This can be the ID or the ARN of the user.
8350
8476
  */
8351
8477
  UserId?: AgentResourceId;
8352
8478
  /**
@@ -9111,6 +9237,14 @@ declare namespace Connect {
9111
9237
  * The distribution of traffic between the instance and its replica(s).
9112
9238
  */
9113
9239
  TelephonyConfig?: TelephonyConfig;
9240
+ /**
9241
+ * The distribution of allowing signing in to the instance and its replica(s).
9242
+ */
9243
+ SignInConfig?: SignInConfig;
9244
+ /**
9245
+ * The distribution of agents between the instance and its replica(s).
9246
+ */
9247
+ AgentConfig?: AgentConfig;
9114
9248
  }
9115
9249
  export interface UpdateTrafficDistributionResponse {
9116
9250
  }
@@ -93,11 +93,11 @@ declare class ELBv2 extends Service {
93
93
  */
94
94
  deleteTargetGroup(callback?: (err: AWSError, data: ELBv2.Types.DeleteTargetGroupOutput) => void): Request<ELBv2.Types.DeleteTargetGroupOutput, AWSError>;
95
95
  /**
96
- * Deregisters the specified targets from the specified target group. After the targets are deregistered, they no longer receive traffic from the load balancer.
96
+ * Deregisters the specified targets from the specified target group. After the targets are deregistered, they no longer receive traffic from the load balancer. Note: If the specified target does not exist, the action returns successfully.
97
97
  */
98
98
  deregisterTargets(params: ELBv2.Types.DeregisterTargetsInput, callback?: (err: AWSError, data: ELBv2.Types.DeregisterTargetsOutput) => void): Request<ELBv2.Types.DeregisterTargetsOutput, AWSError>;
99
99
  /**
100
- * Deregisters the specified targets from the specified target group. After the targets are deregistered, they no longer receive traffic from the load balancer.
100
+ * Deregisters the specified targets from the specified target group. After the targets are deregistered, they no longer receive traffic from the load balancer. Note: If the specified target does not exist, the action returns successfully.
101
101
  */
102
102
  deregisterTargets(callback?: (err: AWSError, data: ELBv2.Types.DeregisterTargetsOutput) => void): Request<ELBv2.Types.DeregisterTargetsOutput, AWSError>;
103
103
  /**
@@ -269,11 +269,11 @@ declare class ELBv2 extends Service {
269
269
  */
270
270
  setRulePriorities(callback?: (err: AWSError, data: ELBv2.Types.SetRulePrioritiesOutput) => void): Request<ELBv2.Types.SetRulePrioritiesOutput, AWSError>;
271
271
  /**
272
- * Associates the specified security groups with the specified Application Load Balancer. The specified security groups override the previously associated security groups. You can't specify a security group for a Network Load Balancer or Gateway Load Balancer.
272
+ * Associates the specified security groups with the specified Application Load Balancer or Network Load Balancer. The specified security groups override the previously associated security groups. You can't perform this operation on a Network Load Balancer unless you specified a security group for the load balancer when you created it. You can't associate a security group with a Gateway Load Balancer.
273
273
  */
274
274
  setSecurityGroups(params: ELBv2.Types.SetSecurityGroupsInput, callback?: (err: AWSError, data: ELBv2.Types.SetSecurityGroupsOutput) => void): Request<ELBv2.Types.SetSecurityGroupsOutput, AWSError>;
275
275
  /**
276
- * Associates the specified security groups with the specified Application Load Balancer. The specified security groups override the previously associated security groups. You can't specify a security group for a Network Load Balancer or Gateway Load Balancer.
276
+ * Associates the specified security groups with the specified Application Load Balancer or Network Load Balancer. The specified security groups override the previously associated security groups. You can't perform this operation on a Network Load Balancer unless you specified a security group for the load balancer when you created it. You can't associate a security group with a Gateway Load Balancer.
277
277
  */
278
278
  setSecurityGroups(callback?: (err: AWSError, data: ELBv2.Types.SetSecurityGroupsOutput) => void): Request<ELBv2.Types.SetSecurityGroupsOutput, AWSError>;
279
279
  /**
@@ -602,7 +602,7 @@ declare namespace ELBv2 {
602
602
  */
603
603
  SubnetMappings?: SubnetMappings;
604
604
  /**
605
- * [Application Load Balancers] The IDs of the security groups for the load balancer.
605
+ * [Application Load Balancers and Network Load Balancers] The IDs of the security groups for the load balancer.
606
606
  */
607
607
  SecurityGroups?: SecurityGroups;
608
608
  /**
@@ -1025,6 +1025,8 @@ declare namespace ELBv2 {
1025
1025
  TargetHealthDescriptions?: TargetHealthDescriptions;
1026
1026
  }
1027
1027
  export type Description = string;
1028
+ export type EnforceSecurityGroupInboundRulesOnPrivateLinkTraffic = string;
1029
+ export type EnforceSecurityGroupInboundRulesOnPrivateLinkTrafficEnum = "on"|"off"|string;
1028
1030
  export interface FixedResponseActionConfig {
1029
1031
  /**
1030
1032
  * The message.
@@ -1188,6 +1190,10 @@ declare namespace ELBv2 {
1188
1190
  * [Application Load Balancers on Outposts] The ID of the customer-owned address pool.
1189
1191
  */
1190
1192
  CustomerOwnedIpv4Pool?: CustomerOwnedIpv4Pool;
1193
+ /**
1194
+ * Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through Amazon Web Services PrivateLink.
1195
+ */
1196
+ EnforceSecurityGroupInboundRulesOnPrivateLinkTraffic?: EnforceSecurityGroupInboundRulesOnPrivateLinkTraffic;
1191
1197
  }
1192
1198
  export interface LoadBalancerAddress {
1193
1199
  /**
@@ -1599,12 +1605,20 @@ declare namespace ELBv2 {
1599
1605
  * The IDs of the security groups.
1600
1606
  */
1601
1607
  SecurityGroups: SecurityGroups;
1608
+ /**
1609
+ * Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through Amazon Web Services PrivateLink. The default is on.
1610
+ */
1611
+ EnforceSecurityGroupInboundRulesOnPrivateLinkTraffic?: EnforceSecurityGroupInboundRulesOnPrivateLinkTrafficEnum;
1602
1612
  }
1603
1613
  export interface SetSecurityGroupsOutput {
1604
1614
  /**
1605
1615
  * The IDs of the security groups associated with the load balancer.
1606
1616
  */
1607
1617
  SecurityGroupIds?: SecurityGroups;
1618
+ /**
1619
+ * Indicates whether to evaluate inbound security group rules for traffic sent to a Network Load Balancer through Amazon Web Services PrivateLink.
1620
+ */
1621
+ EnforceSecurityGroupInboundRulesOnPrivateLinkTraffic?: EnforceSecurityGroupInboundRulesOnPrivateLinkTrafficEnum;
1608
1622
  }
1609
1623
  export interface SetSubnetsInput {
1610
1624
  /**
@@ -1620,7 +1634,7 @@ declare namespace ELBv2 {
1620
1634
  */
1621
1635
  SubnetMappings?: SubnetMappings;
1622
1636
  /**
1623
- * [Network Load Balancers] The type of IP addresses used by the subnets for your load balancer. The possible values are ipv4 (for IPv4 addresses) and dualstack (for IPv4 and IPv6 addresses). You can’t specify dualstack for a load balancer with a UDP or TCP_UDP listener. .
1637
+ * [Network Load Balancers] The type of IP addresses used by the subnets for your load balancer. The possible values are ipv4 (for IPv4 addresses) and dualstack (for IPv4 and IPv6 addresses). You can’t specify dualstack for a load balancer with a UDP or TCP_UDP listener.
1624
1638
  */
1625
1639
  IpAddressType?: IpAddressType;
1626
1640
  }
@@ -1718,7 +1732,7 @@ declare namespace ELBv2 {
1718
1732
  */
1719
1733
  Id: TargetId;
1720
1734
  /**
1721
- * The port on which the target is listening. If the target group protocol is GENEVE, the supported port is 6081. If the target type is alb, the targeted Application Load Balancer must have at least one listener whose port matches the target group port. Not used if the target is a Lambda function.
1735
+ * The port on which the target is listening. If the target group protocol is GENEVE, the supported port is 6081. If the target type is alb, the targeted Application Load Balancer must have at least one listener whose port matches the target group port. This parameter is not used if the target is a Lambda function.
1722
1736
  */
1723
1737
  Port?: Port;
1724
1738
  /**
@@ -1741,7 +1755,7 @@ declare namespace ELBv2 {
1741
1755
  */
1742
1756
  Protocol?: ProtocolEnum;
1743
1757
  /**
1744
- * The port on which the targets are listening. Not used if the target is a Lambda function.
1758
+ * The port on which the targets are listening. This parameter is not used if the target is a Lambda function.
1745
1759
  */
1746
1760
  Port?: Port;
1747
1761
  /**
@@ -1785,7 +1799,7 @@ declare namespace ELBv2 {
1785
1799
  */
1786
1800
  Matcher?: Matcher;
1787
1801
  /**
1788
- * The Amazon Resource Names (ARN) of the load balancers that route traffic to this target group.
1802
+ * The Amazon Resource Name (ARN) of the load balancer that routes traffic to this target group. You can use each target group with only one load balancer.
1789
1803
  */
1790
1804
  LoadBalancerArns?: LoadBalancerArns;
1791
1805
  /**
@@ -2271,6 +2271,10 @@ declare namespace Omics {
2271
2271
  * The number of Graphics Processing Units (GPU) specified in the task.
2272
2272
  */
2273
2273
  gpus?: GetRunTaskResponseGpusInteger;
2274
+ /**
2275
+ * The instance type for a task.
2276
+ */
2277
+ instanceType?: TaskInstanceType;
2274
2278
  }
2275
2279
  export type GetRunTaskResponseCpusInteger = number;
2276
2280
  export type GetRunTaskResponseGpusInteger = number;
@@ -2686,7 +2690,7 @@ declare namespace Omics {
2686
2690
  */
2687
2691
  ids?: ListAnnotationImportJobsRequestIdsList;
2688
2692
  /**
2689
- * Specify the pagination token from a previous request to retrieve the next page of results.
2693
+ * Specifies the pagination token from a previous request to retrieve the next page of results.
2690
2694
  */
2691
2695
  nextToken?: ListAnnotationImportJobsRequestNextTokenString;
2692
2696
  /**
@@ -2703,7 +2707,7 @@ declare namespace Omics {
2703
2707
  */
2704
2708
  annotationImportJobs?: AnnotationImportJobItems;
2705
2709
  /**
2706
- * A pagination token that's included if more results are available.
2710
+ * Specifies the pagination token from a previous request to retrieve the next page of results.
2707
2711
  */
2708
2712
  nextToken?: String;
2709
2713
  }
@@ -4231,6 +4235,7 @@ declare namespace Omics {
4231
4235
  }
4232
4236
  export type TagValue = string;
4233
4237
  export type TaskId = string;
4238
+ export type TaskInstanceType = string;
4234
4239
  export type TaskList = TaskListItem[];
4235
4240
  export interface TaskListItem {
4236
4241
  /**
@@ -4269,6 +4274,10 @@ declare namespace Omics {
4269
4274
  * The number of Graphics Processing Units (GPU) specified for the task.
4270
4275
  */
4271
4276
  gpus?: TaskListItemGpusInteger;
4277
+ /**
4278
+ * The instance type for a task.
4279
+ */
4280
+ instanceType?: TaskInstanceType;
4272
4281
  }
4273
4282
  export type TaskListItemCpusInteger = number;
4274
4283
  export type TaskListItemGpusInteger = number;
@@ -29,11 +29,11 @@ declare class Transfer extends Service {
29
29
  */
30
30
  createAgreement(callback?: (err: AWSError, data: Transfer.Types.CreateAgreementResponse) => void): Request<Transfer.Types.CreateAgreementResponse, AWSError>;
31
31
  /**
32
- * Creates the connector, which captures the parameters for an outbound connection for the AS2 or SFTP protocol. The connector is required for sending files to an externally hosted AS2 or SFTP server. For more details about AS2 connectors, see Create AS2 connectors. You must specify exactly one configuration object: either for AS2 (As2Config) or SFTP (SftpConfig).
32
+ * Creates the connector, which captures the parameters for a connection for the AS2 or SFTP protocol. For AS2, the connector is required for sending files to an externally hosted AS2 server. For SFTP, the connector is required when sending files to an SFTP server or receiving files from an SFTP server. For more details about connectors, see Create AS2 connectors and Create SFTP connectors. You must specify exactly one configuration object: either for AS2 (As2Config) or SFTP (SftpConfig).
33
33
  */
34
34
  createConnector(params: Transfer.Types.CreateConnectorRequest, callback?: (err: AWSError, data: Transfer.Types.CreateConnectorResponse) => void): Request<Transfer.Types.CreateConnectorResponse, AWSError>;
35
35
  /**
36
- * Creates the connector, which captures the parameters for an outbound connection for the AS2 or SFTP protocol. The connector is required for sending files to an externally hosted AS2 or SFTP server. For more details about AS2 connectors, see Create AS2 connectors. You must specify exactly one configuration object: either for AS2 (As2Config) or SFTP (SftpConfig).
36
+ * Creates the connector, which captures the parameters for a connection for the AS2 or SFTP protocol. For AS2, the connector is required for sending files to an externally hosted AS2 server. For SFTP, the connector is required when sending files to an SFTP server or receiving files from an SFTP server. For more details about connectors, see Create AS2 connectors and Create SFTP connectors. You must specify exactly one configuration object: either for AS2 (As2Config) or SFTP (SftpConfig).
37
37
  */
38
38
  createConnector(callback?: (err: AWSError, data: Transfer.Types.CreateConnectorResponse) => void): Request<Transfer.Types.CreateConnectorResponse, AWSError>;
39
39
  /**
@@ -365,11 +365,11 @@ declare class Transfer extends Service {
365
365
  */
366
366
  sendWorkflowStepState(callback?: (err: AWSError, data: Transfer.Types.SendWorkflowStepStateResponse) => void): Request<Transfer.Types.SendWorkflowStepStateResponse, AWSError>;
367
367
  /**
368
- * Begins a file transfer between local Amazon Web Services storage and a remote AS2 or SFTP server. For an AS2 connector, you specify the ConnectorId and one or more SendFilePaths to identify the files you want to transfer. For an SFTP connector, the file transfer can be either outbound or inbound. In both cases, you specify the ConnectorId. Depending on the direction of the transfer, you also specify the following items: If you are transferring file from a partner's SFTP server to a Transfer Family server, you specify one or more RetreiveFilePaths to identify the files you want to transfer, and a LocalDirectoryPath to specify the destination folder. If you are transferring file to a partner's SFTP server from Amazon Web Services storage, you specify one or more SendFilePaths to identify the files you want to transfer, and a RemoteDirectoryPath to specify the destination folder.
368
+ * Begins a file transfer between local Amazon Web Services storage and a remote AS2 or SFTP server. For an AS2 connector, you specify the ConnectorId and one or more SendFilePaths to identify the files you want to transfer. For an SFTP connector, the file transfer can be either outbound or inbound. In both cases, you specify the ConnectorId. Depending on the direction of the transfer, you also specify the following items: If you are transferring file from a partner's SFTP server to Amazon Web Services storage, you specify one or more RetreiveFilePaths to identify the files you want to transfer, and a LocalDirectoryPath to specify the destination folder. If you are transferring file to a partner's SFTP server from Amazon Web Services storage, you specify one or more SendFilePaths to identify the files you want to transfer, and a RemoteDirectoryPath to specify the destination folder.
369
369
  */
370
370
  startFileTransfer(params: Transfer.Types.StartFileTransferRequest, callback?: (err: AWSError, data: Transfer.Types.StartFileTransferResponse) => void): Request<Transfer.Types.StartFileTransferResponse, AWSError>;
371
371
  /**
372
- * Begins a file transfer between local Amazon Web Services storage and a remote AS2 or SFTP server. For an AS2 connector, you specify the ConnectorId and one or more SendFilePaths to identify the files you want to transfer. For an SFTP connector, the file transfer can be either outbound or inbound. In both cases, you specify the ConnectorId. Depending on the direction of the transfer, you also specify the following items: If you are transferring file from a partner's SFTP server to a Transfer Family server, you specify one or more RetreiveFilePaths to identify the files you want to transfer, and a LocalDirectoryPath to specify the destination folder. If you are transferring file to a partner's SFTP server from Amazon Web Services storage, you specify one or more SendFilePaths to identify the files you want to transfer, and a RemoteDirectoryPath to specify the destination folder.
372
+ * Begins a file transfer between local Amazon Web Services storage and a remote AS2 or SFTP server. For an AS2 connector, you specify the ConnectorId and one or more SendFilePaths to identify the files you want to transfer. For an SFTP connector, the file transfer can be either outbound or inbound. In both cases, you specify the ConnectorId. Depending on the direction of the transfer, you also specify the following items: If you are transferring file from a partner's SFTP server to Amazon Web Services storage, you specify one or more RetreiveFilePaths to identify the files you want to transfer, and a LocalDirectoryPath to specify the destination folder. If you are transferring file to a partner's SFTP server from Amazon Web Services storage, you specify one or more SendFilePaths to identify the files you want to transfer, and a RemoteDirectoryPath to specify the destination folder.
373
373
  */
374
374
  startFileTransfer(callback?: (err: AWSError, data: Transfer.Types.StartFileTransferResponse) => void): Request<Transfer.Types.StartFileTransferResponse, AWSError>;
375
375
  /**
@@ -643,7 +643,7 @@ declare namespace Transfer {
643
643
  */
644
644
  BaseDirectory: HomeDirectory;
645
645
  /**
646
- * With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key.
646
+ * Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use. For AS2 connectors With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key. For SFTP connectors Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer request. Additionally, make sure that the role provides secretsmanager:GetSecretValue permission to Secrets Manager.
647
647
  */
648
648
  AccessRole: Role;
649
649
  /**
@@ -671,7 +671,7 @@ declare namespace Transfer {
671
671
  */
672
672
  As2Config?: As2ConnectorConfig;
673
673
  /**
674
- * With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key.
674
+ * Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use. For AS2 connectors With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key. For SFTP connectors Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer request. Additionally, make sure that the role provides secretsmanager:GetSecretValue permission to Secrets Manager.
675
675
  */
676
676
  AccessRole: Role;
677
677
  /**
@@ -1228,7 +1228,7 @@ declare namespace Transfer {
1228
1228
  */
1229
1229
  BaseDirectory?: HomeDirectory;
1230
1230
  /**
1231
- * With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key.
1231
+ * Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use. For AS2 connectors With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key. For SFTP connectors Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer request. Additionally, make sure that the role provides secretsmanager:GetSecretValue permission to Secrets Manager.
1232
1232
  */
1233
1233
  AccessRole?: Role;
1234
1234
  /**
@@ -1312,7 +1312,7 @@ declare namespace Transfer {
1312
1312
  */
1313
1313
  As2Config?: As2ConnectorConfig;
1314
1314
  /**
1315
- * With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key.
1315
+ * Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use. For AS2 connectors With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key. For SFTP connectors Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer request. Additionally, make sure that the role provides secretsmanager:GetSecretValue permission to Secrets Manager.
1316
1316
  */
1317
1317
  AccessRole?: Role;
1318
1318
  /**
@@ -2551,7 +2551,7 @@ declare namespace Transfer {
2551
2551
  */
2552
2552
  ConnectorId: ConnectorId;
2553
2553
  /**
2554
- * One or more source paths for the Transfer Family server. Each string represents a source file path for one outbound file transfer. For example, DOC-EXAMPLE-BUCKET/myfile.txt .
2554
+ * One or more source paths for the Transfer Family server. Each string represents a source file path for one outbound file transfer. For example, DOC-EXAMPLE-BUCKET/myfile.txt . Replace DOC-EXAMPLE-BUCKET with one of your actual buckets.
2555
2555
  */
2556
2556
  SendFilePaths?: FilePaths;
2557
2557
  /**
@@ -2773,7 +2773,7 @@ declare namespace Transfer {
2773
2773
  */
2774
2774
  BaseDirectory?: HomeDirectory;
2775
2775
  /**
2776
- * With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key.
2776
+ * Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use. For AS2 connectors With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key. For SFTP connectors Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer request. Additionally, make sure that the role provides secretsmanager:GetSecretValue permission to Secrets Manager.
2777
2777
  */
2778
2778
  AccessRole?: Role;
2779
2779
  }
@@ -2821,7 +2821,7 @@ declare namespace Transfer {
2821
2821
  */
2822
2822
  As2Config?: As2ConnectorConfig;
2823
2823
  /**
2824
- * With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key.
2824
+ * Connectors are used to send files using either the AS2 or SFTP protocol. For the access role, provide the Amazon Resource Name (ARN) of the Identity and Access Management role to use. For AS2 connectors With AS2, you can send files by calling StartFileTransfer and specifying the file paths in the request parameter, SendFilePaths. We use the file’s parent directory (for example, for --send-file-paths /bucket/dir/file.txt, parent directory is /bucket/dir/) to temporarily store a processed AS2 message file, store the MDN when we receive them from the partner, and write a final JSON file containing relevant metadata of the transmission. So, the AccessRole needs to provide read and write access to the parent directory of the file location used in the StartFileTransfer request. Additionally, you need to provide read and write access to the parent directory of the files that you intend to send with StartFileTransfer. If you are using Basic authentication for your AS2 connector, the access role requires the secretsmanager:GetSecretValue permission for the secret. If the secret is encrypted using a customer-managed key instead of the Amazon Web Services managed key in Secrets Manager, then the role also needs the kms:Decrypt permission for that key. For SFTP connectors Make sure that the access role provides read and write access to the parent directory of the file location that's used in the StartFileTransfer request. Additionally, make sure that the role provides secretsmanager:GetSecretValue permission to Secrets Manager.
2825
2825
  */
2826
2826
  AccessRole?: Role;
2827
2827
  /**
@@ -83,7 +83,7 @@ return /******/ (function(modules) { // webpackBootstrap
83
83
  /**
84
84
  * @constant
85
85
  */
86
- VERSION: '2.1433.0',
86
+ VERSION: '2.1434.0',
87
87
 
88
88
  /**
89
89
  * @api private