Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I am unable to delete an Amazon EBS snapshot because the console says that:
The snapshot snap-xyz is currently in use by ami-1234
I made the snapshot with the intention of moving the server between accounts, which I have done, but now do not wish to keep the snapshot (incurring charges in this account).
The documentation I can find indicates that to remove the snapshot the server must be no longer required.
Is there a way to separate the two, keep the server and delete the snapshot?
If you are done with moving the server across accounts, then it means that you no longer need the AMI also. You need to deregister the AMI and then you can delete the snapshot. Details are mentioned here.
Before you attempt to delete an EBS snapshot, make sure that the AMI
isn’t currently in use. AMIs can be used with a variety of AWS
services, such as Amazon Elastic Compute Cloud (Amazon EC2), AWS Auto
Scaling, AWS CloudFormation, and more. If you delete an AMI that’s
used by another service or application, the function of that service
or application might be affected.
If you no longer need the EBS snapshot or its associated AMI,
deregister the AMI. Then, delete the EBS snapshot in the Amazon EC2
console.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
Details: I have a web app on Elastic Beanstalk (web server) and I need several cronjobs to be executed. These cronjobs must connect to AWS RDS. For this, I created an Elastic Beanstalk Worker but I must pay for the worker instance to be available all day when cronjobs only need some minutes.
You can use AWS Lamda with scheduled events for this. To connect to RDS you need to place the Lambda function inside the VPC which RDS resides with required network accessibility.
This will work for short running jobs which does not exceed 5 minutes, which is the AWS Lambda maximum execution time limit.
For long running jobs you can start and stop a EC2 with AWS Lambda scheduled events, using AWS EC2 SDK.
Alternatively you can also use AWS batch scheduled with EC2 spot instances to lower the costs.
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 days ago.
Improve this question
Currently, I have a Amazon hosting at EU but I want to switch to Singapore. What are the problems when switching the region on Amazon web server?
It sounds like your situation is:
You are currently running an Amazon EC2 instance in either the Frankfurt or Ireland regions
You wish to use a different region
There's two answers to this question, and it depends on whether you want to "move" an instance to another region, or just "use" another region.
Using another region
If you wish to launch an Amazon EC2 instance in a different region, simply select the desired region from the pull-down list in the AWS Management Console, then launch a new instance. Easy!
Moving an EC2 instance to another region
It is not possible to "move" an instance, but you can copy the disk to another region and then launch a new instance using that disk image.
The steps are:
Select your existing instance, and choose Actions/Image/Create Image
Click AMIs in the console to view the AMI
Select Actions/Copy and select a destination region
Once the AMI has been copied, switch the console to the destination region
Select the AMI that was copied, then choose Actions/Launch to launch a new instance from this disk image
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I am running a web-app on an AWS EC2 instance that uses EBS storage as its local drive. The web app runs on an Apache/Tomcat server, handles uploaded files in local storage and uses a MySQL database, all on this local drive. Does AWS guarantee the integrity and availability of EBS data or should I back it up to S3?
If so, how do I do that? I need to have daily incremental backups (i.e. I can only afford to loose recent transactions/files performed today).
Note: I am not worried about human caused errors (accidental deletes, etc.) rather system crashes, underlying service failure, etc.
Thanks..
Amazon does not guarantee the integrity of your EBS volumes, but they are very easy to back up. Simply take a daily snapshot (You could set up a cron using ec2-api-tools to do the daily snapshot).
EBS snapshots are stored in S3. They are not in your own bucket and the details are handled by Amazon, but the infrastructure that the snapshots are stored on is S3.
The snapshots are incremental, and back up the entire volume. Each snapshot stores the changes on the device since the last snapshot, so taking them often will reduce how long they take to make, but you can only have a limited number of snapshots at once per AWS account. I think it is 250. You need to delete your old snapshots eventually to deal with that. You could also do that with a cron job. Deleting old snapshots does not invalidate the newer ones even though they are stored as incremental, because it will actually update the next newest snapshot to contain the information from the previous one upon deletion.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Still reading up on AWS.
Amazon Large Instances comes with 850GB local storage.
However, i read in case of failover and we want to power up another instance, we can just mount a EBS volume on it and start running right? That will mean that we have to configure and store it on a EBS volume to enjoy this capability.
Does that mean that with local storage, say if data are saved in local, we will not able to do it ?
EBS is charged separately, the large local storage of 850GB might not be that advantageous ? Is EBS used normally for Webserver data or primary for MySQL for persistent data?
Anyone who has experience with AWS can have good inside on this?
That will mean that most of the instances i pay for have to buy EBS to enjoy the switch over capability?
I recommend you start out using EBS entirely. That means running an EBS boot AMI, and putting your data (web, database, etc) on a separate EBS volume (recommended) or even the EBS root volume. Here's an article I wrote that describes more details about why I feel this way for beginners:
http://alestic.com/2012/01/ec2-ebs-boot-recommended
The listed 850GB local storage is ephemeral, which means that it is at risk of being lost forever if you stop your instance, terminate your instance, or if the instance fails. It might be useful to use for things like a large /tmp but I recommend against using ephemeral storage for anything valuable.
Note also that the 850 GB is not in a single partition, is not all attached to the instance by default, and is not all formatted with a file system by default.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have some machines created with my account. Some of them uses S3 storage, some EBS.
Now I need to move these machines to my company account to let it pay for.
As I know I can start each machine as my company user and create an image.
I wonder if there is a way to simple copy these machines?
You can copy an EBS boot AMI from one EC2 account to another using the technique I wrote about here:
Copying EBS Boot AMIs Between EC2 Regions
http://alestic.com/2010/10/ec2-ami-copy
The commands I list are for copying an EBS boot AMI from one region to another, but if you simply use the right commands with different accounts instead of different regions, you can accomplish your goal. Note that you'll have to upload your personal ssh key to both accounts following these instructions:
Uploading Personal ssh Keys to Amazon EC2
http://alestic.com/2010/10/ec2-ssh-keys
Copying S3 based AMIs from one account to another is a bit convoluted and involves commands like:
ec2-download-bundle
ec2-unbundle
(switch accounts)
ec2-bundle-vol
ec2-upload-bundle
ec2-register
Alternatively, you hopefully documented the exact steps you took to create the original AMIs. Simply follow these instructions to create the AMIs in the new account.
You can also share the AMIs with your other account. Then launch instances on the new account and create AMIs that will then be associated with the new account.