This certification exam is currently in Beta as I write this. Yes – I plan on going and taking a look and will report back.
The AWS Certified Machine Learning – Specialty beta examination is intended for individuals with one to two years of hands-on experience developing, architecting, or running machine learning (ML)/deep learning workloads on the AWS Cloud.
It validates an examinee’s ability to:
Select and justify the appropriate ML approach for a given business problem.
Identify appropriate AWS services to implement ML solutions.
Design and implement scalable, cost-optimized, reliable, and secure ML solutions.
Recommended AWS and General IT Knowledge and Experience:
The ability to express the intuition behind basic ML algorithms
In this sample Nugget from the AWS Certified Cloud Practitioner course at CBT Nuggets – we examine an AWS solution and how it uses the various services.
Here are just some of the networking components you should be familiar with if you are interested in mastering AWS.
Network Interfaces – this logical network component serves to represent a physical network interface card (NIC); as such, this component can be configured with IPv4 and IPv6 addresses
Route Tables – just as would exist on a physical router, AWS route tables contain a set of rules, called routes, that are used to determine where network traffic is directed
Internet Gateways – an internet gateway serves two purposes: to provide a target in your VPC route tables for internet-routable traffic, and to perform network address translation (NAT) for instances that have been assigned public IPv4 addresses
Egress-Only Internet Gateways – a VPC component that allows outbound communication over IPv6 from instances in your VPC to the Internet, and prevents the Internet from initiating an IPv6 connection with your instances
DHCP Options Sets – DHCP provides a standard for passing configuration information to hosts on a TCP/IP network; the options field of a DHCP message contains the configuration parameters; some of those parameters are the domain name, domain name server, and the netbios-node-type; the option sets allow you to configure such options for your virtual private clouds (VPC)
DNS – AWS provides you with a DNS server for your VPC, but it is important to realize that you can also use you own
Elastic IP Addresses – a static IPv4 address designed for dynamic cloud computing; an Elastic IP address is associated with your AWS account; with this address, you can mask the failure of an instance or software by rapidly remapping the address to another instance in your account
VPC Endpoints – enables you to privately connect your VPC to supported AWS services and VPC endpoint services powered by PrivateLink without requiring an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection
NAT – you can use a NAT device to enable instances in a private subnet to connect to the Internet (for example, for software updates) or other AWS services, but prevent the Internet from initiating connections with the instances; AWS offers two kinds of NAT devices—a NAT gateway or a NAT instance, but strongly recommends the use of NAT gateways
VPCPeering – a networking connection between two VPCs that enables you to route traffic between them privately; you can create a VPC peering connection between your own VPCs, with a VPC in another AWS account, or with a VPC in a different AWS Region
ClassicLink – allows you to link your EC2-Classic instance to a VPC in your account, within the same region; this allows you to associate the VPC security groups with the EC2-Classic instance, enabling communication between your EC2-Classic instance and instances in your VPC using private IPv4 addresses
