Aws

If you have an ElastiCache Memcached cluster that you no longer need, it’s better to delete it. Dno’t believe me? Even AWS said so too: It is almost always a good idea to delete clusters that you are not actively using. Until a cluster’s status is deleted, you continue to incur charges for it. [1] Well, I have a Memcached cluster that I don’t need anymore. But instead of deleting this cluster using AWS console [1], I’m going to do this via AWS CLI. ...

This is a quick note on how to delete VPC endpoints that are no longer needed with AWS CLI. First, we need to find all the vpc-endpoints-ids [1]. ❯ aws ec2 describe-vpc-endpoints --query 'VpcEndpoints[].VpcEndpointId' [ "vpce-097008f8d26caxxxx", "vpce-07aaeabdefd8xxxx", "vpce-0bc6d548ff2e0xxxx" ] Note: I replaced the last 4 digit with ‘xxxx’. It’s a good idea to try out without really deleting the VPC endpoints by supplying --dry-run to the command below: ❯ aws ec2 delete-vpc-endpoints --vpc-endpoint-ids vpce-097008f8d26caxxxx vpce-07aaeabdefd8xxxx vpce-0bc6d548ff2e0xxxx --dry-run An error occurred (DryRunOperation) when calling the DeleteVpcEndpoints operation: Request would have succeeded, but DryRun flag is set. Let’s delete all of the 3 resources: ...

I already wrote a blog post on How to install AWS CLI on RockyLinux, where I shared how to leverage the RPM package from EPEL repository. So what do I need to create a post here? Well, when I tried to use the same method to install the AWS CLI on an AlmaLinux 9.2, there was an issue with dependency. Here is what happened: [kenno@wedev1 ~]$ sudo dnf install awscli [sudo] password for kenno: Last metadata expiration check: 0:05:08 ago on Sun 20 Aug 2023 18:35:23. Error: Problem: conflicting requests - nothing provides python3.9dist(docutils) >= 0.10 needed by awscli-1.23.10-3.el9.noarch (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Good thing is, there are a few ways to install AWS CLI on Linux. I’ll be using the method described at official AWS document to install the CLI. ...

When you are finished with a WorkSpace, you can delete it. You can also delete related resources. In this post, I’ll be using AWS CLI to delete a WorkSpace that is no longer needed. To delete a WorkSpace using AWS CLI, we can use terminate-workspaces command [2]. But first, I’d need to find the workspace id. ➜ aws workspaces describe-workspaces --query 'Workspaces[].WorkspaceId' --output text ws-9xm222222 Now that I got the WorkSpace id as ws-9xm222222, I can proceed to terminate this WorkSpace. ...

I need to stop a WorkSpace now and I don’t want to login to AWS WorkSpace console. The following is the steps I’m literally taking to achieve this goal. Find out the WorkSpace ID, assuming that my AWS CLI has been setup correctly. ❯ aws workspaces describe-workspaces { "Workspaces": [ { "WorkspaceId": "ws-9xm222222", "DirectoryId": "d-9767555555", "UserName": "kenno", "IpAddress": "172.xx.x.xx", "State": "AVAILABLE", "BundleId": "wsb-clj855555", "SubnetId": "subnet-0a4ae4b324a799999", "ComputerName": "A-2B99WV33TITAN", "WorkspaceProperties": { "RunningMode": "AUTO_STOP", "RunningModeAutoStopTimeoutInMinutes": 60, "RootVolumeSizeGib": 80, "UserVolumeSizeGib": 50, "ComputeTypeName": "STANDARD", "Protocols": [ "PCOIP" ] }, "ModificationStates": [] } ] } We can see that the WorkSpace ‘ws-9xm222222’ is in AVAILABLE state. To stop this workspace now, run the following command: ❯ aws workspaces stop-workspaces --stop-workspace-requests WorkSpaceId=ws-9xm222222 Parameter validation failed: Unknown parameter in StopWorkspaceRequests[0]: "WorkSpaceId", must be one of: WorkspaceId ❯ aws workspaces stop-workspaces --stop-workspace-requests WorkspaceId=ws-9xm222222 { "FailedRequests": [] } Notice that the CLI option is case sensitive, and I “deliberately” made a mistake with WorkSpaceId to demonstrate this. Hahaha. ...