amazon-ebs

问题 I've been looking around and haven't found much content with regards to a best practice when it comes to setting up HTTPS/SSL on Amazon Elastic Beanstalk with a Multi-container Docker environment. There is a bunch of stuff when it comes to single container configuration, but nothing when it comes to multi-container. My Dockerrun.aws.json looks like this: { "AWSEBDockerrunVersion": 2, "volumes": [ { "name": "app-frontend", "host": { "sourcePath": "/var/app/current/app-frontend" } }, { "name":

问题 The problem is simple. I need to copy the files from one EBS to Another without passing the files through my local machine. Is this possible? If so how? 回答1: In order to copy files from one EBS volume to another EBS volume, both volumes will (at some point) need to be attached to an instance, though not necessarily the same instance. There are a lot of ways to do this if you allow for multiple instances and/or temporarily storing the files on a third storage option, but without constraints,

问题 The problem is simple. I need to copy the files from one EBS to Another without passing the files through my local machine. Is this possible? If so how? 回答1: In order to copy files from one EBS volume to another EBS volume, both volumes will (at some point) need to be attached to an instance, though not necessarily the same instance. There are a lot of ways to do this if you allow for multiple instances and/or temporarily storing the files on a third storage option, but without constraints,

问题 The problem is simple. I need to copy the files from one EBS to Another without passing the files through my local machine. Is this possible? If so how? 回答1: In order to copy files from one EBS volume to another EBS volume, both volumes will (at some point) need to be attached to an instance, though not necessarily the same instance. There are a lot of ways to do this if you allow for multiple instances and/or temporarily storing the files on a third storage option, but without constraints,

问题 dear Kubernetes guru's! I have spinned kube 1.4.1 cluster on manually created AWS hosts using 'contrib' Ansible playbook (https://github.com/kubernetes/contrib/tree/master/ansible). My problem is that Kube doesn't attach EBS drives to minion hosts. If I define the pod as follows: apiVersion: extensions/v1beta1 kind: Deployment metadata: name: kafka1 spec: replicas: 1 template: spec: containers: - name: kafka1 image: daniilyar/kafka ports: - containerPort: 9092 name: clientconnct protocol: TCP

问题 dear Kubernetes guru's! I have spinned kube 1.4.1 cluster on manually created AWS hosts using 'contrib' Ansible playbook (https://github.com/kubernetes/contrib/tree/master/ansible). My problem is that Kube doesn't attach EBS drives to minion hosts. If I define the pod as follows: apiVersion: extensions/v1beta1 kind: Deployment metadata: name: kafka1 spec: replicas: 1 template: spec: containers: - name: kafka1 image: daniilyar/kafka ports: - containerPort: 9092 name: clientconnct protocol: TCP

问题 I have an EBS volume that displays a state of "in-use - optimizing(%)". What does this mean? What are the optimizations that AWS is performing? This is on a 300gb encrypted gp2 volume attached to a Windows Server 2012 R2 EC2 instance. 回答1: The in-use - optimizing state relates to EBS volume resizing. in-use indicates that this volume is attached to an EC2 instance. optimizing is the volume's modification state. According to the AWS documentation on volume modifications: An EBS volume being

问题 I have an EBS volume that displays a state of "in-use - optimizing(%)". What does this mean? What are the optimizations that AWS is performing? This is on a 300gb encrypted gp2 volume attached to a Windows Server 2012 R2 EC2 instance. 回答1: The in-use - optimizing state relates to EBS volume resizing. in-use indicates that this volume is attached to an EC2 instance. optimizing is the volume's modification state. According to the AWS documentation on volume modifications: An EBS volume being

问题 I've been browsing for a week on how to use AWS. I've always been using cpanel (I'm new to web) but someone recommended AWS to me. From the info I pieced together from various websites, I think I'm supposed to do the following?: 1) copy my website files to S3 2) set up an instance in EC2 3) set up volume in EBS and attach to instance 4) set up elastic IP and attach to instance. 5) ?? The questions are, 1) is this correct? 2) Where and how do I create mySQL database? Do I use SimpleDB, Where

问题 AWS launched sc1 and st1 HDD EBS volume types recently, I can't seem to use these as root volumes while launching new EC2 instances or launching from already created AMI's (tried both). I chose an m4 machine, in any case, the root volume is EBS itself, below is a screenshot, the second volume that I add gets the new options, however the first one I can't choose the same. Is this by design AWS people? 回答1: If you look from http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html