# Can AWS Fargate Deployment Ignore SSL Certificate?

**URL:** <https://community.dynatrace.com/t/can-aws-fargate-deployment-ignore-ssl-certificate/33198>\
**Category:** Cloud platforms\
**Tags:** ssl, aws\
**Created:** [November 8, 2021, 9:35am UTC](https://community.dynatrace.com/t/can-aws-fargate-deployment-ignore-ssl-certificate/33198 "2021-11-08T09:35:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mengsuan\_koe1](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@mengsuan\_koe1](https://community.dynatrace.com/u/mengsuan_koe1)\
**Post date:** [November 8, 2021, 9:35am UTC](https://community.dynatrace.com/t/can-aws-fargate-deployment-ignore-ssl-certificate/33198/1 "2021-11-08T09:35:57Z")

</div>

I am attempting to deploy OneAgent on AWS Fargate using Runtime Injection method as depicted here on documentation:&nbsp;[Monitor AWS Fargate — Dynatrace Docs](https://www.dynatrace.com/support/help/setup-and-configuration/setup-on-cloud-platforms/amazon-web-services/deploy-oneagent-on-aws-fargate/#expand-runtime-injection-3920)

However the Dynatrace cluster I am using is a on-prem managed one, which currently does not have valid SSL certificate due to custom domain name used. (Dynatrace Managed CMC does not support getting Let’s Encrypt certificate with custom domain name)

Is there a parameter that I can put for AWS to ignore the certificate of Dynatrace Managed? Like a --no-check-certificate kind of workaround.

---

<div class="post-metadata">

**Author:** ![rodrigo\_alvare1](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/rodrigo_alvare1/32/1927_2.png) [@rodrigo\_alvare1](https://community.dynatrace.com/u/rodrigo_alvare1)\
**Post date:** [November 8, 2021, 2:40pm UTC](https://community.dynatrace.com/t/can-aws-fargate-deployment-ignore-ssl-certificate/33198/2 "2021-11-08T14:40:48Z")

</div>

Hi,  
this is a limitation in AWS Fargate, here there is a discussion about that topic and possible workarounds like use an EC2 instance and add insecure repository or use ECR&nbsp;[[Fargate] [request]: Support for insecure registry · Issue #740 · aws/containers-roadmap · GitHub](https://github.com/aws/containers-roadmap/issues/740)

The managed cluster should come automatically with a Let’s Encrypt cert looking like [https://xxxxx.dynatrace-managed.com](https://xxxxx.dynatrace-managed.com)&nbsp;, that should work in this scenario

Regards