From 8b5eba40823866912cea9a827903de95c495f0fb Mon Sep 17 00:00:00 2001
From: awstools
In environments created with a CreateEnvironment:NetworkFabricType of NONE
you need to configure
+ * VPC to VPC connectivity between your service VPC and the application proxy VPC to
+ * route traffic through the application proxy to a service with a private URL endpoint. For more
+ * information, see
+ * Create an application in the Refactor Spaces User Guide.
When creating an environment with
- * a network fabric type of TRANSIT_GATEWAY
,
- * Refactor Spaces provisions a transit gateway in your account.
When creating an environment with a CreateEnvironment:NetworkFabricType of TRANSIT_GATEWAY
, Refactor Spaces
+ * provisions a transit gateway to enable services in VPCs to communicate directly across
+ * accounts. If CreateEnvironment:NetworkFabricType is NONE
, Refactor Spaces does not create
+ * a transit gateway and you must use your network infrastructure to route traffic to services
+ * with private URL endpoints.
+ * URL Endpoints + *
*If the service has a URL endpoint, and the endpoint resolves to a private IP address, - * Refactor Spaces routes traffic using the API Gateway VPC link.
- *If the service has a URL endpoint, and the endpoint resolves to a public IP address, - * Refactor Spaces routes traffic over the public internet.
+ * Refactor Spaces routes traffic using the API Gateway VPC link. If a service endpoint + * resolves to a public IP address, Refactor Spaces routes traffic over the public internet. + * Services can have HTTP or HTTPS URL endpoints. For HTTPS URLs, publicly-signed + * certificates are supported. Private Certificate Authorities (CAs) are permitted only if + * the CA's domain is also publicly resolvable. + *Refactor Spaces automatically resolves the public Domain Name System (DNS) names that are
+ * set in CreateService:UrlEndpoint
when you create a service. The DNS names
+ * resolve when the DNS time-to-live (TTL) expires, or every 60 seconds for TTLs less than 60
+ * seconds. This periodic DNS resolution ensures that the route configuration remains
+ * up-to-date.
+ * One-time health check + *
+ *A one-time health check is performed on the service when either the route is updated
+ * from inactive to active, or when it is created with an active state. If the health check
+ * fails, the route transitions the route state to FAILED
, an error code of
+ * SERVICE_ENDPOINT_HEALTH_CHECK_FAILURE
is provided, and no traffic is sent
+ * to the service.
For private URLs, a target group is created on the Network Load Balancer and the load + * balancer target group runs default target health checks. By default, the health check is + * run against the service endpoint URL. Optionally, the health check can be performed + * against a different protocol, port, and/or path using the CreateService:UrlEndpoint parameter. All other health check settings for the + * load balancer use the default values described in the Health + * checks for your target groups in the Elastic Load Balancing + * guide. The health check is considered successful if at least one target + * within the target group transitions to a healthy state.
+ * *+ * Lambda function endpoints + *
*If the service has an Lambda function endpoint, then Refactor Spaces * configures the Lambda function's resource policy to allow the application's * API Gateway to invoke the function.
+ *The Lambda function state is checked. If the function is not active, the
+ * function configuration is updated so that Lambda resources are provisioned. If
+ * the Lambda state is Failed
, then the route creation fails. For
+ * more information, see the GetFunctionConfiguration's State response parameter in the Lambda Developer Guide.
A check is performed to determine that a Lambda function with the specified ARN + * exists. If it does not exist, the health check fails. For public URLs, a connection is + * opened to the public endpoint. If the URL is not reachable, the health check fails. + *
*A one-time health check is performed on the service when either the route is updated from
- * inactive to active, or when it is created with an active state. If the health check fails, the
- * route transitions the route state to FAILED
, an error code of
- * SERVICE_ENDPOINT_HEALTH_CHECK_FAILURE
is provided, and no traffic is sent to
- * the service.
For Lambda functions, the Lambda function state is checked. If the
- * function is not active, the function configuration is updated so that Lambda
- * resources are provisioned. If the Lambda state is Failed
, then the
- * route creation fails. For more information, see the GetFunctionConfiguration's State response parameter in the Lambda Developer Guide.
For Lambda endpoints, a check is performed to determine that a Lambda function with the - * specified ARN exists. If it does not exist, the health check fails. For public URLs, a - * connection is opened to the public endpoint. If the URL is not reachable, the health check - * fails.
- *Refactor Spaces automatically resolves the public Domain Name System (DNS) names that are set in - * CreateServiceRequest$UrlEndpoint when you create a service. The DNS names - * resolve when the DNS time-to-live (TTL) expires, or every 60 seconds for TTLs less than 60 - * seconds. This periodic DNS resolution ensures that the route configuration remains up-to-date.
- *For private URLS, a target group is created on the Elastic Load Balancing and the target
- * group health check is run. The HealthCheckProtocol
, HealthCheckPort
,
- * and HealthCheckPath
are the same protocol, port, and path specified in the URL or
- * health URL, if used. All other settings use the default values, as described in Health checks
- * for your target groups. The health check is considered successful if at least one
- * target within the target group transitions to a healthy state.
Services can have HTTP or HTTPS URL endpoints. For HTTPS URLs, publicly-signed - * certificates are supported. Private Certificate Authorities (CAs) are permitted only if the - * CA's domain is also publicly resolvable.
+ *+ * Environments without a network bridge + *
+ *When you create environments without a network bridge (CreateEnvironment:NetworkFabricType is NONE)
and you use your own
+ * networking infrastructure, you need to configure VPC to VPC connectivity between your network and the application proxy VPC. Route
+ * creation from the application proxy to service endpoints will fail if your network is not
+ * configured to connect to the application proxy VPC. For more information, see Create
+ * a route in the Refactor Spaces User Guide.
In environments created with a CreateEnvironment:NetworkFabricType of NONE
you need to configure
+ * VPC to VPC connectivity between your service VPC and the application proxy VPC to
+ * route traffic through the application proxy to a service with a private URL endpoint. For more
+ * information, see
+ * Create an application in the Refactor Spaces User Guide.
When creating an environment with
- * a network fabric type of TRANSIT_GATEWAY
,
- * Refactor Spaces provisions a transit gateway in your account.
When creating an environment with a CreateEnvironment:NetworkFabricType of TRANSIT_GATEWAY
, Refactor Spaces
+ * provisions a transit gateway to enable services in VPCs to communicate directly across
+ * accounts. If CreateEnvironment:NetworkFabricType is NONE
, Refactor Spaces does not create
+ * a transit gateway and you must use your network infrastructure to route traffic to services
+ * with private URL endpoints.
+ * URL Endpoints + *
*If the service has a URL endpoint, and the endpoint resolves to a private IP address, - * Refactor Spaces routes traffic using the API Gateway VPC link.
- *If the service has a URL endpoint, and the endpoint resolves to a public IP address, - * Refactor Spaces routes traffic over the public internet.
+ * Refactor Spaces routes traffic using the API Gateway VPC link. If a service endpoint + * resolves to a public IP address, Refactor Spaces routes traffic over the public internet. + * Services can have HTTP or HTTPS URL endpoints. For HTTPS URLs, publicly-signed + * certificates are supported. Private Certificate Authorities (CAs) are permitted only if + * the CA's domain is also publicly resolvable. + *Refactor Spaces automatically resolves the public Domain Name System (DNS) names that are
+ * set in CreateService:UrlEndpoint
when you create a service. The DNS names
+ * resolve when the DNS time-to-live (TTL) expires, or every 60 seconds for TTLs less than 60
+ * seconds. This periodic DNS resolution ensures that the route configuration remains
+ * up-to-date.
+ * One-time health check + *
+ *A one-time health check is performed on the service when either the route is updated
+ * from inactive to active, or when it is created with an active state. If the health check
+ * fails, the route transitions the route state to FAILED
, an error code of
+ * SERVICE_ENDPOINT_HEALTH_CHECK_FAILURE
is provided, and no traffic is sent
+ * to the service.
For private URLs, a target group is created on the Network Load Balancer and the load + * balancer target group runs default target health checks. By default, the health check is + * run against the service endpoint URL. Optionally, the health check can be performed + * against a different protocol, port, and/or path using the CreateService:UrlEndpoint parameter. All other health check settings for the + * load balancer use the default values described in the Health + * checks for your target groups in the Elastic Load Balancing + * guide. The health check is considered successful if at least one target + * within the target group transitions to a healthy state.
+ * *+ * Lambda function endpoints + *
*If the service has an Lambda function endpoint, then Refactor Spaces * configures the Lambda function's resource policy to allow the application's * API Gateway to invoke the function.
+ *The Lambda function state is checked. If the function is not active, the
+ * function configuration is updated so that Lambda resources are provisioned. If
+ * the Lambda state is Failed
, then the route creation fails. For
+ * more information, see the GetFunctionConfiguration's State response parameter in the Lambda Developer Guide.
A check is performed to determine that a Lambda function with the specified ARN + * exists. If it does not exist, the health check fails. For public URLs, a connection is + * opened to the public endpoint. If the URL is not reachable, the health check fails. + *
*A one-time health check is performed on the service when either the route is updated from
- * inactive to active, or when it is created with an active state. If the health check fails, the
- * route transitions the route state to FAILED
, an error code of
- * SERVICE_ENDPOINT_HEALTH_CHECK_FAILURE
is provided, and no traffic is sent to
- * the service.
For Lambda functions, the Lambda function state is checked. If the
- * function is not active, the function configuration is updated so that Lambda
- * resources are provisioned. If the Lambda state is Failed
, then the
- * route creation fails. For more information, see the GetFunctionConfiguration's State response parameter in the Lambda Developer Guide.
For Lambda endpoints, a check is performed to determine that a Lambda function with the - * specified ARN exists. If it does not exist, the health check fails. For public URLs, a - * connection is opened to the public endpoint. If the URL is not reachable, the health check - * fails.
- *Refactor Spaces automatically resolves the public Domain Name System (DNS) names that are set in - * CreateServiceRequest$UrlEndpoint when you create a service. The DNS names - * resolve when the DNS time-to-live (TTL) expires, or every 60 seconds for TTLs less than 60 - * seconds. This periodic DNS resolution ensures that the route configuration remains up-to-date.
- *For private URLS, a target group is created on the Elastic Load Balancing and the target
- * group health check is run. The HealthCheckProtocol
, HealthCheckPort
,
- * and HealthCheckPath
are the same protocol, port, and path specified in the URL or
- * health URL, if used. All other settings use the default values, as described in Health checks
- * for your target groups. The health check is considered successful if at least one
- * target within the target group transitions to a healthy state.
Services can have HTTP or HTTPS URL endpoints. For HTTPS URLs, publicly-signed - * certificates are supported. Private Certificate Authorities (CAs) are permitted only if the - * CA's domain is also publicly resolvable.
+ *+ * Environments without a network bridge + *
+ *When you create environments without a network bridge (CreateEnvironment:NetworkFabricType is NONE)
and you use your own
+ * networking infrastructure, you need to configure VPC to VPC connectivity between your network and the application proxy VPC. Route
+ * creation from the application proxy to service endpoints will fail if your network is not
+ * configured to connect to the application proxy VPC. For more information, see Create
+ * a route in the Refactor Spaces User Guide.
A timestamp that indicates when the environment was last updated.
+ *A timestamp that indicates when the environment was last updated.
*/ LastUpdatedTime?: Date; @@ -1475,7 +1475,7 @@ export interface EnvironmentSummary { OwnerAccountId?: string; /** - *The ID of the transit gateway set up by the environment.
+ *The ID of the Transit Gateway set up by the environment.
*/ TransitGatewayId?: string; @@ -1683,7 +1683,7 @@ export interface GetEnvironmentResponse { OwnerAccountId?: string; /** - *The ID of the transit gateway set up by the environment.
+ *The ID of the Transit Gateway set up by the environment, if applicable.
*/ TransitGatewayId?: string; diff --git a/codegen/sdk-codegen/aws-models/migration-hub-refactor-spaces.json b/codegen/sdk-codegen/aws-models/migration-hub-refactor-spaces.json index 85fb699c06c5..52595374bd47 100644 --- a/codegen/sdk-codegen/aws-models/migration-hub-refactor-spaces.json +++ b/codegen/sdk-codegen/aws-models/migration-hub-refactor-spaces.json @@ -433,7 +433,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates an Amazon Web Services Migration Hub Refactor Spaces application. The account that owns the environment also owns the\n applications created inside the environment, regardless of the account that creates the\n application. Refactor Spaces provisions an Amazon API Gateway, API Gateway VPC link, and\n Network Load Balancer for the application proxy inside your account.
", + "smithy.api#documentation": "Creates an Amazon Web Services Migration Hub Refactor Spaces application. The account that owns the environment also owns the\n applications created inside the environment, regardless of the account that creates the\n application. Refactor Spaces provisions an Amazon API Gateway, API Gateway VPC link, and\n Network Load Balancer for the application proxy inside your account.
\nIn environments created with a CreateEnvironment:NetworkFabricType of NONE
you need to configure\n VPC to VPC connectivity between your service VPC and the application proxy VPC to\n route traffic through the application proxy to a service with a private URL endpoint. For more\n information, see \n Create an application in the Refactor Spaces User Guide.
Creates an Amazon Web Services Migration Hub Refactor Spaces environment. The caller owns the environment resource, and all\n Refactor Spaces applications, services, and routes created within the environment. They are referred\n to as the environment owner. The environment owner has cross-account\n visibility and control of Refactor Spaces resources that are added to the environment by other\n accounts that the environment is shared with.
\nWhen creating an environment with \n a network fabric type of TRANSIT_GATEWAY
, \n Refactor Spaces provisions a transit gateway in your account.
Creates an Amazon Web Services Migration Hub Refactor Spaces environment. The caller owns the environment resource, and all\n Refactor Spaces applications, services, and routes created within the environment. They are referred\n to as the environment owner. The environment owner has cross-account\n visibility and control of Refactor Spaces resources that are added to the environment by other\n accounts that the environment is shared with.
\nWhen creating an environment with a CreateEnvironment:NetworkFabricType of TRANSIT_GATEWAY
, Refactor Spaces\n provisions a transit gateway to enable services in VPCs to communicate directly across\n accounts. If CreateEnvironment:NetworkFabricType is NONE
, Refactor Spaces does not create\n a transit gateway and you must use your network infrastructure to route traffic to services\n with private URL endpoints.
A timestamp that indicates when the environment was last updated.
" + "smithy.api#documentation": "A timestamp that indicates when the environment was last updated.
" } }, "CreatedTime": { @@ -752,7 +752,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates an Amazon Web Services Migration Hub Refactor Spaces route. The account owner of the service resource is always the\n environment owner, regardless of which account creates the route. Routes target a service in\n the application. If an application does not have any routes, then the first route must be\n created as a DEFAULT
\n RouteType
.
When created, the default route defaults to an active state so state is not a required\n input. However, like all other state values the state of the default route can be updated\n after creation, but only when all other routes are also inactive. Conversely, no route can be\n active without the default route also being active.
\nWhen you create a route, Refactor Spaces configures the Amazon API Gateway to send traffic\n to the target service as follows:
\nIf the service has a URL endpoint, and the endpoint resolves to a private IP address,\n Refactor Spaces routes traffic using the API Gateway VPC link.
\nIf the service has a URL endpoint, and the endpoint resolves to a public IP address,\n Refactor Spaces routes traffic over the public internet.
\nIf the service has an Lambda function endpoint, then Refactor Spaces\n configures the Lambda function's resource policy to allow the application's\n API Gateway to invoke the function.
\nA one-time health check is performed on the service when either the route is updated from\n inactive to active, or when it is created with an active state. If the health check fails, the\n route transitions the route state to FAILED
, an error code of\n SERVICE_ENDPOINT_HEALTH_CHECK_FAILURE
is provided, and no traffic is sent to\n the service.
For Lambda functions, the Lambda function state is checked. If the\n function is not active, the function configuration is updated so that Lambda\n resources are provisioned. If the Lambda state is Failed
, then the\n route creation fails. For more information, see the GetFunctionConfiguration's State response parameter in the Lambda Developer Guide.
For Lambda endpoints, a check is performed to determine that a Lambda function with the\n specified ARN exists. If it does not exist, the health check fails. For public URLs, a\n connection is opened to the public endpoint. If the URL is not reachable, the health check\n fails.
\nRefactor Spaces automatically resolves the public Domain Name System (DNS) names that are set in\n CreateServiceRequest$UrlEndpoint when you create a service. The DNS names\n resolve when the DNS time-to-live (TTL) expires, or every 60 seconds for TTLs less than 60\n seconds. This periodic DNS resolution ensures that the route configuration remains up-to-date.
\nFor private URLS, a target group is created on the Elastic Load Balancing and the target\n group health check is run. The HealthCheckProtocol
, HealthCheckPort
,\n and HealthCheckPath
are the same protocol, port, and path specified in the URL or\n health URL, if used. All other settings use the default values, as described in Health checks\n for your target groups. The health check is considered successful if at least one\n target within the target group transitions to a healthy state.
Services can have HTTP or HTTPS URL endpoints. For HTTPS URLs, publicly-signed\n certificates are supported. Private Certificate Authorities (CAs) are permitted only if the\n CA's domain is also publicly resolvable.
", + "smithy.api#documentation": "Creates an Amazon Web Services Migration Hub Refactor Spaces route. The account owner of the service resource is always the\n environment owner, regardless of which account creates the route. Routes target a service in\n the application. If an application does not have any routes, then the first route must be\n created as a DEFAULT
\n RouteType
.
When created, the default route defaults to an active state so state is not a required\n input. However, like all other state values the state of the default route can be updated\n after creation, but only when all other routes are also inactive. Conversely, no route can be\n active without the default route also being active.
\nWhen you create a route, Refactor Spaces configures the Amazon API Gateway to send traffic\n to the target service as follows:
\n\n URL Endpoints\n
\nIf the service has a URL endpoint, and the endpoint resolves to a private IP address,\n Refactor Spaces routes traffic using the API Gateway VPC link. If a service endpoint\n resolves to a public IP address, Refactor Spaces routes traffic over the public internet.\n Services can have HTTP or HTTPS URL endpoints. For HTTPS URLs, publicly-signed\n certificates are supported. Private Certificate Authorities (CAs) are permitted only if\n the CA's domain is also publicly resolvable.
\nRefactor Spaces automatically resolves the public Domain Name System (DNS) names that are\n set in CreateService:UrlEndpoint
when you create a service. The DNS names\n resolve when the DNS time-to-live (TTL) expires, or every 60 seconds for TTLs less than 60\n seconds. This periodic DNS resolution ensures that the route configuration remains\n up-to-date.
\n One-time health check\n
\nA one-time health check is performed on the service when either the route is updated\n from inactive to active, or when it is created with an active state. If the health check\n fails, the route transitions the route state to FAILED
, an error code of\n SERVICE_ENDPOINT_HEALTH_CHECK_FAILURE
is provided, and no traffic is sent\n to the service.
For private URLs, a target group is created on the Network Load Balancer and the load\n balancer target group runs default target health checks. By default, the health check is\n run against the service endpoint URL. Optionally, the health check can be performed\n against a different protocol, port, and/or path using the CreateService:UrlEndpoint parameter. All other health check settings for the\n load balancer use the default values described in the Health\n checks for your target groups in the Elastic Load Balancing\n guide. The health check is considered successful if at least one target\n within the target group transitions to a healthy state.
\n \n\n Lambda function endpoints\n
\nIf the service has an Lambda function endpoint, then Refactor Spaces\n configures the Lambda function's resource policy to allow the application's\n API Gateway to invoke the function.
\nThe Lambda function state is checked. If the function is not active, the\n function configuration is updated so that Lambda resources are provisioned. If\n the Lambda state is Failed
, then the route creation fails. For\n more information, see the GetFunctionConfiguration's State response parameter in the Lambda Developer Guide.
A check is performed to determine that a Lambda function with the specified ARN\n exists. If it does not exist, the health check fails. For public URLs, a connection is\n opened to the public endpoint. If the URL is not reachable, the health check fails.\n
\n\n Environments without a network bridge\n
\nWhen you create environments without a network bridge (CreateEnvironment:NetworkFabricType is NONE)
and you use your own\n networking infrastructure, you need to configure VPC to VPC connectivity between your network and the application proxy VPC. Route\n creation from the application proxy to service endpoints will fail if your network is not\n configured to connect to the application proxy VPC. For more information, see Create\n a route in the Refactor Spaces User Guide.
The ID of the transit gateway set up by the environment.
" + "smithy.api#documentation": "The ID of the Transit Gateway set up by the environment.
" } }, "State": { @@ -2216,7 +2216,7 @@ "TransitGatewayId": { "target": "com.amazonaws.migrationhubrefactorspaces#TransitGatewayId", "traits": { - "smithy.api#documentation": "The ID of the transit gateway set up by the environment.
" + "smithy.api#documentation": "The ID of the Transit Gateway set up by the environment, if applicable.
" } }, "State": { @@ -2819,8 +2819,8 @@ "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", - "items": "ApplicationSummaryList", - "pageSize": "MaxResults" + "pageSize": "MaxResults", + "items": "ApplicationSummaryList" }, "smithy.api#readonly": {} } @@ -2904,8 +2904,8 @@ "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", - "items": "EnvironmentVpcList", - "pageSize": "MaxResults" + "pageSize": "MaxResults", + "items": "EnvironmentVpcList" }, "smithy.api#readonly": {} } @@ -2989,8 +2989,8 @@ "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", - "items": "EnvironmentSummaryList", - "pageSize": "MaxResults" + "pageSize": "MaxResults", + "items": "EnvironmentSummaryList" }, "smithy.api#readonly": {} } @@ -3072,8 +3072,8 @@ "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", - "items": "RouteSummaryList", - "pageSize": "MaxResults" + "pageSize": "MaxResults", + "items": "RouteSummaryList" }, "smithy.api#readonly": {} } @@ -3171,8 +3171,8 @@ "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", - "items": "ServiceSummaryList", - "pageSize": "MaxResults" + "pageSize": "MaxResults", + "items": "ServiceSummaryList" }, "smithy.api#readonly": {} } @@ -3252,8 +3252,7 @@ "smithy.api#documentation": "Lists the tags of a resource. The caller account must be the same as the resource’s\n OwnerAccountId
. Listing tags in other accounts is not supported.
This API reference provides descriptions, syntax, and other details about each of the\n actions and data types for Amazon Web Services Migration Hub Refactor Spaces (Refactor Spaces). The topic for each action shows the API\n request parameters and the response. Alternatively, you can use one of the Amazon Web Services SDKs to\n access an API that is tailored to the programming language or platform that you're using. For\n more information, see Amazon Web Services SDKs.
\nTo share Refactor Spaces environments with other Amazon Web Services accounts or with Organizations\n and their OUs, use Resource Access Manager's CreateResourceShare
API. See CreateResourceShare in the Amazon Web Services RAM API Reference.
Removes the tags of a given resource. Tags are metadata which can be used to manage a\n resource. To tag a resource, the caller account must be the same as the resource’s\n OwnerAccountId
. Tagging resources in other accounts is not supported.
Amazon Web Services Migration Hub Refactor Spaces does not propagate tags to orchestrated resources, such as an\n environment’s transit gateway.
\nAdds to or modifies the tags of the given resource. Tags are metadata which can be used to\n manage a resource. To untag a resource, the caller account must be the same as the resource’s\n OwnerAccountId
. Untagging resources across accounts is not supported.