DOCSLIB.ORG

AWS Managed Services (AMS)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
AWS Managed Services (AMS) AWS Managed Services (AMS) Application Developer's Guide AMS Advanced Operations Plan Version September 16, 2020 AWS Managed Services (AMS) Application Developer's Guide AMS Advanced Operations Plan AWS Managed Services (AMS) Application Developer's Guide: AMS Advanced Operations Plan Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. AWS Managed Services (AMS) Application Developer's Guide AMS Advanced Operations Plan Table of Contents Application Onboarding to AMS Introduction ........................................................................................ 1 What is Application Onboarding? ................................................................................................. 1 What we do, what we do not do .................................................................................................. 1 AMS Amazon Machine Images (AMIs) ............................................................................................ 2 Security enhanced AMIs ...................................................................................................... 4 Key terms .................................................................................................................................. 4 What is My Operating Model? ...................................................................................................... 8 AMS service management ................................................................................................................... 9 Account governance ................................................................................................................... 9 Service commencement .............................................................................................................. 9 AMS customer relationship management (CRM) ........................................................................... 10 CRM Process .................................................................................................................... 10 CRM meetings .................................................................................................................. 11 CRM Meeting Arrangements .............................................................................................. 12 CRM monthly reports ........................................................................................................ 12 Updates to shared services: Multi-Account Landing Zone ............................................................... 13 AMS planned event management ............................................................................................... 13 AMS PEM criteria .............................................................................................................. 13 The AMS PEM process ....................................................................................................... 13 Getting help ............................................................................................................................ 14 Service hours ........................................................................................................................... 14 How do I get offboard assistance from AMS Single-Account Landing Zone accounts? ......................... 15 How do I offboard from AMS Multi-Account Landing Zone accounts? .............................................. 15 How do I offboard a Multi-Account Landing Zone environment? ............................................. 16 How do I offboard a Multi-Account Landing Zone application account? .................................... 16 How do I offboard a Multi-Account Landing Zone application account VPC? .............................. 17 Application Development .................................................................................................................. 18 Being Well Architected .............................................................................................................. 18 Application Layer Responsibilities vs Infrastructure Layer Responsibilities ......................................... 19 EC2 Instance Mutability ............................................................................................................. 19 Using AWS Secrets Manager with AMS Resources ......................................................................... 20 Application Deployment .................................................................................................................... 21 Application Deployment Capabilities ........................................................................................... 21 Planning Your Application Deployment ....................................................................................... 23 AMS Workload Ingest (WIGS) ..................................................................................................... 23 Migrating Workloads: Prerequisites for Linux and Windows .................................................... 24 How Migration Changes Your Resource ............................................................................... 26 Migrating Workloads: Standard Process ............................................................................... 27 Migrating Workloads: CloudEndure Landing Zone (SALZ) ....................................................... 28 Tools account, Migrating Workloads: CloudEndure Landing Zone (MALZ) .................................. 30 Migrating workloads: Linux pre-ingestion validation .............................................................. 35 Migrating workloads: Windows pre-ingestion validation ........................................................ 36 Workload Ingest Stack: Creating ......................................................................................... 37 AMS CloudFormation ingest ...................................................................................................... 40 AWS CloudFormation Ingest Guidelines, Best Practices, and Limitations ................................... 41 AWS CloudFormation Ingest: Examples ............................................................................... 54 Create CloudFormation ingest stack .................................................................................... 59 Update AWS CloudFormation ingest stack ........................................................................... 63 Approve a CloudFormation ingest stack changeset ............................................................... 67 Update AWS CloudFormation stacks termination protection ................................................... 69 CodeDeploy requests ................................................................................................................ 72 Create CodeDeploy application .......................................................................................... 72 Create CodeDeploy deployment group ................................................................................ 74 Create CodeDeploy deployment group for EC2 ..................................................................... 77 Version September 16, 2020 iii AWS Managed Services (AMS) Application Developer's Guide AMS Advanced Operations Plan Deploy CodeDeploy application .......................................................................................... 80 Database Migration Service (DMS) .............................................................................................. 83 Database Migration Service (DMS), Planning ........................................................................ 83 DMS Setup, All Tasks ........................................................................................................ 84 Create DMS replication subnet group .................................................................................. 84 2: Create DMS replication instance ..................................................................................... 87 3: DMS Source Endpoint: Create, Create for Mongo DB, Create for S3 ...................................... 90 4: DMS Target Endpoint: Create, Create for S3 ................................................................... 100 5: Create DMS replication task ......................................................................................... 106 Start DMS replication task ............................................................................................... 109 Stop DMS replication task ............................................................................................... 111 Database (DB) Import to AMS SQL RDS ..................................................................................... 114 Setting Up ..................................................................................................................... 114 Importing the Database .................................................................................................. 115 Cleanup ........................................................................................................................
Load more

Recommended publications
  • (AWS) Security Workshop - Pre-Read Material
    Amazon Web Services (AWS) Security Workshop - Pre-read material It is highly recommended to go through the pre-read before attending the AWS Security workshop. Shared Responsibility Model Security and Compliance is a shared responsibility between AWS and the customer. This shared model can help relieve the customer’s operational burden as AWS operates, manages and controls the components from the host operating system and virtualization layer down to the physical security of the facilities in which the service operates. The customer assumes responsibility and management of the guest operating system (including updates and security patches), other associated application software as well as the configuration of the AWS provided security group firewall. Customers should carefully consider the services they choose as their responsibilities vary depending on the services used, the integration of those services into their IT environment, and applicable laws and regulations. The nature of this shared responsibility also provides the flexibility and customer control that permits the deployment. As shown in the chart below, this differentiation of responsibility is commonly referred to as Security “of” the Cloud versus Security “in” the Cloud. AWS responsibility “Security of the Cloud” - AWS is responsible for protecting the infrastructure that runs all of the services offered in the AWS Cloud. This infrastructure is composed of the hardware, software, networking, and facilities that run AWS Cloud services. Customer responsibility “Security in the Cloud” – Customer responsibility will be determined by the AWS Cloud services that a customer selects. This determines the amount of configuration work the customer must perform as part of their security responsibilities.
    [Show full text]
  • Commvault on AWS Comprehensive Cloud Data Management for Hybrid IT Table of Contents
    Commvault on AWS Comprehensive Cloud Data Management for Hybrid IT Table of Contents The Data Management Challenge 3 Commvault and Amazon Web Services 4 Benefits 7 Case Study: Dow Jones 8 Getting Started 9 2 The Data Management Challenge Today, more data is being generated than ever before. Keeping up with the rapid pace of data growth presents a series of challenges. Enterprise organizations are collecting petabytes of customer and application data that must be backed up and accessible to meet compliance requirements. Increased regulation around data retention policies make it more difficult to manage backup and archive storage, as critical data may be required to be kept for years and maybe difficult to find. Further complicating matters, point solutions often overlap and leave gaps where data is unprotected and require additional staff to manage them. These issues lead to increased costs, yet many IT departments are facing budget cuts and cannot expand upon their capital to meet increased performance demands. Today’s hybrid IT organizations realize cloud can help solve many data storage issues. With cloud storage comes the need for a comprehensive data management platform to manage data both on-premises and in the cloud. Savvy organizations streamline IT operations and reduce cloud waste with flexible orchestration to automate resource provisioning, policies and routine tasks. This eBook will demonstrate how Commvault and Amazon Web Services (AWS) deliver a cost-effective data management solution that addresses all of these challenges with a single, scalable solution. 3 Commvault and Amazon Web Services Unlike most backup and recovery solutions, Commvault offers a single data platform solution for all backup and recovery needs; as opposed to having to several point solutions for each use case (i.e.
    [Show full text]
  • Performance Efficiency Pillar
    Performance Efficiency Pillar AWS Well-Architected Framework Performance Efficiency Pillar AWS Well-Architected Framework Performance Efficiency Pillar: AWS Well-Architected Framework Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Performance Efficiency Pillar AWS Well-Architected Framework Table of Contents Abstract and Introduction ................................................................................................................... 1 Abstract .................................................................................................................................... 1 Introduction .............................................................................................................................. 1 Performance Efficiency ....................................................................................................................... 2 Design Principles ........................................................................................................................ 2 Definition .................................................................................................................................
    [Show full text]
  • Amazon Documentdb Deep Dive
    DAT326 Amazon DocumentDB deep dive Joseph Idziorek Antra Grover Principal Product Manager Software Development Engineer Amazon Web Services Fulfillment By Amazon © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Agenda What is the purpose of a document database? What customer problems does Amazon DocumentDB (with MongoDB compatibility) solve and how? Customer use case and learnings: Fulfillment by Amazon What did we deliver for customers this year? What’s next? © 2019, Amazon Web Services, Inc. or its affiliates. All rights reserved. Purpose-built databases Relational Key value Document In-memory Graph Search Time series Ledger Why document databases? Denormalized data Normalized data model model { 'name': 'Bat City Gelato', 'price': '$', 'rating': 5.0, 'review_count': 46, 'categories': ['gelato', 'ice cream'], 'location': { 'address': '6301 W Parmer Ln', 'city': 'Austin', 'country': 'US', 'state': 'TX', 'zip_code': '78729'} } Why document databases? GET https://api.yelp.com/v3/businesses/{id} { 'name': 'Bat City Gelato', 'price': '$', 'rating': 5.0, 'review_count': 46, 'categories': ['gelato', 'ice cream'], 'location': { 'address': '6301 W Parmer Ln', 'city': 'Austin', 'country': 'US', 'state': 'TX', 'zip_code': '78729'} } Why document databases? response = yelp_api.search_query(term='ice cream', location='austin, tx', sort_by='rating', limit=5) Why document databases? for i in response['businesses']: col.insert_one(i) db.businesses.aggregate([ { $group: { _id: "$price", ratingAvg: { $avg: "$rating"}} } ]) db.businesses.find({
    [Show full text]
  • Database Software Market: Billy Fitzsimmons +1 312 364 5112
    Equity Research Technology, Media, & Communications | Enterprise and Cloud Infrastructure March 22, 2019 Industry Report Jason Ader +1 617 235 7519 [email protected] Database Software Market: Billy Fitzsimmons +1 312 364 5112 The Long-Awaited Shake-up [email protected] Naji +1 212 245 6508 [email protected] Please refer to important disclosures on pages 70 and 71. Analyst certification is on page 70. William Blair or an affiliate does and seeks to do business with companies covered in its research reports. As a result, investors should be aware that the firm may have a conflict of interest that could affect the objectivity of this report. This report is not intended to provide personal investment advice. The opinions and recommendations here- in do not take into account individual client circumstances, objectives, or needs and are not intended as recommen- dations of particular securities, financial instruments, or strategies to particular clients. The recipient of this report must make its own independent decisions regarding any securities or financial instruments mentioned herein. William Blair Contents Key Findings ......................................................................................................................3 Introduction .......................................................................................................................5 Database Market History ...................................................................................................7 Market Definitions
    [Show full text]
  • Migrating to Google Cloud Storage Nearline from Amazon Glacier
    Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Migrating to Google Cloud Storage Nearline From Amazon Glacier Page 1 Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Migrating to Google Cloud Storage Nearline From Amazon Glacier Table of contents: Summary Overview Prerequisites Create a Workspace and Staging Area Create a Bucket Using the Nearline Storage Class Choose a Naming Convention Begin Storing New Data in Cloud Storage Nearline Migrating Data Stored Directly in Amazon Glacier Get an Inventory of Archives Make an Archive Available for Download Download the Archive to a Staging Area Upload Data to Cloud Storage Nearline Migrating in Batches Migrating Data Stored in Amazon Glacier via Amazon S3 Get an Inventory of Archives Make an Archive Available for Download Upload Data to Cloud Storage Nearline Migrating in Batches Understanding the Cost of Retrieving Data from Amazon Glacier Recommendations Appendix A: Creating a Workspace and Staging Area Create or Select a Cloud Platform Project Install and Configure the Cloud SDK Create and Configure a Compute Engine Instance References Page 2 Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Page 3 Migrating to Google Cloud PAUL NEWSON | 07/23/15 Storage Nearline ​ Summary Google Cloud Storage Nearline is a low cost storage class available in Google Cloud Storage which is attractive for archival workloads, such as cold storage and disaster recovery. Amazon Glacier also provides a storage service suitable for archival workloads, but retrieval latency in Amazon Glacier is measured in hours whereas Google Cloud Storage Nearline provides retrieval latency measured in seconds.
    [Show full text]
  • Planning and Designing Databases on AWS (AWS-PD-DB)
    Planning and Designing Databases on AWS (AWS-PD-DB) COURSE OVERVIEW: In this course, you will learn about the process of planning and designing both relational and nonrelational databases. You will learn the design considerations for hosting databases on Amazon Elastic Compute Cloud (Amazon EC2). You will learn about our relational database services including Amazon Relational Database Service (Amazon RDS), Amazon Aurora, and Amazon Redshift. You will also learn about our nonrelational database services including Amazon DocumentDB, Amazon DynamoDB, Amazon ElastiCache, Amazon Neptune, and Amazon QLDB. By the end of this course, you will be familiar with the planning and design requirements of all 8 of these AWS databases services, their pros and cons, and how to know which AWS databases service is right for your workloads. WHO WILL BENEFIT FROM THIS COURSE? • Data platform engineers • Database administrators • Solutions architects • IT professionals PREREQUISITES: We recommend that attendees of this course have previously completed the following AWS courses: • AWS Database Offerings digital training • Data Analytics Fundamentals digital training • Architecting on AWS classroom training COURSE OBJECTIVES: After completion of this course, students will be able to... • Apply database concepts, database management, and data modeling techniques • Evaluate hosting databases on Amazon EC2 instances • Evaluate relational database services (Amazon RDS, Amazon Aurora, and Amazon Redshift) and their features • Evaluate nonrelational database services
    [Show full text]
  • Amazon Mechanical Turk Requester UI Guide Amazon Mechanical Turk Requester UI Guide
    Amazon Mechanical Turk Requester UI Guide Amazon Mechanical Turk Requester UI Guide Amazon Mechanical Turk: Requester UI Guide Copyright © 2014 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. The following are trademarks of Amazon Web Services, Inc.: Amazon, Amazon Web Services Design, AWS, Amazon CloudFront, Cloudfront, Amazon DevPay, DynamoDB, ElastiCache, Amazon EC2, Amazon Elastic Compute Cloud, Amazon Glacier, Kindle, Kindle Fire, AWS Marketplace Design, Mechanical Turk, Amazon Redshift, Amazon Route 53, Amazon S3, Amazon VPC. In addition, Amazon.com graphics, logos, page headers, button icons, scripts, and service names are trademarks, or trade dress of Amazon in the U.S. and/or other countries. Amazon©s trademarks and trade dress may not be used in connection with any product or service that is not Amazon©s, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Amazon Mechanical Turk Requester UI Guide Table of Contents Welcome ..................................................................................................................................... 1 How Do I...? ......................................................................................................................... 1 Introduction to Mechanical Turk .......................................................................................................
    [Show full text]
  • All Services Compute Developer Tools Machine Learning Mobile
    AlL services X-Ray Storage Gateway Compute Rekognition d Satellite Developer Tools Amazon Sumerian Athena Machine Learning Elastic Beanstalk AWS Backup Mobile Amazon Transcribe Ground Station EC2 Servertess Application EMR Repository Codestar CloudSearch Robotics Amazon SageMaker Customer Engagement Amazon Transtate AWS Amplify Amazon Connect Application Integration Lightsail Database AWS RoboMaker CodeCommit Management & Governance Amazon Personalize Amazon Comprehend Elasticsearch Service Storage Mobile Hub RDS Amazon Forecast ECR AWS Organizations Step Functions CodeBuild Kinesis Amazon EventBridge AWS Deeplens Pinpoint S3 AWS AppSync DynamoDe Amazon Textract ECS CloudWatch Blockchain CodeDeploy Quicksight EFS Amazon Lex Simple Email Service AWS DeepRacer Device Farm ElastiCache Amazont EKS AWS Auto Scaling Amazon Managed Blockchain CodePipeline Data Pipeline Simple Notification Service Machine Learning Neptune FSx Lambda CloudFormation Analytics Cloud9 AWS Glue Simple Queue Service Amazon Polly Business Applications $3 Glacer AR & VR Amazon Redshift SWF Batch CloudTrail AWS Lake Formation Server Migration Service lot Device Defender Alexa for Business GuardDuty MediaConnect Amazon QLDB WorkLink WAF & Shield Config AWS Well. Architected Tool Route 53 MSK AWS Transfer for SFTP Artifact Amazon Chime Inspector lot Device Management Amazon DocumentDB Personal Health Dashboard C MediaConvert OpsWorks Snowball API Gateway WorkMait Amazon Macie MediaLive Service Catalog AWS Chatbot Security Hub Security, Identity, & Internet of Things loT
    [Show full text]
  • Enter the Purpose-Built Database Era: Finding the Right Database Type for the Right Job
    Enter the Purpose-Built Database Era: Finding the right database type for the right job 1 INTRODUCTION Stepping into the purpose-built era Data is a strategic asset for every organization. As data continues to exponentially grow, databases are becoming increasingly crucial to understanding data and converting it to valuable insights. IT leaders need to look for ways to get more value from their data. If you’re running legacy databases on-premises, you’re likely finding that provisioning, operating, scaling, and managing databases is tedious, time-consuming, and expensive. You need modernized database solutions that allow you to spend time innovating and building new applications—not managing infrastructure. Moving on-premises data to managed databases built for the cloud can help you reduce time and costs. Once your databases are in the cloud, you can innovate and build new applications faster—all while getting deeper and more valuable insights. Migrating to the cloud is the first step toward entering the era of purpose-built databases. But once in the cloud, how do you know which types of databases to use for which functions? Read on to learn more about purpose-built database types—and how you can ensure a smooth transition into an era of innovation, performance, and business success. 2 WHY CHANGE? Going beyond relational only Before we begin discussing purpose-built databases, let’s examine the status quo—using relational databases for just about every use case. Relational databases were designed for tabular data with consistent structure and fixed schema. They work for problems that are well defined at the onset.
    [Show full text]
  • Using Amazon Web Services for Disaster Recovery October 2014
    Amazon Web Services – Using AWS for Disaster Recovery October 2014 Using Amazon Web Services for Disaster Recovery October 2014 Glen Robinson, Attila Narin, and Chris Elleman Page 1 of 22 Amazon Web Services – Using AWS for Disaster Recovery October 2014 Contents Introduction ...............................................................................................................................................................3 Recovery Time Objective and Recovery Point Objective ................................................................................................4 Traditional DR Investment Practices ............................................................................................................................4 AWS Services and Features Essential for Disaster Recovery ...........................................................................................5 Example Disaster Recovery Scenarios with AWS ...........................................................................................................9 Backup and Restore ................................................................................................................................................9 Pilot Light for Quick Recovery into AWS ................................................................................................................. 11 Warm Standby Solution in AWS ............................................................................................................................. 14 Multi-Site Solution Deployed
    [Show full text]
  • Amazon.SAP-C01.V2020-12-07.Q125
    Amazon.SAP-C01.v2020-12-07.q125 Exam Code: SAP-C01 Exam Name: AWS Certified Solutions Architect - Professional Certification Provider: Amazon Free Question Number: 125 Version: v2020-12-07 # of views: 109 # of Questions views: 1253 https://www.freecram.com/torrent/Amazon.SAP-C01.v2020-12-07.q125.html NEW QUESTION: 1 A company has a 24 TB MySQL database in its on-premises data center that grows at the rate of 10 GB per day. The data center is connected to the company's AWS infrastructure with a 50 Mbps VPN connection. The company is migrating the application and workload to AWS. The application code is already installed and tested on Amazon EC2. The company now needs to migrate the database and wants to go live on AWS within 3 weeks. Which of the following approaches meets the schedule with LEAST downtime? A. 1. Take the on-premises application offline.2. Create a database export locally using database-native tools.3. Import that into AWS using AWS Snowball.4. Launch an Amazon RDS Aurora DB instance.5. Load the data in the RDS Aurora DB instance from the export.6. Change the DNS entry to point to the Amazon RDS Aurora DB instance.7. Put the Amazon EC2 hosted application online. B. 1. Create a database export locally using database-native tools.2. Import that into AWS using AWS Snowball.3. Launch an Amazon RDS Aurora DB instance.4. Load the data in the RDS Aurora DB instance from the export.5. Set up database replication from the on-premises database to the RDS Aurora DB instance over the VPN.6.
    [Show full text]