Skip to content

Commit 9535c46

Browse files
author
AWS
committed
Amazon Redshift Update: Adds support for Amazon Redshift RegisterNamespace and DeregisterNamespace APIs to share data to AWS Glue Data Catalog.
1 parent 54f9428 commit 9535c46

File tree

2 files changed

+163
-4
lines changed

2 files changed

+163
-4
lines changed
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"type": "feature",
3+
"category": "Amazon Redshift",
4+
"contributor": "",
5+
"description": "Adds support for Amazon Redshift RegisterNamespace and DeregisterNamespace APIs to share data to AWS Glue Data Catalog."
6+
}

services/redshift/src/main/resources/codegen-resources/service-2.json

Lines changed: 157 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@
278278
{"shape":"UnsupportedOperationFault"},
279279
{"shape":"RedshiftIdcApplicationNotExistsFault"}
280280
],
281-
"documentation":"<p>Creates a new cluster with the specified parameters.</p> <p>To create a cluster in Virtual Private Cloud (VPC), you must provide a cluster subnet group name. The cluster subnet group identifies the subnets of your VPC that Amazon Redshift uses when creating the cluster. For more information about managing clusters, go to <a href=\"https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html\">Amazon Redshift Clusters</a> in the <i>Amazon Redshift Cluster Management Guide</i>.</p>"
281+
"documentation":"<p>Creates a new cluster with the specified parameters.</p> <p>To create a cluster in Virtual Private Cloud (VPC), you must provide a cluster subnet group name. The cluster subnet group identifies the subnets of your VPC that Amazon Redshift uses when creating the cluster. For more information about managing clusters, go to <a href=\"https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html\">Amazon Redshift Clusters</a> in the <i>Amazon Redshift Cluster Management Guide</i>.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a subnet group for a provisioned cluster is in an account with VPC BPA turned on, the following capabilities are blocked:</p> <ul> <li> <p>Creating a public cluster</p> </li> <li> <p>Restoring a public cluster</p> </li> <li> <p>Modifying a private cluster to be public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the subnet group when there's at least one public cluster within the group</p> </li> </ul> <p>For more information about VPC BPA, see <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html\">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>"
282282
},
283283
"CreateClusterParameterGroup":{
284284
"name":"CreateClusterParameterGroup",
@@ -931,6 +931,24 @@
931931
],
932932
"documentation":"<p>Deletes a usage limit from a cluster.</p>"
933933
},
934+
"DeregisterNamespace":{
935+
"name":"DeregisterNamespace",
936+
"http":{
937+
"method":"POST",
938+
"requestUri":"/"
939+
},
940+
"input":{"shape":"DeregisterNamespaceInputMessage"},
941+
"output":{
942+
"shape":"DeregisterNamespaceOutputMessage",
943+
"resultWrapper":"DeregisterNamespaceResult"
944+
},
945+
"errors":[
946+
{"shape":"ClusterNotFoundFault"},
947+
{"shape":"InvalidNamespaceFault"},
948+
{"shape":"InvalidClusterStateFault"}
949+
],
950+
"documentation":"<p>Deregisters a cluster or serverless namespace from the Amazon Web Services Glue Data Catalog.</p>"
951+
},
934952
"DescribeAccountAttributes":{
935953
"name":"DescribeAccountAttributes",
936954
"http":{
@@ -1910,7 +1928,7 @@
19101928
{"shape":"CustomCnameAssociationFault"},
19111929
{"shape":"Ipv6CidrBlockNotFoundFault"}
19121930
],
1913-
"documentation":"<p>Modifies the settings for a cluster.</p> <p>You can also change node type and the number of nodes to scale up or down the cluster. When resizing a cluster, you must specify both the number of nodes and the node type even if one of the parameters does not change.</p> <p>You can add another security or parameter group, or change the admin user password. Resetting a cluster password or modifying the security groups associated with a cluster do not need a reboot. However, modifying a parameter group requires a reboot for parameters to take effect. For more information about managing clusters, go to <a href=\"https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html\">Amazon Redshift Clusters</a> in the <i>Amazon Redshift Cluster Management Guide</i>.</p>"
1931+
"documentation":"<p>Modifies the settings for a cluster.</p> <p>You can also change node type and the number of nodes to scale up or down the cluster. When resizing a cluster, you must specify both the number of nodes and the node type even if one of the parameters does not change.</p> <p>You can add another security or parameter group, or change the admin user password. Resetting a cluster password or modifying the security groups associated with a cluster do not need a reboot. However, modifying a parameter group requires a reboot for parameters to take effect. For more information about managing clusters, go to <a href=\"https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html\">Amazon Redshift Clusters</a> in the <i>Amazon Redshift Cluster Management Guide</i>.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a subnet group for a provisioned cluster is in an account with VPC BPA turned on, the following capabilities are blocked:</p> <ul> <li> <p>Creating a public cluster</p> </li> <li> <p>Restoring a public cluster</p> </li> <li> <p>Modifying a private cluster to be public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the subnet group when there's at least one public cluster within the group</p> </li> </ul> <p>For more information about VPC BPA, see <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html\">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>"
19141932
},
19151933
"ModifyClusterDbRevision":{
19161934
"name":"ModifyClusterDbRevision",
@@ -2033,7 +2051,7 @@
20332051
{"shape":"UnauthorizedOperation"},
20342052
{"shape":"DependentServiceRequestThrottlingFault"}
20352053
],
2036-
"documentation":"<p>Modifies a cluster subnet group to include the specified list of VPC subnets. The operation replaces the existing list of subnets with the new list of subnets.</p>"
2054+
"documentation":"<p>Modifies a cluster subnet group to include the specified list of VPC subnets. The operation replaces the existing list of subnets with the new list of subnets.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a subnet group for a provisioned cluster is in an account with VPC BPA turned on, the following capabilities are blocked:</p> <ul> <li> <p>Creating a public cluster</p> </li> <li> <p>Restoring a public cluster</p> </li> <li> <p>Modifying a private cluster to be public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the subnet group when there's at least one public cluster within the group</p> </li> </ul> <p>For more information about VPC BPA, see <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html\">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p>"
20372055
},
20382056
"ModifyCustomDomainAssociation":{
20392057
"name":"ModifyCustomDomainAssociation",
@@ -2289,6 +2307,24 @@
22892307
],
22902308
"documentation":"<p>Reboots a cluster. This action is taken as soon as possible. It results in a momentary outage to the cluster, during which the cluster status is set to <code>rebooting</code>. A cluster event is created when the reboot is completed. Any pending cluster modifications (see <a>ModifyCluster</a>) are applied at this reboot. For more information about managing clusters, go to <a href=\"https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-clusters.html\">Amazon Redshift Clusters</a> in the <i>Amazon Redshift Cluster Management Guide</i>. </p>"
22912309
},
2310+
"RegisterNamespace":{
2311+
"name":"RegisterNamespace",
2312+
"http":{
2313+
"method":"POST",
2314+
"requestUri":"/"
2315+
},
2316+
"input":{"shape":"RegisterNamespaceInputMessage"},
2317+
"output":{
2318+
"shape":"RegisterNamespaceOutputMessage",
2319+
"resultWrapper":"RegisterNamespaceResult"
2320+
},
2321+
"errors":[
2322+
{"shape":"ClusterNotFoundFault"},
2323+
{"shape":"InvalidNamespaceFault"},
2324+
{"shape":"InvalidClusterStateFault"}
2325+
],
2326+
"documentation":"<p>Registers a cluster or serverless namespace to the Amazon Web Services Glue Data Catalog.</p>"
2327+
},
22922328
"RejectDataShare":{
22932329
"name":"RejectDataShare",
22942330
"http":{
@@ -2398,7 +2434,7 @@
23982434
{"shape":"UnsupportedOperationFault"},
23992435
{"shape":"Ipv6CidrBlockNotFoundFault"}
24002436
],
2401-
"documentation":"<p>Creates a new cluster from a snapshot. By default, Amazon Redshift creates the resulting cluster with the same configuration as the original cluster from which the snapshot was created, except that the new cluster is created with the default cluster security and parameter groups. After Amazon Redshift creates the cluster, you can use the <a>ModifyCluster</a> API to associate a different security group and different parameter group with the restored cluster. If you are using a DS node type, you can also choose to change to another DS node type of the same size during restore.</p> <p>If you restore a cluster into a VPC, you must provide a cluster subnet group where you want the cluster restored.</p> <p> For more information about working with snapshots, go to <a href=\"https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html\">Amazon Redshift Snapshots</a> in the <i>Amazon Redshift Cluster Management Guide</i>.</p>"
2437+
"documentation":"<p>Creates a new cluster from a snapshot. By default, Amazon Redshift creates the resulting cluster with the same configuration as the original cluster from which the snapshot was created, except that the new cluster is created with the default cluster security and parameter groups. After Amazon Redshift creates the cluster, you can use the <a>ModifyCluster</a> API to associate a different security group and different parameter group with the restored cluster. If you are using a DS node type, you can also choose to change to another DS node type of the same size during restore.</p> <p>If you restore a cluster into a VPC, you must provide a cluster subnet group where you want the cluster restored.</p> <p>VPC Block Public Access (BPA) enables you to block resources in VPCs and subnets that you own in a Region from reaching or being reached from the internet through internet gateways and egress-only internet gateways. If a subnet group for a provisioned cluster is in an account with VPC BPA turned on, the following capabilities are blocked:</p> <ul> <li> <p>Creating a public cluster</p> </li> <li> <p>Restoring a public cluster</p> </li> <li> <p>Modifying a private cluster to be public</p> </li> <li> <p>Adding a subnet with VPC BPA turned on to the subnet group when there's at least one public cluster within the group</p> </li> </ul> <p>For more information about VPC BPA, see <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/security-vpc-bpa.html\">Block public access to VPCs and subnets</a> in the <i>Amazon VPC User Guide</i>.</p> <p> For more information about working with snapshots, go to <a href=\"https://docs.aws.amazon.com/redshift/latest/mgmt/working-with-snapshots.html\">Amazon Redshift Snapshots</a> in the <i>Amazon Redshift Cluster Management Guide</i>.</p>"
24022438
},
24032439
"RestoreTableFromClusterSnapshot":{
24042440
"name":"RestoreTableFromClusterSnapshot",
@@ -4069,6 +4105,12 @@
40694105
},
40704106
"exception":true
40714107
},
4108+
"ConsumerIdentifierList":{
4109+
"type":"list",
4110+
"member":{"shape":"String"},
4111+
"max":1,
4112+
"min":1
4113+
},
40724114
"CopyClusterSnapshotMessage":{
40734115
"type":"structure",
40744116
"required":[
@@ -4952,6 +4994,10 @@
49524994
"ManagedBy":{
49534995
"shape":"String",
49544996
"documentation":"<p>The identifier of a datashare to show its managing entity.</p>"
4997+
},
4998+
"DataShareType":{
4999+
"shape":"DataShareType",
5000+
"documentation":"<p> The type of the datashare created by RegisterNamespace.</p>"
49555001
}
49565002
}
49575003
},
@@ -5025,6 +5071,10 @@
50255071
"REJECTED"
50265072
]
50275073
},
5074+
"DataShareType":{
5075+
"type":"string",
5076+
"enum":["INTERNAL"]
5077+
},
50285078
"DataTransferProgress":{
50295079
"type":"structure",
50305080
"members":{
@@ -5417,6 +5467,32 @@
54175467
},
54185468
"exception":true
54195469
},
5470+
"DeregisterNamespaceInputMessage":{
5471+
"type":"structure",
5472+
"required":[
5473+
"NamespaceIdentifier",
5474+
"ConsumerIdentifiers"
5475+
],
5476+
"members":{
5477+
"NamespaceIdentifier":{
5478+
"shape":"NamespaceIdentifierUnion",
5479+
"documentation":"<p>The unique identifier of the cluster or serverless namespace that you want to deregister.</p>"
5480+
},
5481+
"ConsumerIdentifiers":{
5482+
"shape":"ConsumerIdentifierList",
5483+
"documentation":"<p>An array containing the ID of the consumer account that you want to deregister the cluster or serverless namespace from.</p>"
5484+
}
5485+
}
5486+
},
5487+
"DeregisterNamespaceOutputMessage":{
5488+
"type":"structure",
5489+
"members":{
5490+
"Status":{
5491+
"shape":"NamespaceRegistrationStatus",
5492+
"documentation":"<p>The registration status of the cluster or serverless namespace.</p>"
5493+
}
5494+
}
5495+
},
54205496
"DescribeAccountAttributesMessage":{
54215497
"type":"structure",
54225498
"members":{
@@ -8946,6 +9022,28 @@
89469022
}
89479023
}
89489024
},
9025+
"NamespaceIdentifierUnion":{
9026+
"type":"structure",
9027+
"members":{
9028+
"ServerlessIdentifier":{
9029+
"shape":"ServerlessIdentifier",
9030+
"documentation":"<p>The identifier for a serverless namespace.</p>"
9031+
},
9032+
"ProvisionedIdentifier":{
9033+
"shape":"ProvisionedIdentifier",
9034+
"documentation":"<p>The identifier for a provisioned cluster.</p>"
9035+
}
9036+
},
9037+
"documentation":"<p>Object to store union of values for a provisioned cluster or serverless namespace’s identifier.</p>",
9038+
"union":true
9039+
},
9040+
"NamespaceRegistrationStatus":{
9041+
"type":"string",
9042+
"enum":[
9043+
"Registering",
9044+
"Deregistering"
9045+
]
9046+
},
89499047
"NetworkInterface":{
89509048
"type":"structure",
89519049
"members":{
@@ -9394,6 +9492,17 @@
93949492
},
93959493
"documentation":"<p>Describes cluster attributes that are in a pending state. A change to one or more the attributes was requested and is in progress or will be applied.</p>"
93969494
},
9495+
"ProvisionedIdentifier":{
9496+
"type":"structure",
9497+
"required":["ClusterIdentifier"],
9498+
"members":{
9499+
"ClusterIdentifier":{
9500+
"shape":"String",
9501+
"documentation":"<p>The unique identifier for the provisioned cluster.</p>"
9502+
}
9503+
},
9504+
"documentation":"<p>The identifier for a provisioned cluster.</p>"
9505+
},
93979506
"PurchaseReservedNodeOfferingMessage":{
93989507
"type":"structure",
93999508
"required":["ReservedNodeOfferingId"],
@@ -9702,6 +9811,32 @@
97029811
"locationName":"ReferenceLink"
97039812
}
97049813
},
9814+
"RegisterNamespaceInputMessage":{
9815+
"type":"structure",
9816+
"required":[
9817+
"NamespaceIdentifier",
9818+
"ConsumerIdentifiers"
9819+
],
9820+
"members":{
9821+
"NamespaceIdentifier":{
9822+
"shape":"NamespaceIdentifierUnion",
9823+
"documentation":"<p>The unique identifier of the cluster or serverless namespace that you want to register. </p>"
9824+
},
9825+
"ConsumerIdentifiers":{
9826+
"shape":"ConsumerIdentifierList",
9827+
"documentation":"<p>An array containing the ID of the consumer account that you want to register the namespace to.</p>"
9828+
}
9829+
}
9830+
},
9831+
"RegisterNamespaceOutputMessage":{
9832+
"type":"structure",
9833+
"members":{
9834+
"Status":{
9835+
"shape":"NamespaceRegistrationStatus",
9836+
"documentation":"<p>The registration status of the cluster or serverless namespace.</p>"
9837+
}
9838+
}
9839+
},
97059840
"RejectDataShareMessage":{
97069841
"type":"structure",
97079842
"required":["DataShareArn"],
@@ -10886,6 +11021,24 @@
1088611021
"type":"string",
1088711022
"sensitive":true
1088811023
},
11024+
"ServerlessIdentifier":{
11025+
"type":"structure",
11026+
"required":[
11027+
"NamespaceIdentifier",
11028+
"WorkgroupIdentifier"
11029+
],
11030+
"members":{
11031+
"NamespaceIdentifier":{
11032+
"shape":"String",
11033+
"documentation":"<p>The unique identifier for the serverless namespace.</p>"
11034+
},
11035+
"WorkgroupIdentifier":{
11036+
"shape":"String",
11037+
"documentation":"<p>The unique identifier for the workgroup associated with the serverless namespace.</p>"
11038+
}
11039+
},
11040+
"documentation":"<p>The identifier for a serverless namespace.</p>"
11041+
},
1088911042
"ServiceAuthorization":{
1089011043
"type":"string",
1089111044
"enum":[

0 commit comments

Comments
 (0)