The NI AWS S3 toolkit uses Virtual Hosted Style bucket access, i.e. https://yourbucket.s3.amazonaws.com/an/object/in/the/bucket. Per Amazon's documentation, the wildcard cert they use won't work for bucket names with periods when buckets are accessed this way. So here are your options:
1. Don't put periods in your bucket names
2. Don't use HTTPS. The tricky thing here is that, last time I checked, deep down in the guts of the toolkit it builds the url with an https prefix whether or not Verify Server is set to true.
3. Come up with an alternate certificate verification module. In this case, I think you have to swap out all the NI HTTP client VIs and replace them with your own client that will use your certificate verification code.
So if I were you, I'd try really hard to make option 1 work. The toolkit is open source, so 2 is an ok workaround if you don't care about https. Option 3 is going to be a lot of work. Don't do that unless there's literally no other option.
