Kiro + xCloud

Manage SSL and domains with Kiro on xCloud

Managing SSL and domains with Kiro means asking the agent in AWS's agentic IDE to read a site's certificate, test its DNS and install or renew HTTPS on xCloud from the chat panel where you write code.

Skill: xcloud:ssl
Toolsets: ssl-certificates, sites, integrations
Free with every xCloud account

Set up Kiro All Kiro guides

YouCheck SSL and DNS for the domain in this project before the launch.

sites_sslread-only

Agentapp.example.com has xCloud's free certificate, valid for 61 more days. The DNS record points at your server and is not proxied. Nothing to change.

YouGood. Renew it anyway so it is fresh for the launch.

sites_ssl_renewneeds approval

AgentRenewal accepted, but a normal renewal does nothing unless the certificate is within seven days of expiry, and this one has 61 days left. I can force it if you really want that. Say so and I will confirm first.

Last updated: October 2026. Keep a human in the loop: xCloud stops and asks before anything that creates, deploys, updates, reboots, deletes or buys.

Setup

How Do You Set Up Kiro to Manage SSL and domains on xCloud?

Connect Kiro once; every job on this account uses the same connection. Then ask in plain words.

1
Add xCloud to your Kiro MCP config
Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows and Linux), search for MCP and choose Kiro: Open workspace MCP config (JSON) for .kiro/settings/mcp.json, or Kiro: Open user MCP config (JSON) for ~/.kiro/settings/mcp.json. Paste this, save, and Kiro reconnects on its own. The first connection opens the xCloud approval screen in your browser, where you tick the teams and choose Read-only or Full access.
JSON
```
{
  "mcpServers": {
    "xcloud": {
      "url": "https://app.xcloud.host/mcp"
    }
  }
}
```
2
Choose which xCloud tools Kiro may run
Optional. autoApprove lists tools Kiro runs without asking, and disabledTools hides tools from the agent altogether. The two names here are real xCloud tools; swap in your own. Avoid the "*" wildcard in autoApprove, so Kiro's own prompt stays as a second check beside xCloud's confirmation.
JSON
```
{
  "mcpServers": {
    "xcloud": {
      "url": "https://app.xcloud.host/mcp",
      "autoApprove": ["xcloud_docs_search", "xcloud_agent_search"],
      "disabledTools": ["sites_destroy"]
    }
  }
}
```
3
No browser sign-in? Use an API key
Create a token with the mcp:invoke scope plus the read abilities for the areas it will use (read:servers and read:sites, with read:billing and read:addons for billing and add-on tools) and the matching write: abilities if it should change things in Settings, Developers, API Tokens, export it as XCLOUD_API_TOKEN, and pass it in headers. Kiro only expands environment variables you have approved, so add XCLOUD_API_TOKEN under the Mcp Approved Env Vars setting. Never paste the token into the file or into chat.
JSON
```
{
  "mcpServers": {
    "xcloud": {
      "url": "https://app.xcloud.host/mcp",
      "headers": {
        "Authorization": "Bearer ${XCLOUD_API_TOKEN}"
      }
    }
  }
}
```

Check it worked

Then ask Kiro for the job itself, for example:

Prompt

Check the SSL certificate and DNS for the domain used in this project. Tell me the provider, the expiry date and whether DNS points at my server.

In practice

How Does SSL and domains Work from Kiro?

Kiro keeps a conversation open beside your project, and the agent there already knows which workspace you are in. When a launch is close and you want to be sure HTTPS is in place, you write in the chat check the certificate and the DNS for the domain in this project, and Kiro reads the hostname from your files, asks xCloud for the SSL state, the certificate list and a DNS lookup, and answers with the provider, the status, the expiry date and whether the record points at your server. A proxied Cloudflare record is flagged on its own. Those are all reads, so they can run without a prompt if you listed them in autoApprove.

Kiro's own approval layer matters more here than in a quick terminal. The mcp.json entry lets you list tools the agent may run without asking, and tools it must never see. A sensible setup for this job approves the reads, hides the certificate deletion tool if you do not want it reachable at all, and leaves install and renew to prompt twice: once in Kiro, once in xCloud, which requires an explicit confirmation before it installs, renews or switches a certificate. When you answer yes, Kiro names the site and the provider, waits for the certificate status to settle and loads the HTTPS URL before it says the job is done.

Because the entry can live in the workspace or in your user settings, you can decide who gets this. A workspace-level mcp.json with only the URL holds no secret, so it can sit in the repository for a team that signs in with OAuth. The portable Agent Plugins package adds the workflow knowledge for certificates on top. If a task is outside the API, such as adding another domain to a live site, Kiro cannot do it and tells you the dashboard path, Site then Domain.

Kiro specific: MCP support has to be switched on in Kiro's settings before any of this appears. If you list tools in autoApprove, add only the read tools such as the certificate status and the DNS check, and avoid the wildcard so Kiro's prompt stays as a second check before a certificate is installed, renewed or deleted. When the same server name exists in a workspace file and a user file, Kiro's precedence rules decide which entry wins, so check both if the SSL tools seem missing.

What xCloud does for ssl and domains

xCloud lets the agent read a site's certificate status, domains and DNS, then install or renew a certificate from xCloud (Let's Encrypt), your own files or a connected Cloudflare account. Adding or changing a domain on an existing site stays in the dashboard, and the agent gives you the path.

Find the site and read its SSL. The agent resolves the site by name or domain, then reads its current SSL state and the list of certificates before it changes anything. That shows the provider, the status and the expiry date.
Check the domain and DNS. It reads the site's primary and additional domains and asks xCloud whether the domain's DNS record points at the server. Each check is one lookup, so the agent repeats it while a record propagates. A record behind Cloudflare's proxy is reported separately.
Choose the certificate source. You pick xCloud's free Let's Encrypt certificate, your own certificate, or the team's Cloudflare integration. If the site already uses a different provider, the agent tells you that switching needs an explicit override and asks first.
Install or renew, once you approve. The agent restates the site and the provider, then installs or renews the certificate. A renewal only runs when the certificate is within seven days of expiry unless you ask for a forced renewal. For a WordPress site turning on HTTPS for the first time, it asks whether to run the database search-and-replace.
Poll to issuance and verify. Install and renew report success before issuance completes. The agent polls the certificate status until it settles, then checks the site over HTTPS before it calls the job done.
Hand off domain changes. If you want to add, change or remove a domain on an existing site, the agent gives you the dashboard path (Site > Domain) and the site's dashboard link, because the API only reads domains after creation.

Reference

SSL and domains Settings and Limits on xCloud

The facts Kiro works within when it manages SSL and domains. Where a row names the dashboard, that step stays yours to take there.

Setting or limit	What applies
Certificate status	A site's SSL state, its certificate list and one certificate's detail and status are all readable
xCloud certificate	Free Let's Encrypt certificate issued and renewed by xCloud. The domain's DNS should already point at the server before you ask
Custom certificate	You supply the PEM certificate and its private key. The key is a secret and is never returned by a read
Cloudflare certificate	Uses the team's connected Cloudflare account. When the zone is connected, xCloud writes the DNS record and the certificate itself at site creation
Switching provider	Needs an explicit force when another provider is already configured, so the agent asks before it replaces a working certificate
Renewal rule	A renewal does nothing unless the certificate is within seven days of expiry; a forced renewal skips that guard. Renewing needs the site SSL permission on your team role
WordPress first HTTPS	An optional database search-and-replace moves existing http:// URLs to https:// when a WordPress site adopts HTTPS for the first time
DNS check	One lookup per call. A proxied Cloudflare record is flagged, and on a Cloudflare-managed site the proxied record is the finished state, not a fault
Domains (read)	The primary domain, additional domains and the domain update status are readable through the API
Domains (write)	Adding, changing or removing a domain on an existing site is dashboard-only: Site > Domain. A staging site goes live under Site > Domain > Go Live
Deleting a certificate	Available through the API, but it can take a site off HTTPS, so the agent restates the target and waits for your approval
Cloudflare 526 errors	A 526 or a certificate warning is an SSL problem, so the agent reads the certificate first. A 522 is different: it usually means ports 80 and 443 are blocked at the origin

Rules Kiro has to follow

Installing, renewing, switching or deleting a certificate stops for your approval, and the agent names the site and the provider before it asks.
A success response means xCloud accepted the work, not that the certificate was issued: the agent polls the status and checks the live HTTPS URL.
The agent never replaces a working certificate with a different provider without telling you, and it never turns off the Cloudflare proxy on a site xCloud manages through Cloudflare.
Changing a domain on an existing site is a dashboard step; the agent gives you the path and the dashboard link xCloud returned, not a made-up workaround.
A custom certificate's private key is a secret: it is never returned by a read and should not be pasted into a shared channel.

Example prompts

What Can You Ask Kiro to Do for SSL and domains?

Type these as written and swap in your own repository, site and server names. Reads and routine actions such as backups, cache purges, PageSpeed scans and vulnerability scans run straight away; creating, deploying, updating, rebooting, deleting, buying or starting a broken-link scan stops and asks first.

Prompt

Check the SSL certificate and DNS for the domain used in this project. Tell me the provider, the expiry date and whether DNS points at my server.

Prompt

List the sites on my Acme team whose certificate expires in the next 30 days.

Prompt

Renew the certificate on shop.example.com, then verify the site loads over HTTPS and tell me the new expiry date.

Prompt

Check the SSL certificate on shop.example.com and tell me when it expires.

Prompt

Is the DNS A record for example.com pointing at my Frankfurt server yet? Tell me if the Cloudflare proxy is on.

Prompt

Issue a free SSL certificate for example.com once DNS resolves, then confirm the site loads over HTTPS.

Prompt

Renew the certificate on the shop site and tell me the new expiry date.

Prompt

List every domain and additional domain on the shop site and say which is primary.

Prompt

Which of my sites have a certificate that expires in the next 30 days?

Prompt

Use my connected Cloudflare account for the certificate on shop.example.com, and show me what will change first.

Prompt

Visitors get a Cloudflare 526 error on shop.example.com. Check the certificate and tell me what is wrong.

Kiro and SSL and domains: Frequently Asked Questions

What people ask before they let Kiro manage SSL and domains through xCloud.

Should I put the xCloud SSL tools in Kiro's autoApprove list?

Only the reads. Certificate status, the certificate list and the DNS check are safe to approve. Leave install, renew and delete out, so Kiro prompts you and xCloud still asks for its own confirmation before it installs, renews or deletes a certificate.

Can Kiro hide the certificate delete tool from the agent?

Yes. Add the tool's name to disabledTools in the xcloud entry of mcp.json and the agent no longer sees it. Deleting a certificate can take a site off HTTPS, so hiding it is a reasonable choice for most projects.

Can an AI agent add a domain to an existing site?

No. The API reads a site's domains, additional domains and domain update status, but adding, changing or removing a domain on an existing site is a dashboard step under Site > Domain. A domain is chosen when the site is created. The agent can tell you what is currently set and give you the path.

Which certificate options can the agent install?

Three: xCloud's free Let's Encrypt certificate, a custom certificate you supply, and a certificate through your connected Cloudflare account. The agent checks the current state first and asks before it changes anything. Switching a site from one provider to another needs an explicit override.

Why did the agent say a renewal did nothing?

A normal renewal only fires when the certificate is within seven days of expiry. If you need it earlier, ask for a forced renewal and the agent will confirm before it runs. Renewing also needs the site SSL permission on your team role.

Does the agent set up my DNS records?

It reads and checks them rather than writing them. It can tell you whether a domain's record points at your server and whether the Cloudflare proxy is on. DNS and the certificate are written for you only at site creation, when the domain's zone is on a Cloudflare account you connected to xCloud.

What does the agent do about a Cloudflare 526 error?

It treats it as an SSL problem. It reads the site's certificate status and expiry, and fixes it with an installation or renewal after your approval. A 522 is a different fault, usually closed ports 80 and 443 on the origin, so it is checked against the firewall instead.

Other agents