> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/release-delivery/release-delivery-guide.md). # Delivery guide Your application is deployed to your AWS account via the Release Delivery deployment platform. You will need to authorize an AWS CloudFormation template to create a role for Release Delivery to use to configure, deploy, and run your application. You will complete the initial configuration from the AWS Console in your browser. Once the initial configuration is complete, Release Delivery will be able to install, deploy, and access your application. Authorizing the AWS CloudFormation template should take no more than five minutes and thereafter, no further intervention is required from you. Release Delivery will perform an asynchronous, automated installation of your application, which will take approximately 30 minutes. When installation is complete, you will receive an email notification that the application is running. ## Prerequisites To configure Release Delivery to access your AWS account, you will need: 1. To be logged in to your AWS account in a browser tab. 2. Your application landing page URL. Open the URL in a tab in the same browser you used to log in to AWS. 3. The name of the AWS region you will use. This is where the application will create resources. 4. A nonoverlapping CIDR range that won't conflict with your existing VPC. (The application does not communicate outside the VPC until peering or a Transit Gateway is established.) The installation will take around five minutes. ## Complete Initial Configuration Click the URL that was provided to you by the application. You will be taken to a page showing a terms-of-service agreement and a **Create stack** button. Agree to the terms and click the **Create stack** button. You will be prompted to connect your AWS account: ![Connect your AWS account](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-07f74cbb1432c7bceb36160d57852596896d39fc%2Fdelivery-guide-000.png?alt=media\&token=0794e8ec-5a2e-4c4e-a9a5-ce6707e9b7dd) Your browser will open a new tab that will authenticate you via the AWS Console. If you are not logged in, you will be prompted to authenticate with AWS in the normal way. ![Authentication with the target AWS account](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-127b57bee5f0f39fb597e4bda4dd854412e4c25f%2Fdelivery-guide-001.png?alt=media\&token=a0949b46-f70a-4eb0-a8f5-c4b6c6fc161e) When you are logged in, you will see the CloudFormation template ready to agree to and create. You don't need to make any changes here. This step is just to confirm the template and authorize Release Delivery to create a role to deploy the application and infrastructure. ![Review the integration Cloudformation stack and create](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-bf669b3f39683462cf75b1ae1756cd7f99bbf03c%2Fdelivery-guide-002.png?alt=media\&token=495671e4-dacf-4df5-b0de-08652b8f7358) After a few seconds or minutes, the template status should be "Create Complete". ![Cloudformation create is completed](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-c906e0fd74435f8b6fb7038cf416284086db24e8%2Fdelivery-guide-003.png?alt=media\&token=ee037d4d-cd29-4786-9318-58275a1478e7) Switch back to the landing page tab. You should see this: ![Click next when complete](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-6ebdb3279b227fcee05e3f9be7919facbb6c57ff%2Fdelivery-guide-005.png?alt=media\&token=398f9e6f-87b6-4c1d-a763-7df7edb3dc8c) Wait until the integration and webhook are received, then select a region: ![Select a Region](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-45813bc6074150fb8d6a8ba557973b782a891ab4%2Fdelivery-guide-006.png?alt=media\&token=f7927a71-290b-4b27-b94d-533e81cbdad2) Select a CIDR block that does not conflict with any existing VPCs you might have. (The ones that are presented are not used in the current account.) ![Select a non-overlapping CIDR block](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-b7ff8c582f7c24a905668cf377143b51ee6bda1b%2Fdelivery-guide-007.png?alt=media\&token=65089c7e-3d8e-4f60-b5a3-38e88d1e2967) When you are ready, click the **Install** button: ![Ready to install!](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-0dab18c1958c72adab2afb313150a2e5882a11a3%2Fdelivery-guide-008.png?alt=media\&token=0173d344-9583-4cb0-95b1-3b13719f902d) You should see confirmation that Release Delivery is completing the installation: ![Complete](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-a9af4eae9730091d982e3df0838dfd9afc6ea8aa%2Fdelivery-guide-009.png?alt=media\&token=eccf8e84-d59f-421d-bad2-dfeb3615d5f0) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.release.com/release-delivery/release-delivery-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.