s3 ACLs not working as expected

[Rahul Singh]

Tried setting 'public-read' on an object like this(canned ACL):
$ aws s3api put-object-acl --bucket test-acl --key file.txt \
--acl public-read --endpoint-url https://s3.<endpoint>
It gives 400 bad requests if object is accessed by unauthorized request(https://s3.<endpoint>/test-acl/file.txt).
If tried with some separate account, gives 404 bucket does not exist.

Tried setting '--grant-full-control' acl for permission on different account like this:
$ aws s3api put-bucket-acl --bucket test-acl --grant-full-control \
id=<user_name1>:<user_name1> --endpoint-url https://s3.<endpoint>
If this bucket is accessed using the <user_name1> account, it gives 404 bucket does not exist.

After setting the above ACLs, it was checked if the acl was assigned with below command:

$ aws s3api get-bucket-acl --bucket test-acl \
--endpoint-url https://s3.<endpoint>

It seems that the ACLs are getting set properly, but they are not behaving as expected. Let me know If I can provide more info on this.