Enum IntegrationType
Namespace: Amazon.CDK.AWS.APIGateway
Assembly: Amazon.CDK.Lib.dll
Syntax (csharp)
public enum IntegrationType
Syntax (vb)
Public Enum IntegrationType
Remarks
ExampleMetadata: infused
Examples
using Amazon.CDK.AWS.ElasticLoadBalancingV2;
var vpc = new Vpc(this, "VPC");
var nlb = new NetworkLoadBalancer(this, "NLB", new NetworkLoadBalancerProps {
Vpc = vpc
});
var link = new VpcLink(this, "link", new VpcLinkProps {
Targets = new [] { nlb }
});
var integration = new Integration(new IntegrationProps {
Type = IntegrationType.HTTP_PROXY,
IntegrationHttpMethod = "ANY",
Options = new IntegrationOptions {
ConnectionType = ConnectionType.VPC_LINK,
VpcLink = link
}
});
Synopsis
Fields
| AWS | For integrating the API method request with an AWS service action, including the Lambda function-invoking action. |
| AWS_PROXY | For integrating the API method request with the Lambda function-invoking action with the client request passed through as-is. |
| HTTP | For integrating the API method request with an HTTP endpoint, including a private HTTP endpoint within a VPC. |
| HTTP_PROXY | For integrating the API method request with an HTTP endpoint, including a private HTTP endpoint within a VPC, with the client request passed through as-is. |
| MOCK | For integrating the API method request with API Gateway as a "loop-back" endpoint without invoking any backend. |
Fields
| Name | Description |
|---|---|
| AWS | For integrating the API method request with an AWS service action, including the Lambda function-invoking action. |
| AWS_PROXY | For integrating the API method request with the Lambda function-invoking action with the client request passed through as-is. |
| HTTP | For integrating the API method request with an HTTP endpoint, including a private HTTP endpoint within a VPC. |
| HTTP_PROXY | For integrating the API method request with an HTTP endpoint, including a private HTTP endpoint within a VPC, with the client request passed through as-is. |
| MOCK | For integrating the API method request with API Gateway as a "loop-back" endpoint without invoking any backend. |