public CreateCustomKeyStoreRequest withXksProxyConnectivity(XksProxyConnectivityType xksProxyConnectivity) {
        this.xksProxyConnectivity = xksProxyConnectivity.toString();
        return this;
    }
<p>
Indicates how KMS communicates with the external key store proxy. This parameter is required for custom key
stores with a <code>CustomKeyStoreType</code> of <code>EXTERNAL_KEY_STORE</code>.
</p>
<p>
If the external key store proxy uses a public endpoint, specify <code>PUBLIC_ENDPOINT</code>. If the external key
store proxy uses a Amazon VPC endpoint service for communication with KMS, specify
<code>VPC_ENDPOINT_SERVICE</code>. For help making this choice, see <a
href="https://docs.aws.amazon.com/kms/latest/developerguide/plan-xks-keystore.html#choose-xks-connectivity"
>Choosing a connectivity option</a> in the <i>Key Management Service Developer Guide</i>.
</p>
<p>
An Amazon VPC endpoint service keeps your communication with KMS in a private address space entirely within
Amazon Web Services, but it requires more configuration, including establishing a Amazon VPC with multiple
subnets, a VPC endpoint service, a network load balancer, and a verified private DNS name. A public endpoint is
simpler to set up, but it might be slower and might not fulfill your security requirements. You might consider
testing with a public endpoint, and then establishing a VPC endpoint service for production tasks. Note that this
choice does not determine the location of the external key store proxy. Even if you choose a VPC endpoint
service, the proxy can be hosted within the VPC or outside of Amazon Web Services such as in your corporate data
center.
</p>

@param xksProxyConnectivity
       Indicates how KMS communicates with the external key store proxy. This parameter is required for custom
       key stores with a <code>CustomKeyStoreType</code> of <code>EXTERNAL_KEY_STORE</code>.</p>
       <p>
       If the external key store proxy uses a public endpoint, specify <code>PUBLIC_ENDPOINT</code>. If the
       external key store proxy uses a Amazon VPC endpoint service for communication with KMS, specify
       <code>VPC_ENDPOINT_SERVICE</code>. For help making this choice, see <a
       href="https://docs.aws.amazon.com/kms/latest/developerguide/plan-xks-keystore.html#choose-xks-connectivity"
       >Choosing a connectivity option</a> in the <i>Key Management Service Developer Guide</i>.
       </p>
       <p>
       An Amazon VPC endpoint service keeps your communication with KMS in a private address space entirely
       within Amazon Web Services, but it requires more configuration, including establishing a Amazon VPC with
       multiple subnets, a VPC endpoint service, a network load balancer, and a verified private DNS name. A
       public endpoint is simpler to set up, but it might be slower and might not fulfill your security
       requirements. You might consider testing with a public endpoint, and then establishing a VPC endpoint
       service for production tasks. Note that this choice does not determine the location of the external key
       store proxy. Even if you choose a VPC endpoint service, the proxy can be hosted within the VPC or outside
       of Amazon Web Services such as in your corporate data center.
@return Returns a reference to this object so that method calls can be chained together.
@see XksProxyConnectivityType
aws-java-sdk-kms/src/main/java/com/amazonaws/services/kms/model/CreateCustomKeyStoreRequest.java