Request Syntax URI Request Parameters Request Body Response Syntax Response Elements Errors See Also

PutSchemaFromJson

Allows a schema to be updated using JSON upload. Only available for development schemas. See JSON Schema Format for more information.

Request Syntax


PUT /amazonclouddirectory/2017-01-11/schema/json HTTP/1.1
x-amz-data-partition: SchemaArn
Content-type: application/json

{
   "Document": "string"
}

URI Request Parameters

The request uses the following URI parameters.

SchemaArn

The ARN of the schema to update.

Required: Yes

Request Body

The request accepts the following data in JSON format.

Document

The replacement JSON schema.

Type: String

Required: Yes

Response Syntax


HTTP/1.1 200
Content-type: application/json

{
   "Arn": "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.

Arn

The ARN of the schema to update.

Type: String

Errors

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

AccessDeniedException

Access denied or directory not found. Either you don't have permissions for this directory or the directory does not exist. Try calling ListDirectories and check your permissions.

HTTP Status Code: 403

InternalServiceException

Indicates a problem that must be resolved by Amazon Web Services. This might be a transient error in which case you can retry your request until it succeeds. Otherwise, go to the AWS Service Health Dashboard site to see if there are any operational issues with the service.

HTTP Status Code: 500

InvalidArnException

Indicates that the provided ARN value is not valid.

HTTP Status Code: 400

InvalidRuleException

Occurs when any of the rule parameter keys or values are invalid.

HTTP Status Code: 400

InvalidSchemaDocException

Indicates that the provided SchemaDoc value is not valid.

HTTP Status Code: 400

LimitExceededException

Indicates that limits are exceeded. See Limits for more information.

HTTP Status Code: 400

RetryableConflictException

Occurs when a conflict with a previous successful write is detected. For example, if a write operation occurs on an object and then an attempt is made to read the object using “SERIALIZABLE” consistency, this exception may result. This generally occurs when the previous write did not have time to propagate to the host serving the current request. A retry (with appropriate backoff logic) is the recommended response to this exception.

HTTP Status Code: 409

ValidationException

Indicates that your request is malformed in some manner. See the exception message.

HTTP Status Code: 400