- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
Please let me know the procedure to connect S3 bucket from SAS.
We don't create secret key or Access key for id's. In this case, how we can connect S3 bucket from SAS without secret key/Access key for id.
Thanks,
Vishal
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
https://documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.4&docsetId=proc&docsetTarget=n1volod...
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
You're going to have to provide more information for us to help you..
- "Connect S3 bucket from SAS" - SAS where? On an AWS instance?
- If so, what domains, accounts, public/private subnets, etc have been set up?
- Or do you have SAS installed "in premises" but want to connect to an S3 instance?
- And by "connect", do mean "mount", create a SAS libref?
More information, please.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
https://documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.4&docsetId=proc&docsetTarget=n1volod...
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hello SimonDawson, / SAS team,
I work for Oracle Cloud Infrastructure (OCI) and we do offer an Object Storage service in our OCI cloud and we provide an S3 compatible API, so customers/Partners/ISV providers who already have connectors for S3 can reused the same connector to connect to OCI Object Storage .
I reviewed the S3 procedure documentation and currently I am unable to use it, because the S3 endpoint URL is not exposed as a configurable parameter. Other ISV providers like Confluent Kafka also has an S3 connector and we are able to use that connector to integrate with OCI Object Storage, since they made the S3 endpoint URL configurable for their users. Its an optional field, so if users provide it, it will be used, if not, the default logic to create endpount URL based on S3 region will be used.
OCI Object Storage endpoint URL for S3 compatible APIs is here:
- https://<object_storage_namespace>.compat.objectstorage.us-ashburn-1.oraclecloud.com
- https://<object_storage_namespace>.compat.objectstorage.us-phoenix-1.oraclecloud.com
object_storage_namespace is a unique value per OCI Organization/Tenant account. us-ashburn-1 and us-phoenix-1 are example of region of OCI cloud.
By making the above configurable, SASM9.4 will start to work with OCI Object Storage and lot of other S3 compatible Object Storage solutions like Minio too.
Happy to be part of the effort to get this tested with OCI Object Storage, just drop me an email at pinkesh.valdria@oracle.com
Thanks,
Pinkesh Valdria
From Kafka Confluent S3 connector docs: https://docs.confluent.io/current/connect/kafka-connect-s3/index.html
Using Non-AWS Storage Providers
Many cloud providers implement an AWS S3-compatible API. You can use the Kafka Connect S3 connector to connect to object storage on their platform. When configuring the S3 connector for object storage on other cloud providers, include the following configuration option (if applicable for the cloud provider):
store.url
The object storage connection URL.
- Type: string
- Default: null