Interface CpServerlessContainerAppsProps

Serverless container app properties

interface CpServerlessContainerAppsProps {
    cpAccessLogsBucket: CcLoggingBucket;
    cpCloudFrontSecret?: Secret;
    cpCloudfrontAllowedMethods?: AllowedMethods;
    cpCloudfrontWaf?: CcCloudfrontWaf;
    cpCluster?: CcFargateCluster;
    cpCoreRuleExclusions?: CoreRuleName[];
    cpDomainName: string;
    cpFallbackOrigin?: OriginBase;
    cpLoadBalancerOriginRequestPolicy?: OriginRequestPolicy;
    cpLoadBalancerWaf?: CcApiGatewayWaf;
    cpPublicLoadBalancer?: CcPublicApplicationLoadbalancer;
    cpSubDomain?: string;
    cpVpc?: CcVpc;
}

Properties

cpAccessLogsBucket cpCloudFrontSecret? cpCloudfrontAllowedMethods? cpCloudfrontWaf? cpCluster? cpCoreRuleExclusions? cpDomainName cpFallbackOrigin? cpLoadBalancerOriginRequestPolicy? cpLoadBalancerWaf? cpPublicLoadBalancer? cpSubDomain? cpVpc?

Properties

Readonly cpAccessLogsBucket

cpAccessLogsBucket: CcLoggingBucket

Access logs bucket

Optional Readonly cpCloudFrontSecret

cpCloudFrontSecret?: Secret

CLoudFront secret to use with X-Origin-Verify header

Default

A secret is generated and stored in SSM for sharing

Optional Readonly cpCloudfrontAllowedMethods

cpCloudfrontAllowedMethods?: AllowedMethods

Http methods that the distribution should forward to load balancer

Default

AllowedMethods.ALLOW_ALL

Optional Readonly cpCloudfrontWaf

cpCloudfrontWaf?: CcCloudfrontWaf

Waf to use with cloudfront

Default

Waf is created to protect against most commonly used threats

Optional Readonly cpCluster

cpCluster?: CcFargateCluster

You can pass your existing ECS cluster in order to provision fargate service.

Default

A new Well Architected ECS cluster is created

Optional Readonly cpCoreRuleExclusions

cpCoreRuleExclusions?: CoreRuleName[]

Cloudfront WAF rule exclusions, to provide a list of rules that should not be enforced by firewall

Readonly cpDomainName

cpDomainName: string

Domain name

Example

cloudkitect.com

Optional Readonly cpFallbackOrigin

cpFallbackOrigin?: OriginBase

Fall back origin to route traffic to when load balancer is not available

Default

to www subdomain of the provided domain name

Optional Readonly cpLoadBalancerOriginRequestPolicy

cpLoadBalancerOriginRequestPolicy?: OriginRequestPolicy

Load balancer origin request policy

Default

Request cookies, headers and query string forwarded to load balancer

Optional Readonly cpLoadBalancerWaf

cpLoadBalancerWaf?: CcApiGatewayWaf

Waf to use with load balancer

Default

Waf is created that looks for X-Verify_Header from cloudfront

Optional Readonly cpPublicLoadBalancer

cpPublicLoadBalancer?: CcPublicApplicationLoadbalancer

Application Load balancer to use for traffic distribution

Default

A new Well Architected Application Load balancer is created.

Optional Readonly cpSubDomain

cpSubDomain?: string

Subdomain is usually the name of the microservice application such as user-app, account-app etc.

Default

app

Optional Readonly cpVpc

cpVpc?: CcVpc

You can pass your existing VPC where you like ECS cluster to be created

Default

A new Well Architected VPC will be created

Settings

Member Visibility

Theme

On This Page

Generated using TypeDoc