AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Domain used by Amazon SageMaker Studio. A domain consists of
an associated Amazon Elastic File System (EFS) volume, a list of authorized users,
and a variety of security, application, policy, and Amazon Virtual Private Cloud (VPC)
configurations. An Amazon Web Services account is limited to one domain per region.
Users within a domain can share notebook files and other artifacts with each other.
When a domain is created, an EFS volume is created for use by all of the users within the domain. Each user receives a private home directory within the EFS volume for notebooks, Git repositories, and data files.
SageMaker uses the Amazon Web Services Key Management Service (Amazon Web Services KMS) to encrypt the EFS volume attached to the domain with an Amazon Web Services managed key by default. For more control, you can specify a customer managed key. For more information, see Protect Data at Rest Using Encryption.
All SageMaker Studio traffic between the domain and the EFS volume is through the
specified VPC and subnets. For other Studio traffic, you can specify the
AppNetworkAccessType corresponds to the network access type
that you choose when you onboard to Studio. The following options are available:
PublicInternetOnly - Non-EFS traffic goes through a VPC managed by Amazon
SageMaker, which allows internet access. This is the default value.
VpcOnly - All Studio traffic is through the specified VPC and subnets.
Internet access is disabled by default. To allow internet access, you must specify
a NAT gateway.
When internet access is disabled, you won't be able to run a Studio notebook or to train or host models unless your VPC has an interface endpoint to the SageMaker API and runtime or a NAT gateway and your security groups allow outbound connections.
NFS traffic over TCP on port 2049 needs to be allowed in both inbound and outbound rules in order to launch a SageMaker Studio app successfully.
For more information, see Connect SageMaker Studio Notebooks to Resources in a VPC.
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginCreateDomain and EndCreateDomain.
public virtual Task<CreateDomainResponse> CreateDomainAsync( CreateDomainRequest request, CancellationToken cancellationToken )
Container for the necessary parameters to execute the CreateDomain service method.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
.NET Core App:
Supported in: 3.1
Supported in: 2.0
Supported in: 4.5