Make sure to disable `EKS Auto Mode`
You will have the next project structure.
```shell theme={null}
/my-ship-app
/.github
/apps
/api
/web
/deploy
...
```
## AWS Regions
AWS Regions are physical locations of AWS cluster data centers. Each group of logical data centers calls Availability Zone (AZ). AZs allow the operation of production applications and databases that are more highly available, fault-tolerant and scalable.
Now you need to select an AWS region for future use of the services. You can read more about region selection for your workloads here: [What to Consider when Selecting a Region for your Workloads](https://aws.amazon.com/blogs/architecture/what-to-consider-when-selecting-a-region-for-your-workloads/).
For this deployment guide, we will use the **us-east-1** region.
Docker images for each service are stored in a separate repository.
During the deployment process script will automatically create paths to repositories in the next format:
* [**API**](/api-reference/overview) - 276472736030.dkr.ecr.us-east-1.amazonaws.com/api;
* [**Migrator**](/migrator) - 276472736030.dkr.ecr.us-east-1.amazonaws.com/migrator;
* [**Scheduler**](/scheduler) - 276472736030.dkr.ecr.us-east-1.amazonaws.com/scheduler;
* [**Web**](/web/overview) - 276472736030.dkr.ecr.us-east-1.amazonaws.com/web;
After cluster creation, you should attach [EC2](https://aws.amazon.com/ec2) instances to the cluster. You can do it by clicking on the **Add Node Group** button on the **Compute** tab.
Set the node group name as `pool-app` and select the relevant Node IAM role from the list.
If you don't have any IAM roles here, click the `Create recommended role` button. You will be prompted to create properly configured IAM roles with all necessary permissions.
AWS recommends creating at least 2 nodes **t3.medium** instance type for the production environment.
Provider & Region:
Provider & Region:
**Example Connection String:**
```bash theme={null}
mongodb+srv://api-production:your-password@cluster0.xxxxx.mongodb.net/?retryWrites=true&w=majority
```
4. (Optional) Add tags
5. Give the policy a name (e.g. `GitHubActionsDeployPolicy`) and create it
4. Attach the policy you created by selecting:
* **Attach existing policies directly**
* Choose the CI/CD policy created in previous step
4. (Optional) Add user tags
5. Review and create user
3. Select use case: **Third-party service**
4. Save the Access Key ID and Secret Access Key securely
2. Run the following command to grant Kubernetes access:
```bash theme={null}
eksctl create iamidentitymapping \
--cluster my-ship-app \
--group system:masters \
--username github-actions \
--arn YOUR_USER_ARN
```
Replace `YOUR_USER_ARN` with the actual ARN copied earlier.
Now commit all changes to GitHub that will trigger deployment, or you can [run a workflow manually](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow)
Done! Application deployed and can be accessed by the provided domain.
Region Selection: For Kubernetes deployments on AWS, choose the same AWS region as your EKS cluster to minimize latency and data transfer costs.
)} {provider_0 === 'do' && (Region Selection: For Kubernetes deployments on Digital Ocean, choose the same region as your cluster to minimize latency and data transfer costs.
)}
