cdk-lambda-subminute 2.0.285 → 2.0.287

package/node_modules/aws-sdk/clients/gamelift.d.ts

@@ -44,11 +44,11 @@ declare class GameLift extends Service {
    */
   createBuild(callback?: (err: AWSError, data: GameLift.Types.CreateBuildOutput) => void): Request<GameLift.Types.CreateBuildOutput, AWSError>;
   /**
-   * Creates a fleet of Amazon Elastic Compute Cloud (Amazon EC2) instances to host your custom game server or Realtime Servers. Use this operation to configure the computing resources for your fleet and provide instructions for running game servers on each instance. Most Amazon GameLift fleets can deploy instances to multiple locations, including the home Region (where the fleet is created) and an optional set of remote locations. Fleets that are created in the following Amazon Web Services Regions support multiple locations: us-east-1 (N. Virginia), us-west-2 (Oregon), eu-central-1 (Frankfurt), eu-west-1 (Ireland), ap-southeast-2 (Sydney), ap-northeast-1 (Tokyo), and ap-northeast-2 (Seoul). Fleets that are created in other Amazon GameLift Regions can deploy instances in the fleet's home Region only. All fleet instances use the same configuration regardless of location; however, you can adjust capacity settings and turn auto-scaling on/off for each location. To create a fleet, choose the hardware for your instances, specify a game server build or Realtime script to deploy, and provide a runtime configuration to direct Amazon GameLift how to start and run game servers on each instance in the fleet. Set permissions for inbound traffic to your game servers, and enable optional features as needed. When creating a multi-location fleet, provide a list of additional remote locations. If you need to debug your fleet, fetch logs, view performance metrics or other actions on the fleet, create the development fleet with port 22/3389 open. As a best practice, we recommend opening ports for remote access only when you need them and closing them when you're finished.  If successful, this operation creates a new Fleet resource and places it in NEW status, which prompts Amazon GameLift to initiate the fleet creation workflow.  Learn more   Setting up fleets   Debug fleet creation issues   Multi-location fleets 
+   * Creates a fleet of Amazon Elastic Compute Cloud (Amazon EC2) instances to host your custom game server or Realtime Servers. Use this operation to configure the computing resources for your fleet and provide instructions for running game servers on each instance. Most Amazon GameLift fleets can deploy instances to multiple locations, including the home Region (where the fleet is created) and an optional set of remote locations. Fleets that are created in the following Amazon Web Services Regions support multiple locations: us-east-1 (N. Virginia), us-west-2 (Oregon), eu-central-1 (Frankfurt), eu-west-1 (Ireland), ap-southeast-2 (Sydney), ap-northeast-1 (Tokyo), and ap-northeast-2 (Seoul). Fleets that are created in other Amazon GameLift Regions can deploy instances in the fleet's home Region only. All fleet instances use the same configuration regardless of location; however, you can adjust capacity settings and turn auto-scaling on/off for each location. To create a fleet, choose the hardware for your instances, specify a game server build or Realtime script to deploy, and provide a runtime configuration to direct Amazon GameLift how to start and run game servers on each instance in the fleet. Set permissions for inbound traffic to your game servers, and enable optional features as needed. When creating a multi-location fleet, provide a list of additional remote locations. If you need to debug your fleet, fetch logs, view performance metrics or other actions on the fleet, create the development fleet with port 22/3389 open. As a best practice, we recommend opening ports for remote access only when you need them and closing them when you're finished.  If successful, this operation creates a new Fleet resource and places it in NEW status, which prompts Amazon GameLift to initiate the fleet creation workflow. You can track fleet creation by checking fleet status using DescribeFleetAttributes and DescribeFleetLocationAttributes/, or by monitoring fleet creation events using DescribeFleetEvents.  When the fleet status changes to ACTIVE, you can enable automatic scaling with PutScalingPolicy and set capacity for the home Region with UpdateFleetCapacity. When the status of each remote location reaches ACTIVE, you can set capacity by location using UpdateFleetCapacity.  Learn more   Setting up fleets   Debug fleet creation issues   Multi-location fleets 
    */
   createFleet(params: GameLift.Types.CreateFleetInput, callback?: (err: AWSError, data: GameLift.Types.CreateFleetOutput) => void): Request<GameLift.Types.CreateFleetOutput, AWSError>;
   /**
-   * Creates a fleet of Amazon Elastic Compute Cloud (Amazon EC2) instances to host your custom game server or Realtime Servers. Use this operation to configure the computing resources for your fleet and provide instructions for running game servers on each instance. Most Amazon GameLift fleets can deploy instances to multiple locations, including the home Region (where the fleet is created) and an optional set of remote locations. Fleets that are created in the following Amazon Web Services Regions support multiple locations: us-east-1 (N. Virginia), us-west-2 (Oregon), eu-central-1 (Frankfurt), eu-west-1 (Ireland), ap-southeast-2 (Sydney), ap-northeast-1 (Tokyo), and ap-northeast-2 (Seoul). Fleets that are created in other Amazon GameLift Regions can deploy instances in the fleet's home Region only. All fleet instances use the same configuration regardless of location; however, you can adjust capacity settings and turn auto-scaling on/off for each location. To create a fleet, choose the hardware for your instances, specify a game server build or Realtime script to deploy, and provide a runtime configuration to direct Amazon GameLift how to start and run game servers on each instance in the fleet. Set permissions for inbound traffic to your game servers, and enable optional features as needed. When creating a multi-location fleet, provide a list of additional remote locations. If you need to debug your fleet, fetch logs, view performance metrics or other actions on the fleet, create the development fleet with port 22/3389 open. As a best practice, we recommend opening ports for remote access only when you need them and closing them when you're finished.  If successful, this operation creates a new Fleet resource and places it in NEW status, which prompts Amazon GameLift to initiate the fleet creation workflow.  Learn more   Setting up fleets   Debug fleet creation issues   Multi-location fleets 
+   * Creates a fleet of Amazon Elastic Compute Cloud (Amazon EC2) instances to host your custom game server or Realtime Servers. Use this operation to configure the computing resources for your fleet and provide instructions for running game servers on each instance. Most Amazon GameLift fleets can deploy instances to multiple locations, including the home Region (where the fleet is created) and an optional set of remote locations. Fleets that are created in the following Amazon Web Services Regions support multiple locations: us-east-1 (N. Virginia), us-west-2 (Oregon), eu-central-1 (Frankfurt), eu-west-1 (Ireland), ap-southeast-2 (Sydney), ap-northeast-1 (Tokyo), and ap-northeast-2 (Seoul). Fleets that are created in other Amazon GameLift Regions can deploy instances in the fleet's home Region only. All fleet instances use the same configuration regardless of location; however, you can adjust capacity settings and turn auto-scaling on/off for each location. To create a fleet, choose the hardware for your instances, specify a game server build or Realtime script to deploy, and provide a runtime configuration to direct Amazon GameLift how to start and run game servers on each instance in the fleet. Set permissions for inbound traffic to your game servers, and enable optional features as needed. When creating a multi-location fleet, provide a list of additional remote locations. If you need to debug your fleet, fetch logs, view performance metrics or other actions on the fleet, create the development fleet with port 22/3389 open. As a best practice, we recommend opening ports for remote access only when you need them and closing them when you're finished.  If successful, this operation creates a new Fleet resource and places it in NEW status, which prompts Amazon GameLift to initiate the fleet creation workflow. You can track fleet creation by checking fleet status using DescribeFleetAttributes and DescribeFleetLocationAttributes/, or by monitoring fleet creation events using DescribeFleetEvents.  When the fleet status changes to ACTIVE, you can enable automatic scaling with PutScalingPolicy and set capacity for the home Region with UpdateFleetCapacity. When the status of each remote location reaches ACTIVE, you can set capacity by location using UpdateFleetCapacity.  Learn more   Setting up fleets   Debug fleet creation issues   Multi-location fleets 
    */
   createFleet(callback?: (err: AWSError, data: GameLift.Types.CreateFleetOutput) => void): Request<GameLift.Types.CreateFleetOutput, AWSError>;
   /**
@@ -196,11 +196,11 @@ declare class GameLift extends Service {
    */
   deleteGameSessionQueue(callback?: (err: AWSError, data: GameLift.Types.DeleteGameSessionQueueOutput) => void): Request<GameLift.Types.DeleteGameSessionQueueOutput, AWSError>;
   /**
-   * Deletes a custom location. Before deleting a custom location, review any fleets currently using the custom location and deregister the location if it is in use. For more information see, DeregisterCompute.
+   * Deletes a custom location. Before deleting a custom location, review any fleets currently using the custom location and deregister the location if it is in use. For more information, see DeregisterCompute.
    */
   deleteLocation(params: GameLift.Types.DeleteLocationInput, callback?: (err: AWSError, data: GameLift.Types.DeleteLocationOutput) => void): Request<GameLift.Types.DeleteLocationOutput, AWSError>;
   /**
-   * Deletes a custom location. Before deleting a custom location, review any fleets currently using the custom location and deregister the location if it is in use. For more information see, DeregisterCompute.
+   * Deletes a custom location. Before deleting a custom location, review any fleets currently using the custom location and deregister the location if it is in use. For more information, see DeregisterCompute.
    */
   deleteLocation(callback?: (err: AWSError, data: GameLift.Types.DeleteLocationOutput) => void): Request<GameLift.Types.DeleteLocationOutput, AWSError>;
   /**
@@ -853,7 +853,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player delivering the response. This parameter can include one or multiple player IDs.
      */
-    PlayerIds: StringList;
+    PlayerIds: PlayerIdsForAcceptMatch;
     /**
      * Player response to the proposed match.
      */
@@ -1152,11 +1152,11 @@ declare namespace GameLift {
      */
     Description?: NonZeroAndMaxString;
     /**
-     * The unique identifier for a custom game server build to be deployed on fleet instances. You can use either the build ID or ARN. The build must be uploaded to Amazon GameLift and in READY status. This fleet property cannot be changed later.
+     * The unique identifier for a custom game server build to be deployed on fleet instances. You can use either the build ID or ARN. The build must be uploaded to Amazon GameLift and in READY status. This fleet property can't be changed after the fleet is created.
      */
     BuildId?: BuildIdOrArn;
     /**
-     * The unique identifier for a Realtime configuration script to be deployed on fleet instances. You can use either the script ID or ARN. Scripts must be uploaded to Amazon GameLift prior to creating the fleet. This fleet property cannot be changed later.
+     * The unique identifier for a Realtime configuration script to be deployed on fleet instances. You can use either the script ID or ARN. Scripts must be uploaded to Amazon GameLift prior to creating the fleet. This fleet property can't be changed after the fleet is created.
      */
     ScriptId?: ScriptIdOrArn;
     /**
@@ -1204,11 +1204,11 @@ declare namespace GameLift {
      */
     PeerVpcId?: NonZeroAndMaxString;
     /**
-     * Indicates whether to use On-Demand or Spot instances for this fleet. By default, this property is set to ON_DEMAND. Learn more about when to use  On-Demand versus Spot Instances. This property cannot be changed after the fleet is created.
+     * Indicates whether to use On-Demand or Spot instances for this fleet. By default, this property is set to ON_DEMAND. Learn more about when to use  On-Demand versus Spot Instances. This fleet property can't be changed after the fleet is created.
      */
     FleetType?: FleetType;
     /**
-     * A unique identifier for an IAM role that manages access to your Amazon Web Services services. With an instance role ARN set, any application that runs on an instance in this fleet can assume the role, including install scripts, server processes, and daemons (background processes). Create a role or look up a role's ARN by using the IAM dashboard in the Amazon Web Services Management Console. Learn more about using on-box credentials for your game servers at  Access external resources from a game server. This property cannot be changed after the fleet is created.
+     * A unique identifier for an IAM role with access permissions to other Amazon Web Services services. Any application that runs on an instance in the fleet--including install scripts, server processes, and other processes--can use these permissions to interact with Amazon Web Services resources that you own or have access to. For more information about using the role with your game server builds, see  Communicate with other Amazon Web Services resources from your fleets. This fleet property can't be changed after the fleet is created.
      */
     InstanceRoleArn?: NonEmptyString;
     /**
@@ -1231,6 +1231,10 @@ declare namespace GameLift {
      * Amazon GameLift Anywhere configuration options.
      */
     AnywhereConfiguration?: AnywhereConfiguration;
+    /**
+     * Prompts Amazon GameLift to generate a shared credentials file for the IAM role defined in InstanceRoleArn. The shared credentials file is stored on each fleet instance and refreshed as needed. Use shared credentials for applications that are deployed along with the game server executable, if the game server is integrated with server SDK version 5.x. For more information about using shared credentials, see  Communicate with other Amazon Web Services resources from your fleets.
+     */
+    InstanceRoleCredentialsProvider?: InstanceRoleCredentialsProvider;
   }
   export interface CreateFleetLocationsInput {
     /**
@@ -1522,7 +1526,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player. Player IDs are developer-defined.
      */
-    PlayerId: NonZeroAndMaxString;
+    PlayerId: PlayerId;
     /**
      * Developer-defined information related to a player. Amazon GameLift does not use this data, so it can be formatted as needed for use in the game.
      */
@@ -2305,7 +2309,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player to retrieve player sessions for.
      */
-    PlayerId?: NonZeroAndMaxString;
+    PlayerId?: PlayerId;
     /**
      * A unique identifier for a player session to retrieve.
      */
@@ -2413,7 +2417,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player to associate with the player session.
      */
-    PlayerId?: NonZeroAndMaxString;
+    PlayerId?: PlayerId;
     /**
      * Developer-defined information related to a player. Amazon GameLift does not use this data, so it can be formatted as needed for use in the game.
      */
@@ -2523,7 +2527,7 @@ declare namespace GameLift {
      */
     FleetArn?: FleetArn;
     /**
-     * Indicates whether to use On-Demand or Spot instances for this fleet. By default, this property is set to ON_DEMAND. Learn more about when to use  On-Demand versus Spot Instances. This property cannot be changed after the fleet is created.
+     * Indicates whether to use On-Demand or Spot instances for this fleet. By default, this property is set to ON_DEMAND. Learn more about when to use  On-Demand versus Spot Instances. This fleet property can't be changed after the fleet is created.
      */
     FleetType?: FleetType;
     /**
@@ -2596,7 +2600,7 @@ declare namespace GameLift {
      */
     StoppedActions?: FleetActionList;
     /**
-     * A unique identifier for an IAM role that manages access to your Amazon Web Services services. With an instance role ARN set, any application that runs on an instance in this fleet can assume the role, including install scripts, server processes, and daemons (background processes). Create a role or look up a role's ARN by using the IAM dashboard in the Amazon Web Services Management Console. Learn more about using on-box credentials for your game servers at  Access external resources from a game server.
+     * A unique identifier for an IAM role with access permissions to other Amazon Web Services services. Any application that runs on an instance in the fleet--including install scripts, server processes, and other processes--can use these permissions to interact with Amazon Web Services resources that you own or have access to. For more information about using the role with your game server builds, see  Communicate with other Amazon Web Services resources from your fleets.
      */
     InstanceRoleArn?: NonEmptyString;
     CertificateConfiguration?: CertificateConfiguration;
@@ -2605,6 +2609,10 @@ declare namespace GameLift {
      */
     ComputeType?: ComputeType;
     AnywhereConfiguration?: AnywhereConfiguration;
+    /**
+     * Indicates that fleet instances maintain a shared credentials file for the IAM role defined in InstanceRoleArn. Shared credentials allow applications that are deployed with the game server executable to communicate with other Amazon Web Services resources. This property is used only when the game server is integrated with the server SDK version 5.x. For more information about using shared credentials, see  Communicate with other Amazon Web Services resources from your fleets.
+     */
+    InstanceRoleCredentialsProvider?: InstanceRoleCredentialsProvider;
   }
   export type FleetAttributesList = FleetAttributes[];
   export interface FleetCapacity {
@@ -3252,6 +3260,7 @@ declare namespace GameLift {
   export type InstanceDefinitions = InstanceDefinition[];
   export type InstanceId = string;
   export type InstanceList = Instance[];
+  export type InstanceRoleCredentialsProvider = "SHARED_CREDENTIAL_FILE"|string;
   export type InstanceStatus = "PENDING"|"ACTIVE"|"TERMINATING"|string;
   export type Integer = number;
   export type IpAddress = string;
@@ -3267,7 +3276,7 @@ declare namespace GameLift {
     /**
      * A range of allowed IP addresses. This value must be expressed in CIDR notation. Example: "000.000.000.000/[subnet mask]" or optionally the shortened version "0.0.0.0/[subnet mask]".
      */
-    IpRange: NonBlankString;
+    IpRange: IpRange;
     /**
      * The network communication protocol used by the fleet.
      */
@@ -3275,6 +3284,7 @@ declare namespace GameLift {
   }
   export type IpPermissionsList = IpPermission[];
   export type IpProtocol = "TCP"|"UDP"|string;
+  export type IpRange = string;
   export type LargeGameSessionData = string;
   export type LatencyMap = {[key: string]: PositiveInteger};
   export type LaunchParametersStringModel = string;
@@ -3563,7 +3573,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player 
      */
-    PlayerId?: NonZeroAndMaxString;
+    PlayerId?: PlayerId;
     /**
      * A unique identifier for a player session
      */
@@ -3724,7 +3734,6 @@ declare namespace GameLift {
   export type MetricGroupList = MetricGroup[];
   export type MetricName = "ActivatingGameSessions"|"ActiveGameSessions"|"ActiveInstances"|"AvailableGameSessions"|"AvailablePlayerSessions"|"CurrentPlayerSessions"|"IdleInstances"|"PercentAvailableGameSessions"|"PercentIdleInstances"|"QueueDepth"|"WaitTime"|"ConcurrentActivatableGameSessions"|string;
   export type NonBlankAndLengthConstraintString = string;
-  export type NonBlankString = string;
   export type NonEmptyString = string;
   export type NonNegativeDouble = number;
   export type NonNegativeLimitedLengthDouble = string;
@@ -3734,7 +3743,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player that is associated with this player session.
      */
-    PlayerId?: NonZeroAndMaxString;
+    PlayerId?: PlayerId;
     /**
      * A unique identifier for a player session.
      */
@@ -3745,7 +3754,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player
      */
-    PlayerId?: NonZeroAndMaxString;
+    PlayerId?: PlayerId;
     /**
      * A collection of key:value pairs containing player information for use in matchmaking. Player attribute keys must match the playerAttributes used in a matchmaking rule set. Example: "PlayerAttributes": {"skill": {"N": "23"}, "gameMode": {"S": "deathmatch"}}. You can provide up to 10 PlayerAttributes.
      */
@@ -3765,12 +3774,14 @@ declare namespace GameLift {
   export type PlayerAttributeStringList = PlayerAttributeString[];
   export type PlayerData = string;
   export type PlayerDataMap = {[key: string]: PlayerData};
-  export type PlayerIdList = NonZeroAndMaxString[];
+  export type PlayerId = string;
+  export type PlayerIdList = PlayerId[];
+  export type PlayerIdsForAcceptMatch = PlayerId[];
   export interface PlayerLatency {
     /**
      * A unique identifier for a player associated with the latency data.
      */
-    PlayerId?: NonZeroAndMaxString;
+    PlayerId?: PlayerId;
     /**
      * Name of the Region that is associated with the latency value.
      */
@@ -3801,7 +3812,7 @@ declare namespace GameLift {
     /**
      * A unique identifier for a player that is associated with this player session.
      */
-    PlayerId?: NonZeroAndMaxString;
+    PlayerId?: PlayerId;
     /**
      * A unique identifier for the game session that the player session is connected to.
      */

package/node_modules/aws-sdk/clients/globalaccelerator.d.ts

@@ -51,6 +51,14 @@ declare class GlobalAccelerator extends Service {
    * Create an accelerator. An accelerator includes one or more listeners that process inbound connections and direct traffic to one or more endpoint groups, each of which includes endpoints, such as Network Load Balancers.   Global Accelerator is a global service that supports endpoints in multiple Amazon Web Services Regions but you must specify the US West (Oregon) Region to create, update, or otherwise work with accelerators. That is, for example, specify --region us-west-2 on Amazon Web Services CLI commands. 
    */
   createAccelerator(callback?: (err: AWSError, data: GlobalAccelerator.Types.CreateAcceleratorResponse) => void): Request<GlobalAccelerator.Types.CreateAcceleratorResponse, AWSError>;
+  /**
+   * Create a cross-account attachment in Global Accelerator. You create a cross-account attachment to specify the principals who have permission to add to accelerators in their own account the resources in your account that you also list in the attachment. A principal can be an Amazon Web Services account number or the Amazon Resource Name (ARN) for an accelerator. For account numbers that are listed as principals, to add a resource listed in the attachment to an accelerator, you must sign in to an account specified as a principal. Then you can add the resources that are listed to any of your accelerators. If an accelerator ARN is listed in the cross-account attachment as a principal, anyone with permission to make updates to the accelerator can add as endpoints resources that are listed in the attachment. 
+   */
+  createCrossAccountAttachment(params: GlobalAccelerator.Types.CreateCrossAccountAttachmentRequest, callback?: (err: AWSError, data: GlobalAccelerator.Types.CreateCrossAccountAttachmentResponse) => void): Request<GlobalAccelerator.Types.CreateCrossAccountAttachmentResponse, AWSError>;
+  /**
+   * Create a cross-account attachment in Global Accelerator. You create a cross-account attachment to specify the principals who have permission to add to accelerators in their own account the resources in your account that you also list in the attachment. A principal can be an Amazon Web Services account number or the Amazon Resource Name (ARN) for an accelerator. For account numbers that are listed as principals, to add a resource listed in the attachment to an accelerator, you must sign in to an account specified as a principal. Then you can add the resources that are listed to any of your accelerators. If an accelerator ARN is listed in the cross-account attachment as a principal, anyone with permission to make updates to the accelerator can add as endpoints resources that are listed in the attachment. 
+   */
+  createCrossAccountAttachment(callback?: (err: AWSError, data: GlobalAccelerator.Types.CreateCrossAccountAttachmentResponse) => void): Request<GlobalAccelerator.Types.CreateCrossAccountAttachmentResponse, AWSError>;
   /**
    * Create a custom routing accelerator. A custom routing accelerator directs traffic to one of possibly thousands of Amazon EC2 instance destinations running in a single or multiple virtual private clouds (VPC) subnet endpoints. Be aware that, by default, all destination EC2 instances in a VPC subnet endpoint cannot receive traffic. To enable all destinations to receive traffic, or to specify individual port mappings that can receive traffic, see the  AllowCustomRoutingTraffic operation.  Global Accelerator is a global service that supports endpoints in multiple Amazon Web Services Regions but you must specify the US West (Oregon) Region to create, update, or otherwise work with accelerators. That is, for example, specify --region us-west-2 on Amazon Web Services CLI commands. 
    */
@@ -99,6 +107,14 @@ declare class GlobalAccelerator extends Service {
    * Delete an accelerator. Before you can delete an accelerator, you must disable it and remove all dependent resources (listeners and endpoint groups). To disable the accelerator, update the accelerator to set Enabled to false.  When you create an accelerator, by default, Global Accelerator provides you with a set of two static IP addresses. Alternatively, you can bring your own IP address ranges to Global Accelerator and assign IP addresses from those ranges.  The IP addresses are assigned to your accelerator for as long as it exists, even if you disable the accelerator and it no longer accepts or routes traffic. However, when you delete an accelerator, you lose the static IP addresses that are assigned to the accelerator, so you can no longer route traffic by using them. As a best practice, ensure that you have permissions in place to avoid inadvertently deleting accelerators. You can use IAM policies with Global Accelerator to limit the users who have permissions to delete an accelerator. For more information, see Identity and access management in the Global Accelerator Developer Guide. 
    */
   deleteAccelerator(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
+  /**
+   * Delete a cross-account attachment. When you delete an attachment, Global Accelerator revokes the permission to use the resources in the attachment from all principals in the list of principals. Global Accelerator revokes the permission for specific resources by doing the following:   If the principal is an account ID, Global Accelerator reviews every accelerator in the account and removes cross-account endpoints from all accelerators.   If the principal is an accelerator, Global Accelerator reviews just that accelerator and removes cross-account endpoints from it.   If there are overlapping permissions provided by multiple cross-account attachments, Global Accelerator only removes endpoints if there are no current cross-account attachments that provide access permission. For example, if you delete a cross-account attachment that lists an accelerator as a principal, but another cross-account attachment includes the account ID that owns that accelerator, endpoints will not be removed from the accelerator.
+   */
+  deleteCrossAccountAttachment(params: GlobalAccelerator.Types.DeleteCrossAccountAttachmentRequest, callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
+  /**
+   * Delete a cross-account attachment. When you delete an attachment, Global Accelerator revokes the permission to use the resources in the attachment from all principals in the list of principals. Global Accelerator revokes the permission for specific resources by doing the following:   If the principal is an account ID, Global Accelerator reviews every accelerator in the account and removes cross-account endpoints from all accelerators.   If the principal is an accelerator, Global Accelerator reviews just that accelerator and removes cross-account endpoints from it.   If there are overlapping permissions provided by multiple cross-account attachments, Global Accelerator only removes endpoints if there are no current cross-account attachments that provide access permission. For example, if you delete a cross-account attachment that lists an accelerator as a principal, but another cross-account attachment includes the account ID that owns that accelerator, endpoints will not be removed from the accelerator.
+   */
+  deleteCrossAccountAttachment(callback?: (err: AWSError, data: {}) => void): Request<{}, AWSError>;
   /**
    * Delete a custom routing accelerator. Before you can delete an accelerator, you must disable it and remove all dependent resources (listeners and endpoint groups). To disable the accelerator, update the accelerator to set Enabled to false.  When you create a custom routing accelerator, by default, Global Accelerator provides you with a set of two static IP addresses.  The IP addresses are assigned to your accelerator for as long as it exists, even if you disable the accelerator and it no longer accepts or routes traffic. However, when you delete an accelerator, you lose the static IP addresses that are assigned to the accelerator, so you can no longer route traffic by using them. As a best practice, ensure that you have permissions in place to avoid inadvertently deleting accelerators. You can use IAM policies with Global Accelerator to limit the users who have permissions to delete an accelerator. For more information, see Identity and access management in the Global Accelerator Developer Guide. 
    */
@@ -171,6 +187,14 @@ declare class GlobalAccelerator extends Service {
    * Describe the attributes of an accelerator. 
    */
   describeAcceleratorAttributes(callback?: (err: AWSError, data: GlobalAccelerator.Types.DescribeAcceleratorAttributesResponse) => void): Request<GlobalAccelerator.Types.DescribeAcceleratorAttributesResponse, AWSError>;
+  /**
+   * Gets configuration information about a cross-account attachment.
+   */
+  describeCrossAccountAttachment(params: GlobalAccelerator.Types.DescribeCrossAccountAttachmentRequest, callback?: (err: AWSError, data: GlobalAccelerator.Types.DescribeCrossAccountAttachmentResponse) => void): Request<GlobalAccelerator.Types.DescribeCrossAccountAttachmentResponse, AWSError>;
+  /**
+   * Gets configuration information about a cross-account attachment.
+   */
+  describeCrossAccountAttachment(callback?: (err: AWSError, data: GlobalAccelerator.Types.DescribeCrossAccountAttachmentResponse) => void): Request<GlobalAccelerator.Types.DescribeCrossAccountAttachmentResponse, AWSError>;
   /**
    * Describe a custom routing accelerator. 
    */
@@ -235,6 +259,30 @@ declare class GlobalAccelerator extends Service {
    * Lists the IP address ranges that were specified in calls to ProvisionByoipCidr, including the current state and a history of state changes.
    */
   listByoipCidrs(callback?: (err: AWSError, data: GlobalAccelerator.Types.ListByoipCidrsResponse) => void): Request<GlobalAccelerator.Types.ListByoipCidrsResponse, AWSError>;
+  /**
+   * List the cross-account attachments that have been created in Global Accelerator.
+   */
+  listCrossAccountAttachments(params: GlobalAccelerator.Types.ListCrossAccountAttachmentsRequest, callback?: (err: AWSError, data: GlobalAccelerator.Types.ListCrossAccountAttachmentsResponse) => void): Request<GlobalAccelerator.Types.ListCrossAccountAttachmentsResponse, AWSError>;
+  /**
+   * List the cross-account attachments that have been created in Global Accelerator.
+   */
+  listCrossAccountAttachments(callback?: (err: AWSError, data: GlobalAccelerator.Types.ListCrossAccountAttachmentsResponse) => void): Request<GlobalAccelerator.Types.ListCrossAccountAttachmentsResponse, AWSError>;
+  /**
+   * List the accounts that have cross-account endpoints.
+   */
+  listCrossAccountResourceAccounts(params: GlobalAccelerator.Types.ListCrossAccountResourceAccountsRequest, callback?: (err: AWSError, data: GlobalAccelerator.Types.ListCrossAccountResourceAccountsResponse) => void): Request<GlobalAccelerator.Types.ListCrossAccountResourceAccountsResponse, AWSError>;
+  /**
+   * List the accounts that have cross-account endpoints.
+   */
+  listCrossAccountResourceAccounts(callback?: (err: AWSError, data: GlobalAccelerator.Types.ListCrossAccountResourceAccountsResponse) => void): Request<GlobalAccelerator.Types.ListCrossAccountResourceAccountsResponse, AWSError>;
+  /**
+   * List the cross-account endpoints available to add to an accelerator.
+   */
+  listCrossAccountResources(params: GlobalAccelerator.Types.ListCrossAccountResourcesRequest, callback?: (err: AWSError, data: GlobalAccelerator.Types.ListCrossAccountResourcesResponse) => void): Request<GlobalAccelerator.Types.ListCrossAccountResourcesResponse, AWSError>;
+  /**
+   * List the cross-account endpoints available to add to an accelerator.
+   */
+  listCrossAccountResources(callback?: (err: AWSError, data: GlobalAccelerator.Types.ListCrossAccountResourcesResponse) => void): Request<GlobalAccelerator.Types.ListCrossAccountResourcesResponse, AWSError>;
   /**
    * List the custom routing accelerators for an Amazon Web Services account. 
    */
@@ -355,6 +403,14 @@ declare class GlobalAccelerator extends Service {
    * Update the attributes for an accelerator. 
    */
   updateAcceleratorAttributes(callback?: (err: AWSError, data: GlobalAccelerator.Types.UpdateAcceleratorAttributesResponse) => void): Request<GlobalAccelerator.Types.UpdateAcceleratorAttributesResponse, AWSError>;
+  /**
+   * Update a cross-account attachment to add or remove principals or resources. When you update an attachment to remove a principal (account ID or accelerator) or a resource, Global Accelerator revokes the permission for specific resources by doing the following:   If the principal is an account ID, Global Accelerator reviews every accelerator in the account and removes cross-account endpoints from all accelerators.   If the principal is an accelerator, Global Accelerator reviews just that accelerator and removes cross-account endpoints from it.   If there are overlapping permissions provided by multiple cross-account attachments, Global Accelerator only removes endpoints if there are no current cross-account attachments that provide access permission. For example, if you delete a cross-account attachment that lists an accelerator as a principal, but another cross-account attachment includes the account ID that owns that accelerator, endpoints will not be removed from the accelerator.
+   */
+  updateCrossAccountAttachment(params: GlobalAccelerator.Types.UpdateCrossAccountAttachmentRequest, callback?: (err: AWSError, data: GlobalAccelerator.Types.UpdateCrossAccountAttachmentResponse) => void): Request<GlobalAccelerator.Types.UpdateCrossAccountAttachmentResponse, AWSError>;
+  /**
+   * Update a cross-account attachment to add or remove principals or resources. When you update an attachment to remove a principal (account ID or accelerator) or a resource, Global Accelerator revokes the permission for specific resources by doing the following:   If the principal is an account ID, Global Accelerator reviews every accelerator in the account and removes cross-account endpoints from all accelerators.   If the principal is an accelerator, Global Accelerator reviews just that accelerator and removes cross-account endpoints from it.   If there are overlapping permissions provided by multiple cross-account attachments, Global Accelerator only removes endpoints if there are no current cross-account attachments that provide access permission. For example, if you delete a cross-account attachment that lists an accelerator as a principal, but another cross-account attachment includes the account ID that owns that accelerator, endpoints will not be removed from the accelerator.
+   */
+  updateCrossAccountAttachment(callback?: (err: AWSError, data: GlobalAccelerator.Types.UpdateCrossAccountAttachmentResponse) => void): Request<GlobalAccelerator.Types.UpdateCrossAccountAttachmentResponse, AWSError>;
   /**
    * Update a custom routing accelerator. 
    */
@@ -552,6 +608,36 @@ declare namespace GlobalAccelerator {
      */
     AllowAllTrafficToEndpoint?: GenericBoolean;
   }
+  export interface Attachment {
+    /**
+     * The Amazon Resource Name (ARN) of the cross-account attachment.
+     */
+    AttachmentArn?: GenericString;
+    /**
+     * The name of the cross-account attachment.
+     */
+    Name?: AttachmentName;
+    /**
+     * The principals included in the cross-account attachment.
+     */
+    Principals?: Principals;
+    /**
+     * The resources included in the cross-account attachment.
+     */
+    Resources?: Resources;
+    /**
+     * The date and time that the cross-account attachment was last modified.
+     */
+    LastModifiedTime?: Timestamp;
+    /**
+     * The date and time that the cross-account attachment was created.
+     */
+    CreatedTime?: Timestamp;
+  }
+  export type AttachmentName = string;
+  export type Attachments = Attachment[];
+  export type AwsAccountId = string;
+  export type AwsAccountIds = AwsAccountId[];
   export interface ByoipCidr {
     /**
      * The address range, in CIDR notation.
@@ -622,6 +708,34 @@ declare namespace GlobalAccelerator {
      */
     Accelerator?: Accelerator;
   }
+  export interface CreateCrossAccountAttachmentRequest {
+    /**
+     * The name of the cross-account attachment. 
+     */
+    Name: AttachmentName;
+    /**
+     * The principals to list in the cross-account attachment. A principal can be an Amazon Web Services account number or the Amazon Resource Name (ARN) for an accelerator. 
+     */
+    Principals?: Principals;
+    /**
+     * The Amazon Resource Names (ARNs) for the resources to list in the cross-account attachment. A resource can be any supported Amazon Web Services resource type for Global Accelerator. 
+     */
+    Resources?: Resources;
+    /**
+     * A unique, case-sensitive identifier that you provide to ensure the idempotency—that is, the uniqueness—of the request.
+     */
+    IdempotencyToken: IdempotencyToken;
+    /**
+     * Create tags for cross-account attachment. For more information, see Tagging in Global Accelerator in the Global Accelerator Developer Guide.
+     */
+    Tags?: Tags;
+  }
+  export interface CreateCrossAccountAttachmentResponse {
+    /**
+     * Information about the cross-account attachment.
+     */
+    CrossAccountAttachment?: Attachment;
+  }
   export interface CreateCustomRoutingAcceleratorRequest {
     /**
      * The name of a custom routing accelerator. The name can have a maximum of 64 characters, must contain only alphanumeric characters or hyphens (-), and must not begin or end with a hyphen.
@@ -778,6 +892,17 @@ declare namespace GlobalAccelerator {
      */
     Listener?: Listener;
   }
+  export interface CrossAccountResource {
+    /**
+     * The endpoint ID for the endpoint that is listed in a cross-account attachment and can be added to an accelerator by specified principals.
+     */
+    EndpointId?: GenericString;
+    /**
+     * The Amazon Resource Name (ARN) of the cross-account attachment that specifies the endpoints (resources) that can be added to accelerators and principals that have permission to add the endpoints to accelerators.
+     */
+    AttachmentArn?: GenericString;
+  }
+  export type CrossAccountResources = CrossAccountResource[];
   export interface CustomRoutingAccelerator {
     /**
      * The Amazon Resource Name (ARN) of the custom routing accelerator.
@@ -868,6 +993,10 @@ declare namespace GlobalAccelerator {
      * An ID for the endpoint. For custom routing accelerators, this is the virtual private cloud (VPC) subnet ID. 
      */
     EndpointId?: GenericString;
+    /**
+     * The Amazon Resource Name (ARN) of the cross-account attachment that specifies the endpoints (resources) that can be added to accelerators and principals that have permission to add the endpoints to accelerators.
+     */
+    AttachmentArn?: GenericString;
   }
   export type CustomRoutingEndpointConfigurations = CustomRoutingEndpointConfiguration[];
   export interface CustomRoutingEndpointDescription {
@@ -915,6 +1044,12 @@ declare namespace GlobalAccelerator {
      */
     AcceleratorArn: GenericString;
   }
+  export interface DeleteCrossAccountAttachmentRequest {
+    /**
+     * The Amazon Resource Name (ARN) for the cross-account attachment to delete.
+     */
+    AttachmentArn: GenericString;
+  }
   export interface DeleteCustomRoutingAcceleratorRequest {
     /**
      * The Amazon Resource Name (ARN) of the custom routing accelerator to delete.
@@ -1003,6 +1138,18 @@ declare namespace GlobalAccelerator {
      */
     Accelerator?: Accelerator;
   }
+  export interface DescribeCrossAccountAttachmentRequest {
+    /**
+     * The Amazon Resource Name (ARN) for the cross-account attachment to describe.
+     */
+    AttachmentArn: GenericString;
+  }
+  export interface DescribeCrossAccountAttachmentResponse {
+    /**
+     * Information about the cross-account attachment.
+     */
+    CrossAccountAttachment?: Attachment;
+  }
   export interface DescribeCustomRoutingAcceleratorAttributesRequest {
     /**
      * The Amazon Resource Name (ARN) of the custom routing accelerator to describe the attributes for.
@@ -1122,9 +1269,13 @@ declare namespace GlobalAccelerator {
      */
     Weight?: EndpointWeight;
     /**
-     * Indicates whether client IP address preservation is enabled for an endpoint. The value is true or false. The default value is true for new accelerators.  If the value is set to true, the client's IP address is preserved in the X-Forwarded-For request header as traffic travels to applications on the endpoint fronted by the accelerator. Client IP address preservation is supported, in specific Amazon Web Services Regions, for endpoints that are Application Load Balancers, Amazon EC2 instances, and Network Load Balancers with Security Groups. IMPORTANT: You cannot use client IP address preservation with Network Load Balancers with TLS listeners. For more information, see  Preserve client IP addresses in Global Accelerator in the Global Accelerator Developer Guide.
+     * Indicates whether client IP address preservation is enabled for an endpoint. The value is true or false. The default value is true for Application Load Balancer endpoints.  If the value is set to true, the client's IP address is preserved in the X-Forwarded-For request header as traffic travels to applications on the endpoint fronted by the accelerator. Client IP address preservation is supported, in specific Amazon Web Services Regions, for endpoints that are Application Load Balancers, Amazon EC2 instances, and Network Load Balancers with security groups. IMPORTANT: You cannot use client IP address preservation with Network Load Balancers with TLS listeners. For more information, see  Preserve client IP addresses in Global Accelerator in the Global Accelerator Developer Guide.
      */
     ClientIPPreservationEnabled?: GenericBoolean;
+    /**
+     * The Amazon Resource Name (ARN) of the cross-account attachment that specifies the endpoints (resources) that can be added to accelerators and principals that have permission to add the endpoints to accelerators.
+     */
+    AttachmentArn?: GenericString;
   }
   export type EndpointConfigurations = EndpointConfiguration[];
   export interface EndpointDescription {
@@ -1145,7 +1296,7 @@ declare namespace GlobalAccelerator {
      */
     HealthReason?: GenericString;
     /**
-     * Indicates whether client IP address preservation is enabled for an endpoint. The value is true or false. The default value is true for new accelerators.  If the value is set to true, the client's IP address is preserved in the X-Forwarded-For request header as traffic travels to applications on the endpoint fronted by the accelerator. Client IP address preservation is supported, in specific Amazon Web Services Regions, for endpoints that are Application Load Balancers, Amazon EC2 instances, and Network Load Balancers with Security Groups. IMPORTANT: You cannot use client IP address preservation with Network Load Balancers with TLS listeners. For more information, see  Preserve client IP addresses in Global Accelerator in the Global Accelerator Developer Guide.
+     * Indicates whether client IP address preservation is enabled for an endpoint. The value is true or false. The default value is true for Application Load Balancers endpoints.  If the value is set to true, the client's IP address is preserved in the X-Forwarded-For request header as traffic travels to applications on the endpoint fronted by the accelerator. Client IP address preservation is supported, in specific Amazon Web Services Regions, for endpoints that are Application Load Balancers, Amazon EC2 instances, and Network Load Balancers with security groups. IMPORTANT: You cannot use client IP address preservation with Network Load Balancers with TLS listeners. For more information, see  Preserve client IP addresses in Global Accelerator in the Global Accelerator Developer Guide.
      */
     ClientIPPreservationEnabled?: GenericBoolean;
   }
@@ -1273,6 +1424,62 @@ declare namespace GlobalAccelerator {
      */
     NextToken?: GenericString;
   }
+  export interface ListCrossAccountAttachmentsRequest {
+    /**
+     * The number of cross-account attachment objects that you want to return with this call. The default value is 10.
+     */
+    MaxResults?: MaxResults;
+    /**
+     * The token for the next set of results. You receive this token from a previous call.
+     */
+    NextToken?: GenericString;
+  }
+  export interface ListCrossAccountAttachmentsResponse {
+    /**
+     * Information about the cross-account attachments.
+     */
+    CrossAccountAttachments?: Attachments;
+    /**
+     * The token for the next set of results. You receive this token from a previous call.
+     */
+    NextToken?: GenericString;
+  }
+  export interface ListCrossAccountResourceAccountsRequest {
+  }
+  export interface ListCrossAccountResourceAccountsResponse {
+    /**
+     * The account IDs of principals (resource owners) in a cross-account attachment who can add endpoints (resources) listed in the same attachment.
+     */
+    ResourceOwnerAwsAccountIds?: AwsAccountIds;
+  }
+  export interface ListCrossAccountResourcesRequest {
+    /**
+     * The Amazon Resource Name (ARN) of an accelerator in a cross-account attachment.
+     */
+    AcceleratorArn?: GenericString;
+    /**
+     * The account ID of a resource owner in a cross-account attachment.
+     */
+    ResourceOwnerAwsAccountId: AwsAccountId;
+    /**
+     * The number of cross-account endpoints objects that you want to return with this call. The default value is 10.
+     */
+    MaxResults?: MaxResults;
+    /**
+     * The token for the next set of results. You receive this token from a previous call.
+     */
+    NextToken?: GenericString;
+  }
+  export interface ListCrossAccountResourcesResponse {
+    /**
+     * The endpoints attached to an accelerator in a cross-account attachment.
+     */
+    CrossAccountResources?: CrossAccountResources;
+    /**
+     * The token for the next set of results. You receive this token from a previous call.
+     */
+    NextToken?: GenericString;
+  }
   export interface ListCustomRoutingAcceleratorsRequest {
     /**
      * The number of custom routing Global Accelerator objects that you want to return with this call. The default value is 10.
@@ -1528,6 +1735,8 @@ declare namespace GlobalAccelerator {
     ToPort?: PortNumber;
   }
   export type PortRanges = PortRange[];
+  export type Principal = string;
+  export type Principals = Principal[];
   export type Protocol = "TCP"|"UDP"|string;
   export type Protocols = Protocol[];
   export interface ProvisionByoipCidrRequest {
@@ -1566,7 +1775,18 @@ declare namespace GlobalAccelerator {
      */
     EndpointGroupArn: GenericString;
   }
+  export interface Resource {
+    /**
+     * The endpoint ID for the endpoint (Amazon Web Services resource).
+     */
+    EndpointId: GenericString;
+    /**
+     * The Amazon Web Services Region where a resource is located.
+     */
+    Region?: GenericString;
+  }
   export type ResourceArn = string;
+  export type Resources = Resource[];
   export interface SocketAddress {
     /**
      * The IP address for the socket address.
@@ -1667,6 +1887,38 @@ declare namespace GlobalAccelerator {
      */
     Accelerator?: Accelerator;
   }
+  export interface UpdateCrossAccountAttachmentRequest {
+    /**
+     * The Amazon Resource Name (ARN) of the cross-account attachment to update.
+     */
+    AttachmentArn: GenericString;
+    /**
+     * The name of the cross-account attachment. 
+     */
+    Name?: AttachmentName;
+    /**
+     * The principals to add to the cross-account attachment. A principal is an account or the Amazon Resource Name (ARN) of an accelerator that the attachment gives permission to add the resources from another account, listed in the attachment. To add more than one principal, separate the account numbers or accelerator ARNs, or both, with commas.
+     */
+    AddPrincipals?: Principals;
+    /**
+     * The principals to remove from the cross-account attachment. A principal is an account or the Amazon Resource Name (ARN) of an accelerator that is given permission to add the resources from another account, listed in the cross-account attachment. To remove more than one principal, separate the account numbers or accelerator ARNs, or both, with commas.
+     */
+    RemovePrincipals?: Principals;
+    /**
+     * The resources to add to the cross-account attachment. A resource listed in a cross-account attachment can be added to an accelerator by the principals that are listed in the attachment. To add more than one resource, separate the resource ARNs with commas.
+     */
+    AddResources?: Resources;
+    /**
+     * The resources to remove from the cross-account attachment. A resource listed in a cross-account attachment can be added to an accelerator fy principals that are listed in the cross-account attachment. To remove more than one resource, separate the resource ARNs with commas.
+     */
+    RemoveResources?: Resources;
+  }
+  export interface UpdateCrossAccountAttachmentResponse {
+    /**
+     * Information about the updated cross-account attachment.
+     */
+    CrossAccountAttachment?: Attachment;
+  }
   export interface UpdateCustomRoutingAcceleratorAttributesRequest {
     /**
      * The Amazon Resource Name (ARN) of the custom routing accelerator to update attributes for.