Practice Test 3 | AWS Certified Solutions Architect Associate | SAA-C03 | Dumps | Mock Test
Your company wants to use an S3 bucket for web hosting but have several different domains perform operations on the S3 content. In the CORS configuration, you want the following origin sites: http://mysite.com, https://secure.mysite.com, and https://yoursite.com. The site, https://yoursite.com, is not being allowed access to the S3 bucket. What is the most likely cause?
A. Site https://yoursite.com was not correctly added as an origin site; instead included as http://yoursite.com
B. HTTPS must contain a specific port in the request, e.g. https://yoursite.com:443
C. There’s a limit of two origin sites per S3 bucket allowed
D. Adding CORS automatically removes the S3 ACL and bucket policies
Explanation:
Answer: A
- A. The origin was misconfigured as http://yoursite.com instead of https://yoursite.com The exact syntax must be matched. In some cases, wildcards can be used to help in the origin URLs.
Incorrect:
- B. This is not required in allowing an origin domain to be included; although it can be.
- C. The limit is 100
- D. The ACLs and policies continue to apply when you enable CORS on the bucket.
Verify that the Origin header in your request matches at least one of the AllowedOrigin elements in the specified CORSRule.
The scheme, the host, and the port values in the Origin request header must match the AllowedOrigin elements in the CORSRule. For example, if you set the CORSRule to allow the origin http://www.example.com, then both https://www.example.com and http://www.example.com:80 origins in your request don’t match the allowed origin in your configuration.
Reference:
Comments are closed, but trackbacks and pingbacks are open.