Cloudflare One, Access - Access for Infrastructure now supports tagged targets and tag-based target criteria

<p><a href="https://developers.cloudflare.com/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/">Access for Infrastructure</a> now integrates with <a href="https://developers.cloudflare.com/resource-tagging/">Resource Tagging</a>. You can attach key-value tags to <a href="https://developers.cloudflare.com/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/#1-add-a-target">infrastructure targets</a> and use them in access policies.</p> <p>You can manage tags on targets inline when you create or edit a target or through the central <a href="https://developers.cloudflare.com/resource-tagging/how-to/manage-tags/">Resource Tagging API</a>. Cloudflare keeps tags in sync across both methods.</p> <p>Infrastructure applications also support a target criteria model with <code>include</code>, <code>require</code>, and <code>exclude</code> operators. Each operator can match targets by hostname, tag, or both.</p> <ul> <li><strong>Include</strong> matches targets that have any of the specified values.</li> <li><strong>Require</strong> matches targets that have all of the specified values.</li> <li><strong>Exclude</strong> rejects targets that have any of the specified values.</li> </ul> <img src="https://developers.cloudflare.com/cdn-cgi/image/onerror=redirect,width=2372,height=1616,format=webp/_astro/tags-in-infra-app.ja2Tp-Gq.png" alt="Infrastructure application builder showing target criteria with an included tag, port 22, and SSH as the selected protocol" loading="lazy" decoding="async" width="2372" height="1616"> <p>For more information, refer to <a href="https://developers.cloudflare.com/cloudflare-one/access-controls/applications/non-http/infrastructure-apps/">Add an infrastructure application</a>.</p>