AWS lookout-for-equipment documentation change
Summary
Updated service deprecation notice and standardized IAM policy examples with consistent account IDs (111122223333) and JSON formatting
Security assessment
Changes involve updating deprecation timelines and improving policy examples' readability. While IAM policies relate to security, these updates don't address vulnerabilities or introduce new security features - they simply standardize documentation examples.
Diff
diff --git a/lookout-for-equipment/latest/ug/importing-datasets-models.md b/lookout-for-equipment/latest/ug/importing-datasets-models.md index b05e552e1..83e5463ce 100644 --- a//lookout-for-equipment/latest/ug/importing-datasets-models.md +++ b//lookout-for-equipment/latest/ug/importing-datasets-models.md @@ -7 +7 @@ Importing a modelAPIs related to importingImporting a datasetControlling access -Amazon Lookout for Equipment is no longer open to new customers. Existing customers can continue to use the service as normal. For capabilities similar to Amazon Lookout for Equipment see our [blog post](https://aws.amazon.com/blogs/machine-learning/preserve-access-and-explore-alternatives-for-amazon-lookout-for-equipment/). +On October 7, 2026, AWS will discontinue support for Amazon Lookout for Equipment. After October 7, 2026, you will no longer be able to access the Lookout for Equipment console or resources. For more information, [see the following](https://aws.amazon.com/blogs/machine-learning/preserve-access-and-explore-alternatives-for-amazon-lookout-for-equipment/). @@ -89,0 +90,6 @@ If the source account and the target account are the same, then you can skip the +JSON + + +**** + + @@ -94 +100,3 @@ If the source account and the target account are the same, then you can skip the - "Principal": {"AWS": "arn:aws:iam::2222222222:role/Admin"}, + "Principal": { + "AWS": "arn:aws:iam::111122223333:role/Admin" + }, @@ -135,0 +145,6 @@ Here is an example resource policy for setting the import permissions for a data +JSON + + +**** + + @@ -141 +156,3 @@ Here is an example resource policy for setting the import permissions for a data - "Principal": {"AWS": "arn:aws:iam::2222222222:role/Admin"}, + "Principal": { + "AWS": "arn:aws:iam::111122223333:role/Admin" + }, @@ -150,0 +169,6 @@ This is an example policy for setting permissions for importing a specific model +JSON + + +**** + + @@ -156 +180,3 @@ This is an example policy for setting permissions for importing a specific model - "Principal": {"AWS": "arn:aws:iam::2222222222:role/Admin"}, + "Principal": { + "AWS": "arn:aws:iam::111122223333:role/Admin" + }, @@ -165,0 +193,6 @@ This is an example policy to set the permissions to import all model versions (s +JSON + + +**** + + @@ -171 +204,3 @@ This is an example policy to set the permissions to import all model versions (s - "Principal": {"AWS": "arn:aws:iam::2222222222:role/Admin"}, + "Principal": { + "AWS": "arn:aws:iam::111122223333:role/Admin" + }, @@ -222,0 +259,6 @@ Now suppose that we set a policy _only_ at the level of the parent model (Pump_1 +JSON + + +**** + + @@ -228 +270,3 @@ Now suppose that we set a policy _only_ at the level of the parent model (Pump_1 - "Principal": {"AWS": "arn:aws:iam::2222222222:role/Admin"}, + "Principal": { + "AWS": "arn:aws:iam::111122223333:role/Admin" + }, @@ -239,0 +285,6 @@ Now, let us suppose that you also set a policy at the model version level. In th +JSON + + +**** + + @@ -245 +296,3 @@ Now, let us suppose that you also set a policy at the model version level. In th - "Principal": {"AWS": "arn:aws:iam::2222222222:role/Admin"}, + "Principal": { + "AWS": "arn:aws:iam::111122223333:role/Admin" + }, @@ -249 +302 @@ Now, let us suppose that you also set a policy at the model version level. In th - "Resource": "arn:aws:lookoutequipment:us-west-2:111111111111:model/Pump_1/00af0697-095b-433a-889c-9f4eed39dbbc/model-version/2 + "Resource": "arn:aws:lookoutequipment:us-west-2:111111111111:model/Pump_1/00af0697-095b-433a-889c-9f4eed39dbbc/model-version/2" @@ -293,0 +348,6 @@ This is an example policy that will prevent the inference data from being import +JSON + + +**** + + @@ -299 +359,3 @@ This is an example policy that will prevent the inference data from being import - "Principal": {"AWS": "arn:aws:iam::2222222222:role/Admin"}, + "Principal": { + "AWS": "arn:aws:iam::111122223333:role/Admin" + },