- Newest
- Most votes
- Most comments
For cloudfront just use the regional s3 endpoint URL or the global S3 endpoint URL.
I’m not sure if using MRAP provides any functionality with cloudfront.
Not answering the question but here's an alternative solution.
Yes, I know that... but this requires lambda@edge and increases the cost to build a similar routing that MRAP is optimized for :-(
Found. Have you configured this way?
https://docs.aws.amazon.com/AmazonS3/latest/userguide/MultiRegionAccessPointRestrictions.html
To use Multi-Region Access Points with Amazon CloudFront, you must configure the Multi-Region Access Point as a Custom Origin distribution type. For more information about various origin types, see Using various origins with CloudFront distributions. For more information about using Multi-Region Access Points with Amazon CloudFront, see Building an active-active, proximity-based application across multiple Regions.
That's exactly what I tried. And the problem is custom origins types does not have the option for OAC or OAI... so this unfortunately works only for "public" configured buckets...
Relevant content
- Accepted Answerasked 2 months ago
- asked 4 months ago
AWS OFFICIALUpdated 2 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
I want the request coming via CloudFront to go to the nearest S3 bucket. For this MRAP is optimal. And for "public" S3 buckets (and MRAP) it works... it just does not work for "private" ones...