239 Matching Annotations
  1. May 2019
    1. When creating VPCs and VSwitches, you have to specify the private IP address range for the VPC in the form of a Classless Inter-Domain Routing (CIDR) block. Private IP address range of VPC Use 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8 or their subsets as the private IP address range for your VPC. Note the following when planning the private IP address range of VPC: If you have only one VPC and it does not have to communicate with a local data center, you are free to use any of the preceding IP address ranges or their subnets. If you have multiple VPCs, or you want to build a hybrid cloud composed of one or more VPCs and local data centers, we recommend that you use a subset of these standard IP address ranges as the IP address range for your VPC and make sure that the netmask is no larger than /16. You also need to consider whether the classic network is used when selecting a VPC CIDR block. If you plan to connect ECS instances in a classic network with a VPC, we recommend that you do not use the IP address range 10.0.0.0/8, which is also used by the classic network.

      VPC CIDR / IP Addressing plan

  2. Mar 2019
  3. Feb 2019
  4. Dec 2018
    1. Amazon isn’t just an online retailer. It’s infrastructure.

      Another point to make is how Amazon's "other" business, Amazon Web Services (AWS) provides a wide array of widely used web infrastructure. AWS commercial infrastructure (among others) increasingly provides the digital infrastructure used by both public and private systems.

  5. Nov 2018
  6. Jul 2018
  7. May 2018
  8. Jan 2018
  9. Nov 2017
    1. Lambda@Edge lets you run Lambda functions at AWS Regions and Amazon CloudFront edge locations in response to CloudFront events

      Extremely happy to see such an amazing opportunity which I think will help create fined grain API's which are fast and can leverage Caching strategies which will be cheap.

  10. Oct 2017
  11. Sep 2017
  12. Jul 2017
  13. Jun 2017
  14. May 2017
  15. Mar 2017
  16. Dec 2016
    1. Amazon SQS can help you build a distributed application with decoupled components, working closely with the Amazon Elastic Compute Cloud (Amazon EC2) and other AWS infrastructure web services.

      Instâncias EC2 produtoras colocam mensagens em uma fila SQS p/ serem consumidas por instâncias EC2 consumidoras.

    2. With Amazon SQS, you can move data between diverse, distributed application components without losing messages and without requiring each component to be always available.

      Permite desacoplar componentes da aplicação. Acho que pode ser acessado por aplicações fora da infra do AWS

    3. Amazon SQS offers a reliable, highly-scalable, hosted queue for storing messages in transit between computers

      Serviço gerenciado com auto scaling automático e redundância. Usa polling para acesso às msg da fila.

  17. May 2016
    1. To set an environment variable The following command sets the value of the "PARAM1" variable in the "my-env" environment to "ParamValue": aws elasticbeanstalk update-environment --environment-name my-env --option-settings Namespace=aws:elasticbeanstalk:application:environment,OptionName=PARAM1,Value=ParamValue The option-settings parameter takes a namespace in addition to the name and value of the variable. Elastic Beanstalk supports several namespaces for options in addition to environment variables.

      Glad to find this invocation, the analog to eb setenv

  18. Jan 2016
    1. Amazon EC2 Spot instances allow you to bid on spare Amazon EC2 computing capacity. Since Spot instances are often available at a discount compared to On-Demand pricing, you can significantly reduce the cost of running your applications, grow your application’s compute capacity and throughput for the same budget, and enable new types of cloud computing applications.

      Saving money using Amazon EC2 Spot Instances to execute Elastic MapReduce job flows

  19. Mar 2015