create_integration
async
¶
create_integration(
*,
config_overrides: Optional[AsyncRDSClientConfig] = None,
source_arn: Optional[SourceArn] = None,
target_arn: Optional[Arn] = None,
integration_name: Optional[IntegrationName] = None,
kms_key_id: Optional[String] = None,
additional_encryption_context: Optional[EncryptionContextMap] = None,
tags: Optional[TagList] = None,
data_filter: Optional[DataFilter] = None,
description: Optional[IntegrationDescription] = None,
) -> Integration
Creates a zero-ETL integration with Amazon Redshift.
Parameters:
-
source_arn(Optional[SourceArn], default:None) –The Amazon Resource Name (ARN) of the database to use as the source for replication.
-
target_arn(Optional[Arn], default:None) –The ARN of the Redshift data warehouse to use as the target for replication.
-
integration_name(Optional[IntegrationName], default:None) –The name of the integration.
-
kms_key_id(Optional[String], default:None) –The Amazon Web Services Key Management System (Amazon Web Services KMS) key identifier for the key to use to encrypt the integration. If you don't specify an encryption key, RDS uses a default Amazon Web Services owned key.
-
additional_encryption_context(Optional[EncryptionContextMap], default:None) –An optional set of non-secret key–value pairs that contains additional contextual information about the data. For more information, see Encryption context in the Amazon Web Services Key Management Service Developer Guide.
You can only include this parameter if you specify the
KMSKeyIdparameter. -
data_filter(Optional[DataFilter], default:None) –Data filtering options for the integration. For more information, see Data filtering for Aurora zero-ETL integrations with Amazon Redshift or Data filtering for Amazon RDS zero-ETL integrations with Amazon Redshift.
-
description(Optional[IntegrationDescription], default:None) –A description of the integration.
Raises:
-
DBClusterNotFoundFault–DBClusterIdentifierdoesn't refer to an existing DB cluster. -
DBInstanceNotFoundFault–DBInstanceIdentifierdoesn't refer to an existing DB instance. -
IntegrationAlreadyExistsFault–The integration you are trying to create already exists.
-
IntegrationConflictOperationFault–A conflicting conditional operation is currently in progress against this resource. Typically occurs when there are multiple requests being made to the same resource at the same time, and these requests conflict with each other.
-
IntegrationQuotaExceededFault–You can't crate any more zero-ETL integrations because the quota has been reached.
-
KMSKeyNotAccessibleFault–An error occurred accessing an Amazon Web Services KMS key.
-
UnknownServiceError–The service returned an error code this client does not model.
Examples:
To create a zero-ETL integration The following example creates a zero-ETL integration with Amazon Redshift.
>>> await client.create_integration(integration_name='my-integration', source_arn='arn:aws:rds:us-east-1:123456789012:cluster:my-cluster', target_arn='arn:aws:redshift-serverless:us-east-1:123456789012:namespace/62c70612-0302-4db7-8414-b5e3e049f0d8')
Source code in docs_src/capo_rds/_services/async_rds.py
3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 | |