Network access
By default, a cloud environment can reach the internet. Use Internet access to control which external sites the agent can reach from the cloud environment. Limiting internet access helps reduce the risk of unintended access to untrusted resources.
The following modes are available:
- Off (required only)
Access only to domains that Air Teams requires to run agents and reach its own services.
The other modes, except All domains, also allow these domains. They stay allowed for the whole life of the environment, so both the setup script and the agent can reach them.
# JetBrains AI jetbrains.ai *.jetbrains.ai grazie.ai *.grazie.ai *.intellij.net # JetBrains Air services, such as repository connections and secrets *.jetbrains.cloud *.jetbrainscloud.com *.eks.intellij.net *.labs.jb.gg *.jetbrains.com # Claude Agent storage.googleapis.com # Antigravity dl.google.com # Junie, also used by GitHub Copilot *.githubusercontent.com # Gradle and Maven tooling, and Junie releases services.gradle.org github.com plugins.gradle.org repo.maven.apache.org plugins-artifacts.gradle.org # OpenAI Codex nodejs.org registry.npmjs.org # GitHub Copilot api.github.com *.githubcopilot.com # Default agent container image registry.jetbrains.team db2uklzeiyqq6.cloudfront.net s3.*.amazonaws.com # JetBrains Air agent storage jcp-agent-spawner-stgn-jcp-agent-spawner-sidecar-*.s3.*.amazonaws.com jcp-agent-spawner-preprod-jcp-agent-spawner-sidecar-*.s3.*.amazonaws.com jcp-agent-spawner-prod-jcp-agent-spawner-sidecar-*.s3.*.amazonaws.com jcp-agent-spawner-stgn-jcp-agent-spawner-sessions-*.s3.*.amazonaws.com jcp-agent-spawner-preprod-jcp-agent-spawner-sessions-*.s3.*.amazonaws.com jcp-agent-spawner-prod-jcp-agent-spawner-sessions-*.s3.*.amazonaws.com # Local hosts *.docker.localhost *.docker.internal- Specified domains
Access only to domains you list in Additional domains.
- Trusted domains
Access to a preset list of domains commonly used for downloading dependencies, plus any domains you add manually.
The preset includes common source control, package management, and dependency domains.
alpinelinux.org anaconda.com apache.org apt.llvm.org archlinux.org azure.com bitbucket.org bower.io centos.org cocoapods.org continuum.io cpan.org crates.io debian.org docker.com docker.io dot.net dotnet.microsoft.com eclipse.org fedoraproject.org gcr.io ghcr.io github.com githubusercontent.com gitlab.com golang.org google.com goproxy.io gradle.org hashicorp.com haskell.org hex.pm java.com java.net jcenter.bintray.com json-schema.org json.schemastore.org k8s.io launchpad.net maven.org mcr.microsoft.com metacpan.org microsoft.com nodejs.org npmjs.com npmjs.org nuget.org oracle.com packagecloud.io packages.microsoft.com packagist.org pkg.go.dev ppa.launchpad.net pub.dev pypa.io pypi.org pypi.python.org pythonhosted.org quay.io ruby-lang.org rubyforge.org rubygems.org rubyonrails.org rustup.rs rvm.io sourceforge.net spring.io swift.org ubuntu.com visualstudio.com yarnpkg.com- All domains
Unrestricted internet access.
Allow access to specific domains
Use Additional domains to add domains that are required for your project but are not included in the preset list.
Enter one domain per line. You can specify exact domains such as example.com and wildcard domains such as *.example.com.
IP addresses a cloud environment connects from
Your own services (an internal MCP server, a package registry, a staging API, etc.) might be configured to accept requests only from allowlisted addresses. Cloud environments connect out through a fixed pool of public IP addresses, so you can add that pool to the allowlist:
These addresses are fixed, so an allowlist built from them keeps working.
This covers traffic the agent makes from the environment itself, including MCP servers you configure in .mcp.json. An MCP connector doesn't use these addresses, so it can't satisfy an allowlist built from them.