The Wayback Machine - https://web.archive.org/web/20221006023934/https://www.repost.aws/
By using AWS re:Post, you agree to the Terms of Use

Learn AWS faster by following popular topics

see all
1/18

Recent questions

see all
1/18

Sending AS2 messages between two AWS Transfer Family servers

I've set up AWS Transfer Family servers in two different regions to test the sending functionality. However, even though the VPC is created, sending messages fail with either UNABLE_TO_CONNECT_TO_REMOTE_HOST_OR_IP or "File path not found". I'm using S3 for the document to send. I've checked the IP address with a different program (Mendelson AS2) and it's able to connect fine. It even was able to send a test document. Despite that, when sending through a lambda function, it fails. A few things tried: * Checking permissions: I'm able to connect and describe the server, the connectors, etc with no problem so it's not that * Connector with the wrong URL: I used the same URL as the URL in Mendelson with the port attached at the end (http:/s-xxx:5080 in the format specified in [1] with the region). I also tried the URL without the port specified and that didn't work either * Region issue: I thought the mismatch between the region could be an issue since the lambda was set in us-west-1 while the as2 server I was sending to is in us-east2 so I created a different connector and had it send to itself in the same region. Still the same error with being unable to connect * Checked the cloudwatch logs: It actually reports that everything sent successfully with a 200 code Weird things noticed: * After the lambda is triggered, it creates the expected failed and processing folder but after the first few times, it no longer saves the results. I get a .cms file and a .json file sometimes but not every time, even though the cloudwatch logs are correctly created every time. * The failed and processed folders somehow got created a folder above rather than the folder the file was uploaded to. (e.g. the folder structure is bucket/folder 1/folder2/folder 3 and the uploaded file was in folder3. However, the failed and processing folders were created in folder2 instead of the expected folder3. This happened just once though. Additional question: I can upload this as a different question if needed but since it's related to my issue, I figured I'd put it here as well * What's the transfer id for? Is that supposed to be the execution id? There doesn't seem to be an option to view the results of the transfer in the documentation [2]. References: [1] https://docs.aws.amazon.com/transfer/latest/userguide/as2-end-to-end-example.html#as2-create-connector-example [2] https://docs.aws.amazon.com/transfer/latest/userguide/API_StartFileTransfer.html
0
answers
0
votes
2
views
asked 3 hours ago

AWS Official Documentation is Incorrect

I'm following this guide https://aws.amazon.com/premiumsupport/knowledge-center/cognito-user-pool-remembered-devices/ to set up remembered devices and I'm doing most things from scratch because there is no Ruby library like Warrant. First off, let me just say the PasswordVerifier formula in this doc is incorrect/lacks information (when calling ConfirmDevice). I had to look at js source code and warrant source code to reverse-engineer what it was actually looking for. ![errors](/media/postImages/original/IMz1dMMZs3T2Kfl-Vqzkgh_g) Next for, **Call RespondToAuthChallenge for DEVICE_PASSWORD_VERIFIER** it seems like the forumla given does not work at all. Is there any open source code The formula for S_USER = (SRP_B - k * g^(x))^(a + ux) does not seem to be using modular exponentiation and is returning a number so large, that my code isn't able to deal with it without some extra libraries. That does not seem like it's expected if all the other S values in open source code is using modular exponentiation. **Please provide some client-side code where this final formula for DEVICE_PASSWORD_VERIFIER actually works. There does not seem to be a working example anywhere, and it seems like AWS is just posting incorrect guides.** Edit: I'm looking at the code here to respond to device password verifier and it's completely different from what is described in the blog post: https://github.com/aws/aws-sdk-net-extensions-cognito/blob/e79202c2c622839e36e76659141b329c7a044251/src/Amazon.Extensions.CognitoAuthentication/Util/AuthenticationHelper.cs#L255
0
answers
0
votes
7
views
asked 3 hours ago

Recent articles

see all
1/18