None
There are two different methods to configure the STS token for route53 issuer:
OCP-62500: use the pod identity webhook
OCP-65132: use CLOUD_CREDENTIALS_SECRET_NAME env
CM-159 E2E on AWS STS cluster
CM-160 Run e2e on hypershift cluster
openshift/openshift-tests-private#17507: CM-337: add e2e to cover AWS STS env for ACME dns01 route53 solver
openshift/openshift-tests-private#17986: [release-4.16] CM-337: add e2e to cover AWS STS env for ACME dns01 route53 solver
openshift/openshift-tests-private#18546: CM-337: use CLOUD_CREDENTIALS_SECRET_NAME when pod identity webhook is not used
openshift/openshift-tests-private#18598: [release-4.16] CM-337: use CLOUD_CREDENTIALS_SECRET_NAME when pod identity webhook is not used