amazon-ami

I need to use on Elastic Beanstalk a Java application written for Glassfish server. Beacuse of Amazon doesn't let me choose an AMI with Glassfish, I choosed one with Tomcat and i modified my application to work properly on Tomcat. Now, I've seen I also needed to use a Sun JDK, while by default Elastic Beanstalk AMI comes with openjdk. I googled a lot, finding some (not so many resources) interesting posts like this answer on StackOverflow What I can't understand is this part of the answer: Create your custom AMI from a running instance of Amazon's beanstalk AMI that you manually launch from

I'm creating an AMI for a server with 100G files. It's been like an hour and it's still not finished. (The AMI still says pending) Is there something wrong with it? What should I do? Alright so at this moment this seems like a stupid question. But I was very worried during that time :-) Just to let other people know, this process could take very, very long. My 100 GB AMI takes like 2.5 hours to create and the progress bar jumps from 0 to 100 directly after that. So don't worry. I also noticed snapshots take a long time. I have a simple 10 GB t2.micro instance, and it sat on 0% for about 10

I'm using AWS Cloudformation to setup numerous elements of network infrastructure (VPCs, SecurityGroups, Subnets, Autoscaling groups, etc) for my web application. I want the whole process to be automated. I want click a button and be able to fire up the whole thing. I have successfully created a Cloudformation template that sets up all this network infrastructure. However the EC2 instances are currently launched without any needed software on them. Now I'm trying to figure out how best to get that software on them. To do this, I'm creating AMIs using Packer.io . But some people have instead

I'm just getting started with AWS EC2 and not entirely sure I understand it. From what I've read, an instance is basically a virtual server, and you should be able to somehow "duplicate" that virtual server from the AWS console somehow. Then use Load Balancer or Elastic IP to route requests to one or the other. The problem comes in when I try to "duplicate" my instance. I tried a million things, but the only thing that got me close was creating an AMI of my current instance then launching an instance from that, but when I did that, the new instance was basically the default server config. None

I have multiple instances running behind Load balancer with Auto Scaling in AWS. Now, if I have to push some code changes to these instances and any new instances that might launch because of auto scaling policy, what's the best way to do this? The only way I am aware of is, to create a new AMI with latest code, modify the auto scaling policy to use this new AMI and then terminate the existing instances. But this might involve a longer downtime and I am not sure whether the whole process can be automated. Any pointers in this direction will be highly appreciated. The way I do my code changes