amazon-ec2

问题 My developer has created an EC2 instance on AWS and I want to be able to access it via my own dashboard. What I did is: As a root user, I created an IAM account for me and him and assigned us both to a group named PowerUsers I created an Organizational Unit and added his account to it When he goes to his EC2 dashboard, he sees his created instances. But when I go to my EC2 dashboard, I see nothing. We both selected the correct region. I hope someone can help us out here, I can't seem to get

问题 I have a Jupyter Notebook server on an EC2 instance with python2 (default) and ITorch kernels. Everything works fine when run through SSH command line. The problem is that when I try to make this run at startup, the notebook server can't find ITorch kernel. I does work fine for python notebooks though. The error I get is a window saying Kernel not found I couldn't find a kernel matching iTorch. Please select a kernel: (python2) What I did was adding this line to /etc/rc.local /home/ubuntu

问题 I use an Elastic Beanstalk environment for deploying a web application, and I've set up an IAM role for the instances the application will run on. Everything works flawlessy 99.99% of the time, however intermittently I will see errors in our logs with request failures showing botocore errors like the following: File "/opt/python/run/venv/local/lib/python3.6/site-packages/boto3/resources/factory.py", line 339, in property_loader self.load() File "/opt/python/run/venv/local/lib/python3.6/site

问题 The AWS terminated my running spot with the error "instance-terminated-capacity-oversubscribed" Is there a way to see the available capacity of an instance type in the different ec2 zones ? so I can create my new spot in a more "available" zone ? 回答1: Look at the "spot instance history". This will not tell you the future, but will give you a good indication up to now. This link will show you how to use the AWS Console and CLI to get history data. Spot Instance Pricing History 来源： https:/

问题 I had a use case where I was switching to using spot instances for my application instead of on demand instances. According to my requirement i should be able to stop that instance and restart it just the way we do it for on demand ec2-instances. In the aws console, i only found the option to reboot or terminate my instance and hovering over the stop option said "Spot instance cannot be stopped". Is there a workaround to allow stopping the instance or is it not possible as of now? 回答1:

问题 Is there a way to get the availability zones where an instance type (e.g. t3.medium) is available before requesting the instance? I'm trying to run the following code and for certain regions it fails with the following error: Error: Error launching source instance: Unsupported: Your requested instance type (t3.micro) is not supported in your requested Availability Zone (us-east-1e). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1b, us-east-1c

问题 Is there a way to get the availability zones where an instance type (e.g. t3.medium) is available before requesting the instance? I'm trying to run the following code and for certain regions it fails with the following error: Error: Error launching source instance: Unsupported: Your requested instance type (t3.micro) is not supported in your requested Availability Zone (us-east-1e). Please retry your request by not specifying an Availability Zone or choosing us-east-1a, us-east-1b, us-east-1c

问题 I have installed spark on AWS. When I try to execute on AWS it works, but spark doesn't work, when I check the sparkMaster log I see the next: Spark Command: /usr/lib/jvm/java-8-oracle/jre/bin/java -cp /home/ubuntu/spark/conf/:/home/ubuntu/spark/jars/* -Xmx1g org.apache.spark$ ======================================== Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties 16/09/12 09:40:18 INFO Master: Started daemon with process name: 5451@server1 16/09/12 09:40:18

问题 I have installed spark on AWS. When I try to execute on AWS it works, but spark doesn't work, when I check the sparkMaster log I see the next: Spark Command: /usr/lib/jvm/java-8-oracle/jre/bin/java -cp /home/ubuntu/spark/conf/:/home/ubuntu/spark/jars/* -Xmx1g org.apache.spark$ ======================================== Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties 16/09/12 09:40:18 INFO Master: Started daemon with process name: 5451@server1 16/09/12 09:40:18

问题 Using boto3 run_instances The instance is stopping after 30 sec by itself and the State transition reason in the console shows: Client.InstanceInitiatedShutdown: Instance initiated shutdown What might be the issue? 回答1: Check if your AMI type (PV or HVM) and the volumes are compatible and you are mounting the volumes to the correct device . If there is a compatibility issue, the instance shuts down with Client.InstanceInitiatedShutdown: Instance initiated shutdown 来源： https://stackoverflow