- Newest
- Most votes
- Most comments
Thank you for reporting this issue. I apologize for the inconvenience you're experiencing. After reviewing the information provided, I can confirm that this appears to be a user interface bug in the Amazon AppFlow console.
The error message you're receiving is inconsistent with the actual functionality of Amazon AppFlow. According to the service specifications, Amazon AppFlow does support aggregating records into multiple files with a target file size of up to 600 MB. The error message suggesting that the target file size needs to be less than 600 MB is incorrect.
This seems to be a discrepancy between the user interface and the underlying service logic. The dropdown menu correctly offers 600 MB as an option, but the validation logic appears to be incorrectly configured, leading to this erroneous error message.
To work around this issue, you could try the following:
- Attempt to set a slightly lower target file size, such as 599 MB, to see if it bypasses the incorrect validation.
- If possible, use the AWS CLI or SDK to create or update the flow, as these methods might not be affected by the UI bug.
- Contact AWS support to report this bug, as they will be able to escalate it to the appropriate team for resolution.
Rest assured that this is likely a UI issue and not a limitation of the service itself. Amazon AppFlow should be capable of handling the 600 MB target file size for aggregation. We apologize for any confusion or inconvenience this may have caused, and appreciate your patience as AWS works to resolve this issue.
Sources
Partitioning and aggregating data output from an Amazon AppFlow flow - Amazon AppFlow
Managing Amazon AppFlow flows - Amazon AppFlow
Hello,
Thank you for providing the feedback on this. I will be passing this to the Appflow team.
Thank you.
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago