pulumi-aws-native 1.38.0a1761286050__py3-none-any.whl → 1.38.0a1761329030__py3-none-any.whl

pulumi_aws_native/synthetics/_inputs.py

@@ -158,14 +158,22 @@ class CanaryBrowserConfigArgs:
 
 if not MYPY:
     class CanaryCodeArgsDict(TypedDict):
-        handler: pulumi.Input[_builtins.str]
+        blueprint_types: NotRequired[pulumi.Input[Sequence[pulumi.Input[_builtins.str]]]]
         """
-        The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+        `BlueprintTypes` are a list of templates that enable simplified canary creation. You can create canaries for common monitoring scenarios by providing only a JSON configuration file instead of writing custom scripts. `multi-checks` is the only supported value.
+
+        When you specify `BlueprintTypes` , the `Handler` field cannot be specified since the blueprint provides a pre-defined entry point.
         """
         dependencies: NotRequired[pulumi.Input[Sequence[pulumi.Input['CanaryDependencyArgsDict']]]]
         """
         List of Lambda layers to attach to the canary
         """
+        handler: NotRequired[pulumi.Input[_builtins.str]]
+        """
+        The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+
+        This field is required when you don't specify `BlueprintTypes` and is not allowed when you specify `BlueprintTypes` .
+        """
         s3_bucket: NotRequired[pulumi.Input[_builtins.str]]
         """
         If your canary script is located in S3, specify the bucket name here. The bucket must already exist.
@@ -192,25 +200,34 @@ elif False:
 @pulumi.input_type
 class CanaryCodeArgs:
     def __init__(__self__, *,
-                 handler: pulumi.Input[_builtins.str],
+                 blueprint_types: Optional[pulumi.Input[Sequence[pulumi.Input[_builtins.str]]]] = None,
                  dependencies: Optional[pulumi.Input[Sequence[pulumi.Input['CanaryDependencyArgs']]]] = None,
+                 handler: Optional[pulumi.Input[_builtins.str]] = None,
                  s3_bucket: Optional[pulumi.Input[_builtins.str]] = None,
                  s3_key: Optional[pulumi.Input[_builtins.str]] = None,
                  s3_object_version: Optional[pulumi.Input[_builtins.str]] = None,
                  script: Optional[pulumi.Input[_builtins.str]] = None,
                  source_location_arn: Optional[pulumi.Input[_builtins.str]] = None):
         """
-        :param pulumi.Input[_builtins.str] handler: The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+        :param pulumi.Input[Sequence[pulumi.Input[_builtins.str]]] blueprint_types: `BlueprintTypes` are a list of templates that enable simplified canary creation. You can create canaries for common monitoring scenarios by providing only a JSON configuration file instead of writing custom scripts. `multi-checks` is the only supported value.
+               
+               When you specify `BlueprintTypes` , the `Handler` field cannot be specified since the blueprint provides a pre-defined entry point.
         :param pulumi.Input[Sequence[pulumi.Input['CanaryDependencyArgs']]] dependencies: List of Lambda layers to attach to the canary
+        :param pulumi.Input[_builtins.str] handler: The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+               
+               This field is required when you don't specify `BlueprintTypes` and is not allowed when you specify `BlueprintTypes` .
         :param pulumi.Input[_builtins.str] s3_bucket: If your canary script is located in S3, specify the bucket name here. The bucket must already exist.
         :param pulumi.Input[_builtins.str] s3_key: The Amazon S3 key of your script. For more information, see [Working with Amazon S3 Objects](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingObjects.html) .
         :param pulumi.Input[_builtins.str] s3_object_version: The Amazon S3 version ID of your script.
         :param pulumi.Input[_builtins.str] script: If you input your canary script directly into the canary instead of referring to an S3 location, the value of this parameter is the script in plain text. It can be up to 5 MB.
         :param pulumi.Input[_builtins.str] source_location_arn: The ARN of the Lambda layer where Synthetics stores the canary script code.
         """
-        pulumi.set(__self__, "handler", handler)
+        if blueprint_types is not None:
+            pulumi.set(__self__, "blueprint_types", blueprint_types)
         if dependencies is not None:
             pulumi.set(__self__, "dependencies", dependencies)
+        if handler is not None:
+            pulumi.set(__self__, "handler", handler)
         if s3_bucket is not None:
             pulumi.set(__self__, "s3_bucket", s3_bucket)
         if s3_key is not None:
@@ -223,16 +240,18 @@ class CanaryCodeArgs:
             pulumi.set(__self__, "source_location_arn", source_location_arn)
 
     @_builtins.property
-    @pulumi.getter
-    def handler(self) -> pulumi.Input[_builtins.str]:
+    @pulumi.getter(name="blueprintTypes")
+    def blueprint_types(self) -> Optional[pulumi.Input[Sequence[pulumi.Input[_builtins.str]]]]:
         """
-        The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+        `BlueprintTypes` are a list of templates that enable simplified canary creation. You can create canaries for common monitoring scenarios by providing only a JSON configuration file instead of writing custom scripts. `multi-checks` is the only supported value.
+
+        When you specify `BlueprintTypes` , the `Handler` field cannot be specified since the blueprint provides a pre-defined entry point.
         """
-        return pulumi.get(self, "handler")
+        return pulumi.get(self, "blueprint_types")
 
-    @handler.setter
-    def handler(self, value: pulumi.Input[_builtins.str]):
-        pulumi.set(self, "handler", value)
+    @blueprint_types.setter
+    def blueprint_types(self, value: Optional[pulumi.Input[Sequence[pulumi.Input[_builtins.str]]]]):
+        pulumi.set(self, "blueprint_types", value)
 
     @_builtins.property
     @pulumi.getter
@@ -246,6 +265,20 @@ class CanaryCodeArgs:
     def dependencies(self, value: Optional[pulumi.Input[Sequence[pulumi.Input['CanaryDependencyArgs']]]]):
         pulumi.set(self, "dependencies", value)
 
+    @_builtins.property
+    @pulumi.getter
+    def handler(self) -> Optional[pulumi.Input[_builtins.str]]:
+        """
+        The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+
+        This field is required when you don't specify `BlueprintTypes` and is not allowed when you specify `BlueprintTypes` .
+        """
+        return pulumi.get(self, "handler")
+
+    @handler.setter
+    def handler(self, value: Optional[pulumi.Input[_builtins.str]]):
+        pulumi.set(self, "handler", value)
+
     @_builtins.property
     @pulumi.getter(name="s3Bucket")
     def s3_bucket(self) -> Optional[pulumi.Input[_builtins.str]]:
@@ -659,6 +692,9 @@ if not MYPY:
         List of screenshots used as base reference for visual testing
         """
         browser_type: NotRequired[pulumi.Input['CanaryBrowserType']]
+        """
+        The browser type associated with this visual reference configuration. Valid values are `CHROME` and `FIREFOX` .
+        """
 elif False:
     CanaryVisualReferenceArgsDict: TypeAlias = Mapping[str, Any]
 
@@ -671,6 +707,7 @@ class CanaryVisualReferenceArgs:
         """
         :param pulumi.Input[_builtins.str] base_canary_run_id: Canary run id to be used as base reference for visual testing
         :param pulumi.Input[Sequence[pulumi.Input['CanaryBaseScreenshotArgs']]] base_screenshots: List of screenshots used as base reference for visual testing
+        :param pulumi.Input['CanaryBrowserType'] browser_type: The browser type associated with this visual reference configuration. Valid values are `CHROME` and `FIREFOX` .
         """
         pulumi.set(__self__, "base_canary_run_id", base_canary_run_id)
         if base_screenshots is not None:
@@ -705,6 +742,9 @@ class CanaryVisualReferenceArgs:
     @_builtins.property
     @pulumi.getter(name="browserType")
     def browser_type(self) -> Optional[pulumi.Input['CanaryBrowserType']]:
+        """
+        The browser type associated with this visual reference configuration. Valid values are `CHROME` and `FIREFOX` .
+        """
         return pulumi.get(self, "browser_type")
 
     @browser_type.setter

pulumi_aws_native/synthetics/outputs.py

@@ -155,7 +155,9 @@ class CanaryCode(dict):
     @staticmethod
     def __key_warning(key: str):
         suggest = None
-        if key == "s3Bucket":
+        if key == "blueprintTypes":
+            suggest = "blueprint_types"
+        elif key == "s3Bucket":
             suggest = "s3_bucket"
         elif key == "s3Key":
             suggest = "s3_key"
@@ -176,25 +178,34 @@ class CanaryCode(dict):
         return super().get(key, default)
 
     def __init__(__self__, *,
-                 handler: _builtins.str,
+                 blueprint_types: Optional[Sequence[_builtins.str]] = None,
                  dependencies: Optional[Sequence['outputs.CanaryDependency']] = None,
+                 handler: Optional[_builtins.str] = None,
                  s3_bucket: Optional[_builtins.str] = None,
                  s3_key: Optional[_builtins.str] = None,
                  s3_object_version: Optional[_builtins.str] = None,
                  script: Optional[_builtins.str] = None,
                  source_location_arn: Optional[_builtins.str] = None):
         """
-        :param _builtins.str handler: The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+        :param Sequence[_builtins.str] blueprint_types: `BlueprintTypes` are a list of templates that enable simplified canary creation. You can create canaries for common monitoring scenarios by providing only a JSON configuration file instead of writing custom scripts. `multi-checks` is the only supported value.
+               
+               When you specify `BlueprintTypes` , the `Handler` field cannot be specified since the blueprint provides a pre-defined entry point.
         :param Sequence['CanaryDependency'] dependencies: List of Lambda layers to attach to the canary
+        :param _builtins.str handler: The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+               
+               This field is required when you don't specify `BlueprintTypes` and is not allowed when you specify `BlueprintTypes` .
         :param _builtins.str s3_bucket: If your canary script is located in S3, specify the bucket name here. The bucket must already exist.
         :param _builtins.str s3_key: The Amazon S3 key of your script. For more information, see [Working with Amazon S3 Objects](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingObjects.html) .
         :param _builtins.str s3_object_version: The Amazon S3 version ID of your script.
         :param _builtins.str script: If you input your canary script directly into the canary instead of referring to an S3 location, the value of this parameter is the script in plain text. It can be up to 5 MB.
         :param _builtins.str source_location_arn: The ARN of the Lambda layer where Synthetics stores the canary script code.
         """
-        pulumi.set(__self__, "handler", handler)
+        if blueprint_types is not None:
+            pulumi.set(__self__, "blueprint_types", blueprint_types)
         if dependencies is not None:
             pulumi.set(__self__, "dependencies", dependencies)
+        if handler is not None:
+            pulumi.set(__self__, "handler", handler)
         if s3_bucket is not None:
             pulumi.set(__self__, "s3_bucket", s3_bucket)
         if s3_key is not None:
@@ -207,12 +218,14 @@ class CanaryCode(dict):
             pulumi.set(__self__, "source_location_arn", source_location_arn)
 
     @_builtins.property
-    @pulumi.getter
-    def handler(self) -> _builtins.str:
+    @pulumi.getter(name="blueprintTypes")
+    def blueprint_types(self) -> Optional[Sequence[_builtins.str]]:
         """
-        The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+        `BlueprintTypes` are a list of templates that enable simplified canary creation. You can create canaries for common monitoring scenarios by providing only a JSON configuration file instead of writing custom scripts. `multi-checks` is the only supported value.
+
+        When you specify `BlueprintTypes` , the `Handler` field cannot be specified since the blueprint provides a pre-defined entry point.
         """
-        return pulumi.get(self, "handler")
+        return pulumi.get(self, "blueprint_types")
 
     @_builtins.property
     @pulumi.getter
@@ -222,6 +235,16 @@ class CanaryCode(dict):
         """
         return pulumi.get(self, "dependencies")
 
+    @_builtins.property
+    @pulumi.getter
+    def handler(self) -> Optional[_builtins.str]:
+        """
+        The entry point to use for the source code when running the canary. For canaries that use the `syn-python-selenium-1.0` runtime or a `syn-nodejs.puppeteer` runtime earlier than `syn-nodejs.puppeteer-3.4` , the handler must be specified as `*fileName* .handler` . For `syn-python-selenium-1.1` , `syn-nodejs.puppeteer-3.4` , and later runtimes, the handler can be specified as `*fileName* . *functionName*` , or you can specify a folder where canary scripts reside as `*folder* / *fileName* . *functionName*` .
+
+        This field is required when you don't specify `BlueprintTypes` and is not allowed when you specify `BlueprintTypes` .
+        """
+        return pulumi.get(self, "handler")
+
     @_builtins.property
     @pulumi.getter(name="s3Bucket")
     def s3_bucket(self) -> Optional[_builtins.str]:
@@ -577,6 +600,7 @@ class CanaryVisualReference(dict):
         """
         :param _builtins.str base_canary_run_id: Canary run id to be used as base reference for visual testing
         :param Sequence['CanaryBaseScreenshot'] base_screenshots: List of screenshots used as base reference for visual testing
+        :param 'CanaryBrowserType' browser_type: The browser type associated with this visual reference configuration. Valid values are `CHROME` and `FIREFOX` .
         """
         pulumi.set(__self__, "base_canary_run_id", base_canary_run_id)
         if base_screenshots is not None:
@@ -603,6 +627,9 @@ class CanaryVisualReference(dict):
     @_builtins.property
     @pulumi.getter(name="browserType")
     def browser_type(self) -> Optional['CanaryBrowserType']:
+        """
+        The browser type associated with this visual reference configuration. Valid values are `CHROME` and `FIREFOX` .
+        """
         return pulumi.get(self, "browser_type")
 
 

pulumi_aws_native/transfer/_inputs.py

@@ -728,7 +728,9 @@ if not MYPY:
 
         Replace `0.0.0.0` in the example above with the actual IP address you want to use.
 
-        > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) . 
+        > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) .
+        > 
+        > Additionally, avoid placing Network Load Balancers (NLBs) or NAT gateways in front of AWS Transfer Family servers. This configuration increases costs and can cause performance issues. When NLBs or NATs are in the communication path, Transfer Family cannot accurately recognize client IP addresses, which impacts connection sharding and limits FTPS servers to only 300 simultaneous connections instead of 10,000. If you must use an NLB, use port 21 for health checks and enable TLS session resumption by setting `TlsSessionResumptionMode = ENFORCED` . For optimal performance, migrate to VPC endpoints with Elastic IP addresses instead of using NLBs. For more details, see [Avoid placing NLBs and NATs in front of AWS Transfer Family](https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations) . 
 
         *Special values*
 
@@ -772,7 +774,9 @@ class ServerProtocolDetailsArgs:
                
                Replace `0.0.0.0` in the example above with the actual IP address you want to use.
                
-               > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) . 
+               > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) .
+               > 
+               > Additionally, avoid placing Network Load Balancers (NLBs) or NAT gateways in front of AWS Transfer Family servers. This configuration increases costs and can cause performance issues. When NLBs or NATs are in the communication path, Transfer Family cannot accurately recognize client IP addresses, which impacts connection sharding and limits FTPS servers to only 300 simultaneous connections instead of 10,000. If you must use an NLB, use port 21 for health checks and enable TLS session resumption by setting `TlsSessionResumptionMode = ENFORCED` . For optimal performance, migrate to VPC endpoints with Elastic IP addresses instead of using NLBs. For more details, see [Avoid placing NLBs and NATs in front of AWS Transfer Family](https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations) . 
                
                *Special values*
                
@@ -823,7 +827,9 @@ class ServerProtocolDetailsArgs:
 
         Replace `0.0.0.0` in the example above with the actual IP address you want to use.
 
-        > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) . 
+        > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) .
+        > 
+        > Additionally, avoid placing Network Load Balancers (NLBs) or NAT gateways in front of AWS Transfer Family servers. This configuration increases costs and can cause performance issues. When NLBs or NATs are in the communication path, Transfer Family cannot accurately recognize client IP addresses, which impacts connection sharding and limits FTPS servers to only 300 simultaneous connections instead of 10,000. If you must use an NLB, use port 21 for health checks and enable TLS session resumption by setting `TlsSessionResumptionMode = ENFORCED` . For optimal performance, migrate to VPC endpoints with Elastic IP addresses instead of using NLBs. For more details, see [Avoid placing NLBs and NATs in front of AWS Transfer Family](https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations) . 
 
         *Special values*
 

pulumi_aws_native/transfer/outputs.py

@@ -579,7 +579,9 @@ class ServerProtocolDetails(dict):
                
                Replace `0.0.0.0` in the example above with the actual IP address you want to use.
                
-               > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) . 
+               > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) .
+               > 
+               > Additionally, avoid placing Network Load Balancers (NLBs) or NAT gateways in front of AWS Transfer Family servers. This configuration increases costs and can cause performance issues. When NLBs or NATs are in the communication path, Transfer Family cannot accurately recognize client IP addresses, which impacts connection sharding and limits FTPS servers to only 300 simultaneous connections instead of 10,000. If you must use an NLB, use port 21 for health checks and enable TLS session resumption by setting `TlsSessionResumptionMode = ENFORCED` . For optimal performance, migrate to VPC endpoints with Elastic IP addresses instead of using NLBs. For more details, see [Avoid placing NLBs and NATs in front of AWS Transfer Family](https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations) . 
                
                *Special values*
                
@@ -626,7 +628,9 @@ class ServerProtocolDetails(dict):
 
         Replace `0.0.0.0` in the example above with the actual IP address you want to use.
 
-        > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) . 
+        > If you change the `PassiveIp` value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see [Configuring your FTPS server behind a firewall or NAT with AWS Transfer Family](https://docs.aws.amazon.com/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/) .
+        > 
+        > Additionally, avoid placing Network Load Balancers (NLBs) or NAT gateways in front of AWS Transfer Family servers. This configuration increases costs and can cause performance issues. When NLBs or NATs are in the communication path, Transfer Family cannot accurately recognize client IP addresses, which impacts connection sharding and limits FTPS servers to only 300 simultaneous connections instead of 10,000. If you must use an NLB, use port 21 for health checks and enable TLS session resumption by setting `TlsSessionResumptionMode = ENFORCED` . For optimal performance, migrate to VPC endpoints with Elastic IP addresses instead of using NLBs. For more details, see [Avoid placing NLBs and NATs in front of AWS Transfer Family](https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations) . 
 
         *Special values*
 

pulumi_aws_native/wisdom/_enums.py

@@ -166,6 +166,10 @@ class AiPromptAiPromptType(_builtins.str, Enum):
     QUERY_REFORMULATION = "QUERY_REFORMULATION"
     SELF_SERVICE_PRE_PROCESSING = "SELF_SERVICE_PRE_PROCESSING"
     SELF_SERVICE_ANSWER_GENERATION = "SELF_SERVICE_ANSWER_GENERATION"
+    EMAIL_RESPONSE = "EMAIL_RESPONSE"
+    EMAIL_OVERVIEW = "EMAIL_OVERVIEW"
+    EMAIL_GENERATIVE_ANSWER = "EMAIL_GENERATIVE_ANSWER"
+    EMAIL_QUERY_REFORMULATION = "EMAIL_QUERY_REFORMULATION"
 
 
 @pulumi.type_token("aws-native:wisdom:AssistantAssociationAssociationType")

{pulumi_aws_native-1.38.0a1761286050.dist-info → pulumi_aws_native-1.38.0a1761329030.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pulumi_aws_native
-Version: 1.38.0a1761286050
+Version: 1.38.0a1761329030
 Summary: A native Pulumi package for creating and managing Amazon Web Services (AWS) resources.
 License: Apache-2.0
 Project-URL: Homepage, https://pulumi.com