Skip to content

aws_quicksight_refresh_schedule.start_after_date_time is an error if the time zone is included. #42190

@RYOSKATE

Description

@RYOSKATE

Terraform and AWS Provider Version

5.94.1

Affected Resource(s) or Data Source(s)

  • aws_quicksight_refresh_schedule

Expected Behavior

Change the validation so that the ISO 8601 format can be specified based on https://docs.aws.amazon.com/glossary/latest/reference/glos-chap.html#timestamp.
For example 2025-10-10T13:50:40+09:00.

Actual Behavior

Any format other than YYYYY-MM-DDTHH:MM:SS as defined in

startAfterDateTimeFormat = "YYYY-MM-DDTHH:MM:SS"
will result in an error.
+09:00, etc. cannot be entered.

The AWS documentation gives only YYYYY-MM-DDTHH:MM:SS as an example, but that is just one example, and the format including time zone can be used for this timestamp-type item by checking with the AWS CLI or other means.
https://docs.aws.amazon.com/quicksight/latest/APIReference/API_RefreshSchedule.html

Relevant Error/Panic Output

Sample Terraform Configuration

Click to expand configuration
resource "aws_quicksight_refresh_schedule" "example" {
  data_set_id = "dataset-id"
  schedule_id = "schedule-id"
  schedule_id = "2025-04-10T12:34:56+09:00"

  schedule {
    refresh_type = "FULL_REFRESH"

    schedule_frequency {
      interval = "HOURLY"
    }
  }
}

Steps to Reproduce

Apply the configuration

Debug Logging

Click to expand log output

GenAI / LLM Assisted Development

n/a

Important Facts and References

No response

Would you like to implement a fix?

No

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugAddresses a defect in current functionality.service/quicksightIssues and PRs that pertain to the quicksight service.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions