aws/copilot-cli

Prompt to override previously generated pipeline files

Open

Aperta il 22 dic 2020

Vedi su GitHub
 (3 commenti) (0 reazioni) (0 assegnatari)Go (3737 star) (441 fork)auto 404
good first issuesize/Stype/enhancement

Descrizione

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

Guida contributor

Tech stack
goaws
Dominio
backenddevops
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
active
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
GitAWS CLI
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
50
Direzione di ricerca
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.