AWS Systems Manager Maintenance Windows ya es compatible con la definición de comportamientos de corte personalizados para las tareas

Ahora puede definir un comportamiento de corte para las tareas de mantenimiento mediante AWS Systems Manager Maintenance Windows, que le permite detener o continuar las tareas en curso cuando se alcanza la hora de corte. Esto proporciona a los ingenieros de DevOps y de TI un mayor control sobre el comportamiento de corte para garantizar que las tareas perturbadoras no se ejecuten fuera del período deseado. Por ejemplo, ahora se puede configurar el comportamiento de corte para cancelar las tareas en curso al registrar una tarea de automatización con una ventana de mantenimiento. Esto garantizaría que no hay nuevas invocaciones de tareas cuando se alcanza la hora de corte.

Desactivación de las reglas de DNS inverso predeterminadas con Route 53

Amazon Route 53 Resolver es el servicio de DNS recurrente que se ejecuta de forma predeterminada en Virtual Private Cloud (VPC). Junto con Route 53 Resolver Endpoints y Resolver Rules, puede crear una resolución de consultas DNS sin problemas en toda la nube híbrida, con un control preciso sobre la resolución de los espacios de nombre DNS entre su centro de datos local y Amazon Virtual Private Cloud (Amazon VPC).

Anunciamos Amazon RDS Custom for Oracle

Amazon Relational Database Service (Amazon RDS) Custom es un servicio de base de datos administrada para aplicaciones heredadas, personalizadas y empaquetadas que requieren acceso al sistema operativo subyacente y al entorno de la base de datos. Amazon RDS Custom ya está disponible para el motor de base de datos Oracle. Amazon RDS Custom for Oracle automatiza la configuración, el funcionamiento y el escalado de las bases de datos en la nube, al tiempo que concede acceso a la base de datos y al sistema operativo subyacente para configurar los ajustes, instalar parches y habilitar las características nativas para satisfacer los requisitos de la aplicación dependiente.

Amazon SageMaker Autopilot agrega compatibilidad con datos de serie temporal

Amazon SageMaker Autopilot crea, forma y ajusta automáticamente los mejores modelos de machine learning en función de los datos, a la vez que permite mantener el control y la visibilidad completos. Desde hoy, SageMaker Autopilot es compatible con datos de serie temporal. Ahora puede utilizar SageMaker Autopilot para crear modelos de machine learning para problemas de regresión y clasificación para datos de serie temporal o cualquier secuencia de datos, permitiendo escenarios como la detección supervisada de anomalías, la evaluación de riesgos o la predicción de fallos basada en una secuencia de puntos de datos. Por ejemplo, ahora puede construir modelos para identificar y clasificar el tráfico de red anómalo registrado durante un periodo de tiempo, o identificar dispositivos defectuosos basándose en las métricas emitidas.

Amazon QLDB launches new version of QLDB Shell

Amazon Quantum Ledger Database (QLDB) launches a new version of the QLDB Shell that is easier to install and use. QLDB customers can now download the QLDB Shell tailored to their favorite operating system and begin querying a QLDB ledger without any other installation steps or dependencies to install. Expert users have the option to build from source code and tailor to their custom requirements, because the QLDB Shell is open sourced. The updated QLDB Shell also provides improved query runtime statistics, introduces an optional tabular data format for query output, offers config file support for saving preferred options, and adds convenient commands for listing tables and switching ledgers, regions, and endpoints.

Easily connect Google Pay with your preferred payment processor

Posted by Stephen McDonald, Developer Relations Engineer, Google Pay

Easily connect Google Pay with your preferred payment processor

Adding Google Pay as a payment method to your website or Android application provides a secure and fast checkout option for your users. To enable Google Pay, you will first need a Payment Service Provider (PSP). For the integration this means understanding how your payments processing stack works with Google Pay APIs.

End-to-end PSP samples

To make integration easier, we’ve launched a new open source project containing end-to-end samples for a range of PSPs, demonstrating the entire integration process – from client-side configuration, to server-side integration with the PSPs, using their respective APIs and client libraries where applicable. The project uses Node.js and is written in JavaScript, which most developers should find familiar. Each of the samples in the project are implemented in a consistent fashion, and demonstrate best practices for integrating Google Pay and your preferred PSP with your website or Android application.

A recent study by 451 Research showed that for merchants with over 50% of sales occurring online, 69% of merchants used multiple PSPs. With these new samples, we demonstrate how you can implement an entirely consistent interface to multiple PSPs, streamlining your codebase while also providing more flexibility for the future.

Lastly, we’ve also added support to both the Web and Android Google Pay sample applications, making it easy to demonstrate the new PSP samples. Simply run the PSP samples project, and configure the Web or Android samples to send their cart information and Google Pay token to the PSP samples app, which will then send the relevant data to the PSP’s API and return the PSP’s response back.

Initial PSPs

To start with, we’ve included support for 6 popular PSPs: Adyen, Braintree, Checkout.com, Cybersource, Square, and Stripe. But that’s just the beginning. If you’re involved with a PSP that isn’t yet included, we’ve made adding new PSPs to the open source project as simple as possible. Just head on over to the GitHub repository which contains instructions on contributing your preferred PSP to the project.

Launching Google Pay for your website

When you’ve completed your testing, submit your website integration in the Google Pay Business Console. You will need to provide your website’s URL and screenshots to complete the submission.

Summing it up

Integrating Google Pay into your website is a great way to increase conversions and to improve the purchasing experience for your customers, and with these new open source samples, the process is even easier.

What do you think? Follow us on Twitter for the latest updates @GooglePayDevs

Do you have any questions? Let us know in the comments below or tweet using #AskGooglePayDevs.

AWS App2Container now supports ECS Fargate Windows

AWS App2Container (A2C) now supports deployment of containerized Windows applications to AWS Fargate for ECS Windows containers. With this feature, users can now target AWS Fargate for ECS Windows containers as deployment runtime in addition to ECS and EKS that were previously supported. Using App2Container, developers can take a running Windows based .NET application or a Windows service, analyze, containerize, and deploy to AWS Fargate for ECS Windows containers, in few simple steps. Developers can take advantage of auto-scaling, host management, and secured application lifecycle management offered by AWS Fargate.

Anuncio de las instancias DL1 de Amazon EC2 para el entrenamiento rentable de modelos de aprendizaje profundo

Hoy anunciamos la disponibilidad general de las instancias DL1 de Amazon EC2 con aceleradores Gaudi de Habana Labs, una empresa de Intel. Las instancias DL1 de EC2 ofrecen hasta un 40 % más de rendimiento por su precio que la generación actual de instancias EC2 basadas en GPU para el entrenamiento de modelos de aprendizaje profundo y están optimizadas para cargas de trabajo como la clasificación de imágenes, la detección de objetos y el procesamiento del lenguaje natural.

Introducing Amazon EC2 C6i instances

Amazon Web Services (AWS) announces the general availability of compute optimized Amazon EC2 C6i instances. C6i instances are powered by 3rd generation Intel Xeon Scalable processors (code named Ice Lake) with an all-core turbo frequency of 3.5 GHz, offer up to 15% better compute price performance over C5 instances for a wide variety of workloads, and always-on memory encryption using Intel Total Memory Encryption (TME). Designed for compute-intensive workloads, C6i instances are built on the AWS Nitro System, a combination of dedicated hardware and lightweight hypervisor, which delivers practically all of the compute and memory resources of the host hardware to your instances. These instances are an ideal fit for compute-intensive workloads such as batch processing, distributed analytics, high performance computing (HPC), ad serving, highly scalable multiplayer gaming, and video encoding.