AWS AWS CodeDeploy Error Codes

The maximum number of alarms for a deployment group (10) was exceeded.

An application with the specified name with the user or Amazon Web Services account already exists.

The application does not exist with the user or Amazon Web Services account.

More applications were attempted to be created than are allowed.

The minimum number of required application names was not specified.

The specified ARN is not supported. For example, it might be an ARN for a resource that is not expected.

The maximum number of names or IDs allowed for this request (100) was exceeded.

A bucket name is required, but was not provided.

The deployment is already complete.

A deployment to a target was attempted while another deployment was in progress.

A deployment configuration with the specified name with the user or Amazon Web Services account already exists.

The deployment configuration does not exist with the user or Amazon Web Services account.

The deployment configuration is still in use.

The deployment configurations limit was exceeded.

The deployment configuration name was not specified.

The deployment with the user or Amazon Web Services account does not exist.

A deployment group with the specified name with the user or Amazon Web Services account already exists.

The named deployment group with the user or Amazon Web Services account does not exist.

The deployment groups limit was exceeded.

The deployment group name was not specified.

At least one deployment ID must be specified.

The deployment does not have a status of Ready and can't continue yet.

The number of allowed deployments was exceeded.

The specified deployment has not started.

The provided target ID does not belong to the attempted deployment.

A deployment target ID was not provided.

The maximum number of targets that can be associated with an Amazon ECS or Lambda deployment was exceeded. The target list of both types of deployments must have exactly one item. This exception does not apply to EC2/On-premises deployments.

The description is too long.

The Amazon ECS service is associated with more than one deployment groups. An Amazon ECS service can be associated with only one deployment group.

No GitHub account connection exists with the named specified in the call.

The call is missing a required GitHub account connection name.

No IAM ARN was included in the request. You must use an IAM session ARN or user ARN in the request.

The request included an IAM session ARN that has already been used to register a different instance.

The specified user ARN is already registered with an on-premises instance.

An user ARN was not specified.

The specified instance does not exist in the deployment group.

The instance ID was not specified.

The maximum number of allowed on-premises instances in a single call was exceeded.

The specified on-premises instance name is already registered.

An on-premises instance name was not specified.

The specified on-premises instance is not registered.

The format of the alarm configuration is invalid. Possible causes include: The alarm list is null. The alarm object is null. The alarm name is empty or null or exceeds the limit of 255 characters. Two alarms with the same name have been specified. The alarm configuration is enabled, but the alarm list is empty.

The application name was specified in an invalid format.

The specified ARN is not in a valid format.

The automatic rollback configuration was specified in an invalid format. For example, automatic rollback is enabled, but an invalid triggering event type or no event types were listed.

The Auto Scaling group was specified in an invalid format or does not exist.

The configuration for the blue/green deployment group was provided in an invalid format. For information about deployment configuration format, see CreateDeploymentConfig.

The bucket name either doesn't exist or was specified in an invalid format.

The computePlatform is invalid. The computePlatform should be Lambda, Server, or ECS.

The deployed state filter was specified in an invalid format.

The deployment configuration name was specified in an invalid format.

The deployment group name was specified in an invalid format.

At least one of the deployment IDs was specified in an invalid format.

An instance type was specified for an in-place deployment. Instance types are supported for blue/green deployments only.

The specified deployment status doesn't exist or cannot be determined.

An invalid deployment style was specified. Valid deployment types include "IN_PLACE" and "BLUE_GREEN." Valid deployment options include "WITH_TRAFFIC_CONTROL" and "WITHOUT_TRAFFIC_CONTROL."

The target ID provided was not valid.

The wait type is invalid.

A call was submitted that specified both Ec2TagFilters and Ec2TagSet, but only one of these data types can be used in a single call.

The tag was specified in an invalid format.

The Amazon ECS service identifier is not valid.

The external ID was specified in an invalid format.

An invalid fileExistsBehavior option was specified to determine how CodeDeploy handles files or directories that already exist in a deployment target location, but weren't part of the previous successful deployment. Valid values include "DISALLOW," "OVERWRITE," and "RETAIN."

The GitHub token is not valid.

The format of the specified GitHub account connection name is invalid.

The IAM session ARN was specified in an invalid format.

The user ARN was specified in an invalid format.

The IgnoreApplicationStopFailures value is invalid. For Lambda deployments, false is expected. For EC2/On-premises deployments, true or false is expected.

The input was specified in an invalid format.

The on-premises instance name was specified in an invalid format.

The specified instance status does not exist.

An invalid instance type was specified for instances in a blue/green deployment. Valid values include "Blue" for an original environment and "Green" for a replacement environment.

The specified key prefix filter was specified in an invalid format.

A lifecycle event hook is invalid. Review the hooks section in your AppSpec file to ensure the lifecycle events and hooks functions are valid.

The result of a Lambda validation function that verifies a lifecycle event is invalid. It should return Succeeded or Failed.

An invalid load balancer name, or no load balancer name, was specified.

The minimum healthy instance value was specified in an invalid format.

The next token was specified in an invalid format.

A call was submitted that specified both OnPremisesTagFilters and OnPremisesTagSet, but only one of these data types can be used in a single call.

An invalid operation was detected.

The registration status was specified in an invalid format.

The revision was specified in an invalid format.

The service role ARN was specified in an invalid format. Or, if an Auto Scaling group was specified, the specified service role does not grant the appropriate permissions to Amazon EC2 Auto Scaling.

The column name to sort by is either not present or was specified in an invalid format.

The sort order was specified in an invalid format.

The tag was specified in an invalid format.

The tag filter was specified in an invalid format.

The specified tags are not valid.

A target is not valid.

The target filter name is invalid.

A target group pair associated with this deployment is not valid.

The target instance configuration is invalid. Possible causes include: Configuration data for target instances was entered for an in-place deployment. The limit of 10 tags for a tag type was exceeded. The combined length of the tag names exceeded the limit. A specified tag is not currently applied to any instances.

The specified time range was specified in an invalid format.

The configuration that specifies how traffic is routed during a deployment is invalid.

The trigger was specified in an invalid format.

The UpdateOutdatedInstancesOnly value is invalid. For Lambda deployments, false is expected. For EC2/On-premises deployments, true or false is expected.

The ZonalConfig object is not valid.

An attempt to return the status of an already completed lifecycle event occurred.

The limit for lifecycle hooks was exceeded.

Both an user ARN and an IAM session ARN were included in the request. Use only one ARN type.

The API used does not support the deployment.

The ARN of a resource is required, but was not found.

The specified resource could not be validated.

The named revision does not exist with the user or Amazon Web Services account.

The revision ID was not specified.

The role ID was not specified.

The maximum allowed number of tags was exceeded.

A tag was not specified.

The number of tag groups included in the tag set list exceeded the maximum allowed limit of 3.

An API function was called too frequently.

The maximum allowed number of triggers was exceeded.

A call was submitted that is not supported for the specified deployment type.