Julie, Generally, you *shouldn't* need to set the endpoint if you are using standard AWS services, but there should be no harm in setting it consistent with the region you are trying to access. The S3 endpoints <http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region> follow a scheme of "s3-<region>.amazonaws.com" but it's inconsistent for some old like "us-east-1", so check that link for specifics if you set the endpoint.
Are you using a proxy or any configuration in the AWS tools beyond the secret key and access key? In case it's some region specific issue I'm glad to test it on my account, what region you are trying to access? Regards. Joe On Fri, Sep 9, 2016 at 4:00 PM, jmurakami <[email protected]> wrote: > Hi Joe, > > I am able to access the AWS Command Line Interface and was able to copy > files into the S3 Bucket. > > Endpoint Override Property: > Endpoint URL to use instead of the AWS default including scheme, host, > port, > and path. The AWS libraries select an endpoint URL based on the AWS region, > but this property overrides the selected endpoint URL, allowing use with > other S3-compatible endpoints. > > Is the endpoint something like this .. http://region.amazonaws.com/bucket > It didn't seem to work when I put in the correct region and bucket name. > > > Thanks, > Julie > > > > -- > View this message in context: http://apache-nifi-developer- > list.39713.n7.nabble.com/Nifi-Debugging-AWS-PutS3-processor- > tp13311p13315.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
