Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS Cloudwatch Synthetic canary minimum timeout value incorrect #19289

Closed
brendan-sherrin opened this issue May 10, 2021 · 2 comments · Fixed by #19515
Closed

AWS Cloudwatch Synthetic canary minimum timeout value incorrect #19289

brendan-sherrin opened this issue May 10, 2021 · 2 comments · Fixed by #19515
Labels
bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/synthetics Issues and PRs that pertain to the synthetics service.

Comments

@brendan-sherrin
Copy link

brendan-sherrin commented May 10, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.12.30

  • provider.archive v2.1.0
  • provider.aws v3.34.0
  • provider.local v2.1.0

Affected Resource(s)

aws_synthetics_canary

Terraform Configuration Files

resource "aws_synthetics_canary" "canary" {
  for_each = local.site_list
  depends_on = [ data.archive_file.canary-zip, aws_iam_role.canary-execution-role, aws_iam_role_policy_attachment.canary-role_attachment ]
  name                 = lookup(each.value, "friendly_name") #names have to be unique...
  artifact_s3_location = "s3://${aws_s3_bucket.<name>.bucket}/"   
  execution_role_arn   = aws_iam_role.canary-execution-role.arn
  handler              = "${lookup(each.value, "friendly_name")}.handler" 
  zip_file             = data.archive_file.canary-zip[each.key].output_path
  runtime_version      = "syn-python-selenium-1.0"  
  start_canary = true

  schedule {
    expression = "rate(1 minute)"
  }

  run_config {
    timeout_in_seconds = 5  
    memory_in_mb = 960  
  }
}

Expected Behavior

Canary should be created with a timeout of 5 seconds

Per AWS documentation, the minimum is 3 seconds:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-synthetics-canary-runconfig.html
TimeoutInSeconds:
Minimum: 3

Actual Behavior

The following error message was displayed:
Error: expected run_config.0.timeout_in_seconds to be in the range (60 - 840), got 5

22: timeout_in_seconds = 5

Steps to Reproduce

  1. Create a aws_synthetics_canary resource with a run_config, timeout_in_seconds value of less than 60
  2. Terraform apply

Important Factoids

Nope

References

AWS documentation showing minimum value of 3 seconds.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-synthetics-canary-runconfig.html

  • #0000
@ghost ghost added the service/synthetics Issues and PRs that pertain to the synthetics service. label May 10, 2021
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label May 10, 2021
@bill-rich bill-rich added bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed needs-triage Waiting for first response or review from a maintainer. labels May 12, 2021
@ewbankkit
Copy link
Contributor

Relevant AWS API Reference.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/synthetics Issues and PRs that pertain to the synthetics service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants