Amazon Web Services Updated SOA-C02 Exam Questions and Answers by ciaran

AWS Organizations offers features that help manage multiple AWS accounts. To use AWS Compute Optimizer and AWS tag policies across all member accounts, the organization must have all features enabled.

Enable All Features in AWS Organizations:

Open the AWS Organizations console at AWS Organizations Console.

Navigate to Settings and ensure that All features are enabled.

Verify and Enable Trusted Access:

Ensure that trusted access is enabled for AWS Compute Optimizer and other relevant services.

This allows the management account to access and manage resources in member accounts.

Use AWS Compute Optimizer and Tag Policies:

Once all features are enabled, configure and manage AWS Compute Optimizer and tag policies from the management account.

AWS Organizations

Enabling All Features in Your Organization

Enabling Trusted Access with Other AWS Services

To enable HTTPS support on an Application Load Balancer, you must:

Use a public SSL/TLS certificate

Associate it with the HTTPS listener on the ALB

From the AWS Certificate Manager and ALB documentation:

You can use ACM to provision, manage, and deploy public SSL/TLS certificates for your load balancers.

After the certificate is issued, you can attach it to your ALB's HTTPS listener.

To monitor and receive notifications when a KMS key deletion is scheduled, you can implement the following steps:

Create an Amazon EventBridge Rule:AWS KMS emits events to EventBridge when a key deletion is scheduled. You can create an EventBridge rule that listens for these specific events. This rule can then trigger actions, such as sending notifications or initiating automated workflows.

Create an Amazon SNS Topic:Amazon SNS is a fully managed messaging service that enables you to decouple and scale microservices, distributed systems, and serverless applications. By configuring the EventBridge rule to send events to an SNS topic, you can ensure that notifications are sent to the appropriate recipients, such as the security team.

By combining these two services, you can effectively monitor for scheduled deletions of KMS keys and notify the relevant stakeholders without altering the developers' IAM permissions.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html

To maintain full capacity during new deployments in AWS Elastic Beanstalk, you can use the "Immutable" or "Rolling with additional batch" deployment policies.

Immutable Deployment:

This policy ensures that a new set of instances is launched with the new version of the application. The new instances are only promoted to serve traffic if the deployment succeeds. This ensures zero downtime and maintains full capacity during deployment.

Rolling with Additional Batch:

This policy launches a new batch of instances to handle the traffic while the old instances are being updated. This maintains the full capacity during the deployment process, ensuring that the application remains fully operational.

How to Configure Deployment Policies:

Open Elastic Beanstalk Console:

Navigate to the AWS Elastic Beanstalk console at AWS Elastic Beanstalk Console.

Update Environment Configuration:

Select the environment you want to configure.

Go to Configuration and then Rolling updates and deployments.

Choose either Immutable or Rolling with additional batch as the deployment policy.

AWS Elastic Beanstalk Deployment Policies

Managing and Configuring Environments