Modal logo
IntroductionCustom container images Custom containersPrivate registriesFast pull from registryGPUs and other resources GPU accelerationUsing CUDA on ModalReserving CPU and memoryScaling out Scaling outDicts and queuesJob processingConcurrent inputs on a single container (beta)Dynamic batching (beta)Scheduling and cron jobsDeployment Apps, Stubs, and entrypointsManaging deploymentsInvoke deployed functionsContinuous deploymentSecrets and environment variables SecretsEnvironment variablesWeb endpoints Web endpointsStreaming endpointsWeb endpoint URLsRequest timeoutsNetworking Tunnels (beta)Proxies (beta)Data sharing and storage Passing local dataVolumesMounting local files and directoriesStoring model weightsDataset ingestionCloud bucket mountsNetwork file systems (superseded)Sandboxes SandboxesRunning commandsNetworking and securityFile accessPerformance Cold start performanceMemory Snapshot (beta)Geographic latencyReliability and robustness Failures and retriesPreemptionTimeoutsTroubleshootingSecurity and privacyIntegrations Using OIDC to authenticate with external servicesConnecting Modal to your Vercel accountConnecting Modal to your Datadog accountConnecting Modal to your OpenTelemetry providerOkta SSOSlack notifications (beta)Other topics File and project structureDeveloping and debuggingModal user account setupWorkspacesEnvironmentsJupyter notebooksAsynchronous API usageGlobal variablesRegion selectionContainer lifecycle hooksParameterized functionsS3 Gateway endpoints

S3 Gateway endpoints

When running workloads in AWS, our system automatically uses a corresponding S3 Gateway endpoint to ensure low costs, optimal performance, and network reliability between Modal and S3.

Workloads running on Modal should not incur egress or ingress fees associated with S3 operations. No configuration is needed in order for your app to use S3 Gateway endpoints. S3 Gateway endpoints are automatically used when your app runs on AWS.

Endpoint configuration

Only use the region-specific endpoint (s3.<region>.amazonaws.com) or the global AWS endpoint (s3.amazonaws.com). Using an S3 endpoint from one region in another will not use the S3 Gateway Endpoint incurring networking costs.

Avoid specifying regional endpoints manually, as this can lead to unexpected cost or performance degradation.

Inter-region costs

S3 Gateway endpoints guarantee no costs for network traffic within the same AWS region. However, if your Modal Function runs in one region but your bucket resides in a different region you will be billed for inter-region traffic.

You can prevent this by scheduling your Modal App in the same region of your S3 bucket with Region selection.