CORS configuration in AWS - Time & Space Complexity

Time Complexity: CORS configuration

O(n)

Understanding Time Complexity

When setting up CORS (Cross-Origin Resource Sharing) on AWS services, it is important to understand how the time to apply or update these settings changes as you add more rules.

We want to know how the number of CORS rules affects the time it takes to configure them.

Scenario Under Consideration

Analyze the time complexity of updating CORS rules on an AWS S3 bucket.

    aws s3api put-bucket-cors --bucket example-bucket --cors-configuration '{
      "CORSRules": [
        {"AllowedOrigins": ["*"], "AllowedMethods": ["GET"]},
        {"AllowedOrigins": ["https://example.com"], "AllowedMethods": ["POST"]}
      ]
    }'
    

This command updates the CORS configuration by sending all rules at once to the bucket.

Identify Repeating Operations

Look at what happens when you add more CORS rules.

• Primary operation: Sending the entire CORS configuration to the bucket with one API call.
• How many times: One API call per update, regardless of number of rules.

How Execution Grows With Input

Adding more CORS rules means the configuration data grows, but you still send it in one request.

Input Size (n)	Approx. Api Calls/Operations
10 rules	1 API call
100 rules	1 API call
1000 rules	1 API call

Pattern observation: The number of API calls stays the same, but the size of data sent grows with the number of rules.

Final Time Complexity

Time Complexity: O(n)

This means the time to process the CORS configuration grows linearly with the number of rules because the data size increases.

Common Mistake

[X] Wrong: "Adding more CORS rules means more API calls are needed."

[OK] Correct: Actually, you send all rules in one API call, so the number of calls does not increase with rules.

Interview Connect

Understanding how configuration updates scale helps you design efficient cloud setups and explain your reasoning clearly in discussions.

Self-Check

"What if the CORS configuration was updated by sending one rule per API call? How would the time complexity change?"

Practice

1. What does CORS stand for and why is it important in AWS S3 bucket configuration?

easy

A. Cross-Origin Resource Sharing; it controls access to resources from different websites.

B. Cloud-Origin Resource Security; it encrypts data in S3 buckets.

C. Cross-Object Resource Sync; it syncs files between buckets.

D. Cloud-Origin Resource Sharing; it manages AWS user permissions.

Solution

1. Step 1: Understand the acronym CORS

   CORS stands for Cross-Origin Resource Sharing, a web security feature.

2. Step 2: Identify its role in AWS S3

   CORS controls which websites can access resources in an S3 bucket, preventing unauthorized cross-site requests.

3. Final Answer:

   Cross-Origin Resource Sharing; it controls access to resources from different websites. -> Option A

4. Quick Check:

   CORS = Cross-Origin Resource Sharing [OK]

Hint: Remember CORS controls cross-site resource access [OK]

Common Mistakes:

• Confusing CORS with encryption or syncing
• Thinking CORS manages AWS user permissions
• Assuming CORS is only for AWS internal use

2. Which of the following is the correct JSON snippet to allow GET and POST methods from any origin in an S3 bucket CORS configuration?

easy

A. { "CORSRules": [{ "AllowedOrigins": ["http://example.com"], "AllowedMethods": ["PUT"] }] }

B. { "CORSRules": [{ "AllowedOrigins": ["*"], "AllowedMethods": ["DELETE"] }] }

C. { "CORSRules": [{ "AllowedOrigins": ["*"], "AllowedMethods": ["GET", "POST"] }] }

D. { "CORSRules": [{ "AllowedOrigins": ["*"], "AllowedMethods": ["PATCH"] }] }

Solution

1. Step 1: Identify AllowedOrigins and AllowedMethods

   The question asks for allowing any origin (*) and methods GET and POST.

2. Step 2: Match JSON snippet to requirements

   { "CORSRules": [{ "AllowedOrigins": ["*"], "AllowedMethods": ["GET", "POST"] }] } correctly sets AllowedOrigins to ["*"] and AllowedMethods to ["GET", "POST"].

3. Final Answer:

   { "CORSRules": [{ "AllowedOrigins": ["*"], "AllowedMethods": ["GET", "POST"] }] } -> Option C

4. Quick Check:

   AllowedOrigins=* and AllowedMethods=GET,POST [OK]

Hint: Look for AllowedOrigins '*' and methods GET, POST [OK]

Common Mistakes:

• Using wrong HTTP methods like DELETE or PATCH
• Setting AllowedOrigins to a specific domain instead of '*'
• Incorrect JSON structure or missing brackets

3. Given this CORS configuration snippet for an S3 bucket:

{
  "CORSRules": [
    {
      "AllowedOrigins": ["https://example.com"],
      "AllowedMethods": ["GET"],
      "AllowedHeaders": ["*"],
      "MaxAgeSeconds": 3000
    }
  ]
}

What will happen if a browser from https://example.com sends a POST request to this bucket?

medium

A. The POST request will succeed because MaxAgeSeconds is set.

B. The POST request will succeed because AllowedHeaders is '*'.

C. The POST request will be redirected to GET automatically.

D. The POST request will be blocked due to method not allowed.

Solution

1. Step 1: Check AllowedMethods in CORS configuration

   Only GET method is allowed from https://example.com.

2. Step 2: Understand effect on POST request

   POST is not in AllowedMethods, so the browser will block the request due to CORS policy.

3. Final Answer:

   The POST request will be blocked due to method not allowed. -> Option D

4. Quick Check:

   AllowedMethods=GET only, POST blocked [OK]

Hint: AllowedMethods must include the request method [OK]

Common Mistakes:

• Confusing AllowedHeaders with AllowedMethods
• Thinking MaxAgeSeconds affects allowed methods
• Assuming POST auto-converts to GET

4. You configured this CORS rule on your S3 bucket but your web app still gets CORS errors when making PUT requests from https://myapp.com:

{
  "CORSRules": [
    {
      "AllowedOrigins": ["https://myapp.com"],
      "AllowedMethods": ["GET", "POST"],
      "AllowedHeaders": ["*"]
    }
  ]
}

What is the most likely cause of the error?

medium

A. PUT method is not included in AllowedMethods.

B. AllowedOrigins should be '*', not a specific domain.

C. AllowedHeaders cannot be '*'.

D. CORSRules must include MaxAgeSeconds.

Solution

1. Step 1: Review AllowedMethods for PUT requests

   PUT is not listed in AllowedMethods, only GET and POST are allowed.

2. Step 2: Understand CORS behavior for unsupported methods

   Requests with methods not allowed by CORS are blocked by browsers.

3. Final Answer:

   PUT method is not included in AllowedMethods. -> Option A

4. Quick Check:

   AllowedMethods missing PUT causes CORS error [OK]

Hint: Check AllowedMethods includes your HTTP method [OK]

Common Mistakes:

• Assuming AllowedOrigins must be '*' for CORS to work
• Thinking AllowedHeaders '*' is invalid
• Believing MaxAgeSeconds is required

5. You want to configure an S3 bucket to allow only GET and OPTIONS requests from two specific domains: https://site1.com and https://site2.com. You also want browsers to cache the CORS response for 1 hour. Which is the correct CORS configuration JSON?

hard

A. {
"CORSRules": [
{
"AllowedOrigins": ["*"],
"AllowedMethods": ["GET", "OPTIONS"],
"AllowedHeaders": ["*"],
"MaxAgeSeconds": 3600
}
]
}

B. {
"CORSRules": [
{
"AllowedOrigins": ["https://site1.com", "https://site2.com"],
"AllowedMethods": ["GET", "OPTIONS"],
"AllowedHeaders": ["*"],
"MaxAgeSeconds": 3600
}
]
}

C. {
"CORSRules": [
{
"AllowedOrigins": ["https://site1.com"],
"AllowedMethods": ["GET"],
"AllowedHeaders": ["*"],
"MaxAgeSeconds": 3600
},
{
"AllowedOrigins": ["https://site2.com"],
"AllowedMethods": ["GET", "OPTIONS"],
"AllowedHeaders": ["*"],
"MaxAgeSeconds": 3600
}
]
}

D. {
"CORSRules": [
{
"AllowedOrigins": ["https://site1.com", "https://site2.com"],
"AllowedMethods": ["GET"],
"AllowedHeaders": ["*"],
"MaxAgeSeconds": 3600
}
]
}

Solution

1. Step 1: Check AllowedOrigins for both domains

   { "CORSRules": [ { "AllowedOrigins": ["https://site1.com", "https://site2.com"], "AllowedMethods": ["GET", "OPTIONS"], "AllowedHeaders": ["*"], "MaxAgeSeconds": 3600 } ] } correctly lists both https://site1.com and https://site2.com in AllowedOrigins.

2. Step 2: Verify AllowedMethods and MaxAgeSeconds

   { "CORSRules": [ { "AllowedOrigins": ["https://site1.com", "https://site2.com"], "AllowedMethods": ["GET", "OPTIONS"], "AllowedHeaders": ["*"], "MaxAgeSeconds": 3600 } ] } allows GET and OPTIONS methods and sets MaxAgeSeconds to 3600 (1 hour), matching requirements.

3. Final Answer:

   { "CORSRules": [ { "AllowedOrigins": ["https://site1.com", "https://site2.com"], "AllowedMethods": ["GET", "OPTIONS"], "AllowedHeaders": ["*"], "MaxAgeSeconds": 3600 } ] } -> Option B

4. Quick Check:

   AllowedOrigins two domains, methods GET & OPTIONS, cache 3600s [OK]

Hint: List all domains in AllowedOrigins and set MaxAgeSeconds for caching [OK]

Common Mistakes:

• Using '*' for AllowedOrigins when only specific domains are needed
• Missing OPTIONS method which browsers send for CORS preflight
• Splitting domains into multiple rules unnecessarily