copilot-cli: Cert validation lambda times out resulting in validation error

Easy to deploy the application, copilot CLI worked weill but it doesn’t work well after I developed new app with domain. I could create app, env and svc but couldn’t deploy svc. (although it worked well when I develop app without domain)

% copilot svc deploy --name [service-name] --env test
✘ execute "env upgrade --app [application-name]--name test": get template version of environment test in app [application-name]: get template summary for stack [cloudformation-name]: InvalidParameter: 1 validation error(s) found.
- minimum field size of 20, AssumeRoleInput.RoleArn.

And execute the following commands, but nothing changed

% copilot env upgrade --app [application-name] --name test
✘ get template version of environment test in app [application-name]: get template summary for stack [cloudformation-name]: InvalidParameter: 1 validation error(s) found.
- minimum field size of 20, AssumeRoleInput.RoleArn.

So I tried to delete svc or env in copilot, it always results the same like following.

% copilot svc delete [service-name]
Only found one service, defaulting to: [service-name]
Are you sure you want to delete api from application [application-name]? Yes
✘ Failed to delete service [service-name] from environment test: delete stack [application-name]-test-api: InvalidParameter: 1 validation error(s) found.
- minimum field size of 20, AssumeRoleInput.RoleArn.
.
✘ delete service: delete stack [application-name]-test-api: InvalidParameter: 1 validation error(s) found.
- minimum field size of 20, AssumeRoleInput.RoleArn.

I can’t figure out what’s going on.

Using version is here

% copilot -v
copilot version: v1.0.0

thanks in advance

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 1
  • Comments: 30 (15 by maintainers)

Most upvoted comments

Hello @ainoue1995. Im not sure why it is not working. Sometimes it takes really long time to wait for the cert changing to “verified” status. Maybe try it again to see if it works? Also please make sure the domain you are using is valid in your account (not expired although i think on our end we should also do the check). If it is not working still could you please send us the log of the lambda naming as ${appName}-${envName}-CertificateValidationFunction-${uuid}?

Awesome, thanks for letting us know! Yeah I think Copilot got into a weird state with the manual interventions, your outputs look good to me. Let me know if I can help deleting any of the remaining resources that Copilot failed to clean up.

Please feel free to re-open the issue if you see a similar behavior!

Thanks! After setting roles right places, Copilot started to work well, but couldn’t finish delete all. Before I issued here, I tried to fix this problem myself and manually deleted some resources including CloudFormation stacks, so that’s the reason why I guess.

Thus perhaps the data following are not expected value here.

スクリーンショット 2021-02-18 8 48 00 スクリーンショット 2021-02-18 8 48 31