aws/copilot-cli

Prompt to override previously generated pipeline files

Open

#1,777 opened on Dec 22, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (3,737 stars) (441 forks)auto 404
good first issuesize/Stype/enhancement

Description

Hi, I'm back! I think everytime I open an issue, it's somehow related to permissions.

This time, I have successfully set up everything with copilot. For my addons, I have a template for elasticsearch and redis. I can successfully deploy it from my terminal using copilot svc deploy --name myapp --env test. Then I went to set up the pipeline next. It was going well at first, building was successful but the minute it tried to deploy, it failed.

Here is a screenshot from the console. Am I missing something? Should I have done more customization after running copilot pipeline init? Where can I add the S3 access?

This is strange because I've also already deployed a much smaller test app with crud operations on an elasticsearch addon. I was able to set up the pipeline for that too with no problem

Contributor guide

Tech stack
goaws
Domain
backenddevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitAWS CLI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Inspect the pipeline's IAM role and buildspec to ensure it has permissions to write to the S3 bucket used for addon templates. Verify that the S3 bucket policy allows access from the pipeline's AWS account.