In general, AWS services can be accessed using
- AWS web interface,
- API libraries in a programming language, such as
boto3
for Python 3, - AWS command-line interface, i.e.
awscli
.
I opted for the API library since it is
a4b | |
account | |
acm | |
acm-pca | |
amplify | |
apigateway | |
application-autoscaling | |
appstream | |
appsync | |
artifact |
"*" | |
"arn:*:iam::*:role/aws-service-role/s3.data-source.lustre.fsx.amazonaws.com/AWSServiceRoleForFSxS3Access_*" | |
"arn:aws:a4b:*:*:gateway/*" | |
"arn:aws:acm-pca:*:*:certificate-authority/*" | |
"arn:aws:acuity:*:*:stream/deeplens*/*" | |
"arn:aws:apigateway:*::/*" | |
"arn:aws:apigateway:*::/account", | |
"arn:aws:apigateway:*::/clientcertificates", | |
"arn:aws:apigateway:*::/clientcertificates/*", | |
"arn:aws:apigateway:*::/domainnames" |
#!/usr/bin/env bash | |
function walk() { | |
for secret in $(vault list $1 | tail -n +3) | |
do | |
if [[ ${secret} == *"/" ]] ; then | |
walk "${1}${secret}" | |
else | |
echo "${1}${secret}" | |
fi |
# Change the path below to your own audit log path. | |
/var/log/vault/audit.log { | |
rotate 30 | |
daily | |
# Do not execute rotate if the log file is empty. | |
notifempty | |
missingok | |
compress | |
# Set compress on next rotate cycl to prevent entry loss when performing compression. | |
delaycompress |
EventSource, EventName, Recorded Name, Match | |
a4b, AssociateDeviceWithRoom, associatedevicewithroom, True | |
a4b, AssociateSkillGroupWithRoom, associateskillgroupwithroom, True | |
a4b, CreateProfile, createprofile, True | |
a4b, CreateRoom, createroom, True | |
a4b, CreateSkillGroup, createskillgroup, True | |
a4b, CreateUser, createuser, True | |
a4b, DeleteProfile, deleteprofile, True | |
a4b, DeleteRoom, deleteroom, True | |
a4b, DeleteRoomSkillParameter, deleteroomskillparameter, True |
a4b:AssociateContactWithAddressBook | |
a4b:AssociateDeviceWithRoom | |
a4b:AssociateSkillGroupWithRoom | |
a4b:CreateAddressBook | |
a4b:CreateContact | |
a4b:CreateProfile | |
a4b:CreateRoom | |
a4b:CreateSkillGroup | |
a4b:CreateUser | |
a4b:DeleteAddressBook |
5 Abort | |
9 Accept | |
3 Acknowledge | |
4 Activate | |
48 Add | |
23 Admin | |
6 Allocate | |
4 Apply | |
2 Approve | |
1 Archive |
Getting rke and Rancher setup to run kubernetes on arm is interesting. There is no official support yet via rancher, although there is interest and some work done towards those efforts. This is my attempt at getting a cluster of 3 Pis (2 3Bs and 1 3B+) provisioned and registered to a rancher 2 server.
I've successfully completed this both with Hypriot OS 1.9.0 and the arm64 builds https://github.com/DieterReuter/image-builder-rpi64 Both times I used the same basic cloud-init setup
tldr - remove microcode_ctl package - configure dracut to insure needed drivers are included for kernel/initrd updates | |
And exmaple - The Chef way: | |
################ | |
1.) create a recipe with the following code: | |
################ | |
if node['ec2']['instance_type'].include? ( "c5" || "f1" || "g3" || "h1" || "i3" || "m4.16xlarge" || "m5" || "p2" || "p3" || "r4" || "x1" ) | |
template '/etc/dracut.conf' do |