Skip to content

feat(cloudfront-origins): extend max keepaliveTimeout of HttpOrigin to 180#18837

Merged
mergify[bot] merged 2 commits intoaws:masterfrom
taeemo:feature/cloudfront-origins-extend-keep-alive-timeout
Feb 21, 2022
Merged

feat(cloudfront-origins): extend max keepaliveTimeout of HttpOrigin to 180#18837
mergify[bot] merged 2 commits intoaws:masterfrom
taeemo:feature/cloudfront-origins-extend-keep-alive-timeout

Conversation

@taeemo
Copy link
Copy Markdown
Contributor

@taeemo taeemo commented Feb 5, 2022

This pull request extends the maximum value of the keepaliveTimeout property for HttpOriginProps up to 180 seconds. This allows the use of the construct also in the case that a limit increase has been approved for CloudFront origin keep-alive timeout quota.

The 180 seconds cap should be AWS hard limit for that quota.

This is related to #18697, which only extended the readTimeout, but keepaliveTimeout can also be increased.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Feb 5, 2022

@github-actions github-actions bot added the @aws-cdk/aws-cloudfront Related to Amazon CloudFront label Feb 5, 2022
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Feb 5, 2022

Title does not follow the guidelines of Conventional Commits. Please adjust title before merge.

@taeemo taeemo changed the title Extend max keepaliveTimeout of HttpOrigin to 180 feat(cloudfront-origins): extend max keepaliveTimeout of HttpOrigin to 180 Feb 5, 2022
@github-actions github-actions bot added the @aws-cdk/aws-cloudfront-origins Related to CloudFront Origins for the CDK CloudFront Library label Feb 5, 2022
Copy link
Copy Markdown
Contributor

@comcalvi comcalvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Feb 21, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: c69334d
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify mergify bot merged commit 171fdcd into aws:master Feb 21, 2022
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Feb 21, 2022

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@taeemo taeemo deleted the feature/cloudfront-origins-extend-keep-alive-timeout branch February 21, 2022 12:31
TikiTDO pushed a commit to TikiTDO/aws-cdk that referenced this pull request Feb 21, 2022
…o 180 (aws#18837)

This pull request extends the maximum value of the keepaliveTimeout property for HttpOriginProps up to 180 seconds. This allows the use of the construct also in the case that a limit increase has been approved for CloudFront [origin keep-alive timeout quota](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-values-specify.html#DownloadDistValuesOriginKeepaliveTimeout).

The 180 seconds cap should be AWS hard limit for that quota.

This is related to aws#18697, which only extended the readTimeout, but keepaliveTimeout can also be increased.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

@aws-cdk/aws-cloudfront Related to Amazon CloudFront @aws-cdk/aws-cloudfront-origins Related to CloudFront Origins for the CDK CloudFront Library

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants