Auto Deploy to AWS S3

Problem to solve

After we deliver #219084, it would make it easier for us to apply this template for users deploying to AWS from the autoDevOps Flow.

Intended users

Users deploying to AWS EC2

Further details

Based on #215136 (closed) a user will need to define S3 as their deployment target so that AutoDeploy knows where to deploy to

Proposal

If a user has defined S3 as their launch type

then the autoDeploy template will be initiated from autoDevOps that will call the S3 template

Use cases:

• We need to make sure that if the user is using Kubernetes - Auto Deploy will initiate Deploy to Kubernetes template.
• If a user is not using Kubernetes, and has "ECS" as the launch type defined auto Deploy will initiate the template as defined in #208132 (closed)
• If a user is not using Kubernetes, and has "EC2" as the launch type defined auto Deploy will initiate the template as defined in #201742 (closed)
• If a user is not using Kubernetes, and has "S3" as the launch type defined auto Deploy will initiate the template as defined in #219084
• If a user is not using Kubernetes and not using AWS, both templates are skipped - a proper error should be shown "Missing Launch Type"
• If a user is using Kubernetes and deploying to AWS - Only run the deploy Kubernetes template

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.