1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
To register your Avro schema in AWS Glue Schema Registry from an on-premises cluster, you'll need to interact with AWS services over the internet. Since AWS Glue Schema Registry doesn't provide a public endpoint directly, you can use the AWS SDK or AWS CLI to interact with the Schema Registry through the AWS Glue API.
- Ensure your on-premises service has AWS credentials and permissions to access AWS Glue Schema Registry.
- Install the AWS SDK or AWS CLI on your on-premises machine or service.
- Use the AWS SDK or CLI to register your Avro schema with AWS Glue Schema Registry.
- Make sure your on-premises cluster can connect to AWS services over the internet.
Resources:
Contenuto pertinente
AWS UFFICIALEAggiornata un anno fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks for the response , but i would like to understand more on the Point 1, so within AWS we use IAM policies and Service Account permissions to access Glue schema registry but when my service runs on premise(private data centre) I do not have IAM , so just by setting the AWSSchemaregistryConstants values will I be able to register my schema in AWS Glue schema registry.
To add to the answer, the CLI, SDK or boto3 will rely on the Glue endpoint, there is not Schema specific service endpoint
When running services from an on-premises environment, you can still use AWS IAM by creating an IAM user or role with the necessary permissions for AWS Glue Schema Registry and then use its credentials (access key ID and secret access key) in your service. You'll configure these credentials in your application or service environment to authenticate and authorize your requests to AWS Glue Schema Registry. This method extends AWS security and management to your on-premises services, allowing them to interact with AWS resources securely.