Mutual TLS for HTTPS access on an embedded device

0

Hi all,

I am new to AWS, so I apologise in advance if my description is a bit foggy, but I will try my best to supply any information as it becomes relevant.

Im essentially trying to deploy a Content Delivery Network, CDN, for binary files and a little bit of JSON. Behaviourally what I want to do is have an s3 bucket with 3 folders, one for each hardware type, these folders contain binary files of the form binaryfileclass-v1.0.bin. Then I use llambda to intercept the incoming client request for the default endpoint, and instead generate a kind of JSON menu of the binary files that are available and their scraped versions. This way the embedded client device can use its own internal logic to make a choice on what to download.

I want to setup mutual TLS from both the s3 to the cloudfront, and the cloudfront to the client. I assume I need this mediated by ACM in order to export the certs to use on the embedded device itself. I am however having trouble with this, ACM is rejecting each of my certificate requests, despite trying to use a route53 domain with a custom CNAME. I am aware of the ability to upload a cert from a third party CA, but Iam trying to avoid this as long as possible (with the intention of trying to keep everything in AWS Land).

If anyone has any pointers, or is willing to explain how I am going wrong, I would be extremely grateful.

Best Wishes,

Josh C

1 回答
0

Probably cannot be used given the technical considerations of mTLS authentication. In this configuration, HTTP requests specifying a client certificate are first requested to CloudFront. Since there is no client authentication between the client and CloudFront, the specified client certificate is not used. Additionally, it's worth noting that mTLS is not supported for Edge-optimized APIs and can be used with Regional APIs only​​.

is there any specific use case that you are exploring at the moment ?

AWS
已回答 6 个月前

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则