You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing issues, it hasn't been reported yet
Issue description
I first ran the serverless deploy and I got the access denied error as I didn't have permission for elasticloadbalancing: RegisterTargets.
I then added the missing permission so all permissions are added for the deployment.
After this, I ran serverless remove and it went successfully.
However, when I ran serverless deploy again, it gave me the error: Resource of type 'AWS::ElasticLoadBalancingV2::TargetGroup' with identifier '' already exists.
The serverless remove command did not remove the target group, while all permissions were added.
@shuangqiu123 this looks as an issue on AWS side. Framework delegates stack removal to AWS, and it's AWS that's responsible for removing the stack with all the resources that were created in its capacity.
Have you tried contacting AWS support about that, by chance?
Are you certain it's a bug?
Is the issue caused by a plugin?
Are you using the latest v3 release?
Is there an existing issue for this?
Issue description
I first ran the
serverless deploy
and I got the access denied error as I didn't have permission for elasticloadbalancing: RegisterTargets.I then added the missing permission so all permissions are added for the deployment.
After this, I ran
serverless remove
and it went successfully.However, when I ran
serverless deploy
again, it gave me the error:Resource of type 'AWS::ElasticLoadBalancingV2::TargetGroup' with identifier '' already exists.
The
serverless remove
command did not remove the target group, while all permissions were added.Service configuration (serverless.yml) content
Command name and used flags
serverless deploy
Command output
Environment information
The text was updated successfully, but these errors were encountered: