AS2 transfer without a JSON file

hi,

Step 1: Is the .mdn file present in the S3 bucket? to troubleshoot further, verify whether the .mdn file exists in the correct S3 location.

AWS CLI:->

aws s3 ls s3://your-bucket-name/path/to/ --recursive | grep .mdn

Step 2: Once the .mdn file is in S3 You can download it locally to inspect:

aws s3 cp s3://your-bucket-name/path/to/file.mdn .

Step 3: Inspect MDN headers or S/MIME structure (Linux CLI)

To troubleshoot AS2 issues, use Linux tools like cat, grep, awk, or sed to extract useful info like the disposition status.

cat file.mdn | grep -i Disposition

hope it will help.

Best

This situation you're describing is unusual and not the expected behavior for AS2 transfers using AWS Transfer Family. Typically, when an AS2 transfer occurs, both a JSON file and an MDN (Message Disposition Notification) file should be created.

The JSON file is indeed crucial as it contains important details about the transfer, including status codes, file information, and other metadata. The fact that you're only receiving an MDN without the corresponding JSON file is concerning.

There are a few possibilities to consider:

1. Partial Transfer: It's possible that the transfer was only partially completed. The MDN might have been generated, but the process of creating and saving the JSON file may have been interrupted.

2. Configuration Issue: There could be a misconfiguration in your AS2 connector or agreement settings that's preventing the JSON file from being generated or saved properly.

3. Permission Problems: If there are issues with permissions in the S3 bucket where the files are supposed to be saved, it might prevent the JSON file from being written while still allowing the MDN to be generated.

4. Logging Discrepancy: The fact that you only see an MDN response wait event in the CloudWatch logs is unusual. Typically, you should see more detailed logs about the transfer process.

To troubleshoot this issue:

1. Double-check your AS2 connector and agreement configurations to ensure all settings are correct.

2. Verify the permissions on the S3 bucket where the files should be saved.

3. Try the transfer again and closely monitor the CloudWatch logs for any error messages or unusual patterns.

4. If possible, test with a different partner or endpoint to see if the issue persists.

5. Check if there are any recent updates or changes to your AWS Transfer Family setup that might have affected this behavior.

If after these steps you're still encountering this issue, it would be advisable to contact AWS Support. This behavior is not typical, and if it's occurring consistently, it could indeed be a bug in the AS2 transfer process that needs to be addressed by AWS.

Remember, for successful AS2 transfers, you should typically see both a JSON file (with details about the transfer) and an MDN file, along with more comprehensive logging in CloudWatch.

Sources
Sending and receiving AS2 messages - AWS Transfer Family
Troubleshoot AS2 issues - AWS Transfer Family
Transfer Family events detail reference - AWS Transfer Family

Hi! Please reach out to the AWS Transfer Family team via AWS support ticket or your account team to troubleshoot the error you are experiencing. With Transfer Family, JSON status files are expected to be generated for all AS2 message transfers.