Category: <span>Cloud</span>

To create an AWS S3 bucket to use as a backup location for IBM Storage Fusion, you need to configure the bucket in AWS and ensure that it is properly configured for compatibility with IBM Storage Fusion. Below are the steps to achieve this:

Step 1: Sign in to the AWS Management Console

  1. Sign in aws.amazon.com and sign in to your AWS account using your credentials.
  2. After you sign in, navigate to the AWS Management Console.

Step 2: Access the S3 service

  1. In the AWS Management Console, use the search bar at the top and enter S3.
  2. Select S3 from the results to open the Amazon S3 dashboard.

Step 3: Create an S3 bucket

  1. From the S3 dashboard, click the Create bucket button.
  2. Bucket Name: Enter a unique name for your bucket (for example, ibm-storage-fusion-backup-2025).
  3. Region: Choose an AWS Region that aligns with your IBM Storage Fusion implementation for optimal performance and compliance (e.g., us-east-1).
  4. Object ownership: Leave the default setting (ACLs disabled) unless you have specific requirements.
  5. Block public access: For security, keep Block all public access enabled unless IBM Storage Fusion explicitly requires public access (see IBM documentation).
  6. Bucket versioning: Enable versioning if you want to maintain multiple versions of backup objects for recovery purposes. This is recommended for backup scenarios.
  7. Encryption: Enable server-side encryption with Amazon S3-managed keys (SSE-S3) for added security.
  8. Click Create bucket to finish the configuration.

Step 4: Configure the bucket for IBM Storage Fusion

IBM Storage Fusion often integrates with AWS S3 for object backup and storage through its data protection capabilities. To ensure compatibility:

  1. Bucket policy: You may need to configure a bucket policy to allow IBM Storage Fusion to access the bucket. This requires an IAM role or user with appropriate permissions (for example, s3:PutObject, s3:GetObject, s3:ListBucket). Policy example:

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789012:user/ibm-fusion-user"
},
"Action": [
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:ListBucket",
"s3:ListMultipartUploadParts",
"s3:AbortMultipartUpload"
],
"Resource": [
"arn:aws:s3:::my-fusion-bucket",
"arn:aws:s3:::my-fusion-bucket/*"
]
}
]
}

Replace <AWS_ACCOUNT_ID> and <ROLE_NAME> with their specific values.

Access credentials: Create an IAM user or role with programmatic access, and generate an access key ID and a secret access key. These will be used by IBM Storage Fusion to authenticate with S3.

  1. Go to IAM Users >  > Add User, enable programmatic access, attach the AmazonS3FullAccess policy (or a custom policy), and save the credentials. If you use full access, you don’t need the policy exemplified above.

 Lifecycle rules: Optionally, configure lifecycle rules to transition older backups to cost-effective storage classes, such as S3 Glacier or S3 Glacier Deep Archive, to optimize costs.

Cloud

Today i got the following error when i try to run the command :
./cpd-cli manage login-entitled-registry ${IBM_ENTITLEMENT_KEY}

Run command: podman run -d –name olm-utils-play –env CMD_PREFIX=manage -v /opt/cpd-cli-linux-EE-12.0.2-39/cpd-cli-workspace/olm-utils-workspace/work:/tmp/work icr.io/cpopen/cpd/olm-utils:latest[ERROR] 2023-03-06T12:41:55.991666Z Command exception: Failed to start the olm-utils-play container: Error: runc: container_linux.go:370: starting container process caused: error adding seccomp filter rule for syscall bdflush: permission denied: OCI permission denied (exit status 126)[ERROR] 2023-03-06T12:41:55.998354Z RunPluginCommand:Execution error: exit status 1

This error happened due to runc version too low. My bastion host is RHEL 8.4. To solve the problem i just updated the Linux, and everything works.

Cloud openshift podman

This error appears today on my MAC using macOS 12.6 Monterey. I don’t know the cause and . It was woking last time i used podman on this MAC.

To solve the problem:

podman machine rm podman-machine-default

brew uninstall podman

brew install podman

podman machine init

Cloud MAC

 

Cloud service end of marketing and end of service: Connections Cloud

Effective July 16, 2019, HCL® will withdraw from marketing all part numbers related to Connections Cloud (5725-F82), inclusive of but not limited to Verse, SmartCloud Notes, Connections S1, Connections S2, Connections Social Cloud, Connections Engagement Center, Connections Chat, Connections Meetings, Dual Entitlement,  and Domino Applications on Cloud (5900-A1K) as subscribed to under the applicable agreements.  Existing Connections Cloud customers will be able to purchase additional entitlements through the end of service date.

Effective, July 16, 2020, HCL will end service for all part numbers related to Connections Cloud.

More information here

Cloud

I setup the connection to cloudant service to store historical data of my IoT devices. When i click “done” an pop up window appears asking to authorize the connection to Cloudant Service. I confirm to authorize and i get the message 502 Bad Gateway: Registered endpoint failed to handle the request. and i can’t store iot device data on cloudant. I tried several times.

I search a lot about this error message with no luck .  To solve the problem erase all IBM cookies from you browser and restart it.

Cloud IoT