30Aug 2018

Amazon Route 53 Auto Naming is now available in five additional AWS regions: EU (Frankfurt), EU (London), Asia Pacific (Tokyo), Asia Pacific (Singapore), and Asia Pacific (Sydney).

Amazon Route 53 Auto Naming simplifies the management of DNS names and health checks for microservices that run on top of AWS when microservices scale up and down. You can call the Auto Naming APIs to create a service, and then register instances of that service with a single API call. Amazon Route 53 Auto Naming will automatically populate the DNS records and optionally create a health check for the service endpoint. When a new service instance is registered, you can access it by making a simple DNS query for the service name.

Amazon Route 53 Auto Naming API powers Amazon Elastic Container Service (Amazon ECS) service discovery functionality and enables unified service discovery for services managed by Amazon ECS and Kubernetes.

You can use Amazon Route 53 Auto Naming APIs in the following AWS regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), EU (Ireland), EU (Frankfurt), EU (London), Asia Pacific (Tokyo), Asia Pacific (Singapore), and Asia Pacific (Sydney) regions. For more information on AWS regions and services, please visit the AWS global region table.

To learn more about Amazon Route 53 Auto Naming, please see our documentation and product page.

29Aug 2018

Amazon Elastic Container Service (Amazon ECS) now includes integrated service discovery in EU (Frankfurt), EU (London), Asia Pacific (Tokyo), Asia Pacific (Sydney), and Asia Pacific (Singapore) regions.

Amazon ECS service discovery makes it easy for your containerized services to discover and connect with each other. Amazon ECS creates and manages a registry of service names using the Route53 Auto Naming API so you can refer to a service by name in your code and write DNS queries to have the service name resolve to the service’s endpoint at runtime.

Today, service discovery is availablefor all networking modes for EC2 launch type or with AWS Fargate.

To learn more, visit the Amazon ECS Service Discovery documentation.  

You can use Amazon ECS Service Discovery in all AWS regions where Amazon ECS and Amazon Route 53 Auto Naming are available. These now include EU (Frankfurt), EU (London), Asia Pacific (Tokyo), Asia Pacific (Sydney), and Asia Pacific (Singapore) regions in addition to US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), and EU (Ireland) regions where ECS service discovery was already available.

29Aug 2018

AWS CodeBuild now supports build projects with multiple input sources and output artifacts. Your projects can now use one or more sources from Amazon S3, AWS CodeCommit, GitHub, GitHub Enterprise, or Bitbucket and can upload multiple sets of artifacts to one or more Amazon S3 buckets. You can also configure your project to have no input source. You can now use the AWS CodePipeline integration with CodeBuild to create a pipeline with multiple input and output artifacts to a CodeBuild project.

29Aug 2018

The AWS Serverless Application Model (SAM) Command Line Interface (CLI) lets you locally build, test, and debug serverless applications defined by AWS SAM templates. You can now use SAM CLI to debug Lambda functions written in Go in addition to those written in Java, Python, and Node.js. You can also use the sam local generate-event command to generate sample event payloads for 50+ events.

28Aug 2018

Starting today, AWS IoT Core is enabling customers to create additional AWS IoT Core endpoints for their account in each region that will serve an Amazon Trust Services (ATS) signed certificate instead of a VeriSign signed certificate. Using ATS endpoints will help customers avoid potential issues resulting from the upcoming distrust of Symantec Certificate Authorities (CAs) by Google (announcement), Apple (announcement), and Mozilla (announcement) as the ATS root CAs are trusted by default in most popular browsers and operating systems. For more information on how to get started with ATS endpoints refer to this blog post.