Sascha Möllering gave a presentation on deploying applications to the AWS cloud. He began with an overview of AWS services like EC2, S3, RDS and explained how to initially create a simple cloud service with one instance each for a web application and database. He then described how to improve the architecture by separating components, adding redundancy and elasticity using services like ELB, autoscaling and read replicas. Sascha demonstrated deploying a sample application built with JHipster and Docker to AWS Elastic Beanstalk, which handles running the containers and mapping environment variables for the database connection.
Talk at JAWS DAYS '17 at Tokyo as the organizer to AWS User Group Taiwan. Covers Guanyu and kms-local a bit, both internal projects at 104 Corp. that will be opensourced.
Presentation given to NashJS (http://meetup.com/nashjs) on 6/14/2018 about serverless architecture in AWS using the Serverless framework (http://serverless.com).
Kumar Ashwin gives a presentation on securing containers from day one. The presentation covers what containers are, why we need them, the difference between virtual machines and containers, cgroups and namespaces, Docker basics, building optimized Docker images, and best practices for Dockerfile security. Some key points discussed include using minimal base images, ignoring unnecessary files, creating "golden images" as hardened base templates, not running as root, avoiding secrets in Dockerfiles, and using tools like Hadolint and Dockle to scan for issues.
This document provides an overview of Stacktician, which is a tool that allows users to deploy and manage infrastructure on CloudStack using templates similar to AWS CloudFormation. It discusses the history and architecture of Stacktician, including its two main components - StackMate for executing templates and Stacktician for the web interface. It covers the current state including improvements made for error handling, rollbacks, metadata handling and scaling. Finally, it discusses some planned future enhancements such as better plugin support, nested stacks, and stack updates.
In this session we'll discuss and demonstrate key concepts and design patterns for continuous deployment and integration using technologies like AWS OpsWorks and Chef to enable better control of applications and infrastructures.
It's the architect session on AWSome Day to introduce the cloud principles which you need to follow when developing cloud services.
This document summarizes serverless design patterns and tools. It begins with a brief history of cloud computing and an introduction to serverless computing. Common serverless use cases like event-driven applications and stream processing are described. Several serverless patterns are then outlined, such as hosting a static website or REST API using AWS Lambda and API Gateway. Finally, the document demonstrates a serverless application and discusses future directions for serverless technologies.
This document discusses plans to improve the Apache CloudStack project. It outlines proposals to clean up code, infrastructure, documentation and the ecosystem. Specific areas of focus include removing unused code, improving testing, consolidating documentation, and defining a catalog of common cluster configurations. The document also proposes an engineering roadmap to address upgrades, logging, storage, networking, the UI/API and QA. The goal is to modernize the architecture through better abstraction layers and make CloudStack more configurable, composable and developer-friendly.
This document summarizes a presentation about using Amazon ECS and Spot Instances at scale. It discusses the challenges of managing many EC2 instances for microservices and how ECS provides a fully managed container service with auto scaling and cost optimization using Spot Instances. Benefits of ECS include fully managed instances and containers, self-healing, auto scaling, and focus on code instead of infrastructure. ECS is preferable for CPU-bound tasks, long running processes, and internal microservices, while serverless is better for short tasks with limited resources and external APIs. ECS and serverless can also be combined for queue workers and async tasks.
The document discusses deployment best practices and introduces goployer, an open source deployment tool. It summarizes key aspects of infrastructure as code and modern deployment approaches like blue/green and canary deployments. Goployer supports immutable infrastructure, deployment as code, measurement and testing to enable cost effective and simple deployments. The DevOps Art project aims to share infrastructure code, develop open source tools like Terraform and goployer, and conduct online workshops to foster a proper conceptual understanding of DevOps philosophy and ideal implementations based on that philosophy.
Amazon Web Services offers cloud website hosting solutions that provides businesses, non-profits, and governmental organizations with a flexible, highly scalable, and low-cost way to deliver their websites and web applications. Our agenda is "How to deploy a dynamic website using Amazon Web Services". We will discuss some special services on amazon that is AWS Elastic Cloud Compute (EC2), Relational Database Service (RDS), Elastic Load Balancing (ELB), Route 53 (R53).
Tired of having users email you that your Svelte application is broken? Turns out that building reliable applications is hard and requires a lot of testing. You can write unit tests but quite often these all pass and the application is still broken. Why? Because they test parts of the application in isolation. But for a reliable application we need more. We need to make sure that all parts, including the backend API’s, work together as intended. Cypress is a great tool to achieve this. It will test you complete web application in the browser and use it like a real world user would. In this session Maurice will show you how to use Cypress during development and on the CI server with Svelte. He will share tips and tricks to make your tests more resilient and more like how an actual end user would behave.
This document summarizes a presentation about best practices for AWS ECS and serverless architectures. It discusses the challenges of traditional infrastructures and benefits of containerization. It provides an overview of AWS ECS for container management and auto-scaling capabilities. It also introduces AWS Lambda and API Gateway for building serverless applications, including their advantages of being cloud-native and cost-effective with minimal infrastructure to manage. Some limitations of serverless architectures are also outlined. The conclusion encourages embracing immutable infrastructure, event-driven computing, and focusing on business logic over infrastructure when possible.
Amazon Web Services (AWS) provides Elastic Load Balancing to automatically distribute incoming web traffic across multiple Amazon Elastic Compute Cloud (Amazon EC2) instances. With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task.
"Microservices" is one of the hottest buzzwords and, as usual, everyone wants them, but few know how to build them. In this talk we will offer our interpretation of microservice architecture, and show how we are implementing these ideas: using Scala, Akka, sbt and Docker, we modularized Akka applications, Spark jobs and Play servers. In the talk we will discuss design trade-offs and challenges that we faced in the process, and how we have overcome them. The focus is not on particular features of Scala language or a library, but on building modern applications using the Typesafe stack and other open-source tools.
This document discusses how Docker can be used with CloudStack. It provides several options: 1) Running Docker in VMs on CloudStack templates that include Docker, 2) Using Docker-optimized OS templates, 3) Launching containers through a container service API, 4) Using CloudStack plugins within the Docker ecosystem like Docker Machine. The document concludes that CloudStack should not try to write a Docker hypervisor plugin, but instead focus on Docker-optimized OS templates and deploying application frameworks to orchestrate Docker.
In deploying apps that have been containerized, you have a lot to think about regarding what to use in production. There are a lot of things to manage, so orchestrators become a huge help. providing many services together such as scheduling, container communication, scaling, health, and more. There are major platforms to consider from Kubernetes, Swarm to ECS. In this talk we'll go through the overview of orchestrators and some of the differences between the big players. You should come out of the talk knowing where to go next in determining your orchestrator needs.
Nach wochenlanger Arbeit und nervenaufreibendem Approval-Prozess ist die Killer-App jetzt endlich im Store gelandet. Und jetzt? Die Downloadzahlen sind deutlich unter den Erwartungen, und etwas muss getan werden! In diesem Talk wird dargestellt, welche Möglichkeiten der Bewerbung existieren und welche Fallstricke es auf den unterschiedlichen Plattformen zu umschiffen gilt.
This document discusses infrastructure as code. It describes using VMware and SDKs like VMware vSphere and VI Java SDK to programmatically manage virtual machines. It also discusses using Chef to automate the installation of Linux, packages, and middleware like JBoss. The document provides examples of using Chef to configure JBoss and links to GitHub repositories for VIAutomator and autoimport samples. It concludes with a Q&A section.
This document provides an overview of cloud architecture and best practices for deploying applications in the AWS cloud. It begins with an introduction to key AWS services like EC2, ELB, RDS, and Auto Scaling. It then walks through creating a basic cloud deployment and improving it by separating concerns, adding redundancy, caching, and autoscaling. Finally, it discusses a real-world example using services like Kinesis and deploying containers with ECS.
This document discusses using Docker containers in the cloud. It begins with an introduction to Docker and Amazon Web Services (AWS). It then covers deploying Docker containers to AWS using services like OpsWorks, Elastic Beanstalk, and EC2 Container Service. It also discusses the immutable server pattern and using EC2 Container Service to manage Docker containers on EC2 instances.
This document discusses deploying Docker containers on Amazon Web Services. It covers using AWS services like EC2, OpsWorks and Elastic Beanstalk that support Docker. It describes using the EC2 Container Service for container management and deploying containers across a cluster of EC2 instances. It also discusses the immutable server pattern of deploying to new infrastructure with each release rather than changing existing servers.
This document provides an overview of using the Vert.x reactive application platform at the European advertising network zanox. It discusses how zanox used Vert.x to build a new core system requiring low latency and high throughput. The document covers getting started with Vert.x, best practices like encapsulating common code in modules, deployment strategies including fat jars and Docker, and integrating Vert.x with messaging systems like Apache Kafka using available modules. Metrics showed the Vert.x system at zanox could handle 18,000-28,000 requests per second on average with response times under 2ms.
This document discusses using Docker on AWS. It describes using Docker to deploy highly scalable applications across multiple AWS regions and availability zones. It also discusses using a private Docker registry hosted on EC2 and S3 to store custom Docker images. Finally, it summarizes using Amazon EC2 Container Service (ECS) for container management on AWS, including concepts like clusters, tasks, and container instances.
Lift Urban Entrepreneurs is designed to create an urban transversal vision through a series of events bringing together entrepreneurs, designers, developers, academics and corporates to explore new solutions to address these urban challenges. The mission is to foster new ideas in order to co-create, prototype and produce solutions for a better urban future. This is the storyboard of the Seoul Workshop held on Nov. 12, 2016 at Google Campus Seoul. http://www.urbanentrepreneurs.io
This document discusses Vert.x, an open source toolkit for building reactive applications on the JVM. It introduces Vert.x and describes how it was used at Zanox to build a new request processing system with requirements of low latency, high throughput, scalability, resilience, and responsiveness. The document outlines how to start with Vert.x, best practices, using the infrastructure as code and module system, integrating Kafka messaging, and metrics from Zanox's Vert.x project.
This document provides steps to integrate Jenkins with Amazon S3 for artifact storage. It demonstrates installing the Jenkins S3 plugin, configuring credentials for an IAM user with S3 access, and configuring a Jenkins job to upload build artifacts like an index.html file to an S3 bucket after a build. With this integration, artifacts can be reliably stored on S3, which is cheaper for storage than other options and allows easy tracking and management of files.
Sascha Möllering discusses infrastructure as code and provides an overview of VMware SDKs, Chef, and using Chef to configure JBoss middleware. He explains that VMware has multiple SDKs and that the VI Java SDK simplifies development. Chef is introduced as a tool to automate and standardize server configurations. The presentation then covers using Chef recipes to deploy and configure JBoss application servers and integrating with JBoss Operations Network for monitoring.
Sascha Möllering discusses how his company moved from manual server setup and deployment to automated deployments using infrastructure as code and continuous delivery. They now deploy whenever needed using tools like Chef and JBoss to configure servers. Previously they faced challenges like manual processes, difficult rollbacks, and biweekly deployment windows. Now deployments are automated, safer, and can happen continuously.
This document discusses scaling applications in the AWS cloud. It begins with an overview of AWS services like EC2, S3, RDS, and ELB. It then walks through creating a simple cloud application and database, and improving it by separating components, adding redundancy, caching, and autoscaling. A real-world example is shown using Vert.x, Kinesis, Docker, and deployment scripts to dynamically scale a streaming data application across Availability Zones.
This document discusses microservices architecture and how it enables agility. It defines microservices as small, independent units that can be developed and deployed autonomously. The document argues that microservices align with the principles of the Agile Manifesto by allowing teams to work independently, facilitating continuous delivery, and making the architecture adaptable to change. Some benefits outlined are improved scalability, maintainability, and ability to replace services easily. The conclusion is that by structuring an organization and software architecture around microservices, greater agility can be achieved compared to a monolithic architecture.
This document provides an overview of CloudFormation best practices: - It discusses organizing infrastructure using CloudFormation stacks by layers, environments, and services to promote reuse and decoupling. - It recommends starting with existing templates, validation tools, parameter types, and IAM roles to prevent errors. - Debugging tips include viewing stack events, using wait conditions, and logging to CloudWatch. - Safe stack updates involve change sets to review impacts and choosing update styles for minimal disruption.
Learn about new and existing Amazon S3 features that can help you better protect your data, save on cost, and improve usability, security, and performance. We will cover a wide variety of Amazon S3 features and go into depth on several newer features with configuration and code snippets, so you can apply the learnings on to your object storage workloads. Learning Objectives: • Review best practices for to reduce costs, protect against data loss, and increase performance in Amazon S3 • Learn about new S3 storage management features that help you align storage with business needs • Understand data security capabilities available in S3 that help protect against malicious or accidental deletion or other data loss
The document provides information about a webinar on getting started with AWS, including deploying a static website. It outlines the agenda which includes: watching a 15 minute presentation on AWS; watching a 25 minute demo of deploying a static website; and having 45-60 minutes to complete the demo independently. It then details the various sections of the webinar which cover creating an AWS account, enabling security features, using S3 buckets to host the website, configuring permissions, associating a domain name, and using CloudFront for acceleration.
Amazon EC2 Systems Manager provides capabilities that enable automated configuration and ongoing management of systems at scale across Windows and Linux workloads running in Amazon EC2 or on-premises at no additional charge. It offers components like Run Command, State Manager, Inventory, Maintenance Windows, Patch Manager, Automation, and Parameter Store to remotely manage servers, define consistent configurations, gather inventory, schedule maintenance windows, automate patching, simplify deployments, and securely store parameters. Using these capabilities is expected to reduce the total cost of ownership for hybrid and cloud environments compared to traditional management tools.
To help prevent unexpected access to your AWS resources, it is critical to maintain strong identity and access policies. It is equally important to track and alert on changes to your AWS resources. In this tech talk, you will learn how to use AWS Identity and Access Management (IAM) to control access to your AWS resources and integrate your existing authentication system with AWS IAM. We will cover how you can deploy and control your AWS infrastructure using code templates, including change management policies with AWS CloudFormation. In addition, we will explore different options for managing both your AWS access logs and your Amazon Elastic Compute Cloud (EC2) system logs using Amazon CloudWatch Logs. We also will cover how to use these logs to implement an audit and compliance validation process using services such as AWS Config, AWS CloudTrail, and Amazon Inspector. Learning Objectives: • Understand the AWS Shared Responsibility Model. • Understand AWS account and identity management options and configuration. • Learn the concept of infrastructure as code and change management using AWS CloudFormation. • Learn how to audit and log your AWS service usage. • Learn about AWS services to add automatic compliance checks to your AWS infrastructure.
An overview of running Oracle Database, Fusion Middleware and Oracle Applications on AWS. Covers licensing, pricing, support, security, networking, Amazon VPC, Amazon EC2, Amazon EBS, use cases, and customer successes.
AWS Summit 2014 Brisbane - Breakout 6 Technical deep dive in to 10 AWS Cloud best practices with in-depth look at the tips and tricks of architecting on the AWS platform. Presenter: Dean Samuels, Solutions Architect, Amazon Web Services
This document introduces core concepts of AWS through a sample standard web architecture. It discusses what AWS is, how and why Amazon launched it, and provides examples of key AWS services like VPC, EC2, EBS, ELB, and managed services. It also covers AWS architecture concepts like regions, availability zones, and infrastructure as code.
This document discusses auto-scaling in the cloud and provides a case study on MediaHub, a media sharing application. It describes MediaHub's architecture, which uses various AWS services like EC2, RDS, S3, CloudFront, and Elastic Beanstalk. It then provides best practices for developing applications in the cloud, such as automating infrastructure, controlling permissions, automating configuration, and designing for redundancy and parallelism. The document concludes that the cloud is not suitable for all applications and that applications must be designed for cloud-scale to reduce costs.
This document summarizes a 60-minute talk on AWS compute technologies including EC2, ECS, Lambda, and Elastic Beanstalk. The talk provides an introduction to each service, demos of launching EC2 instances, deploying apps with Elastic Beanstalk and ECS, and implementing APIs with Lambda. It also lists upcoming user group events and a new book on AWS Lambda.
Introduction to DevOps on AWS. Basic introduction to Devops principles and practices, and how they can be implemented on AWS. Introduces basic cloudformation.
An overview of the Application Lifecycle Management (ALM) tooling and processes on the Amazon Web Services (AWS) platform
Amazon Web Services (AWS) offers IT infrastructure services to businesses in the form of web services - now commonly known as cloud computing. AWS is an ideal platform to develop on and host enterprise Java applications, due to the zero up front costs and virtually infinite scalability of resources. Learn basic AWS concepts and work with many of the available services. Gain an understanding of how existing JavaEE applications can be migrated to the AWS environment and what the advantages are. Discover how to architect a new JavaEE application from the ground up to leverage the AWS environment for maximum benefit.