Home > Workload Solutions > Data Analytics > Guides > Dell PowerScale and Cloudera Data Platform Private Cloud Data Services > Configure an S3 bucket to store logs
The CDE archive logs would normally be stored in an Ozone bucket. Use the following steps to use a PowerScale OneFS S3 bucket instead.
Step 1: Create a user in the access zone being used for CDP
1. Navigate to Access>Membership and roles
2. Select the Access zone and Provider and create a new user
Step 2: Enable the S3 Service
1. Navigate to Protocols>Object storage (S3)
2. From the Global Settings tab, enable the S3 service and S3 HTTP
Step 3: Create access and secret key credentials
1. Click the Key management tab, select the access zone and choose the cdeuser we previously created, then click ‘Create a key’
Note: Copy the Secret key and store it in a safe place as this is the only opportunity it will be displayed.
In the above screenshot our access key is 5_cdeuser_accid (5 refers to the zone id)
Step 4: Create an S3 bucket
Navigate to the ‘Buckets’ tab and click ‘Create bucket’
Name: Enter the name of the bucket to create
Owner: Select the user who will own the bucket (for example: cdeuser)
Path: The path where the bucket will be created (Note: the path must be created under the access zone path. For example, the access zone path used here is /ifs/data/cdp so the bucket is created as /ifs/data/cdp/cdelogs).
Step 5: Configure the S3 bucket on CDP to store the CDE virtual service logs
Verify that an Environment was created during the installation process by navigating to the Environments tab on the left navbar of the Management Console.
Right-click on the Management Console page and select ‘Inspect’.
Note: The browser you use may require a different way to Inspect the page
Select the Console URL under ‘Cookies’ and copy the ‘cdp-pvt-session-token’ Cookie value from the lower section of the page. Close the Browser Inspection tool
Run the following Curl command to configure the OneFS S3 bucket to store logs.
curl -v '<CP-URL>/api/v1/environments2/setEnvironmentSetting' -H 'Content-Type: application/json' -H \
'Cookie: cdp-pvt-session-token=<CDP-Private-Token>; _gat=1' --data \
'{"environmentName": "<Env-Name>", "settings": \
{"logType":"OZONE","ozoneLogsPath":"/logs","ozoneLogsBucket":"<Bucket-Name>" \
,"ozoneS3Secret":"<S3-SecretKey>","ozoneS3Key":"<S3-Accesskey>","ozoneS \
3RestUrl":"<S3-EndPointUrl>"} }' --compressed –insecure
Where:
CP-URL: Control plane URL
CDP-Private-Token: Private session token
Env-Name: Data Service Environment name
Bucket-Name: S3 bucket name
S3-SecretKey: Secret key to access S3 bucket
S3-AccessKey: Access key to access S3 bucket
S3-EndPointUrl: Endpoint URL to access the S3 bucket
Verify you see an HTTP/1.1 200 OK after running the command.
* upload completely sent off: 249 out of 249 bytes
< HTTP/1.1 200 OK
< Date: Tue, 13 Feb 2024 17:37:43 GMT
< Content-Type: application/json
< Transfer-Encoding: chunked
< Connection: keep-alive
< x-cdp-request-id: c25325cc-c3f9-4ad1-b72c-5dc5adab1bc8
< x-altus-request-id: c25325cc-c3f9-4ad1-b72c-5dc5adab1bc8