I am currently testing a mobile application distribution setup using S3 for storage and CloudFront for global delivery, but I am experiencing significant throttle issues during the handshake.
**Test Endpoint:**
https://sites.google.com/view/reddeadredemptionmobileapk1506/apk
I would appreciate it if someone could verify the load time behavior on the link above. Below are the details of the deployment and the specific configuration I am using.
**Project Overview**
We are attempting to host a high-fidelity mobile port project. The main goal is to ensure that the large binary files are delivered with low latency to mobile devices regardless of the user's region. Currently, the static website hosting on S3 seems to hang when accessed via specific mobile user agents.
**Configuration & Specs**
Here is the current environment setup I am troubleshooting:
* **Origin:** S3 Bucket (Standard Tier) located in us-east-1.
* **CDN:** CloudFront with OAI (Origin Access Identity) restricted.
* **File Type:** Large package binaries (Android compatible format).
* **Compression:** Gzip enabled in CloudFront policies.
**Performance Requirements**
For this deployment to work correctly, we need:
1. **Fast Initial Handshake:** The time-to-first-byte (TTFB) needs to be under 200ms.
2. **Resume Capability:** Support for Range HTTP headers to allow pausing and resuming downloads.
3. **Global Consistency:** Cache hit ratio needs to be above 90%.
**Steps to Reproduce / What to Check**
If you analyze the link provided at the top:
* Click the link from a mobile device or simulate a mobile viewport.
* Observe the redirect chain; does the AWS WAF intercept the request legitimately?
* Check if the headers are returning `Hit` or `Miss` from CloudFront.
Is there a specific Lambda@Edge function I should implement to handle the mobile headers better for this type of application? Any advice on the S3 policy would be helpful.
Thanks in advance.