Questions tagged with Compute
Content language: English
Sort by most recent
I'd like to modify our reserved instance from to a larger instance in the same class. Importantly, it is a convertible instance and I am able to find the documentation regarding how to modify the instance. However, I am not seeing the technical details of what that entails. Do I need to disconnect the EBS drives currently attached to my reserved instance before proceeding with a modification? Does a modified reserved instance just automatically appear and all drives, users, settings, etc move to it? Or do I have to reconfigure the new instance with my original instance's settings?
My EC2 instance suddenly stopped responding. Both status check failed (2/2) and I was unable to connect with SSH. The monitoring graph is also missing during that downtime. Instance Id: **i-0f0a93ed1d9337608**
i have a WordPress instance on my lightsail , so i want Improve the performance of my website by using elasticach memcached service , im on lighsail i can't connect to other services of aws such as memcached , if you know any method to make that possible , and thanks a lot for you help
![Enter image description here](/media/postImages/original/IMbpnTuy9WQ6Wc3ANtspF1cg) I was experimenting with **RDS Blue/Green deployment** , it worked fine with normal instance but when I tried with instance having **read replicas in different region** , after clicking on Create Blue/Green deployment it's just **showing loader** , also console is showing following error eg . Main instance is on **us-east-1** and it has DB read replica in **eu-central-1** it just showing loader screen on clicking create
Hi all, a bit of a strange one here. I've been trying to rework my environment so that we can enable seamless domain join for any and all instances created moving forward and up until now, we have been manually joining Linux EC2 instances using sssd. In following the documentation here (https://docs.aws.amazon.com/directoryservice/latest/admin-guide/seamlessly_join_linux_instance.html) I came to find that the AWS-JoinDirectoryServiceDomain SSM Document instead uses winbind, which threw things for a bit of a loop as nearly every component we configured with sssd in the past was not applicable with winbind (limiting ssh access to the instance to specific groups, realm commands were slightly different, fsx for windows mounting commands, etc). After some reading, it seems that sssd is the preferred method as it is more modern and supports greater flexibility. Is there a reason winbind is being used here? Does AWS plan on updating this document to use sssd instead? Given all of the little challenges initially faced with my first seamless domain joined machine, I'm a little wary of continuing to use this document/method of seamlessly joining machines to my domain. Thanks!
Hi, I started using AWS-SSM, so I can use the SSO solution to connect to the EC2-instances using the SSM. But, as known; to connect to the SSM; should use the instance id. I am looking if there is a way to use the instance name instead of the instance id.
hi, i having a wordpress website and i create multiple instance on same region on lightsail. Add a lightsail managed database and connected loadbalncer but i couldnt able to add most plugins, when we add a plugin and it will activate successfully, but when checking on another site it says woocommerce plugin deactivated due to an error, the plugin does not exist. I can see that both are using same database. when we edit a post and adding update, it reflect on other servers as well any solution?
I want to migrate EC2 Instance from one account to another with Elastic IP Address
I have a nodejs backend running in my instance ec2 and bucket with my files. I need to allow traffic for that users can do a download for this file but the instance show me in return that this connection refused for this.
Hi Team, i have successfully built a Wordpress site on a personal Lightsail account, and post development i was able to package it and the DB, and setup it up on a new instance on the clients AWS account and transferred all the files and the db, the site works completely fine. Except i am unable to update the Wordpress core. I have tried updating the file permissions and nothing has worked, the error i get is "The update cannot be installed because some files could not be copied. This is usually due to inconsistent file permissions.: wp-admin/includes/update-core.php" What i doubt is the problem is with the user role that triggers the update or the write access to these folders, so i tried to do the update through the wp-cli and i got the same error, even though i ran it sudo. all the files have the permission of 664/644 and dir 775/755. and the file ownership is bitnami:daemon. The plugin/theme updates are working fine, the media uploads without an issues, only the core update im having an issue. I will put out a short decription on how to move from lightsail to another account based lightsail, once i can rectify this. Regards, Shiva