Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Support attachment uploads in dev return 503 after ten seconds because Network Firewall drops the TLS handshake to
upload.filestackapi.com. Firewall alerts at 2026-09-09 06:19:27 UTC and 06:21:30 UTC precede the corresponding API timeout warnings by ten seconds. A diagnostic task using the deployed image and the same ECS network reproduced the failure before any HTTP body was sent.Document the required Filestack upload-domain allowlist entry, the storage endpoint requirement, and verification from the ECS network. This explains why local Filestack uploads can succeed while deployed uploads time out.
Validation:
pnpm lint,pnpm build, andgit diff --checkpassed. The dev firewall update adding.filestackapi.comtoAllowed-Domains-Rulegrouppassed the AWS API dry run and was applied with user approval on 2026-09-09. The firewall is READY/IN_SYNC, and the resulting rule group was verified to differ only by the approved domain addition. This PR changes documentation only.Post-change verification: diagnostic tasks using the deployed Support API image successfully uploaded both 32-byte and 2 MiB files from each of the service’s two ECS subnets. All Filestack and S3 stages returned HTTP 200, and the service returned canonical delivery metadata. The 2 MiB uploads completed in 459 ms and 523 ms. Both diagnostic tasks stopped with exit code 0; the Support service remains at its desired running count.