mirror of
https://gitea.com/mcereda/oam.git
synced 2026-02-09 05:44:23 +00:00
chore: improve commands examples after field experience
This commit is contained in:
@@ -33,7 +33,8 @@ aws sagemaker list-endpoint-configs --output 'yaml-stream' --query 'EndpointConf
|
||||
aws sagemaker list-endpoint-configs --output 'json' --query 'EndpointConfigs[].EndpointConfigName' | jq -r '.[]' -
|
||||
|
||||
# Describe all SageMaker EndpointConfigurations.
|
||||
aws sagemaker list-endpoint-configs … | xargs -n '1' aws sagemaker describe-endpoint-config --endpoint-config-name
|
||||
aws sagemaker list-endpoint-configs … \
|
||||
| xargs -n '1' aws sagemaker describe-endpoint-config --endpoint-config-name
|
||||
|
||||
|
||||
# List secrets stored in Secret Manager.
|
||||
|
||||
2
knowledge base/cloud computing/aws/ec2.placeholder
Normal file
2
knowledge base/cloud computing/aws/ec2.placeholder
Normal file
@@ -0,0 +1,2 @@
|
||||
https://instances.vantage.sh/
|
||||
https://ec2instances.github.io/
|
||||
@@ -46,6 +46,10 @@ aws ecr validate-pull-through-cache-rule \
|
||||
docker pull 'aws_account_id.dkr.ecr.region.amazonaws.com/prefix/repository_name/image_name:tag'
|
||||
docker pull '123456789012.dkr.ecr.us-east-2.amazonaws.com/ecr-public/repository_name/image_name:tag'
|
||||
docker pull '123456789012.dkr.ecr.eu-west-1.amazonaws.com/quay/argoproj/argocd:v2.10.0'
|
||||
# DockerHub cache repositories require the full path.
|
||||
# E.g., 'library/alpine' instead of just 'alpine'.
|
||||
docker pull '123456789012.dkr.ecr.eu-south-1.amazonaws.com/docker-hub/library/nginx:perl'
|
||||
docker pull '123456789012.dkr.ecr.us-west-2.amazonaws.com/docker-hub/grafana/grafana'
|
||||
```
|
||||
|
||||
## Pull through cache feature
|
||||
|
||||
@@ -64,6 +64,14 @@ aws s3 sync '.' 's3://arn:aws:s3:us-west-2:123456789012:accesspoint/myaccesspoin
|
||||
aws s3 rb 's3://my-bucket'
|
||||
aws s3 rb 's3://my-bucket' --force
|
||||
|
||||
|
||||
# Lifecycle configurations.
|
||||
aws s3api get-bucket-lifecycle-configuration --bucket 'bucketName'
|
||||
aws s3api put-bucket-lifecycle-configuration --bucket 'bucketName' \
|
||||
--lifecycle-configuration 'file://lifecycle.definition.json'
|
||||
aws s3api delete-bucket-lifecycle-configuration --bucket 'bucketName'
|
||||
|
||||
|
||||
# Show tags on objects.
|
||||
aws s3api list-objects-v2 \
|
||||
--bucket 'my-bucket' --prefix 'someObjectsInHereAreTagged' \
|
||||
@@ -89,6 +97,9 @@ aws s3 delete-bucket-lifecycle --bucket 'batman'
|
||||
|
||||
## Lifecycle configuration
|
||||
|
||||
> Adding, removing or changing lifecycle rules takes a while.<br/>
|
||||
> Wait a couple of minutes after the operation to make sure all the bucket's properties are synced.
|
||||
|
||||
When one has multiple rules in an S3 Lifecycle configuration, an object can become eligible for multiple S3 Lifecycle actions. In such cases, Amazon S3 follows these general rules:
|
||||
|
||||
1. Permanent deletion takes precedence over transition.
|
||||
|
||||
Reference in New Issue
Block a user