Menu
Amazon EC2 Container Registry
API Reference (API Version 2015-09-21)

CreateRepository

Creates an image repository.

Request Syntax

Copy
{ "repositoryName": "string" }

Request Parameters

For information about the parameters that are common to all actions, see Common Parameters.

The request accepts the following data in JSON format.

repositoryName

The name to use for the repository. The repository name may be specified on its own (such as nginx-web-app) or it can be prepended with a namespace to group the repository into a category (such as project-a/nginx-web-app).

Type: String

Length Constraints: Minimum length of 2. Maximum length of 256.

Pattern: (?:[a-z0-9]+(?:[._-][a-z0-9]+)*/)*[a-z0-9]+(?:[._-][a-z0-9]+)*

Required: Yes

Response Syntax

Copy
{ "repository": { "createdAt": number, "registryId": "string", "repositoryArn": "string", "repositoryName": "string", "repositoryUri": "string" } }

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

repository

The repository that was created.

Type: Repository object

Errors

For information about the errors that are common to all actions, see Common Errors.

InvalidParameterException

The specified parameter is invalid. Review the available parameters for the API request.

HTTP Status Code: 400

LimitExceededException

The operation did not succeed because it would have exceeded a service limit for your account. For more information, see Amazon ECR Default Service Limits in the Amazon EC2 Container Registry User Guide.

HTTP Status Code: 400

RepositoryAlreadyExistsException

The specified repository already exists in the specified registry.

HTTP Status Code: 400

ServerException

These errors are usually caused by a server-side issue.

HTTP Status Code: 500

Example

In the following example or examples, the Authorization header contents (AUTHPARAMS) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see Signature Version 4 Signing Process in the AWS General Reference.

You only need to learn how to sign HTTP requests if you intend to manually create them. When you use the AWS Command Line Interface (AWS CLI) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself.

Example

This example creates a repository called nginx-web-app inside the project-a namespace in the default registry for an account.

Sample Request

Copy
POST / HTTP/1.1 Host: ecr.us-east-1.amazonaws.com Accept-Encoding: identity Content-Length: 45 X-Amz-Target: AmazonEC2ContainerRegistry_V20150921.CreateRepository X-Amz-Date: 20151130T203458Z User-Agent: aws-cli/1.9.9 Python/2.7.10 Darwin/14.5.0 botocore/1.3.9 Content-Type: application/x-amz-json-1.1 Authorization: AUTHPARAMS { "repositoryName": "project-a/nginx-web-app" }

Sample Response

Copy
HTTP/1.1 200 OK Server: Server Date: Mon, 30 Nov 2015 20:34:58 GMT Content-Type: application/x-amz-json-1.1 Content-Length: 175 Connection: keep-alive x-amzn-RequestId: 123a4b56-7c89-01d2-3ef4-example5678f { "repository": { "registryId": "012345678910", "repositoryArn": "arn:aws:ecr:us-east-1:012345678910:repository/project-a/nginx-web-app", "repositoryName": "project-a/nginx-web-app" } }

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: