Intercept file sending request to the AS2 partner in Transfer Family Connector

Question

Our AS2 partner requires us to send the AS2 message with a content-disposition header containing the file name. But, we see that Transfer family connector is not including the content-disposition header automatically by deriving the filename from the S3 file we're sending to the partner.
We have added the Content-Disposition header while uploading the file to the S3 bucket & we found that in the file metadata. But, AS2 connector is not generating the header is not generating that automatically while sending the message to the partner.

We want to intercept the request to add the header manually from our side. If the Transfer family does that by itself how can we inspect the request headers. In the cloud watch logs, that information is not present.

Vinamra Jain · Answer

Hello! The AWS Transfer family service team would like to learn more about your use-case to recommend solutions for this need, as well inform the feature roadmap for AS2 offering. Request you to reach out to the service team via AWS support or your account team.

Vinamra Jain · Answer

Hello! Transfer Family documentation now provides a deployable solution to intercept the request and add the custom header for your outbound AS2 messages - https://docs.aws.amazon.com/transfer/latest/userguide/as2-custom-http-headers.html

re:Post Agent · Answer

Unfortunately, AWS Transfer Family does not currently provide a way to directly intercept or modify the outbound AS2 message headers before they are sent to your trading partner. The AS2 connector in Transfer Family handles the message preparation and sending process internally, and there isn't a built-in mechanism to add custom headers like Content-Disposition.

However, there are a few potential workarounds you could consider:

1. Check if your trading partner can accept the filename through alternative means, such as within the AS2 message body or through a pre-arranged naming convention.

2. Contact AWS Support to see if they can provide a solution or if this feature might be added in the future. AWS regularly updates their services based on customer feedback.

3. Consider using a different AS2 solution that allows more granular control over message headers if this is a critical requirement for your use case.

As for inspecting the request headers, you're correct that this information is not available in CloudWatch logs. Transfer Family's logging is primarily focused on the overall transfer status and outcomes rather than the specific message details.

If you need to verify the exact contents of the AS2 messages being sent, you might need to set up a test environment with your trading partner where they can provide you with the full details of the received messages, including headers.

Remember that while Transfer Family aims to be compliant with AS2 standards, it may not support all possible customizations that some legacy or highly specialized AS2 implementations might require.  
**Sources**  
[AWS Transfer Family for AS2 - AWS Transfer Family](https://docs.aws.amazon.com/transfer/latest/userguide/as2-for-transfer-family.html)  
[Monitoring AS2 usage - AWS Transfer Family](https://docs.aws.amazon.com/transfer/latest/userguide/as2-monitoring.html)

Intercept file sending request to the AS2 partner in Transfer Family Connector

Add your answer

Relevant content