URL for public Amazon S3 bucket -

I have an Amazon S3 bucket that I make public with this policy

 < Code: {"version": "2012-10-17", "Statement": [{"Sid": "Allow all objects to public access", "effect": "Allow", "Principal": " "", "Action": "S3: GetObject", "resource": "arn: aws: s3 ::: bucket / *"}]}   
 as my bucket now Seeing  
 I see others in my bucket  
 I like the other URL But it gives an admission prohibition.  
 How can I change my policy to allow another policy?  
 
 
  
 
  Note: Since this reply was originally written, S3, using the new hostnames, leaving existing hostnames in place, Dual-base support has begun at end points. It has now been integrated into the information given below.   
 
 If your bucket is actually in the AWS K-East-1 area - then  http: //s3-us-east-1.amazonaws.com/ The bucket /  is not the right form for that endpoint, even if it seems that it should be. The correct format for that area is either  http://s3.amazonaws.com/bucket/  or  http://s3-external-1.amazonaws.com/bucket/  And sup1 
 
 The format you are using applies to all other S3 areas, but  US Standard  US East (N. Virginia) [us-east-1] 
 
 The S3 is still for the rest, and unlike the original endpoint hostnames, the names of these two have the same format throughout the field, for example  s3.dualstack.us-east -1.amazonaws.com . These endpoint support both IPv4 and IPv6 connectivity and DNS resolution, but otherwise functionally equivalent to the existing comfort points. 
 
 If your permissions and configuration are set up, then Web site Endpoint works, then the rest of the end point 
 
 however ... both endpoint does not offer the same functionality We do. 
 
 Broadly speaking, the rest is better for machine access and the web site finishing point is better suited for human use, because Web Site Endpoint provides friendly error messages, index documents and redirects, While the other is not the end point. On the other hand, the resting point provides HTTPS and supports for signed URLs, while the Web site does not endpoint. 
 
 
 
 
 and sup1; 
 
 Unlike "global endpoint"  s3.amazonaws.com , "northern Virginia end point" as  s3-external-1.amazonaws.com . If the "s3-external-1" hostname was used, it was unofficially possible for you to get read-write-on new objects in this area, because it allows you to have a subset of possible physical closing points Which can provide functionality, now this behavior is officially supported at this endpoint, so it is probably a better option in many applications. First, in the form of "Pacific Northwest Endpoint" for  s3-external-2  US-Standard, though it is now a CNAME in DNS for  s3-external-1   S3-external-2  There is no purpose except for rear-compatibility.