I *believe* that FME transformers which are python based do not support the NTLM authentication and I suspect that the s3 connectors are in fact pyhton based. This looks like it's supported by the article you've linked.

 

 

Can you try perhaps building the Request with an HTTPCaller? If you are simple trying to get a file from the bucket then the HTTP Caller *should* work with NTLM. A good was to track what steps FMEs webtools are doing is often to turn on the DEBUG log in FME (Just make sure to ignore all the BADNEWS stuff). With the HTTPCaller you should see a little more information about FME Trying to connect through the proxy or not.

 

 

Some background maps are also not supported with NTLM so that could be another test to see if NTLM is the issue here: https://knowledge.safe.com/articles/34337/unable-to-access-background-maps-in-data-inspector.html

 

 

 

---

I *believe* that FME transformers which are python based do not support the NTLM authentication and I suspect that the s3 connectors are in fact pyhton based. This looks like it's supported by the article you've linked.

 

 

Can you try perhaps building the Request with an HTTPCaller? If you are simple trying to get a file from the bucket then the HTTP Caller *should* work with NTLM. A good was to track what steps FMEs webtools are doing is often to turn on the DEBUG log in FME (Just make sure to ignore all the BADNEWS stuff). With the HTTPCaller you should see a little more information about FME Trying to connect through the proxy or not.

 

 

Some background maps are also not supported with NTLM so that could be another test to see if NTLM is the issue here: https://knowledge.safe.com/articles/34337/unable-to-access-background-maps-in-data-inspector.html

 

 

 

Many thanks for this. As I understand it I will (should) be able to send an object to an AWS S3 bucket using HTTP put/post as at here:

https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOST.html

Are there things to watch out for? Alongside here,

https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html

could you explain which headers would be required for an http put request to an aws s3 bucket? I seem to be generating a lot of http 400 bad requests... Is it possibleto force https for these requests? Sorry - sounds like I need some s3 training!

 

---

Many thanks for this. As I understand it I will (should) be able to send an object to an AWS S3 bucket using HTTP put/post as at here:

https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPOST.html

Are there things to watch out for? Alongside here,

https://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-auth-using-authorization-header.html

could you explain which headers would be required for an http put request to an aws s3 bucket? I seem to be generating a lot of http 400 bad requests... Is it possibleto force https for these requests? Sorry - sounds like I need some s3 training!

 

I'm afraid that I'm also not really the export here, if you want to experience with REST Calls, I would recommend that you use PostMan. It's a pretty handy tool which you can work with to build your requests. Once you have something working you can then try with the HTTPCaller

 

 

I have no idea how the NTLM stuff will work with a requests though. It looks like for Postman that the NTLM is still in Beta https://learning.getpostman.com/docs/postman/sending_api_requests/authorization/

 

 

It's worth checking. Otherwise perhaps IT have a different method which you could use for the proxy? or whitelist it so that requests to S3 skip the proxy?

 

 

 

---

I *believe* that FME transformers which are python based do not support the NTLM authentication and I suspect that the s3 connectors are in fact pyhton based. This looks like it's supported by the article you've linked.

 

 

Can you try perhaps building the Request with an HTTPCaller? If you are simple trying to get a file from the bucket then the HTTP Caller *should* work with NTLM. A good was to track what steps FMEs webtools are doing is often to turn on the DEBUG log in FME (Just make sure to ignore all the BADNEWS stuff). With the HTTPCaller you should see a little more information about FME Trying to connect through the proxy or not.

 

 

Some background maps are also not supported with NTLM so that could be another test to see if NTLM is the issue here: https://knowledge.safe.com/articles/34337/unable-to-access-background-maps-in-data-inspector.html

 

 

 

Thanks MAtt, A quick look tells me that for me learning the http, authentication requirements and relevant interaction at the low level is likely to be less cost effective than paying for a proxy authentication - so I will probably go down that route.

---

Thanks MAtt, A quick look tells me that for me learning the http, authentication requirements and relevant interaction at the low level is likely to be less cost effective than paying for a proxy authentication - so I will probably go down that route.

Fair enough, i's especially complicated when working with AWS as well. *headache emoji*. Good luck with your work

---