AWS App Runner will no longer be open to new customers starting April 30, 2026. If you would like to use App Runner, sign up prior to that date. Existing customers can continue to use the service as normal. For more information, see [AWS App Runner availability change](https://docs.aws.amazon.com/apprunner/latest/dg/apprunner-availability-change.html). # Using the Go platform **Important** App Runner will end the support for **Go 1.18** on December 1, 2025. For recommendations and more information, see [End of support for managed runtime versions](service-source-code.md#service-source-code.managed-platforms.eos). The AWS App Runner Go platform provides managed runtimes. Each runtime makes it easy to build and run containers with web applications based on a Go version. When you use a Go runtime, App Runner starts with a managed Go runtime image. This image is based on the [Amazon Linux Docker image](https://hub.docker.com/_/amazonlinux) and contains the runtime package for a version of Go and some tools. App Runner uses this managed runtime image as a base image, and adds your application code to build a Docker image. It then deploys this image to run your web service in a container. You specify a runtime for your App Runner service when you [create a service](manage-create.md) using the App Runner console or the [CreateService](https://docs.aws.amazon.com/apprunner/latest/api/API_CreateService.html) API operation. You can also specify a runtime as part of your source code. Use the `runtime` keyword in a [App Runner configuration file](config-file.md) that you include in your code repository. The naming convention of a managed runtime is **. For valid Go runtime names and versions, see [Go runtime release information](service-source-code-go-releases.md). App Runner updates the runtime for your service to the latest version on every deployment or service update. If your application requires a specific version of a managed runtime, you can specify it using the `runtime-version` keyword in the [App Runner configuration file](config-file.md). You can lock to any level of version, including a major or minor version. App Runner only makes lower-level updates to the runtime of your service. Version syntax for Go runtimes: `major[.minor[.patch]]` For example: `1.18.7` The following examples demonstrate version locking: + `1.18` – Lock the major and minor versions. App Runner updates only patch versions. + `1.18.7` – Lock to a specific patch version. App Runner doesn't update your runtime version. **Topics** + [Go runtime configuration](#service-source-code-go1.config) + [Go runtime examples](#service-source-code-go1.examples) + [Go runtime release information](service-source-code-go-releases.md) ## Go runtime configuration When you choose a managed runtime, you must also configure, as a minimum, build and run commands. You configure them while [creating](manage-create.md) or [updating](manage-configure.md) your App Runner service. You can do this using one of the following methods: + **Using the App Runner console** – Specify the commands in the **Configure build** section of the creation process or configuration tab. + **Using the App Runner API** – Call the [CreateService](https://docs.aws.amazon.com/apprunner/latest/api/API_CreateService.html) or [UpdateService](https://docs.aws.amazon.com/apprunner/latest/api/API_UpdateService.html) API operation. Specify the commands using the `BuildCommand` and `StartCommand` members of the [CodeConfigurationValues](https://docs.aws.amazon.com/apprunner/latest/api/API_CodeConfigurationValues.html) data type. + **Using a [configuration file](config-file.md)** – Specify one or more build commands in up to three build phases, and a single run command that serves to start your application. There are additional optional configuration settings. Providing a configuration file is optional. When you create an App Runner service using the console or the API, you specify if App Runner gets your configuration settings directly when it's created or from a configuration file. ## Go runtime examples The following examples show App Runner configuration files for building and running a Go service. ### Minimal Go configuration file This example shows a minimal configuration file that you can use with a Go managed runtime. For the assumptions that App Runner makes with a minimal configuration file, see [Configuration file examples](config-file-examples.md#config-file-examples.managed). **Example apprunner.yaml** ``` version: 1.0 runtime: go1 build: commands: build: - go build main.go run: command: ./main ``` ### Extended Go configuration file This example shows the use of all the configuration keys with a Go managed runtime. **Note** The runtime version that's used in these examples is *1.18.7*. You can replace it with a version you want to use. For latest supported Go runtime version, see [Go runtime release information](service-source-code-go-releases.md). **Example apprunner.yaml** ``` version: 1.0 runtime: go1 build: commands: pre-build: - scripts/prebuild.sh build: - go build main.go post-build: - scripts/postbuild.sh env: - name: MY_VAR_EXAMPLE value: "example" run: runtime-version: 1.18.7 command: ./main network: port: 3000 env: APP_PORT env: - name: MY_VAR_EXAMPLE value: "example" ``` ### Complete Go application source These examples shows the source code for a complete Go application that you can deploy to a Go runtime service. **Example main.go** ``` package main import ( "fmt" "net/http" ) func main() { http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) { fmt.Fprint(w, "

Welcome to App Runner

") }) fmt.Println("Starting the server on :3000...") http.ListenAndServe(":3000", nil) } ``` **Example apprunner.yaml** ``` version: 1.0 runtime: go1 build: commands: build: - go build main.go run: command: ./main network: port: 3000 env: APP_PORT ```