Summary of AWS blogs for the week of Mon Oct 02
In the week of Mon Oct 02 2023 AWS published 103 blog posts – here is an overview of what happened.
Topics Covered
- Desktop and Application Streaming
- AWS DevOps Blog
- AWS for SAP
- Official Machine Learning Blog of AWS
- Announcements, Updates, and Launches
- Containers
- AWS Quantum Technologies Blog
- Official Database Blog of AWS
- AWS Cloud Financial Management
- AWS for Games Blog
- Microsoft Workloads on AWS
- Official Big Data Blog of AWS
- AWS Compute Blog
- AWS for M&E Blog
- AWS Developer Tools Blog
- AWS Architecture Blog
- AWS Partner Network (APN) Blog
- AWS HPC Blog
- AWS Cloud Operations & Migrations Blog
- AWS for Industries
- AWS Messaging & Targeting Blog
- The latest AWS security, identity, and compliance launches, announcements, and how-to posts.
- AWS Startups Blog
- Front-End Web & Mobile
- Innovating in the Public Sector
- The Internet of Things on AWS – Official Blog
- AWS Open Source Blog
Desktop and Application Streaming
Monitoring Amazon WorkSpaces Usage with Custom Reports
Amazon WorkSpaces provides various metrics to allow customers to monitor usage of their workload. These metrics are all emitted at the service level, so granular in-session metrics are not available. With the adoption of NICE DCV as the desktop streaming mechanism for the WorkSpaces Streaming Protocol (WSP), customers can take advantage of different levels of usage reporting.
WSP API and NICE DCV Usage Reports
The Amazon WorkSpaces Streaming Protocol (WSP) API provides customers access to various metrics, such as the number of active sessions and the amount of data transferred. This data is available from the WSP API so customers can generate custom reports. Customers can also access NICE DCV usage data, such as the number of connected users and the length of active sessions.
Benefits of Usage Reports
Having access to usage reports gives customers the ability to gain insights into their workload. This helps customers to better understand how their WorkSpaces are being used and also identify potential areas for improvement. Customers can also use the usage reports to gain visibility into the efficiency of their WorkSpaces deployments.
How Cloud2 Can Help
At Cloud2, we offer a comprehensive suite of services for Amazon WorkSpaces. Our team of experienced AWS consultants can help you with the setup and configuration of your WorkSpaces as well as providing guidance on how to use the usage reports to gain insights into your workload. We also offer managed services for Amazon WorkSpaces, which can help ensure that your WorkSpaces are always running optimally.
Read the full blog posts from AWS
AWS DevOps Blog
Resource Isolation and Build & Deployment With AWS CDK & Amazon CodeCatalyst
When dealing with multiple projects and environments, managing resources can be a challenging task. The Amazon Web Services (AWS) Cloud Development Kit (CDK) simplifies the process of Infrastructure-as-Code (IaC). However, resource isolation can still be difficult. To help address this, we have a new experimental library, the App Staging Synthesizer (App Stage). App Stage enhances resource isolation in AWS CDK, providing a better modularized approach to resource management. App Stage also provides improved visibility into resource dependencies.
Benefits of App Staging Synthesizer
App Stage helps improve resource isolation by allowing developers to define their resources in stages. This enables developers to break up their resources into different stages, like Develop, Test, and Production, for example. Each stage can have its own set of resources assigned to it, making it easier to keep track of resource dependencies. App Stage also offers improved visibility into resource dependencies, providing a better view of which resources are shared between stages.
Deploy to Amazon EKS with CodeCatalyst
Amazon CodeCatalyst is an integrated service for software development teams that embrace continuous integration and deployment (CI/CD) practices. CodeCatalyst provides all the necessary tools for developing, building, and releasing software in one place. By integrating AWS resources with your deployment process, CodeCatalyst helps development teams quickly and easily deploy to Amazon Elastic Kubernetes Service (EKS), and take advantage of the scalability and availability of cloud computing.
Cloud2 and Our End-to-End AWS Services
At Cloud2, we offer both professional and managed services for a wide range of AWS solutions. We are a leading AWS consultancy in Denmark and specialize in helping companies move their applications and data to the cloud. Our team of experienced AWS professionals have in-depth knowledge of the AWS platform and can provide end-to-end services, from strategy and design to deployment and optimization. If you are looking for help with resource isolation, build & deployment, or any other AWS related services, contact us today and let us know how we can help.
Read the full blog posts from AWS
- Enhancing Resource Isolation in AWS CDK with the App Staging Synthesizer
- Build and deploy to Amazon EKS with Amazon CodeCatalyst
AWS for SAP
Upgrading SAP Instances with SUSE Linux Enterprise Server
SAP customers who are running their workloads using SUSE Linux Enterprise Server (SLES) or SUSE Linux Enterprise Server for SAP Applications (SLES for SAP) must be aware of the different methods for upgrading their instances and the potential issues that may arise from upgrades if not done properly. This blog will provide an overview of the best practices for safely upgrading SLES to the next service pack, and performing a major version upgrade from SLES 12 to SLES 15.
Preparing for the Upgrade
Before upgrading any SAP applications, customers must ensure that their applications and hardware are compatible with the intended version of SLES. Customers should confirm that their current SAP application is compatible with the target version of SLES, and ensure that their hardware meets the requirements associated with the target version of SLES.
Performing the Upgrade
SLES upgrades are divided into two main categories: service pack upgrades and major version upgrades. Service pack upgrades are generally simpler and do not require a major version change, while major version upgrades require a more intensive process.
For service pack upgrades, customers will need to install the new version of SLES, perform a system update, and then reboot the system. For major version upgrades, customers will need to backup their existing system, install the new version of SLES, perform a system update, and then restore their existing data.