Template for Deploying to AWS EC2 (#201742) · Issues · GitLab.org / GitLab

Template for Deploying to AWS EC2

Problem to solve

We want to help our users deploy easily to AWS

Intended users

Further details

Following comment &2351 (comment 263237910)

I think just having gitlab-ci.yml template added for AWS (deploy to EC2, ECS, Fargate) would suffice in the short term. We can even use the tool we suggest in our documentation.

I feel that most customers would like to understand our best practices and documentation around how to best deploy using our product and what's needed to be successful. Adding into AutoDevops functionality would be most awesome, but that may be a different issue.

Proposal

Create a gitlab-ci.yml template for deploying to AWS EC2 using Using Dpl as deployment tool

Actions needed to be done

Create gitlab-ci.yml template
Create documentation on how to use the template

We can later expand on this and add deploying to ECS, Fargate.

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

### Problem to solve

We want to help our users deploy easily to AWS

### Intended users

<!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.

* [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager)
* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
* [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer)
* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
* [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst)
* [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst)

Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->

* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)

### Further details

Following comment https://gitlab.com/groups/gitlab-org/-/epics/2351#note_263237910

I think just having gitlab-ci.yml template added for AWS (deploy to EC2, ECS, Fargate) would suffice in the short term. We can even use the tool we suggest in our [documentation](https://docs.gitlab.com/ee/ci/examples/deployment/).

### Proposal

Create a `gitlab-ci.yml` template for deploying to AWS EC2 using [Using Dpl as deployment tool](https://docs.gitlab.com/ee/ci/examples/deployment/)

Actions needed to be done

* [ ] Create `gitlab-ci.yml` template
* [ ] Create documentation on how to use the template

We can later expand on this and add deploying to  ECS, Fargate.

### Permissions and Security

### Documentation

### Availability & Testing

<!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.

What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change

See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning -->

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

### What is the type of buyer?

### Links / references

Edited Feb 24, 2020 by Orit Golowinski

Discussion
Designs